Eric Brander | 2 Mar 22:57 2006

Using BIGLOSS, but I shouldn't I guess..

I'm using BIGLOSS to send me an email when Smokeping encounters big
packet loss. In cases where we lose a site (someone turned off the
power) I get a BIGLOSS notification. Then a few minutes later I get a
report of it clearing... I guess 100%, 100%, 100% (u,u,u) no longer
counts as bigloss...

So what should I be using to notify me when we get complete drop-out?

TIA,

Eric Brander

Leos Bitto | 3 Mar 10:23 2006
Picon

Re: Using BIGLOSS, but I shouldn't I guess..

Eric Brander wrote:
> I'm using BIGLOSS to send me an email when Smokeping encounters big
> packet loss. In cases where we lose a site (someone turned off the
> power) I get a BIGLOSS notification. Then a few minutes later I get a
> report of it clearing... I guess 100%, 100%, 100% (u,u,u) no longer
> counts as bigloss...
> 
> So what should I be using to notify me when we get complete drop-out?
> 
> TIA,
> 
> Eric Brander
> 

This is what I use to monitor hosts being unreachable:

+turnedoff
type = loss
pattern = <100%,==100%,==100%
comment = host not responding

+turnedon
type = loss
pattern = ==100%,==100%,<100%
comment = host back again

I could use only one ==100%, but then I get alarms when the host is just 
quickly restarted, too.

Leos
(Continue reading)

hans | 3 Mar 11:44 2006
Picon

Can't load RRDs.so


hi smoking users ! 

i did setup smokeping 2.0.7 on solaris 9 with perl 5.6.1 
starting the smokeping.cgi terminates with the 
following error: 

# /usr/local/apache2053/cgi-bin/smokeping.cgi 
<h1>Software error:</h1>
<pre>Can't load
'/usr/local/rrdtool-1.2.11/lib/perl/5.6.1/sun4-solaris-64int/auto/RRDs/RRDs.so' for module
RRDs: ld.so.1: /usr/perl5/5.6.1/bin/speedy_backend: fatal: relocation error: file
/usr/local/rrdtool-1.2.11/lib/perl/5.6.1/sun4-solaris-64int/auto/RRDs/RRDs.so: symbol
rrd_set_error: referenced symbol not found at
/usr/perl5/5.6.1/lib/sun4-solaris-64int/DynaLoader.pm line 206.
Compilation failed in require at /opt/smokeping207/lib/Smokeping.pm line 13.
BEGIN failed--compilation aborted at /opt/smokeping207/lib/Smokeping.pm line 13.
Compilation failed in require at /usr/local/apache2053/cgi-bin/smokeping.cgi line 8.
BEGIN failed--compilation aborted at /usr/local/apache2053/cgi-bin/smokeping.cgi line 8.
</pre>
<p>
For help, please send mail to this site's webmaster, giving this error message 
and the time and date of the error.

</p>
[Fri Mar  3 09:58:35 2006] smokeping.cgi: Can't load
'/usr/local/rrdtool-1.2.11/lib/perl/5.6.1/sun4-solaris-64int/auto/RRDs/RRDs.so' for module
RRDs: ld.so.1: /usr/perl5/5.6.1/bin/speedy_backend: fatal: relocation error: file
/usr/local/rrdtool-1.2.11/lib/perl/5.6.1/sun4-solaris-64int/auto/RRDs/RRDs.so: symbol
rrd_set_error: referenced symbol not found at
(Continue reading)

hans | 8 Mar 16:09 2006
Picon

better granularity step 300


hi 

i have the following default configuration at smokeping 

*** Database ***
step     = 300
pings    = 20

i want to have a better granularity, because a break 
of a leased line of even 4 minutes couldn't be detect
in the worst case. 

what happens, if i change to
step     = 30
pings    = 10

would rrdtools show correctly ? 
should i delete the existings rrd-files bevor ? 

best regards 
hans 

--

-- 

PAUL WILLIAMSON | 8 Mar 16:43 2006

Re: better granularity step 300

>>> hans <smokeping <at> m05.yer.at> 03/08/06 10:09 AM >>>
>  i want to have a better granularity, because a 
> break of a leased line of even 4 minutes couldn't 
> be detect in the worst case. 
> 
> what happens, if i change to
> step     = 30
> pings    = 10
> 
> would rrdtools show correctly ? 
> should i delete the existings rrd-files bevor ? 

