Hello,
Thanks! I really appreciate the replies!
Russell's suggestion works, with some modifications.
> try this
> start)
> exec 2>&1 /usr/bin/python /home/pi/temperature/post_temps.py
1>/tmp/post_temps.out &
> echo $! > /var/run/start_sensors.pid;
> ;;
I had to remove the 'exec' since that replaces the shell process with the
python process, so the 'echo...' line never runs. But then it worked!
Fantastic.
For the record, here's the shell script in case someone runs into this
problem:
#!/bin/bash
case $1 in
start)
/usr/bin/python /home/pi/temperature/post_temps.py
1>/tmp/post_temps.out &
echo $! > /var/run/start_sensors.pid ;
;;
stop)
kill `cat /var/run/start_sensors.pid` ;;
*)
echo "usage: start_sensors {start|stop}" ;;
esac
exit 0
Thanks again... great to get this going.
On Mon, Jan 26, 2015 at 7:03 PM, Russell Simpkins <[email protected]
> wrote:
> try this
>
> start)
> exec 2>&1 /usr/bin/python /home/pi/temperature/post_temps.py
> 1>/tmp/post_temps.out &
> echo $! > /var/run/start_sensors.pid;
> ;;
>
> $$ is the current pid and $! is the pid spawned by exec running in the
> background. Since exec spawns a sub process pid, you'll want that in your
> pid file.
>
> On Mon, Jan 26, 2015 at 6:00 PM, Chris Sterritt <[email protected]>
> wrote:
>
>> Hello,
>>
>> First, thanks for monit -- it looks to be very useful. My apologies if
>> I've missed something.
>>
>> I'm having a problem monitoring a program using monit.
>>
>> I'm running this on a raspberry pi, having built monit 5.11 from source;
>> I tried using the version from the repositories, but it was 5.4 and didn't
>> support some of syntax below that I want.
>>
>> I'm trying to follow the "Q: I have a program that does not create its
>> own pid file. Since monit requires all programs to have a pid file, what do
>> I do?" [entry in the FAQ](http://mmonit.com/wiki/Monit/FAQ#pidfile).
>>
>> Here's my start_sensors.sh script (which just runs my python program,
>> instead of
>> the java program in the wiki example):
>>
>> #!/bin/bash
>>
>> case $1 in
>> start)
>> echo $$ > /var/run/start_sensors.pid;
>> exec 2>&1 /usr/bin/python /home/pi/temperature/post_temps.py
>> 1>/tmp/post_temps.out
>> ;;
>> stop)
>> kill `cat /var/run/start_sensors.pid` ;;
>> *)
>> echo "usage: start_sensors {start|stop}" ;;
>> esac
>> exit 0
>>
>> Here's my `/etc/monit/monitrc` entry:
>>
>> # Run temperature sensor monitor
>> check process start_sensors.sh with pidfile /var/run/start_sensors.pid
>> start = "/home/pi/temperature/start_sensors.sh start"
>> stop = "/home/pi/temperature/start_sensors.sh stop"
>>
>> The output in the monit log looks like:
>>
>> [EST Jan 24 14:21:16] info : 'raspberrypi' Monit reloaded
>> [EST Jan 24 14:21:16] error : 'start_sensors.sh' process is not
>> running
>> [EST Jan 24 14:21:16] info : 'start_sensors.sh' trying to restart
>> [EST Jan 24 14:21:16] info : 'start_sensors.sh' start:
>> /home/pi/temperature/start_sensors. sh
>> [EST Jan 24 14:21:46] error : 'start_sensors.sh' failed to start
>> (exit status -1) -- Program /home/pi/temperature/start_sensors.sh timed
>> out
>>
>> So as you can see, monit starts up the program, it runs fine, and then
>> monit kills it thirty seconds later due to the "timeout".
>>
>> My program is running fine, and producing the proper output that I'm
>> sending to the /tmp/post_temps.out file.
>>
>> I don't understand why monit is timing the program out... it's supposed
>> to be a long-running process!
>>
>> I've tried changing the start_sensors.sh script so that it puts the
>> program in the background (and has it write its own
>> /var/run/start_sensors.pid file), but then monit starts a new instance up
>> every thirty seconds or so, not stopping the old ones, and writing over the
>> pid file. It's like it's not even looking at the pid file.
>>
>> THANKS!
>>
>> --
>> To unsubscribe:
>> https://lists.nongnu.org/mailman/listinfo/monit-general
>>
>
>
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general
>
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
