From Bert at samson-it.nl  Thu Nov  1 20:04:08 2012
From: Bert at samson-it.nl (Bert Roelofsen)
Date: Thu, 1 Nov 2012 20:04:08 +0100
Subject: [smokeping-users] do slaves update their config automatic?
Message-ID: <6535ECBD65E2EB4DBCC6F12BA622E2FD18A1BD90D5@SIT-SVR-01.samson-it.local>

Hello to all!

Just asking, the docs seem to be a bit unclear. I have two slaves running smokeping and one master. For the slave to pick up the new config (for example an added target)  I have to restart smokeping on the slave. Is this normal behavior or  should every slave pick-up a new config when delivering it's results to the master. If the latest what would be the best approach to debug my failing system?

Master and slave 1 are Debain squeeze
Slave 2 is Ubuntu 12.04 

Met vriendelijke groet,

Bert Roelofsen
----------------------------
Samson IT BV
Dynamoweg 28
2627 CH Delft
t: 088 - 6 16 16 16
i: www.samson-it.nl
----------------------------



From darren at victoriajd.com  Fri Nov  2 04:50:52 2012
From: darren at victoriajd.com (Darren Murphy)
Date: Fri, 2 Nov 2012 11:50:52 +0800
Subject: [smokeping-users] do slaves update their config automatic?
In-Reply-To: <6535ECBD65E2EB4DBCC6F12BA622E2FD18A1BD90D5@SIT-SVR-01.samson-it.local>
References: <6535ECBD65E2EB4DBCC6F12BA622E2FD18A1BD90D5@SIT-SVR-01.samson-it.local>
Message-ID: <CAJYt4Jsh3wRUkhBqFegLx=GPxhoA6Sb=-9enqj8Re6g4yAJnDg@mail.gmail.com>

Hi Bert,

On 2 November 2012 03:04, Bert Roelofsen <Bert at samson-it.nl> wrote:
> Hello to all!
>
> Just asking, the docs seem to be a bit unclear. I have two slaves running smokeping and one master. For the slave to pick up the new config (for example an added target)  I have to restart smokeping on the slave. Is this normal behavior or  should every slave pick-up a new config when delivering it's results to the master. If the latest what would be the best approach to debug my failing system?
>

No, you should not need to restart your slaves.
Check your slave smokeping log from around the time you updated your
master config.
If all is working correctly, you should see something similar to:

Oct 30 20:27:35 smokeping[22251]: Sent data to Server and got new
config in response.
Oct 30 20:27:35 smokeping[22251]: server has new config for me ...
HUPing the parent

The next step will depend on what you see in the log. If you see
nothing at all, then you may need to start your slave in debug mode so
that you can capture some more information.

cheers,
Darren


From andranik.h89 at gmail.com  Fri Nov  2 18:32:35 2012
From: andranik.h89 at gmail.com (Andranik Hayrapetyan)
Date: Fri, 2 Nov 2012 21:32:35 +0400
Subject: [smokeping-users] How to run the same probe with different steps .
Message-ID: <CAPRiZs=EaPW9VhFxpJo6GUcdc9WfhSHDWeo6P3EQ0wbx9OUtdw@mail.gmail.com>

Good day.

I have smokeping 2.3.6 that is pinging about 100 targets with FPing and its
step is 300 seconds.
Now I need to ping only 2 targets with FPing but in 30 second step.

How can I run the same FPing probe with different steps for different
targets?

Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20121102/a9c41862/attachment-0001.htm 

From rb14060 at gmail.com  Fri Nov  2 18:35:17 2012
From: rb14060 at gmail.com (Ryan Becker)
Date: Fri, 2 Nov 2012 13:35:17 -0400
Subject: [smokeping-users] How to run the same probe with different
	steps .
