David Schweikert | 1 Feb 2012 09:43
Picon
Gravatar

Re: fping6 - where?

Hi,

On Tue, Jan 31, 2012 at 14:52:36 -0500, K. M. Peterson wrote:
> Many thanks.  Actually, the source that I have is
> fping-2.4b2_to4-ipv6, which I think is a bit newer than the version
> you referenced.

You might also want to take my new fping distribution, which includes
Tobi's and the latest Debian patches:

http://fping.org

Also a note about fping6: this is the main change that I plan for
version 3.1: there won't be the need for a separate binary anymore. A
single binary should be able to do both IPv4 and IPv6 and there should
be '-4' and '-6' options to force IPv4-only or IPv6-only name
resolution.

Cheers
David

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

Matthew Ford | 1 Feb 2012 13:12
Favicon

Restarting smokeping

Hi,

I'm at a loss.

I can restart smokeping quite happily from the command line:

# /etc/init.d/smokeping restart
Shutting down latency logger daemon: smokeping.
Starting latency logger daemon: smokeping.

But I cannot get smokeping to restart either using cron directly or by putting the restart command in a shell
script, and adding that to my crontab.

Jan 31 11:52:01 gigondas /USR/SBIN/CRON[19052]: (root) CMD (/etc/init.d/smokeping restart
>/dev/null 2>&1)
Jan 31 11:52:01 gigondas /USR/SBIN/CRON[19051]: (root) END (/etc/init.d/smokeping restart
>/dev/null 2>&1)

Any clue appreciated.

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

Lars Thegler | 1 Feb 2012 13:48
Picon
Gravatar

Re: Restarting smokeping

Try removing the '>/dev/null 2>&1' and see if the resulting output (if
any) gives you any clues.

/Lars

On Wed, Feb 1, 2012 at 1:12 PM, Matthew Ford <ford <at> isoc.org> wrote:
> Hi,
>
> I'm at a loss.
>
> I can restart smokeping quite happily from the command line:
>
> # /etc/init.d/smokeping restart
> Shutting down latency logger daemon: smokeping.
> Starting latency logger daemon: smokeping.
>
> But I cannot get smokeping to restart either using cron directly or by putting the restart command in a
shell script, and adding that to my crontab.
>
> Jan 31 11:52:01 gigondas /USR/SBIN/CRON[19052]: (root) CMD (/etc/init.d/smokeping restart
>/dev/null 2>&1)
> Jan 31 11:52:01 gigondas /USR/SBIN/CRON[19051]: (root) END (/etc/init.d/smokeping restart
>/dev/null 2>&1)
>
> Any clue appreciated.
>
> Mat
> _______________________________________________
> smokeping-users mailing list
> smokeping-users <at> lists.oetiker.ch
(Continue reading)

Matthew Ford | 1 Feb 2012 14:23
Favicon

Re: Restarting smokeping

Initially I was trying to do this without redirecting the output, but there was none.

Mat

On 1 Feb 2012, at 12:48, Lars Thegler wrote:

> Try removing the '>/dev/null 2>&1' and see if the resulting output (if
> any) gives you any clues.
> 
> /Lars
> 
> On Wed, Feb 1, 2012 at 1:12 PM, Matthew Ford <ford <at> isoc.org> wrote:
>> Hi,
>> 
>> I'm at a loss.
>> 
>> I can restart smokeping quite happily from the command line:
>> 
>> # /etc/init.d/smokeping restart
>> Shutting down latency logger daemon: smokeping.
>> Starting latency logger daemon: smokeping.
>> 
>> But I cannot get smokeping to restart either using cron directly or by putting the restart command in a
shell script, and adding that to my crontab.
>> 
>> Jan 31 11:52:01 gigondas /USR/SBIN/CRON[19052]: (root) CMD (/etc/init.d/smokeping restart
>/dev/null 2>&1)
>> Jan 31 11:52:01 gigondas /USR/SBIN/CRON[19051]: (root) END (/etc/init.d/smokeping restart
>/dev/null 2>&1)
>> 
(Continue reading)

Darren Murphy | 1 Feb 2012 14:56
Gravatar

Re: Restarting smokeping

Mat,

Probably a silly question, but how do you know for sure that it isn't
restarting?
eg. Have you compared the PID from before and after the cron task is
executed, and confirmed that it hasn't changed?

cheers,
Darren

On 1 February 2012 21:23, Matthew Ford <ford <at> isoc.org> wrote:
> Initially I was trying to do this without redirecting the output, but there was none.
>
> Mat
>
> On 1 Feb 2012, at 12:48, Lars Thegler wrote:
>
>> Try removing the '>/dev/null 2>&1' and see if the resulting output (if
>> any) gives you any clues.
>>
>> /Lars
>>
>> On Wed, Feb 1, 2012 at 1:12 PM, Matthew Ford <ford <at> isoc.org> wrote:
>>> Hi,
>>>
>>> I'm at a loss.
>>>
>>> I can restart smokeping quite happily from the command line:
>>>
>>> # /etc/init.d/smokeping restart
(Continue reading)