None of the existing RRDs would notice this, 
but anything new would be created with the 
correct step.  So, you could always move the 
existing files out of the way, let smokeping 
create new ones and then put the old RRD 
data into the newly created RRDs.  Just use 
rrdimport.

Paul

Antonín Faltýnek | 8 Mar 16:44 2006
Picon

Re: better granularity step 300

Dne středa 08 březen 2006 16:09 hans napsal(a):
> hi
>
> i have the following default configuration at smokeping
>
> *** Database ***
> step     = 300
> pings    = 20
>
> i want to have a better granularity, because a break
> of a leased line of even 4 minutes couldn't be detect
> in the worst case.
>
> what happens, if i change to
> step     = 30
> pings    = 10
>
> would rrdtools show correctly ?
> should i delete the existings rrd-files bevor ?
>
> best regards
> hans

Hi,

you have to reconfigure whole database definition

*** Database ***
# every 30 seconds send 10 pings (it is quite lot IMHO)
step     = 30
(Continue reading)

cathal.ferris | 10 Mar 13:49 2006
Picon

passing parameters to fping?

Hi.
I have just started trialling smokeping to monitor various customer
satellite connection statistics.
The default timeout of 500msec is causing me headaches though, and I am
getting too many email alerts generated.
I'm getting nice graphs, that make lots of sense, but I am always missing
the first one or two pings, as the rtt can be >800 under perfect
conditions.

I haven't seen in the docs where to pass the parameters to fping,
specifically the -t option.
I need to do a "fping -t 1400"

How can I do this?

Using smokeping 1.38 on debian

Thanks,
Cathal.

hkclark | 11 Mar 03:00 2006
Picon

Re: passing parameters to fping?

On 3/10/06, cathal.ferris <at> mediasat.ie <cathal.ferris <at> mediasat.ie> wrote:
> Hi.
> I have just started trialling smokeping to monitor various customer
> satellite connection statistics.
> The default timeout of 500msec is causing me headaches though, and I am
> getting too many email alerts generated.
> I'm getting nice graphs, that make lots of sense, but I am always missing
> the first one or two pings, as the rtt can be >800 under perfect
> conditions.
>
> I haven't seen in the docs where to pass the parameters to fping,
> specifically the -t option.
> I need to do a "fping -t 1400"
>
> How can I do this?
>
> Using smokeping 1.38 on debian
>
> Thanks,
> Cathal.
>

Hi Cathal,

I ran into this a while back.  My solutions wasn't the most elegant,
but I just modified the FPing.pm file to manually include that "-t"
argument.  Look for FPing.pm in the probes directory (probably make a
backup copy of the file before you change it).  Look for where "my
 <at> cmd" is defined and add the '-t 1400' inside there (line 111 in
SmokePing v2.0.7).
(Continue reading)

cathal.ferris | 12 Mar 02:38 2006
Picon

Re: passing parameters to fping?

Perfect.

I now have the exact behaviour I needed - I now have graphs with green
lines instead of navy or blue...  Looks much prettier, and can be shown
with confidence to the clients.

Appreciated.

Cathal.

> Hi Cathal,
>
> I ran into this a while back.  My solutions wasn't the most elegant,
> but I just modified the FPing.pm file to manually include that "-t"
> argument.  Look for FPing.pm in the probes directory (probably make a
> backup copy of the file before you change it).  Look for where "my
>  <at> cmd" is defined and add the '-t 1400' inside there (line 111 in
> SmokePing v2.0.7).
>
> Regards,
> H
>
> --
> Unsubscribe
> mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=unsubscribe
> Help        mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=help
> Archive     http://lists.ee.ethz.ch/smokeping-users
> WebAdmin    http://lists.ee.ethz.ch/lsg2.cgi
>

(Continue reading)

Peter Klausner | 14 Mar 15:51 2006
Picon

Re: passing parameters to fping?

fping's 500ms default timeout was a problem for me,
so I did exactly the same hack.
Additionally, I wanted to fix it "properly",
but on further research abandoned that:
The solution already exists!

See http://smokeping.paracoda.com/doc/smokeping_upgrade.en.html :
"2.0.4 to 2.0.5
FPing
The 'timeout' variable has been removed. It was used to give the fping
command the -t parameter, but as this parameter is only effective in
fping's default mode, while Smokeping uses the counting mode (-c), it
never actually did anything.

I propose to re-introduce that parameter,
as it
a) seems to work with most installations
b) is actually needed with links of latency > 500ms

Peter Klausner


Gmane