There are plenty of free process monitor scripts out there but I don't have any experience with them. A quick check of sourceforge yielded one in php: http://sourceforge.net/projects/phpdog/ but it's new so "use at your own risk".
Browse the others by going to http://sourceforge.net/softwaremap/trove_list.php?form_cat=253 (sys admin) then search results for process. But, of coures, if smokeping is still running (just not updateing rrd's) than it won't help you. Perhaps you could modify or write your own script to also check some .rrd files using rrdtool like so: $ rrdtool last AnnArbor_Chicago.rrd 1243349909 Compare the output to the current unix epoch time and if it's too old then restart. If you want a more thorough check you could run rrtool dump ping_localhost.rrd > /tmp/rrd.xml and look for sane values. -Russell Dwarshuis On Tue, 26 May 2009, Sipponen, Sami wrote: > Hi, > > I'm running Smokeping 2.3.6 on Debian Squeeze (Linux 2.6.26-2-686 on > i686) and from time to time Smokeping stops measuring and starts drawing > blank graph. This happens maybe once in a month and is that rarely that > I'm not actually interested on the root cause. However I'd like to > monitor when Smokeping stops measuring and restart the Smokeping daemon > or maybe even restart the whole server. > > I have automatical update script which uploads new configuration to > Smokeping once every night and probably it will get Smokeping confused > when the config is reloaded too many times. Usually the measuring stops > when the update script has been run, but when I restart the Smokeping > daemon or the whole server it starts working perfectly well. Smokeping > startup messages: > > May 26 09:49:47 sping1 smokeping: Daemonizing /usr/sbin/smokeping ... > May 26 09:49:47 sping1 smokeping[3536]: Smokeping version 2.003006 > successfully launched. > May 26 09:49:47 sping1 smokeping[3536]: Entering multiprocess mode. > May 26 09:49:47 sping1 smokeping[3536]: No targets defined for probe > EchoPingHttps, skipping. > May 26 09:49:47 sping1 smokeping[3536]: No targets defined for probe > EchoPingIcp, skipping. > May 26 09:49:47 sping1 smokeping[3537]: EchoPingHttp: probing 4 targets with > step 300 s and offset 154 s. > May 26 09:49:47 sping1 smokeping[3536]: Child process 3537 started for probe > EchoPingHttp. > May 26 09:49:47 sping1 smokeping[3538]: FPing: probing 393 targets with step > 300 s and offset 151 s. > May 26 09:49:47 sping1 smokeping[3536]: Child process 3538 started for probe > FPing. > May 26 09:49:47 sping1 smokeping[3539]: EchoPingSmtp: probing 1 targets with > step 300 s and offset 37 s. > May 26 09:49:47 sping1 smokeping[3536]: Child process 3539 started for probe > EchoPingSmtp. > May 26 09:49:47 sping1 smokeping[3536]: Child process 3544 started for probe > LDAP. > May 26 09:49:47 sping1 smokeping[3544]: LDAP: probing 204 targets with step > 300 s and offset 56 s. > May 26 09:49:47 sping1 smokeping[3545]: DNS: probing 9 targets with step 300 > s and offset 239 s. > May 26 09:49:47 sping1 smokeping[3536]: Child process 3545 started for probe > DNS. > May 26 09:49:47 sping1 smokeping[3536]: All probe processes started > successfully. > > So is there any readymade script that can look inside RRD's or some other way > notice that Smokeping is dead even the daemon itself is up and running? (all > graps are showing "nodata_color" only) If there is no such script already > made, any hints how to make one? I'm familiar with PHP, but Perl or Shell > scripts are not my speciality, however I'm willing to try... > > Regards, Sami Sipponen > > _______________________________________________ > smokeping-users mailing list > [email protected] > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users > _______________________________________________ smokeping-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
