Question or issue on macOS:
I’m trying to figure out why my launchd script is not working. It is extremely simple, but I am new to the mac environment and trying to get accustomed. Here’s my plist. I know ProgramArguments is required, so I just put the script path in there.
Label com.tomcat.plist ProgramArguments /opt/apache-tomcat-5.5.27/bin/startup.sh OnDemand
When I try to run launchctl load
I’ve used all the examples I’ve found online and I can’t figure out why this isn’t running my script on start up.
How to solve this problem?
Solution no. 1:
Just in case anyone else runs across this issue, and already has
<key>RunAtLoad</key><true/> in their plist, I want to provide some additional solutions.
Double check permissions to make sure that your script is executable (look for an ‘x’):
ls -l /opt/apache-tomcat-5.5.27/bin/startup.sh
Modify permissions if necessary:
chmod +x /opt/apache-tomcat-5.5.27/bin/startup.sh
Also run the script directly first and make sure it works:
If the script is executable, and runs fine directly, try tailing the system log to debug launchd:
sudo launchctl log level debug tail -f /var/log/system.log
-f flag (basically) continually shows the end (latest entries) of the log. You can remove this flag to just print a snapshot of the end of the log. If you use this flag, you’ll need to open a new terminal to run other commands. Press CTRL + C to end the tail session. For more information:
When you’re finished debugging:
sudo launchctl log level error
There are other log levels. For more information:
If you make any changes to the script or plist, make sure you reload the plist. For example:
launchctl unload ~/Library/LaunchAgents/com.tomcat.plist launchctl load ~/Library/LaunchAgents/com.tomcat.plist
If you ONLY made changes to the script and NOT the plist, you can just restart the plist:
launchctl stop com.tomcat.plist launchctl start com.tomcat.plist
If you add the following key-value to your plist:
Then you can just run:
launchctl stop com.tomcat.plist
And it will restart automatically.
If none of this helps, and you’re specifically having problems with setting up Tomcat on OS X, this tutorial might be of help.
Solution no. 2:
To make your script run automatically when you call launchctl load, you need to add :-
Alternatively you could use :-
launchctl start com.tomcat.plist
Solution no. 3:
Although I imagine most people will not have this problem, I figure it is worth putting here since I spent nearly two hours trying to figure out why
launchd load was not working despite returning a
0 exit code.
The problem was simple. My
plist file had the wrong file extension (I had “
launchctl was silently refusing to load the file. Changing the extension to
plist resolved the issue.