Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a problem with Monit that I use for monitoring of my Node.js app. I just moved from a single core machine to a multi core one. On both of them I run Ubuntu 11.10. On the old one this was working. This script below uses a upstart script that I have configured according to this:

check process nodejs with pidfile "/var/run/"
    start program = "/sbin/start myapp"
    stop program  = "/sbin/stop myapp"
    if failed port 80 protocol HTTP
        request /
        with timeout 10 seconds
        then restart

Now when I try to run it, such as: monit -d 60 -c /etc/monit/monitrc everything goes fine:

monit daemon at 1312 awakened

On the old machine that started myapp right away. On the new one it doesn't.

The mayer problem is that when my Node App crashes monit isn't helping me. I C

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.