Fixed this issue by setting the limits for all users in the file : $ cat /etc/security/limits.d/custom.conf * hard nofile 550000 * soft nofile 550000 REBOOT THE SERVER after setting the limits. VERY IMPORTANT: The /etc/security/limits.d/ folder contains user specific limits. In my case hadoop 2 (cloudera) related limits. These user specific limits would override … Read more
Ok, I’ve found one way to get it : $ sudo initctl log-priority # gives the actual (default) logging level $ sudo initctl log-priority –help # gives available logging levels $ sudo initctl log-priority info # is enough to get : $ tail -f /var/log/syslog # – log of upstart events $ tail -f /var/log/boot.log … Read more
So I’ve worked it out, for some reason upstart doesn’t like using ‘source’ so I changed the line from: source bin/activate to . bin/activate and that works, don’t know why though, so would be interested if someone could explain this
If start-stop-daemon is available on your machine, I would highly recommend using it to launch your process. start-stop-daemon will handle launching the process as an unprivileged user without forking from sudo or su (recommended in the upstart cookbook) AND it also has built in support for pid file management. Eg: /etc/init/app_name.conf #!upstart description “Redis Server” … Read more
Yes, upstart will restart your process without a reboot. Also, you should look into forever.
From your mention of Upstart I will assume that this question is for a service being run on an Ubuntu server. On an Ubuntu server an upstart job is really the simplest and most convenient option for creating an always on service that starts up at the right time and can be stopped or reloaded … Read more
I highly recommend using both Monit AND upstart. Upstart makes it easy to deamonize node.js and Monit comes packed with tons of useful app checks including memory usage, http requests, cpu usage, … This is an example of the most basic setup you can get. You could also easily add another monit config (with the … Read more
You can tell Gunicorn to reload gracefully using the HUP signal like so: kill -HUP <pid> (see the FAQ for details) I use Supervisor to control my Gunicorn server, which allows me to use this (slightly hacky) way of reloading Gunicorn after a deploy: supervisorctl status gunicorn | sed “s/.*[pid ]\([0-9]\+\)\,.*/\1/” | xargs kill -HUP … Read more