headers
Marcos Teixeira | 1 Aug 2012 20:23
Picon
Favicon

Blank .

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
Permalink | Reply | 1 comment |
headers
Ryan Becker | 1 Aug 2012 20:30
Picon
Gravatar

Re: Blank .

>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
 

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 0 comments |
headers
Don Garrett | 5 Aug 2012 20:28
Picon
Favicon
Gravatar

Using Smokeping to measure uptime in minutes

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

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 0 comments |
headers
Nicolas KARP | 6 Aug 2012 15:23
Picon

After a lot of alerts, smokeping do not update the rrd anymore

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

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 4 comments |
headers
Bendtsen, Jon | 6 Aug 2012 15:28
Picon
Favicon

Re: After a lot of alerts, smokeping do not update the rrd anymore

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

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 1 comment |
headers
Nicolas KARP | 6 Aug 2012 15:54
Picon

Re: After a lot of alerts, smokeping do not update the rrd anymore

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



_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 0 comments |
headers
G.W. Haywood | 6 Aug 2012 16:59
Picon
Favicon

Re: After a lot of alerts, smokeping do not update the rrd anymore

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'),
    <at> log,
   '--lower-limit',( <at> log ? ($max->{$s}{$start} > 0.01) ? '0.001' : '0.0001' : '0'),
--- 1371,1377 ----
   '--title',$desc.$from,
   '--rigid',
! '--upper-limit', $max->{$s}{$start},
    <at> log,
   '--lower-limit',( <at> log ? ($max->{$s}{$start} > 0.01) ? '0.001' : '0.0001' : '0'),
----------------------------------------------------------------------

Apologies for any line wrapping.
Permalink | Reply | 1 comment |
headers
Nicolas KARP | 6 Aug 2012 17:08
Picon

Smokeping alarming and pattern

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


_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 0 comments |
headers
Nicolas KARP | 9 Aug 2012 13:44
Picon

Re: After a lot of alerts, smokeping do not update the rrd anymore

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'),
  <at> log,
  '--lower-limit',( <at> log ? ($max->{$s}{$start} > 0.01) ? '0.001' : '0.0001' : '0'),
--- 1371,1377 ----
  '--title',$desc.$from,
  '--rigid',
! '--upper-limit', $max->{$s}{$start},
  <at> log,
  '--lower-limit',( <at> log ? ($max->{$s}{$start} > 0.01) ? '0.001' : '0.0001' : '0'),
----------------------------------------------------------------------

Apologies for any line wrapping.

--

73,
Ged.

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 0 comments |
headers
samy.nashaat | 14 Aug 2012 15:46

Re: Smokeping Help | Master Slave config

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( <at> $y - 3, 12);

        my $imax1 = min( <at> $y - 3, 12);

        my $minlength = 3;

        my $maxlength = 27;

        LLxt if scalar <at> $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
Permalink | Reply | 1 comment |

Gmane