From dano at northpb.com  Wed Aug  1 00:01:46 2012
From: dano at northpb.com (Dan O'Neill)
Date: Tue, 31 Jul 2012 15:01:46 -0700
Subject: [smokeping-users] Smoketrace without Smokeping
In-Reply-To: <88A20A3B-9D81-4904-8889-734EDE8B3F33@oetiker.ch>
References: <50180573.50201@kdr.ms>
	<88A20A3B-9D81-4904-8889-734EDE8B3F33@oetiker.ch>
Message-ID: <CACCnszFgDJWzMQLNrWdxvL22+=PBdyGq-3YKT05eruhJdMx2nA@mail.gmail.com>

Hi Tobi,

I wrote to the list about some problems installing remocular a while back.
Is there a better place than this list to get support?

Thanks,

Dan

On Tue, Jul 31, 2012 at 2:39 PM, Tobi Oetiker <tobi at oetiker.ch> wrote:

>
> On 31.07.2012, at 18:18, Kris De Rocker <kdr at kdr.ms> wrote:
>
> > Dear,
> >
> > Is it possible to install smoketrace without the need to install
> smokeping?
> > I want to install it on a centos 6.2 vps in case that would mather.
> >
> >
>
>
> hi kris
>
> have a look at www.remocular.org
>
> cheers
> tobi
>
>
> > _______________________________________________
> > 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
>



-- 
Dan O'Neill
dano at northpb.com
619-885-1961
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120731/0d541e29/attachment.htm 

From tobi at oetiker.ch  Wed Aug  1 00:26:06 2012
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Wed, 1 Aug 2012 00:26:06 +0200 (CEST)
Subject: [smokeping-users] Smoketrace without Smokeping
In-Reply-To: <CACCnszFgDJWzMQLNrWdxvL22+=PBdyGq-3YKT05eruhJdMx2nA@mail.gmail.com>
References: <50180573.50201@kdr.ms>
	<88A20A3B-9D81-4904-8889-734EDE8B3F33@oetiker.ch>
	<CACCnszFgDJWzMQLNrWdxvL22+=PBdyGq-3YKT05eruhJdMx2nA@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1208010025460.22011@froburg.oetiker.ch>

Yesterday Dan O'Neill wrote:

> Hi Tobi,
>
> I wrote to the list about some problems installing remocular a while back.
> Is there a better place than this list to get support?

write to me ... there is no 'community' yet

cheers
tobi

>
> Thanks,
>
> Dan
>
> On Tue, Jul 31, 2012 at 2:39 PM, Tobi Oetiker <tobi at oetiker.ch> wrote:
>
> >
> > On 31.07.2012, at 18:18, Kris De Rocker <kdr at kdr.ms> wrote:
> >
> > > Dear,
> > >
> > > Is it possible to install smoketrace without the need to install
> > smokeping?
> > > I want to install it on a centos 6.2 vps in case that would mather.
> > >
> > >
> >
> >
> > hi kris
> >
> > have a look at www.remocular.org
> >
> > cheers
> > tobi
> >
> >
> > > _______________________________________________
> > > 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
> >
>
>
>
>

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900


From lanadmin at powerline.com.br  Wed Aug  1 20:23:15 2012
From: lanadmin at powerline.com.br (Marcos Teixeira)
Date: Wed, 01 Aug 2012 15:23:15 -0300
Subject: [smokeping-users] Blank .
Message-ID: <50197413.30505@powerline.com.br>

Chart with blanks.
Hello all.
I have noticed that all my graphics monitoring, are in some blanks. See 
below:
Someone has been there?
I'm using a server with Ubuntu 12.04 64bit



http://www.powerline.com.br/~marcos/smokeping-error.jpg 
<http://www.powerline.com.br/%7Emarcos/smokeping-error.jpg>

-- 
--------------------------------------------------
Marcos Teixeira Pereira
LanAdmin Powerline   -   Powerline Internet  -  (32) 2102-1021
lanadmin at powerline.com.br
www.powerline.com.br


From rb14060 at gmail.com  Wed Aug  1 20:30:11 2012
From: rb14060 at gmail.com (Ryan Becker)
Date: Wed, 1 Aug 2012 14:30:11 -0400
Subject: [smokeping-users] Blank .
In-Reply-To: <50197413.30505@powerline.com.br>
References: <50197413.30505@powerline.com.br>
Message-ID: <CAAjykha+uJz_rRTF725tOS1EWFkHq0tY1omhvB8kv-SiZAEpAA@mail.gmail.com>

>From what I've seen, that means total packet loss.

On Wed, Aug 1, 2012 at 2:23 PM, Marcos Teixeira
<lanadmin at powerline.com.br>wrote:

> Chart with blanks.
> Hello all.
> I have noticed that all my graphics monitoring, are in some blanks. See
> below:
> Someone has been there?
> I'm using a server with Ubuntu 12.04 64bit
>
>
>
> http://www.powerline.com.br/~marcos/smokeping-error.jpg
> <http://www.powerline.com.br/%7Emarcos/smokeping-error.jpg>
>
> --
> --------------------------------------------------
> Marcos Teixeira Pereira
> LanAdmin Powerline   -   Powerline Internet  -  (32) 2102-1021
> lanadmin at powerline.com.br
> www.powerline.com.br
>
> _______________________________________________
> 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/20120801/c52b5f35/attachment-0001.htm 

From dgarrett at acm.org  Sun Aug  5 20:28:49 2012
From: dgarrett at acm.org (Don Garrett)
Date: Sun, 5 Aug 2012 11:28:49 -0700
Subject: [smokeping-users] Using Smokeping to measure uptime in minutes
Message-ID: <CA+hrqxjgbHPWs6QXDUAqVF2CGwzT0QuejbVJv0igzGjqwBP4ag@mail.gmail.com>

I have a network with a number of devices that are frequently turned on or
off based on usage (picture lab computers, a television with ethernet,
etc). And I'd like to measure how much time they spend turned on. I'm
already monitoring network performance using smokeping, and pinging the
devices will give enough data so it seemed a natural fit.

I'm having a hard enough time figuring this out that I was considering
building my own tool. I thought I'd ask here if it's reasonable to try to
adapt smokeping for this usage or how to go about it.


What I want:
  Assume if that if a single ping response during a probe, then the device
is up for 5 minutes, otherwise it's down for 5 minutes.

  Store minutes up per hour for the last week;  Viewable for day, week
  Store minutes up per day (with exact day boundaries at midnight) for the
last year; Viewable for last month, year.

I also intend to extract some of this data to embed current on/off values
in a different web page and to help publish weekly usage reports. Below is
a bash CGI test script to pull On/Off values directly out of rrdtool. I'll
want to do something similar for the weekly reports.


#!/bin/bash

RRDTOOL=/usr/bin/rrdtool
TAIL=/usr/bin/tail
CUT=/usr/bin/cut

# This pulls out the number of timeout pings in the last attempt
# to ping the TV. We normally see 0 failures when it's on. Could
# also test for 20 failures to show it's off.
fail_count=`${RRDTOOL} lastupdate /var/lib/smokeping/Local/TV.rrd | \
              ${TAIL} -n 1 | \
              ${CUT} -f 3 -d ' '`

result=0

[ "${fail_count}" == "0" ] && result=1

echo Content-type: text/plain
echo ""
echo "${result}"

-- 
Don
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120805/43e5a2c3/attachment.htm 

From liste at karp.fr  Mon Aug  6 15:23:58 2012
From: liste at karp.fr (Nicolas KARP)
Date: Mon, 6 Aug 2012 15:23:58 +0200
Subject: [smokeping-users] After a lot of alerts,
	smokeping do not update the rrd anymore
Message-ID: <CAELGAXcQdopLuD67EkaCB+qbW=m+pOn68VmGbyg3Lk=eDx+udg@mail.gmail.com>

Hi Guys,

I ran several smokeping for several months now and all was fine until we
had an issue with our ISP... Following these issues, smokeping sent a lot
of alarms which is what we wanted :-) But after that, smokeping stopped to
update the RRD file and the graphs were not updated.

Do you know what could cause this problem with smokeping ?  Too much
unresponsive devices ?

Thanks for your help.

Nicolas KARP
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120806/d7c81ee2/attachment.htm 

From Jon.Bendtsen at laerdal.dk  Mon Aug  6 15:28:05 2012
From: Jon.Bendtsen at laerdal.dk (Bendtsen, Jon)
Date: Mon, 6 Aug 2012 13:28:05 +0000
Subject: [smokeping-users] After a lot of alerts,
 smokeping do not update the rrd anymore
In-Reply-To: <CAELGAXcQdopLuD67EkaCB+qbW=m+pOn68VmGbyg3Lk=eDx+udg@mail.gmail.com>
References: <CAELGAXcQdopLuD67EkaCB+qbW=m+pOn68VmGbyg3Lk=eDx+udg@mail.gmail.com>
Message-ID: <5DA1D2E8-A117-4445-B331-9BAABCC18A7C@laerdal.dk>

On 06/08/2012, at 15.23, Nicolas KARP wrote:
> Hi Guys,
> 
> I ran several smokeping for several months now and all was fine until we had an issue with our ISP... Following these issues, smokeping sent a lot of alarms which is what we wanted :-) But after that, smokeping stopped to update the RRD file and the graphs were not updated. 

Did you or the ISP get a new IP address?

Did the ISP change their setup to disallow you to measure their performance? such that the server/router you measured against does not reply to you?




JonB



From liste at karp.fr  Mon Aug  6 15:54:12 2012
From: liste at karp.fr (Nicolas KARP)
Date: Mon, 6 Aug 2012 15:54:12 +0200
Subject: [smokeping-users] After a lot of alerts,
 smokeping do not update the rrd anymore
In-Reply-To: <5DA1D2E8-A117-4445-B331-9BAABCC18A7C@laerdal.dk>
References: <CAELGAXcQdopLuD67EkaCB+qbW=m+pOn68VmGbyg3Lk=eDx+udg@mail.gmail.com>
	<5DA1D2E8-A117-4445-B331-9BAABCC18A7C@laerdal.dk>
Message-ID: <CAELGAXd75Uk4zWW0DQhSJaP=EbnyiWYmSju80nQuCf7hdG0WAg@mail.gmail.com>

Jon,

No it's not the problem. All the IPs we are using as Targets still respond
to ping and after a reload of the smokeping, the RRDs were updated
correclty after the reload.
Without a reload of the process, the smokeping is like **frozen** for all
our targets even if they respond to ping.

An idea ?

Nicolas KARP


2012/8/6 Bendtsen, Jon <Jon.Bendtsen at laerdal.dk>

> On 06/08/2012, at 15.23, Nicolas KARP wrote:
> > Hi Guys,
> >
> > I ran several smokeping for several months now and all was fine until we
> had an issue with our ISP... Following these issues, smokeping sent a lot
> of alarms which is what we wanted :-) But after that, smokeping stopped to
> update the RRD file and the graphs were not updated.
>
> Did you or the ISP get a new IP address?
>
> Did the ISP change their setup to disallow you to measure their
> performance? such that the server/router you measured against does not
> reply to you?
>
>
>
>
> JonB
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120806/df344725/attachment.htm 

From ged at jubileegroup.co.uk  Mon Aug  6 16:59:03 2012
From: ged at jubileegroup.co.uk (G.W. Haywood)
Date: Mon, 6 Aug 2012 15:59:03 +0100 (BST)
Subject: [smokeping-users] After a lot of alerts,
 smokeping do not update the rrd anymore
In-Reply-To: <CAELGAXcQdopLuD67EkaCB+qbW=m+pOn68VmGbyg3Lk=eDx+udg@mail.gmail.com>
References: <CAELGAXcQdopLuD67EkaCB+qbW=m+pOn68VmGbyg3Lk=eDx+udg@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1208061426490.9866@mail5.jubileegroup.co.uk>

B11;rgb:ffff/ffff/ffffHi there,

On Mon, 6 Aug 2012, Nicolas KARP wrote:

> I ran several smokeping for several months now and all was fine until we
> had an issue with our ISP... Following these issues, smokeping sent a lot
> of alarms which is what we wanted :-) But after that, smokeping stopped to
> update the RRD file and the graphs were not updated.
>
> Do you know what could cause this problem with smokeping ?  Too much
> unresponsive devices ?

Are you by any chance using logarithmic graphs?

I've seem Smokeping fail to update graphs (and the smokeping processes
hanging using 100% CPU) when using logarithmic graphs.  I have a patch
which has been in testing for a week but seems stable enough to release.

The problem I had was that sometimes when you use logarithmic graphs the
minimum for the vertical scale is greater than the maximum, and this
causes something in RRD to get confused.

My fix is to make sure that the minimum is less than the maximum, but it
seems to me that a fix is also needed in RRD for the problem behaviour.

In Smokeping.pm:
----------------------------------------------------------------------
   '--title',$desc.$from,
   '--rigid',
! '--upper-limit', ($max->{$s}{$start} > 0.01 ? $max->{$s}{$start} : '0.01'),
   @log,
   '--lower-limit',(@log ? ($max->{$s}{$start} > 0.01) ? '0.001' : '0.0001' : '0'),
--- 1371,1377 ----
   '--title',$desc.$from,
   '--rigid',
! '--upper-limit', $max->{$s}{$start},
   @log,
   '--lower-limit',(@log ? ($max->{$s}{$start} > 0.01) ? '0.001' : '0.0001' : '0'),