In-Reply-To: <CAPRiZs=EaPW9VhFxpJo6GUcdc9WfhSHDWeo6P3EQ0wbx9OUtdw@mail.gmail.com>
References: <CAPRiZs=EaPW9VhFxpJo6GUcdc9WfhSHDWeo6P3EQ0wbx9OUtdw@mail.gmail.com>
Message-ID: <CAAjykhZvZn=71ak-V5nGRb+DbSfH4g786_++Us7bYeZn=xWsbg@mail.gmail.com>

Hello,
Looking at the SmokePing configuration file, it looks like the steps option
is defined globally, not per probe.  Due to this it would appear that there
is no way to run multiple probes with different steps.  Perhaps someone
else can provide some insight but this is the best I've got.


On Fri, Nov 2, 2012 at 1:32 PM, Andranik Hayrapetyan <andranik.h89 at gmail.com
> wrote:

> Good day.
>
> I have smokeping 2.3.6 that is pinging about 100 targets with FPing and
> its step is 300 seconds.
> Now I need to ping only 2 targets with FPing but in 30 second step.
>
> How can I run the same FPing probe with different steps for different
> targets?
>
> Thanks in advance.
>
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20121102/fb056791/attachment.htm 

From joshua at qcsitter.com  Mon Nov  5 21:29:34 2012
From: joshua at qcsitter.com (Joshua M. Andrews)
Date: Mon, 05 Nov 2012 14:29:34 -0600
Subject: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New targets
	don't show up
Message-ID: <509821AE.8080707@qcsitter.com>

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


From slyons at fxcm.com  Mon Nov  5 22:13:15 2012
From: slyons at fxcm.com (Seth Lyons)
Date: Mon, 5 Nov 2012 21:13:15 +0000
Subject: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New
	targets	don't show up
In-Reply-To: <509821AE.8080707@qcsitter.com>
References: <509821AE.8080707@qcsitter.com>
Message-ID: <9BF379D91EE4D442A823DCC8C7EDF3DD17230A92@EXCASHUBMBXp01.usa.fxcorp.prv>

Make sure that your www user can write to /usr/local/var/smokeping.

-----Original Message-----
From: smokeping-users-bounces+slyons=fxcm.com at lists.oetiker.ch [mailto:smokeping-users-bounces+slyons=fxcm.com at lists.oetiker.ch] On Behalf Of Joshua M. Andrews
Sent: Monday, November 05, 2012 3:30 PM
To: smokeping-users at 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 at lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


From joshua at qcsitter.com  Mon Nov  5 23:42:48 2012
From: joshua at qcsitter.com (Joshua M. Andrews)
Date: Mon, 05 Nov 2012 16:42:48 -0600
Subject: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New targets
 don't show up
In-Reply-To: <9BF379D91EE4D442A823DCC8C7EDF3DD17230A92@EXCASHUBMBXp01.usa.fxcorp.prv>
References: <509821AE.8080707@qcsitter.com>
	<9BF379D91EE4D442A823DCC8C7EDF3DD17230A92@EXCASHUBMBXp01.usa.fxcorp.prv>
Message-ID: <509840E8.9060104@qcsitter.com>

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: smokeping-users-bounces+slyons=fxcm.com at lists.oetiker.ch [mailto:smokeping-users-bounces+slyons=fxcm.com at lists.oetiker.ch] On Behalf Of Joshua M. Andrews
> Sent: Monday, November 05, 2012 3:30 PM
> To: smokeping-users at 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 at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


From slyons at fxcm.com  Mon Nov  5 23:48:30 2012
From: slyons at fxcm.com (Seth Lyons)
Date: Mon, 5 Nov 2012 22:48:30 +0000
Subject: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New targets
 don't show up
In-Reply-To: <509840E8.9060104@qcsitter.com>
References: <509821AE.8080707@qcsitter.com>
	<9BF379D91EE4D442A823DCC8C7EDF3DD17230A92@EXCASHUBMBXp01.usa.fxcorp.prv>
	<509840E8.9060104@qcsitter.com>
