We've been using wrapper for quite some time. We just upgraded to wrapper 3.5.7 and noticed that executing the wrapper shell script (sh.script.in file that's been modified and renamed to fit our environment) with start, stop, or status does nothing. Even the wrapper.log does not show any messages of trying to start. We replaced the wrapper shell script with a previous version shell script (3.5.4) and the start/stop/status commands work as expected. We've verified the file ownerships and permissions are exactly the same and the properties specific to the environment are the same so have deduced that something in the new script is causing the problem.
Log in to post a comment.