----------------------------------------------------------------------

Apologies for any line wrapping.

--

73,
Ged.


From liste at karp.fr  Mon Aug  6 17:08:56 2012
From: liste at karp.fr (Nicolas KARP)
Date: Mon, 6 Aug 2012 17:08:56 +0200
Subject: [smokeping-users] Smokeping alarming and pattern
Message-ID: <CAELGAXc5K1KvDNUOBjMdAjapC8-SLCo=hU_GgEk=HuDC45bCHw@mail.gmail.com>

Hi Guys,

I configured some months ago my alarm patterns and my own script which is
working fine.

I just wanted to know if the following example is the normal behaviour :


+packetloss_warning
type = loss
# in percent
pattern = <100%,<100%,>20%,>20%
comment = packetloss_warning (>20% for 10 minutes)
priority=30

+packetloss_critical
type = loss
# in percent
pattern = <100%,<100%,>60%,>60%
comment = packetloss_critical (>60% for 10 minutes)
priority=20

+packetloss_ok
type = loss
# in percent
pattern = >20%,>20%,==0%,==0%,==0%
comment = No packet Loss : OK
priority=10



And I don't understand why an alarm occured when this pattern happens :

packetloss_warning : i'm ok with that
    LOSS=loss: 5%, 0%, 0%, 65%, 60%
    RTT=rtt: 20ms, 20ms, 20ms, 20ms, 20ms

packetloss_critical is triggered : why ?
    LOSS=loss: 65%, 60%, 85%, 75%, 0%
    RTT=rtt: 20ms, 20ms, 20ms, 20ms, 11ms

packetloss_ok is triggered : i'm ok with that
    LOSS=loss: 85%, 75%, 0%, 0%, 0%
    RTT=rtt: 20ms, 20ms, 11ms, 3ms, 3ms

packetloss_ok is triggered : why ?
    LOSS=loss: 75%, 0%, 0%, 0%, 0%
    RTT=rtt: 20ms, 11ms, 3ms, 3ms, 3ms



Thanks for your help on this case !

Best Regards,

Nicolas KARP
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120806/bd0c08eb/attachment-0001.htm 

From liste at karp.fr  Thu Aug  9 13:44:43 2012
From: liste at karp.fr (Nicolas KARP)
Date: Thu, 9 Aug 2012 13:44:43 +0200
Subject: [smokeping-users] After a lot of alerts,
 smokeping do not update the rrd anymore
In-Reply-To: <Pine.LNX.4.64.1208061426490.9866@mail5.jubileegroup.co.uk>
References: <CAELGAXcQdopLuD67EkaCB+qbW=m+pOn68VmGbyg3Lk=eDx+udg@mail.gmail.com>
	<Pine.LNX.4.64.1208061426490.9866@mail5.jubileegroup.co.uk>
Message-ID: <CAELGAXfPCkEtAiDLMWC+kQuCgxhUnMzqDNQNfYkCbEpBMg0TiA@mail.gmail.com>

I think it's more related to the time spent by smokeping to do his Job.
When my ISP failed, a lot of Targets were unresponsive..

 FPing: WARNING: smokeping took 493 seconds to complete 1 round of polling.
It should complete polling in 300 seconds..
 You may have unresponsive devices in your setup.

Is it possible ?   I just see one line for this alarm in my smokeping logs
but on my graphs, i see a blank for 1 or 2 hours...
So far, I have 94 targets which are using the Fping probes. Do I need to
reduce the offset ?

Best Regards,

Nicolas.

2012/8/6 G.W. Haywood <ged at jubileegroup.co.uk>

> B11;rgb:ffff/ffff/ffffHi there,
>
>
> On Mon, 6 Aug 2012, Nicolas KARP wrote:
>
>  I ran several smokeping for several months now and all was fine until we
>> had an issue with our ISP... Following these issues, smokeping sent a lot
>> of alarms which is what we wanted :-) But after that, smokeping stopped to
>> update the RRD file and the graphs were not updated.
>>
>> Do you know what could cause this problem with smokeping ?  Too much
>> unresponsive devices ?
>>
>
> Are you by any chance using logarithmic graphs?
>
> I've seem Smokeping fail to update graphs (and the smokeping processes
> hanging using 100% CPU) when using logarithmic graphs.  I have a patch
> which has been in testing for a week but seems stable enough to release.
>
> The problem I had was that sometimes when you use logarithmic graphs the
> minimum for the vertical scale is greater than the maximum, and this
> causes something in RRD to get confused.
>
> My fix is to make sure that the minimum is less than the maximum, but it
> seems to me that a fix is also needed in RRD for the problem behaviour.
>
> In Smokeping.pm:
> ------------------------------**------------------------------**----------
>   '--title',$desc.$from,
>   '--rigid',
> ! '--upper-limit', ($max->{$s}{$start} > 0.01 ? $max->{$s}{$start} :
> '0.01'),
>   @log,
>   '--lower-limit',(@log ? ($max->{$s}{$start} > 0.01) ? '0.001' : '0.0001'
> : '0'),
> --- 1371,1377 ----
>   '--title',$desc.$from,
>   '--rigid',
> ! '--upper-limit', $max->{$s}{$start},
>   @log,
>   '--lower-limit',(@log ? ($max->{$s}{$start} > 0.01) ? '0.001' : '0.0001'
> : '0'),
> ------------------------------**------------------------------**----------
>
> Apologies for any line wrapping.
>
> --
>
> 73,
> Ged.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120809/f205eaf5/attachment.htm 

From samy.nashaat at orange.com  Tue Aug 14 15:46:56 2012
From: samy.nashaat at orange.com (samy.nashaat at orange.com)
Date: Tue, 14 Aug 2012 15:46:56 +0200
Subject: [smokeping-users] Smokeping Help | Master Slave config
In-Reply-To: <CAJYt4JutTiKu-DW5YOARwvp+CzLGo54hcbMwdsU0MCV0AvpOpg@mail.gmail.com>
References: <30301_1342436221_5003F37D_30301_3794_1_6F4FECEA3919634CA6E08F8E88083821E71B3C@PUEXCBJ0.nanterre.francetelecom.fr><CAJYt4Jv-pfxHeTKPTaZ=EqJ6Q567VxZo5SxyWCowzgTG=t87sg@mail.gmail.com><22077_1343636405_501643B5_22077_11939_1_6F4FECEA3919634CA6E08F8E88083821F89387@PUEXCBJ0.nanterre.francetelecom.fr><3029_1343636473_501643F9_3029_845_1_6F4FECEA3919634CA6E08F8E88083821F8938A@PUEXCBJ0.nanterre.francetelecom.fr>
	<CAJYt4JutTiKu-DW5YOARwvp+CzLGo54hcbMwdsU0MCV0AvpOpg@mail.gmail.com>
Message-ID: <19941_1344952035_502A56E3_19941_11540_1_6F4FECEA3919634CA6E08F8E88083821010DACFB@PUEXCBJ0.nanterre.francetelecom.fr>

Hello Darren,

 

I'm very thankful for your support however I still have problems.

 

Please help me.

 

On the MASTER: the rrd files of the slave are not updated.

smoke at XXXXXinvk0093:/var/lib/smokeping/LLor_Core$ ls -l

total 15300

-rw-r--r-- 1 root     root 1039576 Jul 10 15:47 CORE_LL_G10_XXXXXLLvk0306b~XXXXXLLvk0099.rrd

-rwxrwxrwx 1 www-data sudo 1039576 Jul 10 15:11 CORE_LL_G10_XXXXXLLvk0306b~XXXXXLLvk0142.rrd

-rw-r--r-- 1 root     root 1039576 Aug 14 16:24 CORE_LL_G10_XXXXXLLvk0306b.rrd

-rw-r--r-- 1 root     root 1039576 Jul 10 15:47 CORE_LL_G1_2_XXXXXLLvk0309~XXXXXLLvk0099.rrd

-rwxrwxrwx 1 root     root 1039576 Jul 10 15:11 CORE_LL_G1_2_XXXXXLLvk0309~XXXXXLLvk0142.rrd

-rw-r--r-- 1 root     root 1039576 Aug 14 16:24 CORE_LL_G1_2_XXXXXLLvk0309.rrd

-rw-r--r-- 1 root     root 1039576 Jul 10 15:47 CORE_LL_G1_XXXXXLLvk0300~XXXXXLLvk0099.rrd

-rw-r--r-- 1 root     root 1039576 Jul 10 15:11 CORE_LL_G1_XXXXXLLvk0300~XXXXXLLvk0142.rrd

-rw-r--r-- 1 root     root 1039576 Aug 14 16:24 CORE_LL_G1_XXXXXLLvk0300.rrd

-rw-r--r-- 1 root     root 1039576 Jul 10 15:47 CORE_LL_G9_RZ_XXXXXLLvk0302a~XXXXXLLvk0099.rrd

-rw-r--r-- 1 root     root 1039576 Jul 10 15:11 CORE_LL_G9_RZ_XXXXXLLvk0302a~XXXXXLLvk0142.rrd

-rw-r--r-- 1 root     root 1039576 Aug 14 16:24 CORE_LL_G9_RZ_XXXXXLLvk0302a.rrd

-rw-r--r-- 1 root     root 1039576 Jul 10 15:47 CORE_LL_G9_TK_XXXXXLLvk0201x~XXXXXLLvk0099.rrd

-rw-r--r-- 1 root     root 1039576 Jul 10 15:11 CORE_LL_G9_TK_XXXXXLLvk0201x~XXXXXLLvk0142.rrd

-rw-r--r-- 1 root     root 1039576 Aug 14 16:24 CORE_LL_G9_TK_XXXXXLLvk0201x.rrd

smoke at XXXXXLLvk0093:/var/lib/smokepLLg/LLor_Core$

no errors are shown in the debug LLither the log

smoke at XXXXXLLvk0093:/var/lib/smokepLLg/LLor_Core$ cat /tmp/smokelog

Tue Aug 14 15:39:30 2012 - Smokeping version  successfully launched.

Tue Aug 14 15:39:30 2012 - Not entering multiprocess mode for just a single probe.

Tue Aug 14 15:39:30 2012 - FPing: probing 41 targets with step 300 s and offset 238 s.

 

smoke at XXXXXinvk0093:/var/lib/smokeping/LLor_Core$ sudo smokeping --debug

[sudo] password for smoke:

### Compiling alert detector pattern 'someloss'

### >0%,*12*,>0%,*12*,>0%

sub {

    my $d = shift;

    my $y = $d->{loss};

    for(1){

        my $imax2 = min(@$y - 3, 12);

        my $imax1 = min(@$y - 3, 12);

        my $minlength = 3;

        my $maxlength = 27;

        LLxt if scalar @$y < $minlength ;

        my $i1;

        for($i1=0; $i1 < min($maxlength,$imax1); $i1++){

            my $i2;

            for($i2=0; $i2 < min($maxlength-$i1,$imax2); $i2++){

                LLxt unless defiLLd $y->[-3-$i1-$i2]

                                and $y->[-3-$i1-$i2] =~ /^\d/

                                and $y->[-3-$i1-$i2] > 0

                                     ;                last;

            }

            return 0 if $i2 >= min($maxlength-$i1-$i2,$imax2);

            LLxt unless defiLLd $y->[-2-$i1]

                            and $y->[-2-$i1] =~ /^\d/

                            and $y->[-2-$i1] > 0

                                 ;            last;

        }

        return 0 if $i1 >= min($maxlength-$i1,$imax1);

        LLxt unless defiLLd $y->[-1]

                        and $y->[-1] =~ /^\d/

                        and $y->[-1] > 0

                             ;        return 1;

    }

    return 0;

}

 

 

 

Smokeping version  successfully launched.

Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for that.

FPing: probing 41 targets with step 300 s and offset 24 s.

FPing: Executing /usr/bin/fping -C 6 -q -B1 -r1 -b40 -i10 -p1000 10.197.63.84 10.247.0.86 10.197.63.114 10.247.244.23 10.247.2.124 10.247.239.6 10.215.0.137 10.247.255.250 10.247.250.250 10.247.1.158 10.197.63.36 10.247.251.253 10.247.244.13 10.247.1.22 10.247.168.123 10.247.1.254 10.247.0.64 10.215.0.30 10.247.1.189 10.247.246.6 10.197.63.9 localhost 10.247.252.250 10.215.0.92 10.247.249.250 10.197.63.150 10.197.63.132 10.197.63.72 10.247.1.123 10.247.2.30 10.247.251.122 10.247.249.122 10.247.242.254 10.215.0.76 10.247.1.94 10.247.2.91 10.215.0.108 10.247.253.250 10.247.1.222 10.247.247.251 10.247.254.251

FPing: Got fping output: 'ICMP Time Exceeded from 10.251.160.2 for ICMP Echo sent to 10.247.251.122'

FPing: Got fping output: 'ICMP Host Unreachable from 192.168.50.26 for ICMP Echo sent to 10.215.0.76'

FPing: Got fping output: 'ICMP Time Exceeded from 10.251.160.2 for ICMP Echo sent to 10.247.251.122'

FPing: Got fping output: 'ICMP Time Exceeded from 10.251.160.2 for ICMP Echo sent to 10.247.251.122'

FPing: Got fping output: 'ICMP Time Exceeded from 10.251.160.2 for ICMP Echo sent to 10.247.251.122'

