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
For those experiencing on Debian buster: Editing nano /etc/systemd/system/redis.service and adding this line below redis [Service] ExecStartPost=/bin/sh -c “echo $MAINPID > /var/run/redis/redis.pid” It suppose to look like this: [Service] Type=forking ExecStart=/usr/bin/redis-server /etc/redis/redis.conf ExecStop=/bin/kill -s TERM $MAINPID ExecStartPost=/bin/sh -c “echo $MAINPID > /var/run/redis/redis.pid” PIDFile=/run/redis/redis-server.pid then: sudo systemctl daemon-reload sudo systemctl restart redis.service Check redis.service status: sudo … Read more
edit vim /etc/monit/monitrc, starting from line 118 and uncomment below lines set httpd port 2812 use address localhost # only accept connection from localhost allow localhost # allow localhost to connect to the server and allow admin:monit sudo monit reload to take affect 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
God leaks memory pretty badly so I chose Monit for my VPS. Monit runs at about 2MB of RAM constantly, whereas my god install running on Ruby 1.8.6 leaked out to about 60MB of RAM in about 36 hours. I didn’t want to monitor my system monitoring tool so I scrapped God and went over … Read more
Here is how I got this working. Use the collectiveidea fork of delayed_job besides being actively maintained, this version has a nice script/delayed_job daemon you can use with monit. Railscasts has a good episode about this version of delayed_job (ASCIICasts version). This script also has some other nice features, like the ability to run multiple … Read more
I’ve had the same problem. Using monit’s verbose command-line option helps a bit, but I found the best way was to create an environment as similar as possible to the monit environment and run the start/stop program from there. # monit runs as superuser $ sudo su # the -i option ignores the inherited environment … Read more
I’d look in to daemontools (http://cr.yp.to/daemontools.html). Supervise was built for exactly this purpose — to start processes and watch them, restarting them immediately if they ever terminate. You could still use monit if you need to do anything more complicated than a simple “is it still running” check, and if the process needs to be … Read more
I contacted M/Monit support directly about the pricing issue… When asked if they offer a discount for education: “Unfortunately no, but for not-for profit organisations we might donate a license.” But the fact remains that the unlimited license cost is intentionally low at ~$590. As for free alternative monitoring frameworks, I worked at a DevOps-focused … Read more
This is not what’s supposed to happen. monit reload only rereads its config file and applies new changes. Do you have the same problem if you service monit restart? How do you know Tomcat is actually restarting? Please paste the output of monit status.