Message-ID: <9BF379D91EE4D442A823DCC8C7EDF3DD17231A8B@EXCASHUBMBXp01.usa.fxcorp.prv>

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:joshua at qcsitter.com] 
Sent: Monday, November 05, 2012 5:43 PM
To: Seth Lyons
Cc: smokeping-users at lists.oetiker.ch
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: smokeping-users-bounces+slyons=fxcm.com at lists.oetiker.ch 
> [mailto:smokeping-users-bounces+slyons=fxcm.com at lists.oetiker.ch] On 
> Behalf Of Joshua M. Andrews
> Sent: Monday, November 05, 2012 3:30 PM
> To: smokeping-users at 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 at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


From smokeping at museum.rain.com  Tue Nov  6 03:37:34 2012
From: smokeping at museum.rain.com (Jim Long)
Date: Mon, 5 Nov 2012 18:37:34 -0800
Subject: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New targets
 don't show up
In-Reply-To: <9BF379D91EE4D442A823DCC8C7EDF3DD17231A8B@EXCASHUBMBXp01.usa.fxcorp.prv>
References: <509821AE.8080707@qcsitter.com>
	<9BF379D91EE4D442A823DCC8C7EDF3DD17230A92@EXCASHUBMBXp01.usa.fxcorp.prv>
	<509840E8.9060104@qcsitter.com>
	<9BF379D91EE4D442A823DCC8C7EDF3DD17231A8B@EXCASHUBMBXp01.usa.fxcorp.prv>
Message-ID: <20121106023734.GA20333@ns.umpquanet.com>

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:joshua at qcsitter.com] 
> Sent: Monday, November 05, 2012 5:43 PM
> To: Seth Lyons
> Cc: smokeping-users at lists.oetiker.ch
> 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: smokeping-users-bounces+slyons=fxcm.com at lists.oetiker.ch 
> > [mailto:smokeping-users-bounces+slyons=fxcm.com at lists.oetiker.ch] On 
> > Behalf Of Joshua M. Andrews
> > Sent: Monday, November 05, 2012 3:30 PM
> > To: smokeping-users at 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 at lists.oetiker.ch
> > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
> 
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


From joshua at qcsitter.com  Tue Nov  6 18:03:22 2012
From: joshua at qcsitter.com (Joshua M. Andrews)
Date: Tue, 06 Nov 2012 11:03:22 -0600
Subject: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New targets
 don't show up
In-Reply-To: <20121106023734.GA20333@ns.umpquanet.com>
References: <509821AE.8080707@qcsitter.com>
	<9BF379D91EE4D442A823DCC8C7EDF3DD17230A92@EXCASHUBMBXp01.usa.fxcorp.prv>
	<509840E8.9060104@qcsitter.com>
	<9BF379D91EE4D442A823DCC8C7EDF3DD17231A8B@EXCASHUBMBXp01.usa.fxcorp.prv>
	<20121106023734.GA20333@ns.umpquanet.com>
Message-ID: <509942DA.8040609@qcsitter.com>

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:joshua at qcsitter.com]
>> Sent: Monday, November 05, 2012 5:43 PM
>> To: Seth Lyons
>> Cc: smokeping-users at lists.oetiker.ch
>> 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: smokeping-users-bounces+slyons=fxcm.com at lists.oetiker.ch
>>> [mailto:smokeping-users-bounces+slyons=fxcm.com at lists.oetiker.ch] On
>>> Behalf Of Joshua M. Andrews
>>> Sent: Monday, November 05, 2012 3:30 PM
>>> To: smokeping-users at 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 at lists.oetiker.ch
>>> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>> _______________________________________________
>> smokeping-users mailing list
>> smokeping-users at lists.oetiker.ch
>> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


From Vinny_Abello at Dell.com  Tue Nov  6 21:05:04 2012
From: Vinny_Abello at Dell.com (Vinny_Abello at Dell.com)
Date: Tue, 6 Nov 2012 20:05:04 +0000
Subject: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New
	targets	don't show up