FPing: Got fping output: 'ICMP Host Unreachable from 192.168.50.26 for ICMP Echo sent to 10.215.0.76'

FPing: Got fping output: 'ICMP Time Exceeded from 10.251.160.2 for ICMP Echo sent to 10.247.251.122'

FPing: Got fping output: 'ICMP Time Exceeded from 10.251.160.2 for ICMP Echo sent to 10.247.251.122'

FPing: Got fping output: '10.197.63.84   : 7.40 7.42 7.44 7.36 7.44 7.33'

FPing: Got fping output: '10.247.0.86    : 1.95 0.21 0.22 0.26 0.22 0.21'

FPing: Got fping output: '10.197.63.114  : 7.30 7.35 7.84 7.47 7.53 7.48'

FPing: Got fping output: '10.247.244.23  : - - - - - -'

FPing: Got fping output: '10.247.2.124   : 0.76 0.74 0.75 0.76 0.78 0.76'

FPing: Got fping output: '10.247.239.6   : 1.81 1.81 18.37 1.84 1.81 1.81'

FPing: Got fping output: '10.215.0.137   : 38.37 38.13 37.74 37.71 37.88 38.27'

FPing: Got fping output: '10.247.255.250 : 1.87 1.86 1.86 1.93 1.87 1.85'

FPing: Got fping output: '10.247.250.250 : 1.81 1.92 1.96 1.91 1.90 1.96'

FPing: Got fping output: '10.247.1.158   : 0.77 0.74 0.73 0.78 0.73 0.77'

FPing: Got fping output: '10.197.63.36   : 7.49 7.39 7.41 7.42 7.54 7.41'

FPing: Got fping output: '10.247.251.253 : - - - - - -'

FPing: Got fping output: '10.247.244.13  : - - - - - -'

FPing: Got fping output: '10.247.1.22    : 0.41 0.36 0.36 0.37 0.35 0.37'

FPing: Got fping output: '10.247.168.123 : 1.76 1.79 1.81 1.80 1.81 1.84'

FPing: Got fping output: '10.247.1.254   : 0.75 0.74 0.75 0.73 0.73 0.75'

FPing: Got fping output: '10.247.0.64    : 0.24 0.23 0.23 0.22 0.24 0.23'

FPing: Got fping output: '10.215.0.30    : 38.81 37.75 37.91 37.74 37.97 37.66'

FPing: Got fping output: '10.247.1.189   : 0.46 0.41 0.43 0.31 0.65 0.42'

FPing: Got fping output: '10.247.246.6   : 1.30 1.21 1.19 1.18 1.19 1.22'

FPing: Got fping output: '10.197.63.9    : 6.86 7.03 6.91 7.02 7.03 6.89'

FPing: Got fping output: 'localhost      : 0.02 0.02 0.02 0.01 0.02 0.01'

FPing: Got fping output: '10.247.252.250 : 1.74 1.70 1.97 23.96 1.90 1.79'

FPing: Got fping output: '10.215.0.92    : 38.76 38.33 38.30 38.21 38.72 38.21'

FPing: Got fping output: '10.247.249.250 : 1.66 1.78 5.33 5.58 1.54 1.61'

FPing: Got fping output: '10.197.63.150  : 7.05 7.20 7.08 7.18 7.21 7.10'

FPing: Got fping output: '10.197.63.132  : 14.95 15.27 14.85 15.17 19.62 14.95'

FPing: Got fping output: '10.197.63.72   : 7.54 7.65 7.42 7.41 7.42 7.51'

FPing: Got fping output: '10.247.1.123   : 0.72 0.77 0.75 0.77 0.71 0.70'

FPing: Got fping output: '10.247.2.30    : 1.14 0.60 0.60 0.66 0.60 0.60'

FPing: Got fping output: '10.247.251.122 : - - - - - -'

FPing: Got fping output: '10.247.249.122 : - - - - - -'

FPing: Got fping output: '10.247.242.254 : 1.06 0.99 1.00 0.99 0.98 0.96'

FPing: Got fping output: '10.215.0.76    : - - - - - -'

FPing: Got fping output: '10.247.1.94    : 32.03 0.77 0.74 0.75 0.79 0.73'

FPing: Got fping output: '10.247.2.91    : 0.74 0.74 0.71 0.77 0.75 0.73'

FPing: Got fping output: '10.215.0.108   : 44.25 44.10 44.14 44.17 45.35 44.91'

FPing: Got fping output: '10.247.253.250 : 1.86 1.86 1.78 1.83 1.85 1.83'

FPing: Got fping output: '10.247.1.222   : 0.60 0.60 0.58 0.60 0.60 0.58'

FPing: Got fping output: '10.247.247.251 : 2.13 1.92 1.91 1.87 3.94 1.87'

FPing: Got fping output: '10.247.254.251 : 1.95 1.92 1.94 1.88 1.97 1.87'

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_GVZ_XXXXXinvk0211.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:7.6000000000e-04:7.4000000000e-04:7.5000000000e-04:7.6000000000e-04:7.6000000000e-04:7.8000000000e-04)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Hoch_Str_1d_2OGI_EB11_XXXXXinvk0098.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:1.1900000000e-03:1.1800000000e-03:1.1900000000e-03:1.1900000000e-03:1.2100000000e-03:1.2200000000e-03)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Theo_Heuss_XXXXXinvk0136c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:1.7800000000e-03:1.5400000000e-03:1.6100000000e-03:1.7800000000e-03:5.3300000000e-03:5.5800000000e-03)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_SE_Mar_Cur_XXXXXinvk0132c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:1.9200000000e-03:1.8700000000e-03:1.8800000000e-03:1.9200000000e-03:1.9400000000e-03:1.9700000000e-03)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Fried_str_XXXXXinvk0108c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:1.8600000000e-03:1.8500000000e-03:1.8600000000e-03:1.8600000000e-03:1.8700000000e-03:1.9300000000e-03)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Akad_Schluet_Str_XXXXXinvk0201.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:5:U:U:U:U:U:U)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_A58_XXXXXinvk0208.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:7.4000000000e-04:7.3000000000e-04:7.3000000000e-04:7.4000000000e-04:7.7000000000e-04:7.8000000000e-04)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_GebA50_H117_XXXXXinvk0330.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:3.6000000000e-04:3.5000000000e-04:3.6000000000e-04:3.6000000000e-04:3.7000000000e-04:3.7000000000e-04)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Sachs_Str_16_18_XXXXXinvk0147c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:1.8300000000e-03:1.7800000000e-03:1.8300000000e-03:1.8300000000e-03:1.8500000000e-03:1.8600000000e-03)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_T22_XXXXXinvk0200.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:7.5000000000e-04:7.0000000000e-04:7.1000000000e-04:7.5000000000e-04:7.7000000000e-04:7.7000000000e-04)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_T20_XXXXXinvk0215.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:6.0000000000e-04:5.8000000000e-04:5.8000000000e-04:6.0000000000e-04:6.0000000000e-04:6.0000000000e-04)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_A51_XXXXXinvk0216.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:7.4000000000e-04:7.3000000000e-04:7.3000000000e-04:7.4000000000e-04:7.5000000000e-04:7.5000000000e-04)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Hoch_Str_1d_3OGI_EK2P_XXXXXinvk0096.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:5:U:U:U:U:U:U)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_T01_XXXXXinvk0223.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:6.0000000000e-04:6.0000000000e-04:6.0000000000e-04:6.0000000000e-04:6.0000000000e-04:6.6000000000e-04)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_A50_N113_XXXXXinvk0207.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:7.5000000000e-04:7.3000000000e-04:7.4000000000e-04:7.5000000000e-04:7.7000000000e-04:7.9000000000e-04)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Sachs_Str_11_XXXXXinvk0149c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:5:U:U:U:U:U:U)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Sachs_Str_14_Gaim_XXXXXinvk0151c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:1.9000000000e-03:1.7000000000e-03:1.7900000000e-03:1.9000000000e-03:1.9700000000e-03:2.3960000000e-02)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_ARG_XXXXXinvk0110c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:1.8100000000e-03:1.8100000000e-03:1.8100000000e-03:1.8100000000e-03:1.8400000000e-03:1.8370000000e-02)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_DR_L_K_XXXXXinvk0112c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:1.9100000000e-03:1.8700000000e-03:1.8700000000e-03:1.9100000000e-03:1.9200000000e-03:3.9400000000e-03)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Test_LLust_XXXXXinvk0134c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:1.9200000000e-03:1.9000000000e-03:1.9100000000e-03:1.9200000000e-03:1.9600000000e-03:1.9600000000e-03)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_S29_XXXXXinvk0302.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:4.2000000000e-04:3.1000000000e-04:4.1000000000e-04:4.2000000000e-04:4.3000000000e-04:6.5000000000e-04)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Staud_Ha_XXXXXinvk0128c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:1.8100000000e-03:1.7900000000e-03:1.8000000000e-03:1.8100000000e-03:1.8100000000e-03:1.8400000000e-03)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_N30_XXXXXinvk0217.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:7.4000000000e-04:7.1000000000e-04:7.3000000000e-04:7.4000000000e-04:7.5000000000e-04:7.7000000000e-04)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Akad_Egerl_Str_XXXXXiinvk0101c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:5:U:U:U:U:U:U)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_RZ_IN1_Geb_A57_XXXXXinvk0305c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:2.2000000000e-04:2.1000000000e-04:2.1000000000e-04:2.2000000000e-04:2.2000000000e-04:2.6000000000e-04)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_RZ_IN2_Geb_N10_XXXXXinvk0326c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:2.3000000000e-04:2.2000000000e-04:2.3000000000e-04:2.3000000000e-04:2.3000000000e-04:2.4000000000e-04)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Dies_Str_22_Gaim_XXXXXinvk0218.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:9.9000000000e-04:9.6000000000e-04:9.8000000000e-04:9.9000000000e-04:9.9000000000e-04:1.0000000000e-03)

Calling RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Hindenb_Str_XXXXXinvk0153c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:5:U:U:U:U:U:U)

Calling RRDs::update(/var/lib/smokeping/LLor_Core/CORE_LL_G9_RZ_XXXXXLLvk0302a.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:3.7750000000e-02:3.7660000000e-02:3.7740000000e-02:3.7750000000e-02:3.7910000000e-02:3.7970000000e-02)

Calling RRDs::update(/var/lib/smokeping/LLor_Core/CORE_LL_G9_TK_XXXXXLLvk0201x.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:4.4170000000e-02:4.4100000000e-02:4.4140000000e-02:4.4170000000e-02:4.4910000000e-02:4.5350000000e-02)

Calling RRDs::update(/var/lib/smokeping/LLor_Core/CORE_LL_G10_XXXXXLLvk0306b.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:3.7880000000e-02:3.7710000000e-02:3.7740000000e-02:3.7880000000e-02:3.8130000000e-02:3.8270000000e-02)

Calling RRDs::update(/var/lib/smokeping/LLor_Core/CORE_LL_G1_2_XXXXXLLvk0309.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:3.8300000000e-02:3.8210000000e-02:3.8210000000e-02:3.8300000000e-02:3.8330000000e-02:3.8720000000e-02)

Calling RRDs::update(/var/lib/smokeping/LLor_Core/CORE_LL_G1_XXXXXLLvk0300.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:5:U:U:U:U:U:U)

Calling RRDs::update(/var/lib/smokeping/Local/LocalMachiLL.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:2.0000000000e-05:1.0000000000e-05:1.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05)

Calling RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_Geb_B09_XXXXXLLvk0310c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:7.1800000000e-03:7.0800000000e-03:7.1000000000e-03:7.1800000000e-03:7.2000000000e-03:7.2100000000e-03)

Calling RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_Geb_A17_XXXXXLLvk0301a.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:7.0200000000e-03:6.8900000000e-03:6.9100000000e-03:7.0200000000e-03:7.0300000000e-03:7.0300000000e-03)

Calling RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_Geb_B18_XXXXXLLvk0220.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:7.4200000000e-03:7.3300000000e-03:7.3600000000e-03:7.4200000000e-03:7.4400000000e-03:7.4400000000e-03)

Calling RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_GIF_XXXXXLLvk0250.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:7.4800000000e-03:7.3500000000e-03:7.4700000000e-03:7.4800000000e-03:7.5300000000e-03:7.8400000000e-03)

Calling RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_Geb_B05_XXXXXLLvk0230.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:7.4100000000e-03:7.3900000000e-03:7.4100000000e-03:7.4100000000e-03:7.4200000000e-03:7.5400000000e-03)

Calling RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_Geb_B12_XXXXXLLvk0210.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:7.4200000000e-03:7.4100000000e-03:7.4200000000e-03:7.4200000000e-03:7.5100000000e-03:7.6500000000e-03)

Calling RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_Talh_XXXXXLLvk0171c.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5 1344954701:U:0:1.5170000000e-02:1.4850000000e-02:1.4950000000e-02:1.5170000000e-02:1.5270000000e-02:1.9620000000e-02)

 

Although the SLAVE says all is ok, in the debug and the log

 

smoke at XXXXXLLvk0142:/usr/sbin$ sudo ./smokeping --master-url=http://10.247.0.51/smokeping/smokeping.cgi              --cache-dir=/var/lib/smokeping              --shared-secret=/var/smokeping/secret.txt --debug --logfile=/tmp/smokelog

Sent data to Server and got LLw config in response

 