Matthew Ford | 1 Feb 2012 15:01
Favicon

Re: Restarting smokeping

On 1 Feb 2012, at 13:56, Darren Murphy wrote:

> Mat,
> 
> Probably a silly question, but how do you know for sure that it isn't
> restarting?
> eg. Have you compared the PID from before and after the cron task is
> executed, and confirmed that it hasn't changed?
> 

Yes, PID unchanged, process start time unchanged. But...

>> On 1 Feb 2012, at 12:48, Lars Thegler wrote:
>> 
>>> Try removing the '>/dev/null 2>&1' and see if the resulting output (if
>>> any) gives you any clues.
>>> 

This led me to redirect output to a file instead, which helped trace the issue - cron PATH did not include
/sbin, so no way to find start-stop-daemon.

All working now :)

Thanks!

Mat

>>> /Lars
>>> 
>>> On Wed, Feb 1, 2012 at 1:12 PM, Matthew Ford <ford <at> isoc.org> wrote:
(Continue reading)

Lars Thegler | 1 Feb 2012 15:50
Picon
Gravatar

Re: Restarting smokeping

On Wed, Feb 1, 2012 at 3:01 PM, Matthew Ford <ford <at> isoc.org> wrote:
> This led me to redirect output to a file instead, which helped trace the issue - cron PATH did not include
/sbin, so no way to find start-stop-daemon.

Ah, normally, cron will mail any stdout/stderr output, you may want to
look into why you don't receive that.

> All working now :)

Good to hear that :)

/Lars

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

Kris De Rocker | 4 Feb 2012 18:12
Favicon

Smokeping installer

I'm looking for someone who wants to set up a smokeping application on a
system (running centos 6) and that could give me a little howto he've
done it (so i can do it by myself on other systems).  I've tried some
how-to's on the internet, but none seems to work for centos 6.

There is a budget available, but not too high (around 50 euro).
I can give you full access to the server (the master) and a vps (the 
slave).

The meaning of it all is to provide a smokeping solution in around 9
countries where users can sign up to monitor their sites.

Cheers,
Kris

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

G.W. Haywood | 4 Feb 2012 19:01
Picon
Favicon

Re: Smokeping installer

Hi there,

On Sat, 4 Feb 2012, Kris De Rocker wrote:

> I'm looking for someone who wants to set up a smokeping application on a
> system (running centos 6) and that could give me a little howto he've
> done it (so i can do it by myself on other systems).  I've tried some
> how-to's on the internet, but none seems to work for centos 6.

There is plenty of documentation for Smokeping and it's better quality
than a lot of packages I can think of.  Forget Howtos, in general they
suck big-time.  Read the documentation which comes with Smokeping, and
follow the instructions.  One thing that often gets missed is what you
might call the 'bigger picture'.  That is take a step back and look at
what the system is made of.  Here's the bigger picture, in necessarily
rather broad brush-strokes.

Leaving aside slaving for the moment, you basically have three things:

(1) A smokeping daemon, which simply pings some other machines and
saves the resulting data in some RRD files (so you need the RRD tools
on the master machine).  Once this daemon has been installed it must
be started, then it just gets on with it.  It can log information to
files for debugging your installation if you like.  I like logs, they
help a great deal especially if (er, sorry, when) things don't work.
The daemon calls on a number of other 'helpers' so you need them to be
installed in the master (and probably slaves) and smokeping needs to
be avble to find them and use them.  That's all documented.  There are
a couple of little niggles with some of the helpers (instructions from
Smokeping sometimes, rarely, won't match a version of a helper that you
(Continue reading)

Boonie | 5 Feb 2012 20:22
Picon

Alerts - not working as I expected

Hi,
 
I don't understand what's wrong with this bit of config. It results in the error message below.
 
I'm running Version 2.3.6 on Ubuntu.
 
Thanks,
 
Dave
 
 
The relevant part from the Alerts file
----------------------------------------------
+mediumloss
type = loss
# in percent
pattern = >5%,>5%<=55%,>5%<=55%
comment = There is over 5 percent packet loss but not down
----------------------------------------------
 
The error message
----------------------------------------------
/etc/smokeping/config.d# /etc/init.d/smokeping restart
 * Shutting down latency logger daemon smokeping                                                                                                                                                        [ OK ]
 * Starting latency logger daemon smokeping                                                                                                                                                                    ERROR: Alert mediumloss pattern entry '>5%<=55%' is invalid
----------------------------------------------
 
 
 
 
 
_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users

Gmane