In-Reply-To: <509821AE.8080707@qcsitter.com>
References: <509821AE.8080707@qcsitter.com>
Message-ID: <FD9B2CB2B33E394FAE3B7466954760571D395641@DFWX10HMPTC01.AMER.DELL.COM>

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.com at lists.oetiker.ch [mailto:smokeping-users-bounces+vinny_abello=dell.com at lists.oetiker.ch] On Behalf Of Joshua M. Andrews
Sent: Monday, November 05, 2012 3:30 PM
To: smokeping-users at 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 at lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


From joshua at qcsitter.com  Tue Nov  6 21:11:15 2012
From: joshua at qcsitter.com (Joshua M. Andrews)
Date: Tue, 06 Nov 2012 14:11:15 -0600
Subject: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New targets
 don't show up
In-Reply-To: <FD9B2CB2B33E394FAE3B7466954760571D395641@DFWX10HMPTC01.AMER.DELL.COM>
References: <509821AE.8080707@qcsitter.com>
	<FD9B2CB2B33E394FAE3B7466954760571D395641@DFWX10HMPTC01.AMER.DELL.COM>
Message-ID: <50996EE3.6090508@qcsitter.com>

Vinny:

Thank you for the response.  What process are you killing?

- Joshua

On 11/6/2012 2:05 PM, Vinny_Abello at 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.com at lists.oetiker.ch [mailto:smokeping-users-bounces+vinny_abello=dell.com at lists.oetiker.ch] On Behalf Of Joshua M. Andrews
> Sent: Monday, November 05, 2012 3:30 PM
> To: smokeping-users at 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 at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


From joshua at qcsitter.com  Tue Nov  6 21:16:31 2012
From: joshua at qcsitter.com (Joshua M. Andrews)
Date: Tue, 06 Nov 2012 14:16:31 -0600
Subject: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New targets
 don't show up
In-Reply-To: <50996EE3.6090508@qcsitter.com>
References: <509821AE.8080707@qcsitter.com>
	<FD9B2CB2B33E394FAE3B7466954760571D395641@DFWX10HMPTC01.AMER.DELL.COM>
	<50996EE3.6090508@qcsitter.com>
Message-ID: <5099701F.6090500@qcsitter.com>

Actually, I thought for fun I would try restarting apache and after 
doing so everything showed up. Thanks for the idea Vinny!

- Joshua

On 11/6/2012 2:11 PM, Joshua M. Andrews wrote:
> Vinny:
>
> Thank you for the response.  What process are you killing?
>
> - Joshua
>
> On 11/6/2012 2:05 PM, Vinny_Abello at 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.com at lists.oetiker.ch [mailto:smokeping-users-bounces+vinny_abello=dell.com at lists.oetiker.ch] On Behalf Of Joshua M. Andrews
>> Sent: Monday, November 05, 2012 3:30 PM
>> To: smokeping-users at 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 at lists.oetiker.ch
>> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


From jan.rockstedt at gmail.com  Wed Nov  7 08:20:20 2012
From: jan.rockstedt at gmail.com (Jan Rockstedt)
Date: Wed, 7 Nov 2012 08:20:20 +0100
Subject: [smokeping-users] Two probes with fping
Message-ID: <CAPk8Vd_juBx3n9p58PY0-ShjdY+NUCbkAEQzapBtUjAn_f7W+A@mail.gmail.com>

Hi all,



I use fping as probes today with as the below config and I want to have
another fping that ping often than every 5 minutes.

Is this possible and how?



+ FPing

binary = /usr/local/sbin/fping
blazemode = true

# + FPing2

# binary = /usr/local/sbin/fping
# blazemode = true
# pings = 10
# step = 120



Regards Jan Rockstedt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20121107/eaa14b94/attachment-0001.htm 