LOG FILE:

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.1.189   : 7.20 7.10 6.97 7.01 7.19 7.20'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: 'localhost      : 0.01 0.01 0.01 0.01 0.01 0.01'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.2.30    : 7.37 7.63 7.52 7.37 7.51 7.53'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.197.63.84   : 0.64 0.63 0.61 0.62 0.61 0.60'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.1.123   : 7.49 7.40 7.59 7.62 7.51 26.11'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.1.254   : 7.26 7.22 7.27 7.23 7.23 7.31'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.242.254 : 7.73 7.61 7.49 7.47 7.53 7.43'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.197.63.9    : 0.10 0.09 0.09 0.09 0.10 0.09'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.255.250 : 8.20 10.01 8.13 8.12 8.76 8.10'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.249.250 : 7.96 7.79 7.92 7.72 7.85 7.99'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.250.250 : 8.41 8.20 8.29 8.34 8.16 8.40'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.197.63.114  : 0.61 0.65 0.64 0.62 0.64 0.63'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.1.158   : 7.32 7.49 7.28 7.25 7.26 7.21'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.1.94    : 7.34 7.42 7.37 7.38 7.53 7.32'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.247.251 : 8.46 8.42 8.31 12.39 8.28 8.34'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.244.13  : - - - - - -'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.244.23  : - - - - - -'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.168.123 : 8.30 8.32 8.38 8.29 8.44 8.27'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.251.122 : - - - - - -'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.197.63.72   : 0.72 0.62 0.81 0.60 0.61 0.62'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.252.250 : 11.15 7.55 8.12 8.12 7.95 8.23'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.1.222   : 8.01 7.42 7.34 7.37 7.39 7.46'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.197.63.36   : 0.64 0.63 0.63 0.61 0.61 0.61'

Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.215.0.76    : - - - - - -'

Tue Aug 14 16:23:57 2012 - Sent data to Server. Server said OK

 

Thanks in advance

         

Samy Nashaat

BusiLLss Operations Manager

FT/SCE/EQUANT/CS&O/Telephony Services Operations 

tel. +202 2292 2784 | CVS 382 2784 | mob. +20122 3372 815 | samy.nashaat at orange.com

Equant, City Stars Tower 2 Floor 10 Omar Ebn El Khatab Street, Heliopolis, Cairo, ELLpt

www.orange-busiLLss.com

?God will make a way when there seems to be no way?

? Please do not print this e-mail unless you really LLed to

 

 

-----Original Message-----
From: Darren Murphy [mailto:darren at victoriajd.com] 
Sent: Monday, July 30, 2012 11:48 AM
To: NASHAAT Samy SCE/CSO
Cc: smokeping-users at lists.oetiker.ch; YOUWAKIM Ramez SCE/CSO
Subject: Re: [smokeping-users] Smokeping Help | Master Slave config

 

On 30 July 2012 16:21, <samy.nashaat at orange.com <mailto:samy.nashaat at orange.com> > wrote:

> 

> I mean its NOW fixed  J

> 

> however I still cannot see any stats from the SLAVE on the Master 

> server web interface.

> 

> 

 

Okay, so check your master smokeping log - are there any errors?

If so, what are they?

 

The most common problem at this point is that the user that smokeping runs as does not have permissions to create/update the rrd files.

Check your master config file for the 'datadir' option - this will be where smokeping stores the rrd files.

Check the permissions on that directory, and make sure your smokeping user can write to it.

 

If the permissions look okay, check to make sure the slave rrd files actually exist.

If they do, look at the timestamps on the files and check if they are being updated.

 

If you're still stuck, start your master in debug mode and then check to see what gets logged. That should provide you with clues.

 

regards,

Darren


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120814/cb428ad5/attachment-0001.htm 

From liste at karp.fr  Tue Aug 14 16:37:02 2012
From: liste at karp.fr (Nicolas KARP)
Date: Tue, 14 Aug 2012 16:37:02 +0200
Subject: [smokeping-users] Smokeping Help | Master Slave config
In-Reply-To: <19941_1344952035_502A56E3_19941_11540_1_6F4FECEA3919634CA6E08F8E88083821010DACFB@PUEXCBJ0.nanterre.francetelecom.fr>
References: <30301_1342436221_5003F37D_30301_3794_1_6F4FECEA3919634CA6E08F8E88083821E71B3C@PUEXCBJ0.nanterre.francetelecom.fr>
	<CAJYt4Jv-pfxHeTKPTaZ=EqJ6Q567VxZo5SxyWCowzgTG=t87sg@mail.gmail.com>
	<22077_1343636405_501643B5_22077_11939_1_6F4FECEA3919634CA6E08F8E88083821F89387@PUEXCBJ0.nanterre.francetelecom.fr>
	<3029_1343636473_501643F9_3029_845_1_6F4FECEA3919634CA6E08F8E88083821F8938A@PUEXCBJ0.nanterre.francetelecom.fr>
	<CAJYt4JutTiKu-DW5YOARwvp+CzLGo54hcbMwdsU0MCV0AvpOpg@mail.gmail.com>
	<19941_1344952035_502A56E3_19941_11540_1_6F4FECEA3919634CA6E08F8E88083821010DACFB@PUEXCBJ0.nanterre.francetelecom.fr>
Message-ID: <CAELGAXd5HmBSRTt90_u4Xb29TGbkdSnmLR3bVn-iO=5SNf6dAA@mail.gmail.com>

Hi Samy,

Please check that the user which runs apache (www-data / apache /  httpd :
... )  is able to write in the "data" directory *on the master* -which
should be */var/lib/smokeping/LLor_Core* for you ).

On my server, CentOS 6.2, i added the apache user in the smokeping group
with the usermod command.

Here is the list of my files, permission :
Please take a look at the files which has the extension slave_cache : they
are owned owned by the user apache, not smokeping.

As you can see 2 files have been created for each targets :

-rw-r--r-- 1 smokeping smokeping 2.9M Aug 14 14:25 Cora~Paris-Telecity.rrd
-rw-r--r-- 1 apache    apache     410 Aug 14 14:26
Cora.Paris-Telecity.slave_cache

-rw-r--r-- 1 smokeping smokeping 2.9M Aug 14 14:25
HSBC-Lognes~Paris-Telecity.rrd
-rw-r--r-- 1 apache    apache     410 Aug 14 14:26
HSBC-Lognes.Paris-Telecity.slave_cache


And here are the permission i put on the 2 directories on the master :

drwxrwx---. 15 apache    apache    4.0K Jul 13 13:44 cache
drwxrwx---. 14 smokeping smokeping 4.0K Jul 12 07:48 data


If you want you can try to do a debug daemon on your master.

Best Regards,


# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
# - -   Nicolas KARP
# - -   Network and Security Engineer
# - -    Email : liste at karp.fr <nicolas at karp.fr>
# - -    Linkedin :  http://www.linkedin.com/pub/nicolas-karp/39/60b/21a
<http://www.linkedin.com/pub/nicolas-karp/39/60b/21a%20>
# - -    Viadeo : http://www.viadeo.com/fr/profile/nicolas.karp
<http://www.viadeo.com/fr/profile/nicolas.karp%20>
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -





2012/8/14 <samy.nashaat at orange.com>

