Linux – Run python script inside /etc/rc.local doesn’t work

amazon ec2amazon-amilinuxpythonrc.local

I modified /etc/rc.local on my Amazon AWS AMI

#!/bin/sh
touch /var/lock/subsys/local
# setup hostname properly
/usr/bin/python /root/automation/initSystem.py

so last line calls Python script that does configuration (Env variables, hostname, networking settings etc) and then does /etc/init.d/network restart

if I run rc.local manually
/etc/rc.local
everything is just fine

when system auto starts it doesn't work. So touch command (2nd line – worked), but python script is never executed, at least results of it's execution (setting up a hostname and restarting network interface seems doesn't work at all)

Any ideas?

Best Answer

We can't debug a mystery script. Does running the python script work with an empty environment? Try:

env -i /usr/bin/python /root/automation/initSystem.py

Modify your script to capture the output of your command in the script:

/usr/bin/python /root/automation/initSystem.py > /root/init.stdout 2> /root/init.stderr

and it'll probably contain hints as to why it failed.

Related Solutions

Debian – Running python script in incrontab in Debian

There's a big difference between cron and incron: the way they execute the commands. Cron sees the command as one argument and calls a shell to run it. Roughly like this:

execvp('/bin/sh', ['/bin/sh', '-c', 'whatever is in the crontab']);

So all shell constructs like && and | work. Incron does not do this, it parses the command itself and execs it directly. So what incron runs in your case is:

execvp('/home/dropbox/monitor.py', ['/home/dropbox/monitor.py', '|', 'logger']);

So your monitor.py gets run with | and logger as arguments. You can either wrap your script in another script that does monitor.py | logger or use the python logging module to do the logging from monitor.py itself.

Nginx – Configure basic python 3.5, flask, uwsgi, nginx app

Let's go...

Remove /var/www/flasktest/uwsgi.ini, you don't need this.
uwsgi:
- ...can't bind to your socket; change the socket directive in your uwsgi.ini to /tmp/%n.sock. %n will get evaluated to the name of the config file, sans extension.
- Does uwsgi work if you start it? Have a look inside the logs; if you'll find errors, please post these.
Nginx:
- Change your uwsgi_pass directive to uwsgi_pass unix:///tmp/flasktest.sock and insert include uwsgi_params; at the next line.
- Reverse the order of the / and /static config blocks to make sure these work as expected. As it stands, / will be hit for all requests, including /static, so these would be served by your backend, which isn't wise to do, given the files being served are static and not dynamic.

Best Answer

Related Solutions

Debian – Running python script in incrontab in Debian

Nginx – Configure basic python 3.5, flask, uwsgi, nginx app

Related Topic