From jul.collas at gmail.com  Wed Nov  7 13:59:56 2012
From: jul.collas at gmail.com (Julien Collas)
Date: Wed, 7 Nov 2012 13:59:56 +0100
Subject: [smokeping-users] Two probes with fping
In-Reply-To: <CAPk8Vd_juBx3n9p58PY0-ShjdY+NUCbkAEQzapBtUjAn_f7W+A@mail.gmail.com>
References: <CAPk8Vd_juBx3n9p58PY0-ShjdY+NUCbkAEQzapBtUjAn_f7W+A@mail.gmail.com>
Message-ID: <CAHK+TY8SSDuRMQOhjKti5_EsQmGGrNQAC+qn6=UCU_69PPcUAQ@mail.gmail.com>

HI,

This configuration works for me

+ FPing

binary = /usr/local/sbin/fping
blazemode = true


++ FPing


++ FPing2
pings = 10
step = 120

Regards,

Julien


2012/11/7 Jan Rockstedt <jan.rockstedt at gmail.com>

>  Hi all,
>
>
>
> I use fping as probes today with as the below config and I want to have
> another fping that ping often than every 5 minutes.
>
> Is this possible and how?
>
>
>
> + FPing
>
> binary = /usr/local/sbin/fping
> blazemode = true
>
> # + FPing2
>
> # binary = /usr/local/sbin/fping
> # blazemode = true
> # pings = 10
> # step = 120
>
>
>
> Regards Jan Rockstedt
>
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20121107/bc241c82/attachment.htm 

From Vinny_Abello at Dell.com  Thu Nov  8 19:47:06 2012
From: Vinny_Abello at Dell.com (Vinny_Abello at Dell.com)
Date: Thu, 8 Nov 2012 18:47:06 +0000
Subject: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New targets
 don't show up
In-Reply-To: <5099701F.6090500@qcsitter.com>
References: <509821AE.8080707@qcsitter.com>
	<FD9B2CB2B33E394FAE3B7466954760571D395641@DFWX10HMPTC01.AMER.DELL.COM>
	<50996EE3.6090508@qcsitter.com> <5099701F.6090500@qcsitter.com>
Message-ID: <FD9B2CB2B33E394FAE3B7466954760571D39A03C@DFWX10HMPTC01.AMER.DELL.COM>

Yes, that will work also since they're child processes of Apache. The processes I normally kill, however, are the perl processes running smokeping_cgi. It's less disruptive, unless of course all you run off of Apache is Smokeping in which case restarting Apache is fine.

-Vinny

-----Original Message-----
From: smokeping-users-bounces+vinny_abello=dell.com at lists.oetiker.ch [mailto:smokeping-users-bounces+vinny_abello=dell.com at lists.oetiker.ch] On Behalf Of Joshua M. Andrews
Sent: Tuesday, November 06, 2012 3:17 PM
To: smokeping-users at lists.oetiker.ch
Subject: Re: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New targets don't show up

Actually, I thought for fun I would try restarting apache and after 
doing so everything showed up. Thanks for the idea Vinny!

- Joshua

On 11/6/2012 2:11 PM, Joshua M. Andrews wrote:
> Vinny:
>
> Thank you for the response.  What process are you killing?
>
> - Joshua
>
> On 11/6/2012 2:05 PM, Vinny_Abello at 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.com at lists.oetiker.ch [mailto:smokeping-users-bounces+vinny_abello=dell.com at lists.oetiker.ch] On Behalf Of Joshua M. Andrews
>> Sent: Monday, November 05, 2012 3:30 PM
>> To: smokeping-users at 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 at lists.oetiker.ch
>> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users

_______________________________________________
smokeping-users mailing list
smokeping-users at lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


From joshua at qcsitter.com  Thu Nov  8 20:11:03 2012
From: joshua at qcsitter.com (Joshua M. Andrews)
Date: Thu, 08 Nov 2012 13:11:03 -0600
Subject: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New targets
 don't show up
