Vinny: Thank you for the response. What process are you killing?
- Joshua On 11/6/2012 2:05 PM, vinny_abe...@dell.com wrote: > I continue to have the same issue under FreeBSD as well ever since FastCGI > was used. It's related to FastCGI not loading the new configuration file. > From what I was told, smokeping is supposed to signal it, but it fails to do > this for me. I always have to kill the processes and let them respawn on next > hit of a web page for things to update. I unfortunately don't have the time > or skill to debug it any further. I suspect maybe it's something to do with a > difference in FreeBSD's security model and being able to have smokeping > successfully signal the FastCGI process... or it could be something much > simpler. > > Basically, if anyone installs smokeping on FreeBSD from ports, you can > reproduce this. I have half a dozen FreeBSD systems like this that all behave > this way. > > -Vinny > > -----Original Message----- > From: smokeping-users-bounces+vinny_abello=dell....@lists.oetiker.ch > [mailto:smokeping-users-bounces+vinny_abello=dell....@lists.oetiker.ch] On > Behalf Of Joshua M. Andrews > Sent: Monday, November 05, 2012 3:30 PM > To: smokeping-users@lists.oetiker.ch > Subject: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New targets > don't show up > > Tech Specs: > --------------- > > FreeBSD 9.0-RELEASE > SmokePing 2.6.7 > Apache 2.2 > > Config Excerpt: > --------------------- > > + Network > menu = Targets > > ++ QCSitter > menu = QCSitter > title = WWW - QCSitter.com > host = www.qcsitter.com > > + Services > menu = Services (DNS) > title = DNS > > ++ DNS > > probe = DNS > > menu = Latency > title = Service latency (DNS) > > +++ GoogleDNS > host = 8.8.8.8 > > That is an excerpt of what I have working properly. So, now I add a new > target like this: > > + Network > menu = Targets > > ++ QCSitter > menu = QCSitter > title = WWW - QCSitter.com > host = www.qcsitter.com > > ++ TestTarget > menu = TestTarget > title = Test Target > host = 8.8.4.4 > > So then I do: smokeping reload (also tried restart). I then wait 20 > minutes and no graphs show up. So I tail the log and get the following: > > Mon Nov 5 14:16:59 2012 - Reloading configuration. > Mon Nov 5 14:16:59 2012 - Got HUP signal, exiting gracefully. > Mon Nov 5 14:16:59 2012 - Got HUP signal, exiting gracefully. > Mon Nov 5 14:16:59 2012 - Exiting due to HUP signal. > Mon Nov 5 14:16:59 2012 - Exiting due to HUP signal. > Mon Nov 5 14:16:59 2012 - Waiting for child processes to terminate. > Mon Nov 5 14:16:59 2012 - Child processes terminated, restarting with > new configuration. > Mon Nov 5 14:16:59 2012 - Entering multiprocess mode. > Mon Nov 5 14:16:59 2012 - Child process 68606 started for probe FPing. > Mon Nov 5 14:16:59 2012 - Child process 68607 started for probe DNS. > Mon Nov 5 14:16:59 2012 - FPing: probing 7 targets with step 300 s and > offset 239 s. > Mon Nov 5 14:16:59 2012 - All probe processes started successfully. > Mon Nov 5 14:16:59 2012 - DNS: probing 3 targets with step 300 s and > offset 179 s. > > You can see that it reloaded and then restarted and that all my targets > and working fine. There are no other logs to report after that. I then > check Apache's logs and find nothing out of the ordinary. It just seems > that SmokePing isn't generating the graphs for the new entries, it's > only keeping the ones that were already there. > > What am I missing? > > - Joshua > > _______________________________________________ > smokeping-users mailing list > smokeping-users@lists.oetiker.ch > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users _______________________________________________ smokeping-users mailing list smokeping-users@lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users