Jim: Thank you for your response. I made the suggest changes you recommended and have waited 15 minutes for the graphs to change. The current sites are updating but the new ones refuse to show up??
I implemented your changes, did a restart on smokeping, and the logs reveal nothing different as shown here: Tue Nov 6 10:55:50 2012 - Got TERM signal, terminating child processes. Tue Nov 6 10:55:50 2012 - got TERM signal, terminating. Tue Nov 6 10:55:50 2012 - got TERM signal, terminating. Tue Nov 6 10:55:50 2012 - All child processes successfully terminated, exiting. Tue Nov 6 10:55:51 2012 - Smokeping version 2.006007 successfully launched. Tue Nov 6 10:55:51 2012 - Entering multiprocess mode. Tue Nov 6 10:55:51 2012 - FPing: probing 9 targets with step 300 s and offset 242 s. Tue Nov 6 10:55:51 2012 - Child process 87260 started for probe FPing. Tue Nov 6 10:55:51 2012 - Child process 87261 started for probe DNS. Tue Nov 6 10:55:51 2012 - All probe processes started successfully. Tue Nov 6 10:55:51 2012 - DNS: probing 3 targets with step 300 s and offset 186 s. In Apache's error log I get this: [Tue Nov 06 10:57:16 2012] [warn] [client 192.168.1.87] mod_fcgid: stderr: g median/Network/Europe from sortercache, referer: http://gvsmoke/?target=_charts [Tue Nov 06 10:57:16 2012] [warn] [client 192.168.1.87] mod_fcgid: stderr: [Tue Nov 6 10:57:16 2012] smokeping_cgi [client 192.168.1.87]: Warning: Dropping median/Network/House from sortercache, referer: http://gvsmoke/?target=_charts [Tue Nov 06 10:57:16 2012] [warn] [client 192.168.1.87] mod_fcgid: stderr: [Tue Nov 6 10:57:16 2012] smokeping_cgi [client 192.168.1.87]: Warning: Dropping median/Network/NC from sortercache, referer: http://gvsmoke/?target=_charts [Tue Nov 06 10:57:16 2012] [warn] [client 192.168.1.87] mod_fcgid: stderr: [Tue Nov 6 10:57:16 2012] smokeping_cgi [client 192.168.1.87]: Warning: Dropping median/Network/Moline from sortercache, referer: http://gvsmoke/?target=_charts Not sure what's going on. I had SmokePing running on FreeBSD 8.3 a few months ago and adding a new one, doing a reload, worked fine. No idea what's up with this one!? - Joshua On 11/5/2012 8:37 PM, Jim Long wrote: > Hopefully not to muddle things further, but .... > > www needs READ access to /usr/local/var/smokeping (and all below) > > Seth mentioned write acess -- I don't know of any reason why www > needs WRITE access to /usr/local/var/smokeping. But I could be > ignorant of what the reason is. My FreeBSD smokeping > installation works with www having only read-only access. It > provides a modest security measure also, so that if your www user > gets cracked, they can't damage smokeping's .rrd file data. > > Perhaps the simplest way to give www read access to the 'datadir' > heirarchy is: > > chown -R smokeping:www /usr/local/var/smokeping > > and then make sure that all your files under > /usr/local/var/smokeping are chmod 640 and dirs chmod 750. No > need to mess with groups in /etc/group. > > find /usr/local/var/smokeping -type d | xargs chmod 750 > find /usr/local/var/smokeping -type f | xargs chmod 640 > > www does need WRITE access to /usr/local/smokeping/htdocs/img, > because the www creates graphs on-demand when a web client > requests them, and stores the generated graphs under > /usr/local/smokeping/htdocs/img. > > I hope this helps! :) > > Jim > > > On Mon, Nov 05, 2012 at 10:48:30PM +0000, Seth Lyons wrote: >> To be more clear, both smokeping and www need write access. On my >> FreeBSD/smokeping boxes, I add www to the smokeping group. >> >> -----Original Message----- >> From: Joshua M. Andrews [mailto:[email protected]] >> Sent: Monday, November 05, 2012 5:43 PM >> To: Seth Lyons >> Cc: [email protected] >> Subject: Re: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New targets >> don't show up >> >> When I did that the graphs stopped reporting completely. :( It seems on my >> FreeBSD box it prefers the owner to be smokeping:smokeping to work. >> Any other suggestions or data I can provide? >> >> - Joshua >> >> On 11/5/2012 3:13 PM, Seth Lyons wrote: >>> Make sure that your www user can write to /usr/local/var/smokeping. >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On >>> Behalf Of Joshua M. Andrews >>> Sent: Monday, November 05, 2012 3:30 PM >>> To: [email protected] >>> 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 >>> [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 _______________________________________________ smokeping-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