In-Reply-To: <FD9B2CB2B33E394FAE3B7466954760571D39A03C@DFWX10HMPTC01.AMER.DELL.COM>
References: <509821AE.8080707@qcsitter.com>
	<FD9B2CB2B33E394FAE3B7466954760571D395641@DFWX10HMPTC01.AMER.DELL.COM>
	<50996EE3.6090508@qcsitter.com> <5099701F.6090500@qcsitter.com>
	<FD9B2CB2B33E394FAE3B7466954760571D39A03C@DFWX10HMPTC01.AMER.DELL.COM>
Message-ID: <509C03C7.4070206@qcsitter.com>

Vinny:

Yes, only runs SmokePing so it was no big deal to restart Apache. Thanks 
for your help, problem resolved!

- Joshua

On 11/8/2012 12:47 PM, Vinny_Abello at Dell.com wrote:
> Yes, that will work also since they're child processes of Apache. The processes I normally kill, however, are the perl processes running smokeping_cgi. It's less disruptive, unless of course all you run off of Apache is Smokeping in which case restarting Apache is fine.
>
> -Vinny
>
> -----Original Message-----
> From: smokeping-users-bounces+vinny_abello=dell.com at lists.oetiker.ch [mailto:smokeping-users-bounces+vinny_abello=dell.com at lists.oetiker.ch] On Behalf Of Joshua M. Andrews
> Sent: Tuesday, November 06, 2012 3:17 PM
> To: smokeping-users at lists.oetiker.ch
> Subject: Re: [smokeping-users] FreeBSD 9 x64 + SmokePing 2.6.7 - New targets don't show up
>
> Actually, I thought for fun I would try restarting apache and after
> doing so everything showed up. Thanks for the idea Vinny!
>
> - Joshua
>
> On 11/6/2012 2:11 PM, Joshua M. Andrews wrote:
>> Vinny:
>>
>> Thank you for the response.  What process are you killing?
>>
>> - Joshua
>>
>> On 11/6/2012 2:05 PM, Vinny_Abello at 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.com at lists.oetiker.ch [mailto:smokeping-users-bounces+vinny_abello=dell.com at lists.oetiker.ch] On Behalf Of Joshua M. Andrews
>>> Sent: Monday, November 05, 2012 3:30 PM
>>> To: smokeping-users at 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 at lists.oetiker.ch
>>> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>> _______________________________________________
>> smokeping-users mailing list
>> smokeping-users at lists.oetiker.ch
>> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


From Niko at 51hosting.com  Sat Nov 10 15:36:27 2012
From: Niko at 51hosting.com (NIKO)
Date: Sat, 10 Nov 2012 22:36:27 +0800
Subject: [smokeping-users] start slave smokeping error
Message-ID: <509E666B.8050307@51hosting.com>

when I at last start the smokeping service?it apears some error ?I
dont know what does it mean???slave is not work ?the syslog is below

