monit-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Very simple monit of a perl file - how to do it?


From: Bruce B
Subject: Re: Very simple monit of a perl file - how to do it?
Date: Wed, 29 Dec 2010 00:10:50 -0500

Thanks for the feedback. To clarify things:

I have a perl program named "test.pl" which runs fine if I simply run it like this at the shell level:

nohup perl /tmp/test.pl >> /dev/null

Once above line is entered, the program test.pl creates a /var/log/test.pid file which includes the PID of the program running and keeps doing the things I need it to do which is some report recording to SQL. So, I guess as you suggested I can run monit after running the program and have it monitor the PID file however I am not sure at all how to do it. Because all the examples have PROCESS in the first line and I don't think my simple program is a process like HTTP or others. Plus I don't have a START or STOP script for it. I only do "nohup" because I want it it to run if I am closing the terminal window and ">> /dev/null" is so there are no outputs on the screen.

I hope I am a bit more clear and I appreciate if you can give me a sample of what should go in the /etc/monit.conf.

In addition, I would appreciate it if you point me to monit.log (or whatever it's called) and also let me know what happens if the system is restarted? Should I expect Monit to start the program for me automatically?

Thanks,



On Tue, Dec 28, 2010 at 10:19 PM, EzCom Keith <address@hidden> wrote:
On Tue, Dec 28, 2010 at 3:22 PM, Bruce B <address@hidden> wrote:
Anything to this guys?

Thanks,


On Mon, Dec 27, 2010 at 9:57 PM, Bruce B <address@hidden> wrote:
Hi Everyone,

I am very new to monit. I have a perl program (test.pl) which should be running 24/7 and should re-spawn if it goes dead. Of course monit is the right tool for it but I have no clue how to use it.

Here is what I do to start the program each time:

nohup perl /usr/src/test.pl >> /dev/null

The program actually creates a file with PID in it in /var/log/test.pid

I have the following so far in my /etc/monit.conf    ( I am running CentOS) and it doesn't seem to work. 

check process holdreport with pidfile /var/log/test.pid
   start program = "/usr/src/holdReport/startTest.sh"
   if 5 restarts within 5 cycles then timeout

And startTest.sh includes:
nohup perl /usr/src/test.pl >> /dev/null


I would love to receive alerts to my gmail if program shuts down. Please enlighten me on that too.

Thanks,
Bruce



--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general

Sorry Bruce,

Not enough info for me to be much help. When you say "it doesn't seem to work", what does that mean, exactly?
I can assume that if you run sh /usr/src/holdReport/startTest.sh from your shell, the script creates a pid file and
begins to do its job. So what happens when you request Monit to start monitoring? Does it do anything at all?
Can you post the relevant section of your Monit log? Best thing to do is (especially if this is the only process you
are attempting to monitor atm), rm -f your entire monit log. Manually start your perl script, then start monit. Check
the Monit webserver and note anything it says there regarding your script (also note if it does not even exist there).

Shut down Monit, and cat your monit log, copy/paste it to here.

As stated in an earlier thread, I used the 'wrapper' technique, outlined in the Monit FAQ, to successfully monitor
a PHP script that runs 24/7. It was surprisingly easy, and worked as advertised. Review that section, and see if
any of it can help you try a few things.

http://mmonit.com/wiki/Monit/FAQ

Best,
- Keith

--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general


reply via email to

[Prev in Thread] Current Thread [Next in Thread]