> Hello Darren,****
>
> ** **
>
> I'm very thankful for your support however I still have problems.****
>
> ** **
>
> Please help me.****
>
> ** **
>
> *On the MASTER: the rrd files of the slave are not updated.*
>
> smoke at XXXXXinvk0093:/var/lib/smokeping/LLor_Core$ ls -l****
>
> total 15300****
>
> -rw-r--r-- 1 root     root 1039576 Jul 10 15:47
> CORE_LL_G10_XXXXXLLvk0306b~XXXXXLLvk0099.rrd****
>
> -rwxrwxrwx 1 www-data sudo 1039576 Jul 10 15:11
> CORE_LL_G10_XXXXXLLvk0306b~XXXXXLLvk0142.rrd****
>
> -rw-r--r-- 1 root     root 1039576 Aug 14 16:24
> CORE_LL_G10_XXXXXLLvk0306b.rrd****
>
> -rw-r--r-- 1 root     root 1039576 Jul 10 15:47
> CORE_LL_G1_2_XXXXXLLvk0309~XXXXXLLvk0099.rrd****
>
> -rwxrwxrwx 1 root     root 1039576 Jul 10 15:11
> CORE_LL_G1_2_XXXXXLLvk0309~XXXXXLLvk0142.rrd****
>
> -rw-r--r-- 1 root     root 1039576 Aug 14 16:24
> CORE_LL_G1_2_XXXXXLLvk0309.rrd****
>
> -rw-r--r-- 1 root     root 1039576 Jul 10 15:47
> CORE_LL_G1_XXXXXLLvk0300~XXXXXLLvk0099.rrd****
>
> -rw-r--r-- 1 root     root 1039576 Jul 10 15:11
> CORE_LL_G1_XXXXXLLvk0300~XXXXXLLvk0142.rrd****
>
> -rw-r--r-- 1 root     root 1039576 Aug 14 16:24
> CORE_LL_G1_XXXXXLLvk0300.rrd****
>
> -rw-r--r-- 1 root     root 1039576 Jul 10 15:47
> CORE_LL_G9_RZ_XXXXXLLvk0302a~XXXXXLLvk0099.rrd****
>
> -rw-r--r-- 1 root     root 1039576 Jul 10 15:11
> CORE_LL_G9_RZ_XXXXXLLvk0302a~XXXXXLLvk0142.rrd****
>
> -rw-r--r-- 1 root     root 1039576 Aug 14 16:24
> CORE_LL_G9_RZ_XXXXXLLvk0302a.rrd****
>
> -rw-r--r-- 1 root     root 1039576 Jul 10 15:47
> CORE_LL_G9_TK_XXXXXLLvk0201x~XXXXXLLvk0099.rrd****
>
> -rw-r--r-- 1 root     root 1039576 Jul 10 15:11
> CORE_LL_G9_TK_XXXXXLLvk0201x~XXXXXLLvk0142.rrd****
>
> -rw-r--r-- 1 root     root 1039576 Aug 14 16:24
> CORE_LL_G9_TK_XXXXXLLvk0201x.rrd****
>
> smoke at XXXXXLLvk0093:/var/lib/smokepLLg/LLor_Core$****
>
> no errors are shown in the debug LLither the log****
>
> smoke at XXXXXLLvk0093:/var/lib/smokepLLg/LLor_Core$ cat /tmp/smokelog****
>
> Tue Aug 14 15:39:30 2012 - Smokeping version  successfully launched.****
>
> Tue Aug 14 15:39:30 2012 - Not entering multiprocess mode for just a
> single probe.****
>
> Tue Aug 14 15:39:30 2012 - FPing: probing 41 targets with step 300 s and
> offset 238 s.****
>
> ** **
>
> smoke at XXXXXinvk0093:/var/lib/smokeping/LLor_Core$ sudo smokeping --debug**
> **
>
> [sudo] password for smoke:****
>
> ### Compiling alert detector pattern 'someloss'****
>
> ### >0%,*12*,>0%,*12*,>0%****
>
> sub {****
>
>     my $d = shift;****
>
>     my $y = $d->{loss};****
>
>     for(1){****
>
>         my $imax2 = min(@$y - 3, 12);****
>
>         my $imax1 = min(@$y - 3, 12);****
>
>         my $minlength = 3;****
>
>         my $maxlength = 27;****
>
>         LLxt if scalar @$y < $minlength ;****
>
>         my $i1;****
>
>         for($i1=0; $i1 < min($maxlength,$imax1); $i1++){****
>
>             my $i2;****
>
>             for($i2=0; $i2 < min($maxlength-$i1,$imax2); $i2++){****
>
>                 LLxt unless defiLLd $y->[-3-$i1-$i2]****
>
>                                 and $y->[-3-$i1-$i2] =~ /^\d/****
>
>                                 and $y->[-3-$i1-$i2] > 0****
>
>                                      ;                last;****
>
>             }****
>
>             return 0 if $i2 >= min($maxlength-$i1-$i2,$imax2);****
>
>             LLxt unless defiLLd $y->[-2-$i1]****
>
>                             and $y->[-2-$i1] =~ /^\d/****
>
>                             and $y->[-2-$i1] > 0****
>
>                                  ;            last;****
>
>         }****
>
>         return 0 if $i1 >= min($maxlength-$i1,$imax1);****
>
>         LLxt unless defiLLd $y->[-1]****
>
>                         and $y->[-1] =~ /^\d/****
>
>                         and $y->[-1] > 0****
>
>                              ;        return 1;****
>
>     }****
>
>     return 0;****
>
> }****
>
> ** **
>
> ** **
>
> ** **
>
> Smokeping version  successfully launched.****
>
> Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for
> that.****
>
> FPing: probing 41 targets with step 300 s and offset 24 s.****
>
> FPing: Executing /usr/bin/fping -C 6 -q -B1 -r1 -b40 -i10 -p1000
> 10.197.63.84 10.247.0.86 10.197.63.114 10.247.244.23 10.247.2.124
> 10.247.239.6 10.215.0.137 10.247.255.250 10.247.250.250 10.247.1.158
> 10.197.63.36 10.247.251.253 10.247.244.13 10.247.1.22 10.247.168.123
> 10.247.1.254 10.247.0.64 10.215.0.30 10.247.1.189 10.247.246.6 10.197.63.9
> localhost 10.247.252.250 10.215.0.92 10.247.249.250 10.197.63.150
> 10.197.63.132 10.197.63.72 10.247.1.123 10.247.2.30 10.247.251.122
> 10.247.249.122 10.247.242.254 10.215.0.76 10.247.1.94 10.247.2.91
> 10.215.0.108 10.247.253.250 10.247.1.222 10.247.247.251 10.247.254.251****
>
> FPing: Got fping output: 'ICMP Time Exceeded from 10.251.160.2 for ICMP
> Echo sent to 10.247.251.122'****
>
> FPing: Got fping output: 'ICMP Host Unreachable from 192.168.50.26 for
> ICMP Echo sent to 10.215.0.76'****
>
> FPing: Got fping output: 'ICMP Time Exceeded from 10.251.160.2 for ICMP
> Echo sent to 10.247.251.122'****
>
> FPing: Got fping output: 'ICMP Time Exceeded from 10.251.160.2 for ICMP
> Echo sent to 10.247.251.122'****
>
> FPing: Got fping output: 'ICMP Time Exceeded from 10.251.160.2 for ICMP
> Echo sent to 10.247.251.122'****
>
> FPing: Got fping output: 'ICMP Host Unreachable from 192.168.50.26 for
> ICMP Echo sent to 10.215.0.76'****
>
> FPing: Got fping output: 'ICMP Time Exceeded from 10.251.160.2 for ICMP
> Echo sent to 10.247.251.122'****
>
> FPing: Got fping output: 'ICMP Time Exceeded from 10.251.160.2 for ICMP
> Echo sent to 10.247.251.122'****
>
> FPing: Got fping output: '10.197.63.84   : 7.40 7.42 7.44 7.36 7.44 7.33'*
> ***
>
> FPing: Got fping output: '10.247.0.86    : 1.95 0.21 0.22 0.26 0.22 0.21'*
> ***
>
> FPing: Got fping output: '10.197.63.114  : 7.30 7.35 7.84 7.47 7.53 7.48'*
> ***
>
> FPing: Got fping output: '10.247.244.23  : - - - - - -'****
>
> FPing: Got fping output: '10.247.2.124   : 0.76 0.74 0.75 0.76 0.78 0.76'*
> ***
>
> FPing: Got fping output: '10.247.239.6   : 1.81 1.81 18.37 1.84 1.81 1.81'
> ****
>
> FPing: Got fping output: '10.215.0.137   : 38.37 38.13 37.74 37.71 37.88
> 38.27'****
>
> FPing: Got fping output: '10.247.255.250 : 1.87 1.86 1.86 1.93 1.87 1.85'*
> ***
>
> FPing: Got fping output: '10.247.250.250 : 1.81 1.92 1.96 1.91 1.90 1.96'*
> ***
>
> FPing: Got fping output: '10.247.1.158   : 0.77 0.74 0.73 0.78 0.73 0.77'*
> ***
>
> FPing: Got fping output: '10.197.63.36   : 7.49 7.39 7.41 7.42 7.54 7.41'*
> ***
>
> FPing: Got fping output: '10.247.251.253 : - - - - - -'****
>
> FPing: Got fping output: '10.247.244.13  : - - - - - -'****
>
> FPing: Got fping output: '10.247.1.22    : 0.41 0.36 0.36 0.37 0.35 0.37'*
> ***
>
> FPing: Got fping output: '10.247.168.123 : 1.76 1.79 1.81 1.80 1.81 1.84'*
> ***
>
> FPing: Got fping output: '10.247.1.254   : 0.75 0.74 0.75 0.73 0.73 0.75'*
> ***
>
> FPing: Got fping output: '10.247.0.64    : 0.24 0.23 0.23 0.22 0.24 0.23'*
> ***
>
> FPing: Got fping output: '10.215.0.30    : 38.81 37.75 37.91 37.74 37.97
> 37.66'****
>
> FPing: Got fping output: '10.247.1.189   : 0.46 0.41 0.43 0.31 0.65 0.42'*
> ***
>
> FPing: Got fping output: '10.247.246.6   : 1.30 1.21 1.19 1.18 1.19 1.22'*
> ***
>
> FPing: Got fping output: '10.197.63.9    : 6.86 7.03 6.91 7.02 7.03 6.89'*
> ***
>
> FPing: Got fping output: 'localhost      : 0.02 0.02 0.02 0.01 0.02 0.01'*
> ***
>
> FPing: Got fping output: '10.247.252.250 : 1.74 1.70 1.97 23.96 1.90 1.79'
> ****
>
> FPing: Got fping output: '10.215.0.92    : 38.76 38.33 38.30 38.21 38.72
> 38.21'****
>
> FPing: Got fping output: '10.247.249.250 : 1.66 1.78 5.33 5.58 1.54 1.61'*
> ***
>
> FPing: Got fping output: '10.197.63.150  : 7.05 7.20 7.08 7.18 7.21 7.10'*
> ***
>
> FPing: Got fping output: '10.197.63.132  : 14.95 15.27 14.85 15.17 19.62
> 14.95'****
>
> FPing: Got fping output: '10.197.63.72   : 7.54 7.65 7.42 7.41 7.42 7.51'*
> ***
>
> FPing: Got fping output: '10.247.1.123   : 0.72 0.77 0.75 0.77 0.71 0.70'*
> ***
>
> FPing: Got fping output: '10.247.2.30    : 1.14 0.60 0.60 0.66 0.60 0.60'*
> ***
>
> FPing: Got fping output: '10.247.251.122 : - - - - - -'****
>
> FPing: Got fping output: '10.247.249.122 : - - - - - -'****
>
> FPing: Got fping output: '10.247.242.254 : 1.06 0.99 1.00 0.99 0.98 0.96'*
> ***
>
> FPing: Got fping output: '10.215.0.76    : - - - - - -'****
>
> FPing: Got fping output: '10.247.1.94    : 32.03 0.77 0.74 0.75 0.79 0.73'
> ****
>
> FPing: Got fping output: '10.247.2.91    : 0.74 0.74 0.71 0.77 0.75 0.73'*
> ***
>
> FPing: Got fping output: '10.215.0.108   : 44.25 44.10 44.14 44.17 45.35
> 44.91'****
>
> FPing: Got fping output: '10.247.253.250 : 1.86 1.86 1.78 1.83 1.85 1.83'*
> ***
>
> FPing: Got fping output: '10.247.1.222   : 0.60 0.60 0.58 0.60 0.60 0.58'*
> ***
>
> FPing: Got fping output: '10.247.247.251 : 2.13 1.92 1.91 1.87 3.94 1.87'*
> ***
>
> FPing: Got fping output: '10.247.254.251 : 1.95 1.92 1.94 1.88 1.97 1.87'*
> ***
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_GVZ_XXXXXinvk0211.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:7.6000000000e-04:7.4000000000e-04:7.5000000000e-04:7.6000000000e-04:7.6000000000e-04:7.8000000000e-04)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Hoch_Str_1d_2OGI_EB11_XXXXXinvk0098.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:1.1900000000e-03:1.1800000000e-03:1.1900000000e-03:1.1900000000e-03:1.2100000000e-03:1.2200000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Theo_Heuss_XXXXXinvk0136c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:1.7800000000e-03:1.5400000000e-03:1.6100000000e-03:1.7800000000e-03:5.3300000000e-03:5.5800000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_SE_Mar_Cur_XXXXXinvk0132c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:1.9200000000e-03:1.8700000000e-03:1.8800000000e-03:1.9200000000e-03:1.9400000000e-03:1.9700000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Fried_str_XXXXXinvk0108c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:1.8600000000e-03:1.8500000000e-03:1.8600000000e-03:1.8600000000e-03:1.8700000000e-03:1.9300000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Akad_Schluet_Str_XXXXXinvk0201.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:5:U:U:U:U:U:U)****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_A58_XXXXXinvk0208.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:7.4000000000e-04:7.3000000000e-04:7.3000000000e-04:7.4000000000e-04:7.7000000000e-04:7.8000000000e-04)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_GebA50_H117_XXXXXinvk0330.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:3.6000000000e-04:3.5000000000e-04:3.6000000000e-04:3.6000000000e-04:3.7000000000e-04:3.7000000000e-04)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Sachs_Str_16_18_XXXXXinvk0147c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:1.8300000000e-03:1.7800000000e-03:1.8300000000e-03:1.8300000000e-03:1.8500000000e-03:1.8600000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_T22_XXXXXinvk0200.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:7.5000000000e-04:7.0000000000e-04:7.1000000000e-04:7.5000000000e-04:7.7000000000e-04:7.7000000000e-04)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_T20_XXXXXinvk0215.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:6.0000000000e-04:5.8000000000e-04:5.8000000000e-04:6.0000000000e-04:6.0000000000e-04:6.0000000000e-04)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_A51_XXXXXinvk0216.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:7.4000000000e-04:7.3000000000e-04:7.3000000000e-04:7.4000000000e-04:7.5000000000e-04:7.5000000000e-04)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Hoch_Str_1d_3OGI_EK2P_XXXXXinvk0096.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:5:U:U:U:U:U:U)****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_T01_XXXXXinvk0223.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:6.0000000000e-04:6.0000000000e-04:6.0000000000e-04:6.0000000000e-04:6.0000000000e-04:6.6000000000e-04)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_A50_N113_XXXXXinvk0207.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:7.5000000000e-04:7.3000000000e-04:7.4000000000e-04:7.5000000000e-04:7.7000000000e-04:7.9000000000e-04)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Sachs_Str_11_XXXXXinvk0149c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:5:U:U:U:U:U:U)****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Sachs_Str_14_Gaim_XXXXXinvk0151c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:1.9000000000e-03:1.7000000000e-03:1.7900000000e-03:1.9000000000e-03:1.9700000000e-03:2.3960000000e-02)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_ARG_XXXXXinvk0110c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:1.8100000000e-03:1.8100000000e-03:1.8100000000e-03:1.8100000000e-03:1.8400000000e-03:1.8370000000e-02)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_DR_L_K_XXXXXinvk0112c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:1.9100000000e-03:1.8700000000e-03:1.8700000000e-03:1.9100000000e-03:1.9200000000e-03:3.9400000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Test_LLust_XXXXXinvk0134c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:1.9200000000e-03:1.9000000000e-03:1.9100000000e-03:1.9200000000e-03:1.9600000000e-03:1.9600000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_S29_XXXXXinvk0302.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:4.2000000000e-04:3.1000000000e-04:4.1000000000e-04:4.2000000000e-04:4.3000000000e-04:6.5000000000e-04)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Staud_Ha_XXXXXinvk0128c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:1.8100000000e-03:1.7900000000e-03:1.8000000000e-03:1.8100000000e-03:1.8100000000e-03:1.8400000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Geb_N30_XXXXXinvk0217.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:7.4000000000e-04:7.1000000000e-04:7.3000000000e-04:7.4000000000e-04:7.5000000000e-04:7.7000000000e-04)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Akad_Egerl_Str_XXXXXiinvk0101c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:5:U:U:U:U:U:U)****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_RZ_IN1_Geb_A57_XXXXXinvk0305c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:2.2000000000e-04:2.1000000000e-04:2.1000000000e-04:2.2000000000e-04:2.2000000000e-04:2.6000000000e-04)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_RZ_IN2_Geb_N10_XXXXXinvk0326c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:2.3000000000e-04:2.2000000000e-04:2.3000000000e-04:2.3000000000e-04:2.3000000000e-04:2.4000000000e-04)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Dies_Str_22_Gaim_XXXXXinvk0218.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:9.9000000000e-04:9.6000000000e-04:9.8000000000e-04:9.9000000000e-04:9.9000000000e-04:1.0000000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/Ingolstadt_Core/CORE_IN_Hindenb_Str_XXXXXinvk0153c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:5:U:U:U:U:U:U)****
>
> Calling
> RRDs::update(/var/lib/smokeping/LLor_Core/CORE_LL_G9_RZ_XXXXXLLvk0302a.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:3.7750000000e-02:3.7660000000e-02:3.7740000000e-02:3.7750000000e-02:3.7910000000e-02:3.7970000000e-02)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/LLor_Core/CORE_LL_G9_TK_XXXXXLLvk0201x.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:4.4170000000e-02:4.4100000000e-02:4.4140000000e-02:4.4170000000e-02:4.4910000000e-02:4.5350000000e-02)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/LLor_Core/CORE_LL_G10_XXXXXLLvk0306b.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:3.7880000000e-02:3.7710000000e-02:3.7740000000e-02:3.7880000000e-02:3.8130000000e-02:3.8270000000e-02)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/LLor_Core/CORE_LL_G1_2_XXXXXLLvk0309.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:3.8300000000e-02:3.8210000000e-02:3.8210000000e-02:3.8300000000e-02:3.8330000000e-02:3.8720000000e-02)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/LLor_Core/CORE_LL_G1_XXXXXLLvk0300.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:5:U:U:U:U:U:U)****
>
> Calling RRDs::update(/var/lib/smokeping/Local/LocalMachiLL.rrd --template
> uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:2.0000000000e-05:1.0000000000e-05:1.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_Geb_B09_XXXXXLLvk0310c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:7.1800000000e-03:7.0800000000e-03:7.1000000000e-03:7.1800000000e-03:7.2000000000e-03:7.2100000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_Geb_A17_XXXXXLLvk0301a.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:7.0200000000e-03:6.8900000000e-03:6.9100000000e-03:7.0200000000e-03:7.0300000000e-03:7.0300000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_Geb_B18_XXXXXLLvk0220.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:7.4200000000e-03:7.3300000000e-03:7.3600000000e-03:7.4200000000e-03:7.4400000000e-03:7.4400000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_GIF_XXXXXLLvk0250.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:7.4800000000e-03:7.3500000000e-03:7.4700000000e-03:7.4800000000e-03:7.5300000000e-03:7.8400000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_Geb_B05_XXXXXLLvk0230.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:7.4100000000e-03:7.3900000000e-03:7.4100000000e-03:7.4100000000e-03:7.4200000000e-03:7.5400000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_Geb_B12_XXXXXLLvk0210.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:7.4200000000e-03:7.4100000000e-03:7.4200000000e-03:7.4200000000e-03:7.5100000000e-03:7.6500000000e-03)
> ****
>
> Calling
> RRDs::update(/var/lib/smokeping/LLckarsulm_Core/CORE_LL_Talh_XXXXXLLvk0171c.rrd
> --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
> 1344954701:U:0:1.5170000000e-02:1.4850000000e-02:1.4950000000e-02:1.5170000000e-02:1.5270000000e-02:1.9620000000e-02)
> ****
>
> ** **
>
> *Although the SLAVE says all is ok, in the debug and the log*
>
> ** **
>
> smoke at XXXXXLLvk0142:/usr/sbin$ sudo ./smokeping --master-url=
> http://10.247.0.51/smokeping/smokeping.cgi
> --cache-dir=/var/lib/smokeping
> --shared-secret=/var/smokeping/secret.txt --debug --logfile=/tmp/smokelog*
> ***
>
> Sent data to Server and got LLw config in response****
>
> ** **
>
> LOG FILE:****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.1.189   : 7.20
> 7.10 6.97 7.01 7.19 7.20'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: 'localhost      : 0.01
> 0.01 0.01 0.01 0.01 0.01'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.2.30    : 7.37
> 7.63 7.52 7.37 7.51 7.53'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.197.63.84   : 0.64
> 0.63 0.61 0.62 0.61 0.60'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.1.123   : 7.49
> 7.40 7.59 7.62 7.51 26.11'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.1.254   : 7.26
> 7.22 7.27 7.23 7.23 7.31'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.242.254 : 7.73
> 7.61 7.49 7.47 7.53 7.43'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.197.63.9    : 0.10
> 0.09 0.09 0.09 0.10 0.09'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.255.250 : 8.20
> 10.01 8.13 8.12 8.76 8.10'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.249.250 : 7.96
> 7.79 7.92 7.72 7.85 7.99'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.250.250 : 8.41
> 8.20 8.29 8.34 8.16 8.40'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.197.63.114  : 0.61
> 0.65 0.64 0.62 0.64 0.63'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.1.158   : 7.32
> 7.49 7.28 7.25 7.26 7.21'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.1.94    : 7.34
> 7.42 7.37 7.38 7.53 7.32'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.247.251 : 8.46
> 8.42 8.31 12.39 8.28 8.34'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.244.13  : - -
> - - - -'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.244.23  : - -
> - - - -'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.168.123 : 8.30
> 8.32 8.38 8.29 8.44 8.27'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.251.122 : - -
> - - - -'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.197.63.72   : 0.72
> 0.62 0.81 0.60 0.61 0.62'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.252.250 :
> 11.15 7.55 8.12 8.12 7.95 8.23'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.247.1.222   : 8.01
> 7.42 7.34 7.37 7.39 7.46'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.197.63.36   : 0.64
> 0.63 0.63 0.61 0.61 0.61'****
>
> Tue Aug 14 16:23:07 2012 - FPing: Got fping output: '10.215.0.76    : - -
> - - - -'****
>
> Tue Aug 14 16:23:57 2012 - Sent data to Server. Server said OK****
>
> ** **
>
> Thanks in advance****
>
>          ****
>
> Samy Nashaat****
>
> BusiLLss Operations Manager****
>
> FT/SCE/EQUANT/CS&O/Telephony Services Operations ****
>
> tel. +202 2292 2784 | CVS 382 2784 | mob. +20122 3372 815 |
> samy.nashaat at orange.com****
>
> Equant, City Stars Tower 2 Floor 10 Omar Ebn El Khatab Street, Heliopolis,
> Cairo, ELLpt****
>
> www.orange-busiLLss.com****
>
> ?God will make a way when there seems to be no way?****
>
> ? Please do not print this e-mail unless you really LLed to****
>
> ** **
>
> ** **
>
> -----Original Message-----
> From: Darren Murphy [mailto:darren at victoriajd.com]
> Sent: Monday, July 30, 2012 11:48 AM
> To: NASHAAT Samy SCE/CSO
> Cc: smokeping-users at lists.oetiker.ch; YOUWAKIM Ramez SCE/CSO
> Subject: Re: [smokeping-users] Smokeping Help | Master Slave config
>
> ** **
>
> On 30 July 2012 16:21, <samy.nashaat at orange.com> wrote:****
>
> >** **
>
> > I mean its NOW fixed  J****
>
> >** **
>
> > however I still cannot see any stats from the SLAVE on the Master ****
>
> > server web interface.****
>
> >** **
>
> >** **
>
> ** **
>
> Okay, so check your master smokeping log - are there any errors?****
>
> If so, what are they?****
>
> ** **
>
> The most common problem at this point is that the user that smokeping runs
> as does not have permissions to create/update the rrd files.****
>
> Check your master config file for the 'datadir' option - this will be
> where smokeping stores the rrd files.****
>
> Check the permissions on that directory, and make sure your smokeping user
> can write to it.****
>
> ** **
>
> If the permissions look okay, check to make sure the slave rrd files
> actually exist.****
>
> If they do, look at the timestamps on the files and check if they are
> being updated.****
>
> ** **
>
> If you're still stuck, start your master in debug mode and then check to
> see what gets logged. That should provide you with clues.****
>
> ** **
>
> regards,****
>
> Darren****
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>
> _______________________________________________
> 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/20120814/e0b6384c/attachment-0001.htm 

From david at schweikert.ch  Sun Aug 19 23:13:36 2012
From: david at schweikert.ch (David Schweikert)
Date: Sun, 19 Aug 2012 23:13:36 +0200
Subject: [smokeping-users] ANNOUNCE: fping 3.3
Message-ID: <20120819211336.GA9836@schweikert.ch>

Hi,

I have just released fping 3.3 with the following changes since 3.2:

  * Do not output icmp errors with -q (#1)
  * Add --enable-ipv4 and --enable-ipv6 options to configure (Niclas Zeising)
  * Fix removing of unreachable hosts when doing loop (Thomas Liske, #13 #23)
  * Fix -A for fping6 (reported by Matt LaPlante, #14)
  * Fix "options inet6" breaking IPv4 name resolution (reported by Matt LaPlante, #17)
  * Output statistics to stdout instead of stderr (suggested by Simon Leinen, #9)
  * Set default data size to 56 bytes on all architectures (#18)
  * Added contrib/fping.spec (Stephen Schaefer, #24)
  * Convert man-page source to POD for easier maintenance
  * Fix error message on DNS error for IPv6 hosts (#27)
  * Fix -n flag in fping6 (#28)
  * Man-page fix: TOS option typo (Thomas Liske, #23)
  * Man-page fix: inconsistency in regards to numeric arguments (Robert Henney)
  * Man-page fix: better description of option -q (#15)

You can download it here: http://fping.org/

Cheers
David


From liste at karp.fr  Thu Aug 23 17:31:36 2012
From: liste at karp.fr (Nicolas KARP)
Date: Thu, 23 Aug 2012 17:31:36 +0200
Subject: [smokeping-users] Alerts: Edgetrigger not sending a "0" as argument
	when lowering alert
Message-ID: <CAELGAXcgbNpAt6vhu5j=uWzREitEmpWEk92EARya9u7iR=yrpA@mail.gmail.com>

Hi Niko,

I don't understand why the patch was not commited to the current version of
smokeping ?
I'm running the smokeping version 2.6.7 and i still not receive a 0 when
the alarm is lowered and when i used the argument "edgetrigger".
It would be great if we can dissociate a alarm which is cleared if we use
edgetrigger (6 args, last arg = 0) and a alarm which is raised if se don't
use edgetrigger (5 args).

We will have 3 cases :

edgetrigger :
6 args and last arg = 1 : Alarm is raised
6 args and last arg = 0 : Alarm is cleared

no edgetrigger
5 args : Alarm is always raised

BTW, i applied your patch and it works perfectly.

What do you think ?

Best Regards,

This indeed seems to be a bug. Thanks for reporting it.

Looking at the code, the lower edge will call your script with six
arguments, but the last one is an empty string instead of zero. There is a
difference to the five argument case, and it should be possible to detect
this in your script (for Bourne shell scripts, looking at $# should do.)

That said, does this patch work for you? It should make the behaviour
conform to the documentation.
-- 
Niko



# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
# - -   Nicolas KARP
# - -   Network and Security Engineer
# - -    Email : liste at karp.fr <nicolas at karp.fr>
# - -    Linkedin :  http://www.linkedin.com/pub/nicolas-karp/39/60b/21a
<http://www.linkedin.com/pub/nicolas-karp/39/60b/21a%20>
# - -    Viadeo : http://www.viadeo.com/fr/profile/nicolas.karp
<http://www.viadeo.com/fr/profile/nicolas.karp%20>
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120823/8ddcc90f/attachment.htm 

From tobi at oetiker.ch  Thu Aug 23 22:59:31 2012
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Thu, 23 Aug 2012 22:59:31 +0200 (CEST)
Subject: [smokeping-users] Alerts: Edgetrigger not sending a "0" as
 argument when lowering alert
In-Reply-To: <CAELGAXcgbNpAt6vhu5j=uWzREitEmpWEk92EARya9u7iR=yrpA@mail.gmail.com>
References: <CAELGAXcgbNpAt6vhu5j=uWzREitEmpWEk92EARya9u7iR=yrpA@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1208232257450.18366@froburg.oetiker.ch>

Hi Nicolas,

Today Nicolas KARP wrote:

> Hi Niko,
>
> I don't understand why the patch was not commited to the current version of
> smokeping ?
> I'm running the smokeping version 2.6.7 and i still not receive a 0 when
> the alarm is lowered and when i used the argument "edgetrigger".
> It would be great if we can dissociate a alarm which is cleared if we use
> edgetrigger (6 args, last arg = 0) and a alarm which is raised if se don't
> use edgetrigger (5 args).
>
> We will have 3 cases :
>
> edgetrigger :
> 6 args and last arg = 1 : Alarm is raised
> 6 args and last arg = 0 : Alarm is cleared
>
> no edgetrigger
> 5 args : Alarm is always raised
>
> BTW, i applied your patch and it works perfectly.
>
> What do you think ?
>
> Best Regards,
>
> This indeed seems to be a bug. Thanks for reporting it.
>
> Looking at the code, the lower edge will call your script with six
> arguments, but the last one is an empty string instead of zero. There is a
> difference to the five argument case, and it should be possible to detect
> this in your script (for Bourne shell scripts, looking at $# should do.)
>
> That said, does this patch work for you? It should make the behaviour
> conform to the documentation.

that patch seems to have passed me by ... cant find any
pullrequests on https://github.com/oetiker/SmokePing

please just send me that patch or create a pull request if you are
working on a fork

cheers
tobi

>

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900


From ntyni+smokeping-users at mappi.helsinki.fi  Fri Aug 24 09:33:53 2012
From: ntyni+smokeping-users at mappi.helsinki.fi (Niko Tyni)
Date: Fri, 24 Aug 2012 10:33:53 +0300
Subject: [smokeping-users] Alerts: Edgetrigger not sending a "0" as
 argument when lowering alert
In-Reply-To: <alpine.DEB.2.02.1208232257450.18366@froburg.oetiker.ch>
References: <CAELGAXcgbNpAt6vhu5j=uWzREitEmpWEk92EARya9u7iR=yrpA@mail.gmail.com>
	<alpine.DEB.2.02.1208232257450.18366@froburg.oetiker.ch>
Message-ID: <20120824073353.GB4506@madeleine.local.invalid>

On Thu, Aug 23, 2012 at 10:59:31PM +0200, Tobias Oetiker wrote:
> Today Nicolas KARP wrote:

> > I don't understand why the patch was not commited to the current version of
> > smokeping ?

Looks like I forgot about it. Sorry about that, I'm not doing much with
SmokePing nowadays.

> > I'm running the smokeping version 2.6.7 and i still not receive a 0 when
> > the alarm is lowered and when i used the argument "edgetrigger".
> > It would be great if we can dissociate a alarm which is cleared if we use
> > edgetrigger (6 args, last arg = 0) and a alarm which is raised if se don't
> > use edgetrigger (5 args).
> >
> > We will have 3 cases :
> >
> > edgetrigger :
> > 6 args and last arg = 1 : Alarm is raised
> > 6 args and last arg = 0 : Alarm is cleared
> >
> > no edgetrigger
> > 5 args : Alarm is always raised
> >
> > BTW, i applied your patch and it works perfectly.
> >
> > What do you think ?
> >
> > Best Regards,
> >
> > This indeed seems to be a bug. Thanks for reporting it.
> >
> > Looking at the code, the lower edge will call your script with six
> > arguments, but the last one is an empty string instead of zero. There is a
> > difference to the five argument case, and it should be possible to detect
> > this in your script (for Bourne shell scripts, looking at $# should do.)
> >
> > That said, does this patch work for you? It should make the behaviour
> > conform to the documentation.
> 
> that patch seems to have passed me by ... cant find any
> pullrequests on https://github.com/oetiker/SmokePing

Found it in my mailbox from May 2010, attached. Tobi, feel free
to pick this up.

Sorry for dropping the ball on this.
-- 
Niko
-------------- next part --------------
A non-text attachment was scrubbed...
Name: edgetrigger.patch
Type: text/x-diff
Size: 694 bytes
Desc: not available
Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120824/6522c63c/attachment.patch 

From saq at thesaq.net  Sat Aug 25 02:22:28 2012
From: saq at thesaq.net (Aaron Boerup)
Date: Sat, 25 Aug 2012 00:22:28 +0000
Subject: [smokeping-users] smokeping fping probe with high resolution / low
	interval possible?
Message-ID: <3D4426F08A57164FA68A85B0F249A68D8D9AABE1@server.domain.local>

Hello,
I've been diving into the fun of smokeping lately and using it to monitor my LAN and I am enjoying it quite a bit, especially with multiple probes to correlate information. I have one problem and one question.

My problem is that I seem to be running into a problem with the shortest (most flood-like) interval for fping. If I set the hostinterval to anything lower than .1 (which is 100ms) then I seem to get nothing but 100% packet loss on the graph. Is this an intentional limit? If I do an fping <ip> -p 1 -I 1 -c 300 I will be able to send all 300 packets in about 4 seconds. I would like to be able to do this kind of granularity for some special troubleshooting I am doing. Anyone know of a way to do this?

My question is a way to get a combined multi-probe graph like you get on the summary screen on the detail page. I did some looking and didn't see an obvious way to do this.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120825/1c27c910/attachment.htm 

From ged at jubileegroup.co.uk  Sat Aug 25 12:50:07 2012
From: ged at jubileegroup.co.uk (G.W. Haywood)
Date: Sat, 25 Aug 2012 11:50:07 +0100 (BST)
Subject: [smokeping-users] smokeping fping probe with high resolution /
 low interval possible?
In-Reply-To: <3D4426F08A57164FA68A85B0F249A68D8D9AABE1@server.domain.local>
References: <3D4426F08A57164FA68A85B0F249A68D8D9AABE1@server.domain.local>
Message-ID: <Pine.LNX.4.64.1208251135370.13457@mail5.jubileegroup.co.uk>

Hi there,

On Sat, 25 Aug 2012, Aaron Boerup wrote:

> ... problem with the shortest (most flood-like) interval for
> fping. If I set the hostinterval to anything lower than .1 (which is
> 100ms) then I seem to get nothing but 100% packet loss on the
> graph. Is this an intentional limit? If I do an fping <ip> -p 1 -I 1
> -c 300 I will be able to send all 300 packets in about 4 seconds.

There are several versions of fping in existence and you haven't said
which one you're using.  If you read the man page for it you might
find that fping itself places restrictions on the sorts of things that
can be done by non-privilieged users, and you might discover things
which can only be done by a user with root permissions.  Setting the
interval between packets going to an individual target to something as
low as one millisecond (if that's what '-p 1' does in your version of
fping - it does in at least one of mine and there isn't an '-I' switch
in any of them) is the sort of thing that would usually only be done
by root, as it might be considered abusive.

> I would like to be able to do this kind of granularity for some
> special troubleshooting I am doing.

Perhaps you can be more specific about the troubleshooting.

> My question is a way to get a combined multi-probe graph like you
> get on the summary screen on the detail page. I did some looking and
> didn't see an obvious way to do this.

I don't know what the "summary screen" and the "detail page" are.
You have acess to the full source to do whatever you wish to it, but
there's a lot of fairly densely coded Perl in there and that will be
hard going if you aren't an experienced Perl programmer.

--

73,
Ged.


From saq at thesaq.net  Sun Aug 26 08:16:57 2012
From: saq at thesaq.net (Aaron Boerup)
Date: Sun, 26 Aug 2012 06:16:57 +0000
Subject: [smokeping-users] smokeping fping probe with high resolution /
 low interval possible?
In-Reply-To: <Pine.LNX.4.64.1208251135370.13457@mail5.jubileegroup.co.uk>
References: <3D4426F08A57164FA68A85B0F249A68D8D9AABE1@server.domain.local>
	<Pine.LNX.4.64.1208251135370.13457@mail5.jubileegroup.co.uk>
Message-ID: <3D4426F08A57164FA68A85B0F249A68D8D9AB1C6@server.domain.local>

Whoops, should have included those details.
Running smokeping version 2.006007
The "default" fping I'm using is 2.4b2_to $Date: 2002/01/16 00:33:42
I'm not much of a linux expert so I missed this obvious part. I did indeed have a problem with the smokeping daemon user not having sufficient privileges to go faster than 100ms. I fixed this and it does let me run a finer resolution than 100ms, though it seems to take much longer (and generating errors in the logs) than running the command manually. Its only able to do about 10-11 pings a second.
I've also downloaded fping 3.3 from www.fping.org but I can't seem to make this binary work for my smokeping. Not sure what it doesn't like, I've compared the output from the commands smokeping is sending and it looks identical other than access times. Running Ubuntu Server 12.04

For speed comparison

Fping 2.4b2
fping -c 3000 -i 1 -p 1 -q -s <hostname> yields me about 72 pings/second

Fping 3.3
fping -c 3000 -i 1 -p 1 -q -s <hostname> yields me about 860 pings/second

-----Original Message-----
From: G.W. Haywood [mailto:ged at jubileegroup.co.uk] 
Sent: Saturday, August 25, 2012 3:50 AM
To: Aaron Boerup
Cc: smokeping-users at lists.oetiker.ch
Subject: Re: [smokeping-users] smokeping fping probe with high resolution / low interval possible?

Hi there,

On Sat, 25 Aug 2012, Aaron Boerup wrote:

> ... problem with the shortest (most flood-like) interval for fping. If 
> I set the hostinterval to anything lower than .1 (which is
> 100ms) then I seem to get nothing but 100% packet loss on the graph. 
> Is this an intentional limit? If I do an fping <ip> -p 1 -I 1 -c 300 I 
> will be able to send all 300 packets in about 4 seconds.

There are several versions of fping in existence and you haven't said which one you're using.  If you read the man page for it you might find that fping itself places restrictions on the sorts of things that can be done by non-privilieged users, and you might discover things which can only be done by a user with root permissions.  Setting the interval between packets going to an individual target to something as low as one millisecond (if that's what '-p 1' does in your version of fping - it does in at least one of mine and there isn't an '-I' switch in any of them) is the sort of thing that would usually only be done by root, as it might be considered abusive.

> I would like to be able to do this kind of granularity for some 
> special troubleshooting I am doing.

Perhaps you can be more specific about the troubleshooting.

> My question is a way to get a combined multi-probe graph like you get 
> on the summary screen on the detail page. I did some looking and 
> didn't see an obvious way to do this.

I don't know what the "summary screen" and the "detail page" are.
You have acess to the full source to do whatever you wish to it, but there's a lot of fairly densely coded Perl in there and that will be hard going if you aren't an experienced Perl programmer.

--

73,
Ged.


From saq at thesaq.net  Sun Aug 26 10:17:41 2012
From: saq at thesaq.net (Aaron Boerup)
Date: Sun, 26 Aug 2012 08:17:41 +0000
Subject: [smokeping-users] smokeping fping probe with high resolution /
 low interval possible?
References: <3D4426F08A57164FA68A85B0F249A68D8D9AABE1@server.domain.local>
	<Pine.LNX.4.64.1208251135370.13457@mail5.jubileegroup.co.uk> 
Message-ID: <3D4426F08A57164FA68A85B0F249A68D8D9AB251@server.domain.local>

Updating to 2.006008 and using fping 3.2 seems to have solved my high resolution problems. 

-----Original Message-----
From: Aaron Boerup 
Sent: Saturday, August 25, 2012 11:16 PM
To: 'G.W. Haywood'
Cc: smokeping-users at lists.oetiker.ch
Subject: RE: [smokeping-users] smokeping fping probe with high resolution / low interval possible?

Whoops, should have included those details.
Running smokeping version 2.006007
The "default" fping I'm using is 2.4b2_to $Date: 2002/01/16 00:33:42 I'm not much of a linux expert so I missed this obvious part. I did indeed have a problem with the smokeping daemon user not having sufficient privileges to go faster than 100ms. I fixed this and it does let me run a finer resolution than 100ms, though it seems to take much longer (and generating errors in the logs) than running the command manually. Its only able to do about 10-11 pings a second.
I've also downloaded fping 3.3 from www.fping.org but I can't seem to make this binary work for my smokeping. Not sure what it doesn't like, I've compared the output from the commands smokeping is sending and it looks identical other than access times. Running Ubuntu Server 12.04

For speed comparison

Fping 2.4b2
fping -c 3000 -i 1 -p 1 -q -s <hostname> yields me about 72 pings/second

Fping 3.3
fping -c 3000 -i 1 -p 1 -q -s <hostname> yields me about 860 pings/second

-----Original Message-----
From: G.W. Haywood [mailto:ged at jubileegroup.co.uk]
Sent: Saturday, August 25, 2012 3:50 AM
To: Aaron Boerup
Cc: smokeping-users at lists.oetiker.ch
Subject: Re: [smokeping-users] smokeping fping probe with high resolution / low interval possible?

Hi there,

On Sat, 25 Aug 2012, Aaron Boerup wrote:

> ... problem with the shortest (most flood-like) interval for fping. If 
> I set the hostinterval to anything lower than .1 (which is
> 100ms) then I seem to get nothing but 100% packet loss on the graph. 
> Is this an intentional limit? If I do an fping <ip> -p 1 -I 1 -c 300 I 
> will be able to send all 300 packets in about 4 seconds.

There are several versions of fping in existence and you haven't said which one you're using.  If you read the man page for it you might find that fping itself places restrictions on the sorts of things that can be done by non-privilieged users, and you might discover things which can only be done by a user with root permissions.  Setting the interval between packets going to an individual target to something as low as one millisecond (if that's what '-p 1' does in your version of fping - it does in at least one of mine and there isn't an '-I' switch in any of them) is the sort of thing that would usually only be done by root, as it might be considered abusive.

> I would like to be able to do this kind of granularity for some 
> special troubleshooting I am doing.

Perhaps you can be more specific about the troubleshooting.

> My question is a way to get a combined multi-probe graph like you get 
> on the summary screen on the detail page. I did some looking and 
> didn't see an obvious way to do this.

I don't know what the "summary screen" and the "detail page" are.
You have acess to the full source to do whatever you wish to it, but there's a lot of fairly densely coded Perl in there and that will be hard going if you aren't an experienced Perl programmer.

--

73,
Ged.


From spirrello at gmail.com  Tue Aug 28 03:43:29 2012
From: spirrello at gmail.com (Stefano Pirrello)
Date: Mon, 27 Aug 2012 21:43:29 -0400
Subject: [smokeping-users] Changing Steps of a Probe
Message-ID: <CAJ_tR7V_mc5sMnhPxdZnRjM4QCJ7rfsQ0MWockXnj6oe=r+tWw@mail.gmail.com>

Hi,

If I make a change to the "steps" of a probe, is there a way to save
and reference historical information?  I know when you change the step
value, you have to delete the data as it doesn't match up with the
historical information.

Thanks,
Stefano


From rb14060 at gmail.com  Tue Aug 28 04:24:18 2012
From: rb14060 at gmail.com (Ryan Becker)
Date: Mon, 27 Aug 2012 22:24:18 -0400
Subject: [smokeping-users] Changing Steps of a Probe
In-Reply-To: <CAJ_tR7V_mc5sMnhPxdZnRjM4QCJ7rfsQ0MWockXnj6oe=r+tWw@mail.gmail.com>
References: <CAJ_tR7V_mc5sMnhPxdZnRjM4QCJ7rfsQ0MWockXnj6oe=r+tWw@mail.gmail.com>
Message-ID: <CAAjykhY2Vp6qFnh6q2w0s3GMN07ZMM1esRs7SYbk5EdWASc9bQ@mail.gmail.com>

Hello,

You could just back up the data, but I don't believe it has any raw data,
just RRD files, which you would have to generate the graphs for yourself.

-Ryan

On Mon, Aug 27, 2012 at 9:43 PM, Stefano Pirrello <spirrello at gmail.com>wrote:

> Hi,
>
> If I make a change to the "steps" of a probe, is there a way to save
> and reference historical information?  I know when you change the step
> value, you have to delete the data as it doesn't match up with the
> historical information.
>
> Thanks,
> Stefano
>
> _______________________________________________
> 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/20120827/ca324719/attachment.htm 

From alter3d at alter3d.ca  Tue Aug 28 14:56:40 2012
From: alter3d at alter3d.ca (Peter Kristolaitis)
Date: Tue, 28 Aug 2012 08:56:40 -0400
Subject: [smokeping-users] Changing Steps of a Probe
In-Reply-To: <CAAjykhY2Vp6qFnh6q2w0s3GMN07ZMM1esRs7SYbk5EdWASc9bQ@mail.gmail.com>
References: <CAJ_tR7V_mc5sMnhPxdZnRjM4QCJ7rfsQ0MWockXnj6oe=r+tWw@mail.gmail.com>
	<CAAjykhY2Vp6qFnh6q2w0s3GMN07ZMM1esRs7SYbk5EdWASc9bQ@mail.gmail.com>
Message-ID: <503CC008.8020600@alter3d.ca>

It IS possible to 're-aggregate' the data from the old file into the new 
file if you write a custom script to do it.  By its nature, it's not a 
perfect transfer (e.g. if you had steps=12 before and you have steps=20 
now, and you have a sample that had 1 lost packet, do you scale up to 2 
lost packets or down to 1 in the new data?  Both results skew your 
percentages.   Plus, for the older samples, you're aggregating an 
aggregate, which itself loses accuracy...) but at least it gives you 
SOME kind of historical basis.

This approach can also be a significant amount of work as (AFAIK) no one 
has released a ready-made script to do it.  I've never been attached to 
my history enough to bother, and I try not to change my database 
settings after it's running anyways.

If you're really, really tied to your history and want to put the work 
into it, it is possible, however.

- Pete


On 8/27/2012 10:24 PM, Ryan Becker wrote:
> Hello,
>
> You could just back up the data, but I don't believe it has any raw 
> data, just RRD files, which you would have to generate the graphs for 
> yourself.
>
> -Ryan
>
> On Mon, Aug 27, 2012 at 9:43 PM, Stefano Pirrello <spirrello at gmail.com 
> <mailto:spirrello at gmail.com>> wrote:
>
>     Hi,
>
>     If I make a change to the "steps" of a probe, is there a way to save
>     and reference historical information?  I know when you change the step
>     value, you have to delete the data as it doesn't match up with the
>     historical information.
>
>     Thanks,
>     Stefano
>
>     _______________________________________________
>     smokeping-users mailing list
>     smokeping-users at lists.oetiker.ch
>     <mailto: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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120828/8714a9d9/attachment-0001.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4431 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120828/8714a9d9/attachment-0001.bin 

From klausman at schwarzvogel.de  Wed Aug 29 09:38:01 2012
From: klausman at schwarzvogel.de (Tobias Klausmann)
Date: Wed, 29 Aug 2012 09:38:01 +0200
Subject: [smokeping-users]  Re: ANNOUNCE: fping 3.3
In-Reply-To: <20120819211336.GA9836@schweikert.ch>
Message-ID: <20120829073801.GA15530@kaini.schwarzvogel.de>

David Schweikert wrote:
> * Output statistics to stdout instead of stderr (suggested by
> Simon Leinen, #9)

For the benefit of those who are not aware: this breaks Smokeping
(at least up to and including 2.6.8 since it expects this data on
stderr. My current workaround is a shell wrapper that simply does
1>&2 so data lands on stderr again.

Regards,
Tobias

-- 
Sent from aboard the Culture ship
	GCU You'll Thank Me Later


From Kumara_N at mahindrasatyam.com  Wed Aug 29 09:49:08 2012
From: Kumara_N at mahindrasatyam.com (Kumara_N)
Date: Wed, 29 Aug 2012 07:49:08 +0000
Subject: [smokeping-users] I want to use Smoketrace
Message-ID: <7814DBB8E0C2AB47B8CC9968E27CF8840ED6F8AC@HICMSATMBX005.mahindrasatyam.ad>

Hi,

I have a Smokeing setup in Windows based system. Now I want to use smoke trace with it. Can anyone help me in this regard.

Thx
Kumara

________________________________

DISCLAIMER:
This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120829/2a7bde4a/attachment.htm 

From tobi at oetiker.ch  Wed Aug 29 09:51:15 2012
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Wed, 29 Aug 2012 09:51:15 +0200 (CEST)
Subject: [smokeping-users] ANNOUNCE: fping 3.3
In-Reply-To: <20120829073801.GA15530@kaini.schwarzvogel.de>
References: <20120829073801.GA15530@kaini.schwarzvogel.de>
Message-ID: <alpine.DEB.2.02.1208290950440.29136@froburg.oetiker.ch>

Hoi Tobi,

Today Tobias Klausmann wrote:

> David Schweikert wrote:
> > * Output statistics to stdout instead of stderr (suggested by
> > Simon Leinen, #9)
>
> For the benefit of those who are not aware: this breaks Smokeping
> (at least up to and including 2.6.8 since it expects this data on
> stderr. My current workaround is a shell wrapper that simply does
> 1>&2 so data lands on stderr again.

habe soeben einen change auf github gepusht, damit sich das
konfigurieren laesst.

https://github.com/oetiker/SmokePing/commit/491498b57a427230069604d10b68073c0f6f5e33

lg
tobi

>
> Regards,
> Tobias
>
>

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900


From tobi at oetiker.ch  Wed Aug 29 09:54:49 2012
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Wed, 29 Aug 2012 09:54:49 +0200 (CEST)
Subject: [smokeping-users] I want to use Smoketrace
In-Reply-To: <7814DBB8E0C2AB47B8CC9968E27CF8840ED6F8AC@HICMSATMBX005.mahindrasatyam.ad>
References: <7814DBB8E0C2AB47B8CC9968E27CF8840ED6F8AC@HICMSATMBX005.mahindrasatyam.ad>
Message-ID: <alpine.DEB.2.02.1208290953160.29136@froburg.oetiker.ch>

Hi Kumara,

Today Kumara_N wrote:

> Hi,
>
> I have a Smokeing setup in Windows based system. Now I want to
> use smoke trace with it. Can anyone help me in this regard.

two things:

a) smoketrace is not developed anymore ... it has been superseeded
   by Remocular : www.remocular.org

b) I have no idea if anyone has ever tried (or managed) to get
   these two to work on a windows server ...

cheers
tobi


>
> Thx
> Kumara
>
> ________________________________
>
> DISCLAIMER:
> This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.
>

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900


From Kumara_N at mahindrasatyam.com  Wed Aug 29 10:02:08 2012
From: Kumara_N at mahindrasatyam.com (Kumara_N)
Date: Wed, 29 Aug 2012 08:02:08 +0000
Subject: [smokeping-users] I want to use Smoketrace
In-Reply-To: <alpine.DEB.2.02.1208290953160.29136@froburg.oetiker.ch>
References: <7814DBB8E0C2AB47B8CC9968E27CF8840ED6F8AC@HICMSATMBX005.mahindrasatyam.ad>
	<alpine.DEB.2.02.1208290953160.29136@froburg.oetiker.ch>
Message-ID: <7814DBB8E0C2AB47B8CC9968E27CF8840ED6F946@HICMSATMBX005.mahindrasatyam.ad>

Ok. Can anybody tell me how I can use remocular software to get the trace reports..

Thx
Kumara

-----Original Message-----
From: Tobias Oetiker [mailto:tobi at oetiker.ch]
Sent: Wednesday, August 29, 2012 1:25 PM
To: Kumara_N
Cc: smokeping-users at lists.oetiker.ch
Subject: Re: [smokeping-users] I want to use Smoketrace

Hi Kumara,

Today Kumara_N wrote:

> Hi,
>
> I have a Smokeing setup in Windows based system. Now I want to use
> smoke trace with it. Can anyone help me in this regard.

two things:

a) smoketrace is not developed anymore ... it has been superseeded
   by Remocular : www.remocular.org

b) I have no idea if anyone has ever tried (or managed) to get
   these two to work on a windows server ...

cheers
tobi


>
> Thx
> Kumara
>
> ________________________________
>
> DISCLAIMER:
> This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.
>

--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900


________________________________

DISCLAIMER:
This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.


From gregs at sloop.net  Wed Aug 29 10:23:42 2012
From: gregs at sloop.net (Gregory Sloop)
Date: Wed, 29 Aug 2012 01:23:42 -0700
Subject: [smokeping-users] I want to use Smoketrace
In-Reply-To: <7814DBB8E0C2AB47B8CC9968E27CF8840ED6F946@HICMSATMBX005.mahindrasatyam.ad>
References: <7814DBB8E0C2AB47B8CC9968E27CF8840ED6F8AC@HICMSATMBX005.mahindrasatyam.ad>
	<alpine.DEB.2.02.1208290953160.29136@froburg.oetiker.ch>
	<7814DBB8E0C2AB47B8CC9968E27CF8840ED6F946@HICMSATMBX005.mahindrasatyam.ad>
Message-ID: <1482294310.20120829012342@sloop.net>

Since all of about 10 minutes passed from the reply from Tobi to your
plea for "Can anybody tell me how I can use remocular software to get
the trace reports.." - I have to wonder....

Did you spend any time looking at the docs and trying anything before
asking for help?

---
Even if you did, are you asking for help in making it run on Windows,
or something else, because you don't make that clear at all.

If you're asking about running it on Windows, Tobi already said he's
unaware of anyone who got it running on Windows, so I'd guess it's
pretty unlikely anyone here will have better info.

I'm normally pretty easy on folks asking "newbie" questions - I know
I've done it more than a few times and probably more than a few when I
could have figured it out via more careful review of the docs and
poking around till something works...

But your line of inquiry just seemed pretty far over the "I don't want
to try much, won't someone please do it for me." line.


K> Ok. Can anybody tell me how I can use remocular software to get the trace reports..

K> Thx
K> Kumara



From ged at jubileegroup.co.uk  Wed Aug 29 11:23:58 2012
From: ged at jubileegroup.co.uk (G.W. Haywood)
Date: Wed, 29 Aug 2012 10:23:58 +0100 (BST)
Subject: [smokeping-users] ANNOUNCE: fping 3.3
In-Reply-To: <20120829073801.GA15530@kaini.schwarzvogel.de>
References: <20120829073801.GA15530@kaini.schwarzvogel.de>
Message-ID: <Pine.LNX.4.64.1208291020500.3200@mail5.jubileegroup.co.uk>

Hi there,

On Wed, 29 Aug 2012, Tobias Klausmann wrote:

> David Schweikert wrote:
>> * Output statistics to stdout instead of stderr (suggested by
>> Simon Leinen, #9)
>
> For the benefit of those who are not aware: this breaks Smokeping
> (at least up to and including 2.6.8 since it expects this data on
> stderr. My current workaround is a shell wrapper that simply does
> 1>&2 so data lands on stderr again.

Thanks Tobi.  There's quite a bit of fragility because of what I might
call the vagueness of the various ping-alike 'helpers', this isn't the
first time that something like this has cropped up.  Of course this is
not a criticism of Smokeping itself, but I wonder if the possibility
of this kind of issue should be more prominent in the documentation?

--

73,
Ged.

>
> Regards,
> Tobias
>
>


From david at schweikert.ch  Wed Aug 29 15:21:02 2012
From: david at schweikert.ch (David Schweikert)
Date: Wed, 29 Aug 2012 15:21:02 +0200
Subject: [smokeping-users] ANNOUNCE: fping 3.3
In-Reply-To: <20120829073801.GA15530@kaini.schwarzvogel.de>
References: <20120819211336.GA9836@schweikert.ch>
	<20120829073801.GA15530@kaini.schwarzvogel.de>
Message-ID: <20120829132102.GA18612@schweikert.ch>

On Wed, Aug 29, 2012 at 09:38:01 +0200, Tobias Klausmann wrote:
> > * Output statistics to stdout instead of stderr
> 
> For the benefit of those who are not aware: this breaks Smokeping
> (at least up to and including 2.6.8 since it expects this data on
> stderr. My current workaround is a shell wrapper that simply does
> 1>&2 so data lands on stderr again.

That was a mistake to change that behavior. I didn't realize that it
would break programs using it like this.

I will shortly release a new fping release (3.4) with that change
reverted and with a new option to put statistics on stdout.

Cheers
David


From ged at jubileegroup.co.uk  Wed Aug 29 23:50:46 2012
From: ged at jubileegroup.co.uk (G.W. Haywood)
Date: Wed, 29 Aug 2012 22:50:46 +0100 (BST)
Subject: [smokeping-users] ANNOUNCE: fping 3.3
In-Reply-To: <20120829132102.GA18612@schweikert.ch>
References: <20120819211336.GA9836@schweikert.ch>
	<20120829073801.GA15530@kaini.schwarzvogel.de>
	<20120829132102.GA18612@schweikert.ch>
Message-ID: <Pine.LNX.4.64.1208292246540.24807@mail5.jubileegroup.co.uk>

Hi there,

On Wed, 29 Aug 2012, David Schweikert wrote:

> ... I will shortly release a new fping release (3.4) ...

While you're working on that, please check the man page for the number
of bytes sent by default.  According to all the fping man pages that
I've seen, by default fping sends 56 bytes, the same as ping.  As far
as I can tell this is not the actual behaviour, the fpings that I have
here send 96 bytes.  I was puzzling over the large differences between
Somkeping graphs generated using fping and my manual ping RTTs.  This
appears to be the explaination.

--

73,
Ged.


From sab_arshad07 at yahoo.com  Thu Aug 30 15:27:46 2012
From: sab_arshad07 at yahoo.com (Saba Arshad)
Date: Thu, 30 Aug 2012 06:27:46 -0700 (PDT)
Subject: [smokeping-users] problem getting data on browser
Message-ID: <1346333266.70195.YahooMailNeo@web112814.mail.gq1.yahoo.com>

I am very much in trouble that my data has been generated in the folders that I specified in the config file of smokping as imgcache in the www folder but it is not coming in the browser as expected. please help me in this regard.

?
regards,
Saba Arshad
Bachelors in Electrical Engineering (Final year)
NUST-SEECS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20120830/45b15830/attachment.htm