#/opt/smokeping/bin/smokeping
--master-url=http://ping.emagineconcept.com/smokeping/smokeping.cgi
--cache-dir=/opt/smokeping/cache/
--shared-secret=/opt/smokeping/etc/secrets.txt
Sent data to Server and got new config in response.
Use of uninitialized value in pattern match (m//) at
/opt/smokeping/lib/Smokeping/probes/FPing.pm line 67.
Use of uninitialized value in pattern match (m//) at
/opt/smokeping/lib/Smokeping/probes/FPing.pm line 68.
Use of uninitialized value in pattern match (m//) at
/opt/smokeping/lib/Smokeping/probes/FPing.pm line 70.
Use of uninitialized value in pattern match (m//) at
/opt/smokeping/lib/Smokeping/probes/FPing.pm line 73.
### assuming you are using an fping copy reporting in milliseconds
### parsing dig output...OK
Note: logging to syslog as local0/info.
Daemonizing /opt/smokeping/bin/smokeping ...


From mmoryakov at gmail.com  Fri Nov 23 11:50:05 2012
From: mmoryakov at gmail.com (=?KOI8-R?B?7cHL08nNIO3P0tHLz9c=?=)
Date: Fri, 23 Nov 2012 12:50:05 +0200
Subject: [smokeping-users] Can't call method "_pings"
Message-ID: <CAEtKLwRv2E89w-2Pb42QAYGpLEhHi-f+a3oc_xCzOOAEUW=j-g@mail.gmail.com>

please help to solve the problem

Can't call method "_pings" on an undefined value at
/usr/local/smokeping/lib/Smokeping.pm line 884.

thanks


From list.smokeping-users at natch.dyndns.org  Fri Nov 23 20:18:06 2012
From: list.smokeping-users at natch.dyndns.org (xavier renaut)
Date: Fri, 23 Nov 2012 14:18:06 -0500
Subject: [smokeping-users] HPing.pm ?
Message-ID: <20121123191806.GB9022@asura.magic.8d.com>


I'm trying to use hping3 with smokeping.
(my use case is "# probe the 5th host on route to 8.8.8.8"
hping3 -1 --tr-keep-ttl --traceroute --ttl 5 8.8.8.8

since it wont answer the icmp request ping packet.

I saw some references in the mailing list archives to :

http://lists.ee.ethz.ch/p/HPing.pm 

but it's 404 now.

it's not in the smokeping distribution either, nor in the trunk.

any clues ?

I would rather reuse one than starting from scratch.

thanks.

-- 


From jean at wedebugyou.com  Fri Nov 23 20:41:30 2012
From: jean at wedebugyou.com (Jean)
Date: Fri, 23 Nov 2012 20:41:30 +0100
Subject: [smokeping-users] smokeping+fping6 broken on ubuntu 12.04
Message-ID: <50AFD16A.4050208@wedebugyou.com>

Hello,

I installed smokeping on Ubuntu 12.04.1 LTS with aptitude and I ended up 
with smokeping version 2.006007

I can graph icmp, dns and http without a problem on ipv4. As soon as I 
try to graph something with fping6, the graphs stay empty.
Smokeping is run as smokeping user. It seems the fping6 command is never 
issue because I never see traffic going out for this type of traffic. 
Here is the command


/usr/bin/fping6 -C 21 -q -B1 -r1 -b500 -i1 -p1500 -Smy:ip:v6:ad:dr:e:ss

When I try this command as smokeping user here is what I received.

/usr/bin/fping6: these options are too risky for mere mortals.

Funny error message, I like that. So my fping6 is setuid. Maybe I am wrong.

# ls -la /usr/bin/fping*
-rwsr-xr-x 1 root root 31528 Feb  2  2010 /usr/bin/fping
-rwsr-xr-x 1 root root 31560 Feb  2  2010 /usr/bin/fping6

Is that good?

So, to fix it, running it as root is working, but I guess it's not the 
best way to fix it.

Is there something you can do?

thanks

Jean


From jrizzo at rizzos.net  Sat Nov 24 02:02:17 2012
From: jrizzo at rizzos.net (Joe Rizzo)
Date: Fri, 23 Nov 2012 19:02:17 -0600
Subject: [smokeping-users] HPing.pm ?
In-Reply-To: <20121123191806.GB9022@asura.magic.8d.com>
References: <20121123191806.GB9022@asura.magic.8d.com>
Message-ID: <CAHyALFKO_rk4Kp3pLqpAs2361eimXX1rbwDJQXUtRGVvr9jG2w@mail.gmail.com>

http://dl.dropbox.com/u/2723331/HPing.pm

Joe

On Fri, Nov 23, 2012 at 1:18 PM, xavier renaut <
list.smokeping-users at natch.dyndns.org> wrote:

>
> I'm trying to use hping3 with smokeping.
> (my use case is "# probe the 5th host on route to 8.8.8.8"
> hping3 -1 --tr-keep-ttl --traceroute --ttl 5 8.8.8.8
>
> since it wont answer the icmp request ping packet.
>
> I saw some references in the mailing list archives to :
>
> http://lists.ee.ethz.ch/p/HPing.pm
>
> but it's 404 now.
>
> it's not in the smokeping distribution either, nor in the trunk.
>
> any clues ?
>
> I would rather reuse one than starting from scratch.
>
> thanks.
>
> --
>
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20121123/f67f64c5/attachment.htm 

From rumpole2012 at outlook.com  Wed Nov 28 02:50:27 2012
From: rumpole2012 at outlook.com (Rumpole A)
Date: Wed, 28 Nov 2012 12:50:27 +1100
Subject: [smokeping-users] Graph question
Message-ID: <COL002-W23C3CAD4122BC08DCF118BA15D0@phx.gbl>



Hi all

 

I have a couple of questions regarding smokeping and rrdtool
which I?m hoping someone can assist with.

 

I would like the graphs generated via smokeping to be
smooth, instead of stair-case jagged like. 
According to the RRDtool page, the ?--slope-mode? switch can be used to
accomplish this.  I don?t have much knowledge
of perl or RRD but I did manage to find this file called ?RRDtools.pm? located
at ?/opt/smokeping/lib/Smokeping/RRDtools.pm? . 
I modified the following lines below from the RRDtools.pm file but it
didn?t make a difference.  

 

# or compare them
against another create list

 my @create = ('--step', 60,
'DS:ds0:GAUGE:120:0:U', 'RRA:AVERAGE:0.5:1:1008', '--slope-mode');

 

Not really sure what I?m doing here, was just taking a
guess.  If anyone knows how to apply the
slope-mode parameter and can give an example config paste that would definitely
be appreciated J

 

Thanks,Rumpole 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20121128/a2b39f87/attachment.htm 

From losburn at thepinnaclegroup.com  Fri Nov 30 01:44:33 2012
From: losburn at thepinnaclegroup.com (Lynn Osburn)
Date: Thu, 29 Nov 2012 16:44:33 -0800
Subject: [smokeping-users] all lost packets
Message-ID: <30D2770F2F340F48A85D65112C52AA8A46ECA5B7D4@EXVMBX020-10.exch020.serverdata.net>

Hello, all

This is a new installation, which seems to be working except that the fping data is being incorrectly recorded in RRD as 100% lost packets.

./bin/smokeping --config=/opt/smokeping/etc/config --debug shows 3 probes, with all packets lost.

Smokeping version 2.006008 successfully launched.
Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for that.
FPing: probing 3 targets with step 300 s and offset 266 s.
FPing: Executing /usr/sbin/fping -C 20 -q -B1 -r1 -i10 10.15.6.239 10.15.6.11 10.10.1.251
Calling RRDs::update(/opt/smokeping/data/FRII/drrpa.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1354235704:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U)
Calling RRDs::update(/opt/smokeping/data/FRII/drsbsa.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1354235704:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U)
Calling RRDs::update(/opt/smokeping/data/GRLL/core.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1354235704:U:20:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U:U)

But when I execute the same fping that smokeping launched on our behalf, I get real data.
/usr/sbin/fping -C 20 -q -B1 -r1 -i10 10.15.6.239 10.15.6.11 10.10.1.251
10.15.6.239 : 43.04 57.77 87.80 5.85 5.80 72.17 49.73 5.87 5.81 5.79 5.79 5.78 5.79 6.05 5.86 62.64 5.85 6.19 8.43 5.81
10.15.6.11  : 39.21 59.65 86.34 5.86 5.79 73.59 49.71 5.76 5.74 5.72 5.76 5.72 6.56 5.76 5.72 58.18 5.85 5.80 11.55 5.97
10.10.1.251 : 0.96 0.50 1.91 3.72 0.48 0.70 0.52 0.62 0.49 0.49 0.57 0.48 0.48 0.55 0.48 1.06 1.85 0.49 0.60 0.91

Anyone have any idea why the fping data isn't making its way back into the RRD::update process correctly?

Thanks!