From jtaylor at redbanaus.com Tue Mar 2 02:40:34 2010 From: jtaylor at redbanaus.com (Jason Taylor) Date: Mon, 1 Mar 2010 17:40:34 -0800 Subject: [smokeping-users] tcpping Message-ID: When I try to tcpping from my debian machine, I get this response when I use the -C option. What am I doing wrong? it-tools:/usr/bin# ./tcpping -C www.google.com www.google.com : - - - - - - -^C it-tools:/usr/bin# ./tcpping www.google.com traceroute to www.google.com (74.125.19.106), 255 hops max, 40 byte packets seq 0: tcp response from nuq04s01-in-f106.1e100.net (74.125.19.106) 6.879 ms traceroute to www.google.com (74.125.19.99), 255 hops max, 40 byte packets seq 1: tcp response from nuq04s01-in-f99.1e100.net (74.125.19.99) 8.997 ms traceroute to www.google.com (74.125.19.104), 255 hops max, 40 byte packets seq 2: tcp response from nuq04s01-in-f104.1e100.net (74.125.19.104) 9.014 ms ^C it-tools:/usr/bin# -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100301/a56af016/attachment.htm From slyons at fxcm.com Wed Mar 3 03:38:39 2010 From: slyons at fxcm.com (Seth Lyons) Date: Tue, 2 Mar 2010 21:38:39 -0500 Subject: [smokeping-users] tcpping reporting in seconds Message-ID: Hi all - I saw that last March someone posted that his tcpping graphs were showing the correct values, but the graph was labeled in seconds instead of milliseconds. I am now having this problem as well. Does anyone know if it was ever resolved? One thing that is interesting to note is that the graphs for 3 hours, 30 hours, and 10 days are labeled in seconds, while the graph for 400 days is properly labeled in milliseconds. My system is: FreeBSD 8.0-RELEASE amd64 tcptraceroute-devel-1.5.b7 smokeping-2.4.2_5 tcpping v1.7 apache-2.2.14_5 Any help is appreciated. Thanks. Seth -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100302/6539d9d0/attachment.htm From tslura at gmail.com Wed Mar 3 06:53:58 2010 From: tslura at gmail.com (TS Lura) Date: Wed, 3 Mar 2010 05:53:58 +0000 Subject: [smokeping-users] 3 issues: configure, timer, and debian package in smokeping 2.3.6 Message-ID: <701659a81003022153g1c3f79d0ge5216cbde629814b@mail.gmail.com> Dear smokeping community, Maybe you guys could tell me if this is a bug or not. And/or if it has been fixed in a later release. 1. Configure ---------------------------------------------------------------- I am running Debian testing (squeeze), and I have apt-get installed smokeping. I had problems with getting the charts to show. At first I got the tiny overview charts, but not the larger detailed one. After going RavingRabbit on my system I found out that: This works -------------------------------- Config, Targets file: -------------------------------- ++ googlecouk menu = google.co.uk title = google.co.uk host = google.co.uk -------------------------------- This does not work -------------------------------- ++ google.co.uk menu = google.co.uk title = google.co.uk host = google.co.uk -------------------------------- 2. Timer ---------------------------------------------------------------- I use the EchoPingHttp probe as well, and I get these errors sometimes. Mar 3 01:37:36 pwwrpad smokeping[9285]: EchoPingHttp: www.thewebsite.comtimeout (6 s) reached, killing the probe. Is there a way to increase the timer? 3. Debian package, testing(squeeze) ---------------------------------------------------------------- And rrdtools did not get installed when I did the apt-get install smokeping. I also had to go into the smokeping.cgi and set the lib pointer to rrdtools up manually. On purpose? Anyways thanks for the good software! Cheers, TSLura GNU/Debian - Testing [0531][root at pwwrpad:/var/lib/smokeping/Local]$ smokeping --version 2.003006 [0539][root at pwwrpad:/var/lib/smokeping/Local]$ uname -a Linux pwwrpad 2.6.26-2-686 #1 SMP Wed Feb 10 08:59:21 UTC 2010 i686 GNU/Linux [0539][root at pwwrpad:/var/lib/smokeping/Local]$ rrdtool -V RRDtool 1.3.8 Copyright 1997-2009 by Tobias Oetiker Compiled Jun 2 2009 18:22:37 [0539][root at pwwrpad:/var/lib/smokeping/Local]$ perl -V Summary of my perl5 (revision 5 version 10 subversion 1) configuration: Platform: osname=linux, osvers=2.6.26-2-amd64, archname=i486-linux-gnu-thread-multi uname='linux biber 2.6.26-2-amd64 #1 smp tue jan 12 22:12:20 utc 2010 i686 gnulinux -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100303/aa07892e/attachment-0001.htm From alter3d at alter3d.ca Wed Mar 3 14:07:39 2010 From: alter3d at alter3d.ca (Peter Kristolaitis) Date: Wed, 03 Mar 2010 08:07:39 -0500 Subject: [smokeping-users] 3 issues: configure, timer, and debian package in smokeping 2.3.6 In-Reply-To: <701659a81003022153g1c3f79d0ge5216cbde629814b@mail.gmail.com> References: <701659a81003022153g1c3f79d0ge5216cbde629814b@mail.gmail.com> Message-ID: <4B8E5F1B.4050007@alter3d.ca> Responses inline... On 3/3/2010 12:53 AM, TS Lura wrote: > Dear smokeping community, > > Maybe you guys could tell me if this is a bug or not. And/or if it has > been fixed in a later release. > > 1. Configure > ---------------------------------------------------------------- > > I am running Debian testing (squeeze), and I have apt-get installed > smokeping. > > I had problems with getting the charts to show. At first I got the > tiny overview charts, but not the larger detailed one. > > After going RavingRabbit on my system I found out that: > > > > This works > -------------------------------- > Config, Targets file: > -------------------------------- > ++ googlecouk > > menu = google.co.uk > title = google.co.uk > host = google.co.uk > -------------------------------- > > > This does not work > > -------------------------------- > ++ google.co.uk > > menu = google.co.uk > title = google.co.uk > host = google.co.uk > -------------------------------- This is by design and is documented in the configuration guide; section names must match /[-_0-9a-zA-Z]+/. The period character is used as a hierarchy separator in the web front end, and thus cannot be used in individual names. > > 2. Timer > ---------------------------------------------------------------- > I use the EchoPingHttp probe as well, and I get these errors sometimes. > > Mar 3 01:37:36 pwwrpad smokeping[9285]: EchoPingHttp: > www.thewebsite.com timeout (6 s) reached, > killing the probe. > > Is there a way to increase the timer? Yes; change the probe options. See http://oss.oetiker.ch/smokeping/probe/EchoPingHttp.en.html > > > 3. Debian package, testing(squeeze) > ---------------------------------------------------------------- > > And rrdtools did not get installed when I did the apt-get install > smokeping. > I also had to go into the smokeping.cgi and set the lib pointer to > rrdtools up manually. > On purpose? Squeeze is in 'testing' for a reason. ;) File a bug report with the package maintainers. > > > Anyways thanks for the good software! > > > Cheers, > > TSLura > > GNU/Debian - Testing > > [0531][root at pwwrpad:/var/lib/smokeping/Local]$ smokeping --version > 2.003006 > > [0539][root at pwwrpad:/var/lib/smokeping/Local]$ uname -a > Linux pwwrpad 2.6.26-2-686 #1 SMP Wed Feb 10 08:59:21 UTC 2010 i686 > GNU/Linux > > [0539][root at pwwrpad:/var/lib/smokeping/Local]$ rrdtool -V > RRDtool 1.3.8 Copyright 1997-2009 by Tobias Oetiker > > Compiled Jun 2 2009 18:22:37 > > [0539][root at pwwrpad:/var/lib/smokeping/Local]$ perl -V > Summary of my perl5 (revision 5 version 10 subversion 1) configuration: > Platform: > osname=linux, osvers=2.6.26-2-amd64, > archname=i486-linux-gnu-thread-multi > uname='linux biber 2.6.26-2-amd64 #1 smp tue jan 12 22:12:20 utc > 2010 i686 gnulinux > > > _______________________________________________ > 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/20100303/505ee3b7/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6444 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100303/505ee3b7/attachment.bin From slyons at fxcm.com Wed Mar 3 19:51:40 2010 From: slyons at fxcm.com (Seth Lyons) Date: Wed, 3 Mar 2010 13:51:40 -0500 Subject: [smokeping-users] update: tcpping reporting in seconds In-Reply-To: References: Message-ID: So I went back to the original TCPPing.pm file after trying to make a few modifications, and now there is no data at all in the graphs. smokeping -debug shows: TCPPing: Executing /usr/local/bin/tcpping -C -x 5 193.108.158.113 443 TCPPing: TCPPing.pm: pingone: Got output: '193.108.158.113 : 8.188 8.192 8.136 8.158 42.831' TCPPing: TCPPing.pm: pingone: Parsed times: : 8.188 8.192 8.136 8.158 42.831 I included the debugging found here: https://lists.oetiker.ch/pipermail/smokeping-users/2008-June/003158.html A sample of rrdtool info XXXX shows: ds[ping1].value = NaN Please advise. From: Seth Lyons Sent: Tuesday, March 02, 2010 9:39 PM To: smokeping-users at lists.oetiker.ch Subject: tcpping reporting in seconds Hi all - I saw that last March someone posted that his tcpping graphs were showing the correct values, but the graph was labeled in seconds instead of milliseconds. I am now having this problem as well. Does anyone know if it was ever resolved? One thing that is interesting to note is that the graphs for 3 hours, 30 hours, and 10 days are labeled in seconds, while the graph for 400 days is properly labeled in milliseconds. My system is: FreeBSD 8.0-RELEASE amd64 tcptraceroute-devel-1.5.b7 smokeping-2.4.2_5 tcpping v1.7 apache-2.2.14_5 Any help is appreciated. Thanks. Seth -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100303/fe842d12/attachment-0001.htm From wimpunk+smoke at gmail.com Thu Mar 4 15:05:53 2010 From: wimpunk+smoke at gmail.com (wimpunk) Date: Thu, 4 Mar 2010 15:05:53 +0100 Subject: [smokeping-users] Slave data not updated at server side Message-ID: <5c43128e1003040605sbf8d3dcw2c75026290ad54c8@mail.gmail.com> Hi, I'm looking at a situation which have been handled before in this list but the solutions offered doesn't seem to work for me. As far as I can see, client side works pretty correct. Running `/usr/sbin/smokeping --master-url=http://megaton/cgi-bin/smokeping --cache-dir=/var/cache/smokeping/ --shared-secret=/etc/smokeping/secret.txt --debug --nodaemon` I get this result: Sent data to Server and got new config in response. Smokeping version 2.004002 successfully launched. Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for that. FPing: probing 9 targets with step 300 s and offset 79 s. FPing: Executing /usr/sbin/fping -C 20 -q -B1 -r1 -i10 10.129.88.142 10.129.88.211 10.134.8.4 10.134.10.19 10.134.10.18 10.134.8.34 10.129.88.10 10.134.10.42 10.134.8.10 FPing: Got fping output: '10.129.88.142 : 6.32 5.25 4.88 4.39 4.90 4.77 4.76 4.62 4.63 14.64 4.63 5.29 5.13 5.75 4.87 10.28 4.39 5.90 6.26 4.51' FPing: Got fping output: '10.129.88.211 : 5.00 4.51 10.16 4.39 4.57 4.63 9.39 15.13 5.15 5.52 5.01 5.02 4.38 16.12 8.15 9.88 8.24 11.04 12.84 11.92' FPing: Got fping output: '10.134.8.4 : 0.37 0.35 0.35 0.36 0.37 0.36 0.36 0.34 0.36 0.37 0.36 0.36 0.36 0.36 0.35 0.36 0.36 0.36 0.36 0.37' FPing: Got fping output: '10.134.10.19 : 0.11 0.10 0.11 0.11 0.11 0.11 0.11 0.11 0.11 0.11 0.11 0.11 0.11 0.11 0.11 0.11 0.11 0.11 0.11 0.11' FPing: Got fping output: '10.134.10.18 : 0.03 0.02 0.02 0.02 0.02 0.02 0.03 0.03 0.02 0.02 0.02 0.02 0.02 0.02 0.02 0.02 0.02 0.02 0.02 0.02' FPing: Got fping output: '10.134.8.34 : 5.84 0.19 0.19 0.19 0.19 0.19 0.19 0.19 0.19 0.20 0.20 0.20 0.19 0.19 0.19 0.18 0.19 0.19 0.20 0.19' FPing: Got fping output: '10.129.88.10 : 5.15 5.89 5.92 4.78 5.29 5.03 6.02 5.87 4.76 5.87 5.67 8.91 14.14 28.01 4.88 5.15 8.00 10.00 5.90 5.52' FPing: Got fping output: '10.134.10.42 : 0.13 0.13 0.11 0.13 0.11 0.11 0.13 0.15 0.13 0.13 0.11 0.13 0.11 0.11 0.11 0.11 0.11 0.11 0.12 0.11' FPing: Got fping output: '10.134.8.10 : 0.52 5.75 0.90 0.52 0.52 0.51 0.52 0.51 0.51 0.51 0.52 0.54 0.50 0.51 0.52 0.51 0.51 0.49 6.32 4.82' Sent data to Server. Server said OK As far as I can tell, this is the result needed. Unfortunately, the data doesn't get stored at the server. Looking at the head of the rrd file with ` rrdtool dump /var/lib/smokeping/data/LocalNetwork/router~f1.rrd | head -10` I get next result: 0003 300 1267624232 uptime GAUGE 600 The lastupdate value is the date I configured the slave, it is not the date I tested the configuration. I tried to change the rights on the file to 777 hoping to fix it but it didn't helped. I even tried to fix it by changing the ownership to www but it didn't helped me either. Does anyone has any suggestion what I missed? Kind regards, wimpunk. -- I would love to change the world, but they wont give me the source code. From blahu77 at gmail.com Mon Mar 8 11:33:01 2010 From: blahu77 at gmail.com (Mateusz Blaszczyk) Date: Mon, 8 Mar 2010 10:33:01 +0000 Subject: [smokeping-users] CiscoRTTMonEchoICMP probe and IOS 15.x Message-ID: <383357751003080233n12756926lb527eb173281baa7@mail.gmail.com> Hello List, Just wanted to give a heads up on the issue I had with CiscoRTTMonEchoICMP probe and new IOS version 15.0. I have tested and confirmed the problem on 15.0(1)M on both c7206VXR and c7301 on both adv ip serv and sp serv train. The main problem is that for some reason the minimal acceptable value for rttMonCtrlAdminTimeout (or .1.3.6.1.4.1.9.9.42.1.2.1.1.7) is now 5000ms (btw equal to MIB default value). I propose to increase the variable pingtimeout to 5. --- /tmp/CiscoRTTMonEchoICMP.pm 2010-03-08 10:17:18.000000000 +0000 +++ CiscoRTTMonEchoICMP.pm 2010-03-05 15:53:39.000000000 +0000 @@ -75,7 +75,7 @@ } } -my $pingtimeout =2; +my $pingtimeout =5; sub new($$$) { Also the probe calculated timeout must be more then 100s so the probe configuration should be at least: +CiscoRTTMonEchoICMP timeout = 10 That way the probe timeout is 201s, enough for all packets to be send and response to be collected. Problem in detail: Any value less the 5000ms results in snmp row values to be refused with error commitFailed: Mar 5 15:52:30 server1 smokeping[20588]: SNMP Error: Received SNMP response with error code error status: commitFailed index 1 (OID: 1.3.6.1.4.1.9.9.42.1.2.1.1.9.20588) SNMPv2c_Session (remote host: "router1" [IP.IP.IP.IP].161) community: "community1" request ID: 2130628395 PDU bufsize: 8000 bytes timeout: 2s retries: 5 backoff: 1) at /usr/share/perl5/SNMP_util.pm line 828 On cisco side it is failing on the third pass of the snmp oid values: rttMonCtrlAdminTimeout.$row is set to 2000: Mar 5 11:58:15.900: SNMP: Packet received via UDP from IP.IP.IP.IP on GigabitEthernet0/0 Mar 5 11:58:15.900: SNMP: Set request, reqid -154319046, errstat 0, erridx 0 rttMonCtrlAdminStatus.8147 = 5 rttMonCtrlAdminRttType.8147 = 1 rttMonEchoAdminProtocol.8147 = 2 rttMonEchoAdminTargetAddress.8147 = XX.XX.XX.XX rttMonCtrlAdminTimeout.8147 = 2000 rttMonCtrlAdminFrequency.8147 = 2 rttMonHistoryAdminNumBuckets.8147 = 20 rttMonHistoryAdminNumLives.8147 = 1 rttMonHistoryAdminFilter.8147 = 2 rttMonEchoAdminPktDataRequestSize.8147 = 48 rttMonScheduleAdminRttStartTime.8147 = 1 rttMonScheduleAdminRttLife.8147 = 43 rttMonScheduleAdminConceptRowAgeout.8147 = 60 rttMonEchoAdminTOS.8147 = 0 rttMonCtrlAdminNvgen.8147 = 2 SrDoSnmp: received set pdu CheckMIBView: OID is in MIB view. set_row_status: completed successfully. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. do_sets: pass 1 of set request processing done do_sets: pass 2 of set request processing done do_sets: set failed, undoing make_error_pdu: No variables were updated. The correct minimum value of 5000ms: Mar 5 15:51:43.262: SNMP: Packet received via UDP from IP.IP.IP.IP on GigabitEthernet0/0 Mar 5 15:51:43.262: SNMP: Set request, reqid -1506387565, errstat 0, erridx 0 rttMonCtrlAdminStatus.25137 = 5 rttMonCtrlAdminRttType.25137 = 1 rttMonEchoAdminProtocol.25137 = 2 rttMonEchoAdminTargetAddress.25137 = XX.XX.XX.XX rttMonCtrlAdminTimeout.25137 = 5000 rttMonCtrlAdminFrequency.25137 = 5 rttMonHistoryAdminNumBuckets.25137 = 20 rttMonHistoryAdminNumLives.25137 = 1 rttMonHistoryAdminFilter.25137 = 2 rttMonEchoAdminPktDataRequestSize.25137 = 48 rttMonScheduleAdminRttStartTime.25137 = 1 rttMonScheduleAdminRttLife.25137 = 103 rttMonScheduleAdminConceptRowAgeout.25137 = 60 rttMonEchoAdminTOS.25137 = 0 rttMonCtrlAdminNvgen.25137 = 2 SrDoSnmp: received set pdu CheckMIBView: OID is in MIB view. set_row_status: completed successfully. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. CheckMIBView: OID is in MIB view. do_sets: pass 1 of set request processing done do_sets: pass 2 of set request processing done do_sets: pass 3 of set request processing done Best Regards, -mat From tobi at oetiker.ch Mon Mar 8 17:49:16 2010 From: tobi at oetiker.ch (Tobias Oetiker) Date: Mon, 8 Mar 2010 17:49:16 +0100 (CET) Subject: [smokeping-users] CiscoRTTMonEchoICMP probe and IOS 15.x In-Reply-To: <383357751003080233n12756926lb527eb173281baa7@mail.gmail.com> References: <383357751003080233n12756926lb527eb173281baa7@mail.gmail.com> Message-ID: Hi Mateusz, Today Mateusz Blaszczyk wrote: > Hello List, > > Just wanted to give a heads up on the issue I had with > CiscoRTTMonEchoICMP probe and new IOS version 15.0. > I have tested and confirmed the problem on 15.0(1)M on both c7206VXR > and c7301 on both adv ip serv and sp serv train. > > The main problem is that for some reason the minimal acceptable value > for rttMonCtrlAdminTimeout (or .1.3.6.1.4.1.9.9.42.1.2.1.1.7) is now > 5000ms (btw equal to MIB default value). > > I propose to increase the variable pingtimeout to 5. > > --- /tmp/CiscoRTTMonEchoICMP.pm 2010-03-08 10:17:18.000000000 +0000 > +++ CiscoRTTMonEchoICMP.pm 2010-03-05 15:53:39.000000000 +0000 > @@ -75,7 +75,7 @@ > } > } > > -my $pingtimeout =2; > +my $pingtimeout =5; > > sub new($$$) > { > > > Also the probe calculated timeout must be more then 100s so the probe > configuration should be at least: > > +CiscoRTTMonEchoICMP > timeout = 10 > > That way the probe timeout is 201s, enough for all packets to be send > and response to be collected. > > > Problem in detail: > [...] I don't have such a router at my disposal, but I'll be glad to integrate your patch ... not sure what you mean with the timeout of 100s ... this seems a rather long time to me ... especially as you mention $pingtimeout=5. how would your complete patch look like ? 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 slyons at fxcm.com Mon Mar 8 17:52:10 2010 From: slyons at fxcm.com (Seth Lyons) Date: Mon, 8 Mar 2010 11:52:10 -0500 Subject: [smokeping-users] update: tcpping reporting in seconds In-Reply-To: References: Message-ID: Hi - does anyone have any information/help on this issue? Thanks. Seth From: Seth Lyons Sent: Wednesday, March 03, 2010 1:52 PM To: 'smokeping-users at lists.oetiker.ch' Subject: update: tcpping reporting in seconds So I went back to the original TCPPing.pm file after trying to make a few modifications, and now there is no data at all in the graphs. smokeping -debug shows: TCPPing: Executing /usr/local/bin/tcpping -C -x 5 193.108.158.113 443 TCPPing: TCPPing.pm: pingone: Got output: '193.108.158.113 : 8.188 8.192 8.136 8.158 42.831' TCPPing: TCPPing.pm: pingone: Parsed times: : 8.188 8.192 8.136 8.158 42.831 I included the debugging found here: https://lists.oetiker.ch/pipermail/smokeping-users/2008-June/003158.html A sample of rrdtool info XXXX shows: ds[ping1].value = NaN Please advise. From: Seth Lyons Sent: Tuesday, March 02, 2010 9:39 PM To: smokeping-users at lists.oetiker.ch Subject: tcpping reporting in seconds Hi all - I saw that last March someone posted that his tcpping graphs were showing the correct values, but the graph was labeled in seconds instead of milliseconds. I am now having this problem as well. Does anyone know if it was ever resolved? One thing that is interesting to note is that the graphs for 3 hours, 30 hours, and 10 days are labeled in seconds, while the graph for 400 days is properly labeled in milliseconds. My system is: FreeBSD 8.0-RELEASE amd64 tcptraceroute-devel-1.5.b7 smokeping-2.4.2_5 tcpping v1.7 apache-2.2.14_5 Any help is appreciated. Thanks. Seth -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100308/99a91dcb/attachment.htm From tobi at oetiker.ch Mon Mar 8 17:55:08 2010 From: tobi at oetiker.ch (Tobias Oetiker) Date: Mon, 8 Mar 2010 17:55:08 +0100 (CET) Subject: [smokeping-users] update: tcpping reporting in seconds In-Reply-To: References: Message-ID: Hi Seth, maybe there are different output formats in tcpping ? we had that with fping and added compensation to the module ... just guessing. cheers tobi > Hi - does anyone have any information/help on this issue? > > Thanks. > > Seth > > From: Seth Lyons > Sent: Wednesday, March 03, 2010 1:52 PM > To: 'smokeping-users at lists.oetiker.ch' > Subject: update: tcpping reporting in seconds > > So I went back to the original TCPPing.pm file after trying to make a few modifications, and now there is no data at all in the graphs. > > smokeping -debug shows: > TCPPing: Executing /usr/local/bin/tcpping -C -x 5 193.108.158.113 443 > TCPPing: TCPPing.pm: pingone: Got output: '193.108.158.113 : 8.188 8.192 8.136 8.158 42.831' > TCPPing: TCPPing.pm: pingone: Parsed times: : 8.188 8.192 8.136 8.158 42.831 > > I included the debugging found here: https://lists.oetiker.ch/pipermail/smokeping-users/2008-June/003158.html > > A sample of rrdtool info XXXX shows: > ds[ping1].value = NaN > > Please advise. > > From: Seth Lyons > Sent: Tuesday, March 02, 2010 9:39 PM > To: smokeping-users at lists.oetiker.ch > Subject: tcpping reporting in seconds > > Hi all - > > I saw that last March someone posted that his tcpping graphs were showing the correct values, but the graph was labeled in seconds instead of milliseconds. I am now having this problem as well. Does anyone know if it was ever resolved? One thing that is interesting to note is that the graphs for 3 hours, 30 hours, and 10 days are labeled in seconds, while the graph for 400 days is properly labeled in milliseconds. > > My system is: > FreeBSD 8.0-RELEASE amd64 > tcptraceroute-devel-1.5.b7 > smokeping-2.4.2_5 > tcpping v1.7 > apache-2.2.14_5 > > Any help is appreciated. > > Thanks. > > Seth > -- 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 slyons at fxcm.com Mon Mar 8 17:56:52 2010 From: slyons at fxcm.com (Seth Lyons) Date: Mon, 8 Mar 2010 11:56:52 -0500 Subject: [smokeping-users] update: tcpping reporting in seconds In-Reply-To: References: Message-ID: Hi Tobi -- thanks for your reply. The wrong label was a result of me trying to make some changes to the tccping probe and the tcpping script. Now that I'm back to the original probe and script, I have no data at all. Thanks. -----Original Message----- From: Tobias Oetiker [mailto:tobi at oetiker.ch] Sent: Monday, March 08, 2010 11:55 AM To: Seth Lyons Cc: smokeping-users at lists.oetiker.ch Subject: Re: [smokeping-users] update: tcpping reporting in seconds Hi Seth, maybe there are different output formats in tcpping ? we had that with fping and added compensation to the module ... just guessing. cheers tobi > Hi - does anyone have any information/help on this issue? > > Thanks. > > Seth > > From: Seth Lyons > Sent: Wednesday, March 03, 2010 1:52 PM > To: 'smokeping-users at lists.oetiker.ch' > Subject: update: tcpping reporting in seconds > > So I went back to the original TCPPing.pm file after trying to make a few modifications, and now there is no data at all in the graphs. > > smokeping -debug shows: > TCPPing: Executing /usr/local/bin/tcpping -C -x 5 193.108.158.113 443 > TCPPing: TCPPing.pm: pingone: Got output: '193.108.158.113 : 8.188 8.192 8.136 8.158 42.831' > TCPPing: TCPPing.pm: pingone: Parsed times: : 8.188 8.192 8.136 8.158 42.831 > > I included the debugging found here: https://lists.oetiker.ch/pipermail/smokeping-users/2008-June/003158.html > > A sample of rrdtool info XXXX shows: > ds[ping1].value = NaN > > Please advise. > > From: Seth Lyons > Sent: Tuesday, March 02, 2010 9:39 PM > To: smokeping-users at lists.oetiker.ch > Subject: tcpping reporting in seconds > > Hi all - > > I saw that last March someone posted that his tcpping graphs were showing the correct values, but the graph was labeled in seconds instead of milliseconds. I am now having this problem as well. Does anyone know if it was ever resolved? One thing that is interesting to note is that the graphs for 3 hours, 30 hours, and 10 days are labeled in seconds, while the graph for 400 days is properly labeled in milliseconds. > > My system is: > FreeBSD 8.0-RELEASE amd64 > tcptraceroute-devel-1.5.b7 > smokeping-2.4.2_5 > tcpping v1.7 > apache-2.2.14_5 > > Any help is appreciated. > > Thanks. > > Seth > -- 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 blahu77 at gmail.com Mon Mar 8 22:00:55 2010 From: blahu77 at gmail.com (Mateusz Blaszczyk) Date: Mon, 8 Mar 2010 21:00:55 +0000 Subject: [smokeping-users] CiscoRTTMonEchoICMP probe and IOS 15.x In-Reply-To: References: <383357751003080233n12756926lb527eb173281baa7@mail.gmail.com> Message-ID: <383357751003081300v67621c9exf8d2360d51243663@mail.gmail.com> Tobi, >> > [...] > > I don't have such a router at my disposal, but I'll be glad to > integrate your patch ... not sure what you mean with the timeout of > 100s ... this seems a rather long time to me ... especially as you > mention $pingtimeout=5. > well - I am talking about this (probe timeout, not target timeout) probes/basefork.pm:168 # we add 1 so that the probes doing their own timeout handling # have time to do it even in the worst case my $timeout = $maxpings * $maxtimeout + 1; 20 pings * 5s + 1 = 101 so default $timeout==5 for probe is not enough So that's why I have suggested $timeout for probe == 10. there are a lot timeouts here :) > how would your complete patch look like ? > the probes/basefork.pm is a generic file for all probes so I assume that only the one that I have posted before. Not sure if I can specify the default probe timeout in each probe source file? --- /tmp/CiscoRTTMonEchoICMP.pm ? ? ? 2010-03-08 10:17:18.000000000 +0000 +++ CiscoRTTMonEchoICMP.pm ? ?2010-03-05 15:53:39.000000000 +0000 @@ -75,7 +75,7 @@ ? ? ? } ?} -my $pingtimeout =2; +my $pingtimeout =5; sub new($$$) { Best Regards, -mat From tobi at oetiker.ch Tue Mar 9 09:12:16 2010 From: tobi at oetiker.ch (Tobias Oetiker) Date: Tue, 9 Mar 2010 09:12:16 +0100 (CET) Subject: [smokeping-users] CiscoRTTMonEchoICMP probe and IOS 15.x In-Reply-To: <383357751003081300v67621c9exf8d2360d51243663@mail.gmail.com> References: <383357751003080233n12756926lb527eb173281baa7@mail.gmail.com> <383357751003081300v67621c9exf8d2360d51243663@mail.gmail.com> Message-ID: Hi Mateusz, iiks, this is a bit twisted I see ... without going into brain surgery, how about this: Index: CiscoRTTMonEchoICMP.pm =================================================================== --- CiscoRTTMonEchoICMP.pm (revision 1087) +++ CiscoRTTMonEchoICMP.pm (working copy) @@ -59,7 +59,7 @@ The above configuration grants SNMP read-write only to 10.37.3.5 (the smokeping host) and only to the ciscoRttMon MIB tree. The probe does not need access to SNMP variables outside the RttMon tree. DOC bugs => < < @@ -75,7 +75,7 @@ } } -my $pingtimeout =2; +my $pingtimeout = 5; sub new($$$) { @@ -274,6 +274,12 @@ execute the pings, as well as the SNMP community string on the router. DOC }, + timeout => { + _re => '\d+', + _example => 15, + _default => $pingtimeout+10, + _doc => "How long a single RTTMonEcho ICMP 'ping' take at maximum plus 10 seconds to spare. Since we control our own timeout the only purpose of this is to not have us killed by the ping method from basefork.", + }, iosint => { _example => '10.33.22.11', _doc => < Tobi, > > > >> > > [...] > > > > I don't have such a router at my disposal, but I'll be glad to > > integrate your patch ... not sure what you mean with the timeout of > > 100s ... this seems a rather long time to me ... especially as you > > mention $pingtimeout=5. > > > > well - I am talking about this (probe timeout, not target timeout) > > probes/basefork.pm:168 > # we add 1 so that the probes doing their own timeout handling > # have time to do it even in the worst case > my $timeout = $maxpings * $maxtimeout + 1; > > 20 pings * 5s + 1 = 101 so default $timeout==5 for probe is not enough > > So that's why I have suggested $timeout for probe == 10. > > there are a lot timeouts here :) > > > how would your complete patch look like ? > > > > the probes/basefork.pm is a generic file for all probes so I assume > that only the one that I have posted before. Not sure if I can specify > the default probe timeout in each probe source file? > > > --- /tmp/CiscoRTTMonEchoICMP.pm ? ? ? 2010-03-08 10:17:18.000000000 +0000 > +++ CiscoRTTMonEchoICMP.pm ? ?2010-03-05 15:53:39.000000000 +0000 > @@ -75,7 +75,7 @@ > ? ? ? } > ?} > > -my $pingtimeout =2; > +my $pingtimeout =5; > > sub new($$$) > { > > > Best Regards, > > -mat > > -- 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 jjackson at aninetworks.net Tue Mar 9 16:54:14 2010 From: jjackson at aninetworks.net (Joseph Jackson) Date: Tue, 9 Mar 2010 07:54:14 -0800 Subject: [smokeping-users] exclude hosts from charts. Message-ID: <695277448C537A469D28FF68D0938C8372F41A4FFE@EXMBX04.exchhosting.com> Is there any way to exclude hosts from the charts? I have a few hosts that on the end of high latency links and aren't as mission critical. Thanks! Joseph From blahu77 at gmail.com Tue Mar 9 17:39:48 2010 From: blahu77 at gmail.com (Mateusz Blaszczyk) Date: Tue, 9 Mar 2010 16:39:48 +0000 Subject: [smokeping-users] CiscoRTTMonEchoICMP probe and IOS 15.x In-Reply-To: References: <383357751003080233n12756926lb527eb173281baa7@mail.gmail.com> <383357751003081300v67621c9exf8d2360d51243663@mail.gmail.com> Message-ID: <383357751003090839v7ecf516fne618baa5a33bb7b1@mail.gmail.com> Tobias, > iiks, this is a bit twisted I see ... without going into brain > surgery, how about this: > > Index: CiscoRTTMonEchoICMP.pm > =================================================================== [...] > + _default => $pingtimeout+10, > + _doc => "How long a single RTTMonEcho ICMP 'ping' take at maximum plus 10 seconds to spare. Since we control our own timeout the only purpose of this is to not have us killed by the ping method from basefork.", > + I understand that this is a mistake, it should be + _default => $pingtimeout+5, + _doc => "How long a single RTTMonEcho ICMP 'ping' take at maximum plus 5 seconds to spare. Since we control our own timeout the only purpose of this is to not have us killed by the ping method from basefork.", according to the below: > the idea is to set the timeout 'per ping' to pingtimeout+5 seconds > ... this may be a bit of a long timeout but since we control our own time anyway it will never hit. > apart from that as I understand the code it looks ok. I will test it now and let you know the results Best Regards, -mat From robert.mersberger at goldenliving.com Tue Mar 9 17:56:38 2010 From: robert.mersberger at goldenliving.com (Mersberger, Robert) Date: Tue, 9 Mar 2010 10:56:38 -0600 Subject: [smokeping-users] Is there a probe that I can use to get RRT between 2 Cisco routes. Message-ID: <77AF43BAFA571044A7520788C54EDDEB02831E80D3@GLEXCH04401.GoldenLiving.Com> Is this possible with Smokeping. I was wondering if you could provide me with answers and guidance about using Smokeping. I am currently running version 20070126 on Linux 2.2.11.4-21-bibsmp server using rrdtools. I would like to upgrade to either the latest or newer version of Smokeping but have limited experience working with any Unix. I took over this server and application after the prior server owner left the company. 1. What do I need to do to accomplish this upgrade and keep or migrate my current data? 2. Is there a probe that will allow me to capture RRT between two remote routers. primary is in California and Other is in OHIO. My server is in Arkansas and we use bgp and mpls for our backbone. All router are Cisco 2811's I would appreciate any help or advice you could provide. Thanks Robert Mersberger LAN Consultant, Information Technology Phone 479-201-3442 Fax 479-478-3837 Email robert.mersberger at goldenliving.com www.Goldenliving.com Golden Living 1000 Fianna Way Fort Smith, AR 72919 ________________________________ Please consider the environment before printing this e-mail. CONFIDENTIAL NOTICE: This e-mail message and any attachment(s) (collectively, this 'Email') are intended only for the confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient named above or an agent responsible for delivering it to the intended recipient named above, you have received this Email in error. Please notify the sender immediately and permanently delete this Email and any copies thereof. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100309/eeaf3ae0/attachment-0001.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: Mersberger, Robert.vcf Type: text/x-vcard Size: 241 bytes Desc: Mersberger, Robert.vcf Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100309/eeaf3ae0/attachment-0001.vcf From hardenrm at uiuc.edu Tue Mar 9 20:38:11 2010 From: hardenrm at uiuc.edu (Ryan Harden) Date: Tue, 09 Mar 2010 13:38:11 -0600 Subject: [smokeping-users] Alerts mailtemplate <##ALERT##> output Message-ID: <4B96A3A3.8090105@uiuc.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ## Resent from the address I'm actually subscribed by, so my apologies if this is a duplicate. ## In setting up my mailtemplate for smokeping alerts I assumed that <##ALERT##> would display the name of the "Target" that triggered the alert. This is based on the documentation definition of "<##ALERT##> - - target name" Instead it prints the name of the Alert. Is there a variable that will display the information I'm looking for? Right now I have to parse the URL to get the 'host' that triggered it. Smokeping 2.4.2 Thanks /Ryan - -- Ryan M. Harden, BS, KC9IHX Office: 217-265-5192 CITES - Network Engineering Cell: 217-689-1363 2130 Digital Computer Lab Fax: 217-244-7089 1304 W. Springfield email: hardenrm at illinois.edu Urbana, IL 61801 University of Illinois at Urbana/Champaign - AS38 University of Illinois - ICCN - AS40387 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkuWo6EACgkQtuPckBBbXbrX/gCaA359X+PAWqOQug6LkVu3rZb5 DtQAn1ohlgGlc5qU96DHODAM77KIEty2 =js/V -----END PGP SIGNATURE----- From blahu77 at gmail.com Tue Mar 9 21:13:40 2010 From: blahu77 at gmail.com (Mateusz Blaszczyk) Date: Tue, 9 Mar 2010 20:13:40 +0000 Subject: [smokeping-users] CiscoRTTMonEchoICMP probe and IOS 15.x In-Reply-To: <383357751003090839v7ecf516fne618baa5a33bb7b1@mail.gmail.com> References: <383357751003080233n12756926lb527eb173281baa7@mail.gmail.com> <383357751003081300v67621c9exf8d2360d51243663@mail.gmail.com> <383357751003090839v7ecf516fne618baa5a33bb7b1@mail.gmail.com> Message-ID: <383357751003091213t2ad5bee2hec532187ccfd3fe1@mail.gmail.com> On 9 March 2010 16:39, Mateusz Blaszczyk wrote: > Tobias, > >> iiks, this is a bit twisted I see ... without going into brain >> surgery, how about this: >> >> Index: CiscoRTTMonEchoICMP.pm >> =================================================================== > > [...] > >> + ? ? ? ? ? ? _default => $pingtimeout+10, >> + ? ? ? ? ? ? _doc => "How long a single RTTMonEcho ICMP 'ping' take at maximum plus 10 seconds to spare. Since we control our own timeout the only purpose of this is to not have us killed by the ping method from basefork.", >> + > > I understand that this is a mistake, it should be > > + ? ? ? ? ? ? _default => $pingtimeout+5, > + ? ? ? ? ? ? _doc => "How long a single RTTMonEcho ICMP 'ping' take > at maximum plus 5 seconds to spare. Since we control our own timeout > the only purpose of this is to not have us killed by the ping method > from basefork.", > > according to the below: > >> the idea is to set the timeout 'per ping' to pingtimeout+5 seconds >> ... this may be a bit of a long timeout but since we control our own time anyway it will never hit. >> > > apart from that as I understand the code it looks ok. > I will test it now and let you know the results > works. the probe is not killed by basefork, without any timeout option in config-file. ... with "_default => $pingtimeout+5" settings. Best Regards, -mat From tobi at oetiker.ch Tue Mar 9 22:59:47 2010 From: tobi at oetiker.ch (Tobias Oetiker) Date: Tue, 9 Mar 2010 22:59:47 +0100 (CET) Subject: [smokeping-users] Alerts mailtemplate <##ALERT##> output In-Reply-To: <4B96A3A3.8090105@uiuc.edu> References: <4B96A3A3.8090105@uiuc.edu> Message-ID: Hi Ryan, Today Ryan Harden wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > ## Resent from the address I'm actually subscribed by, so my apologies > if this is a duplicate. ## > > In setting up my mailtemplate for smokeping alerts I assumed that > <##ALERT##> would display the name of the "Target" that triggered the > alert. This is based on the documentation definition of "<##ALERT##> > - - target name" > > Instead it prints the name of the Alert. > > Is there a variable that will display the information I'm looking for? > Right now I have to parse the URL to get the 'host' that triggered it. > > Smokeping 2.4.2 I guess we have a little documentation deficit ... this is the built-in template ... Subject: [SmokeAlert] <##ALERT##> <##WHAT##> on <##LINE##> <##STAMP##> Alert "<##ALERT##>" <##WHAT##> for <##URL##> Pattern ------- <##PAT##> Data (old --> now) ------------------ <##LOSS##> <##RTT##> Comment ------- <##COMMENT##> does this help ? I guess you are looking for WHAT cheers tobi > Thanks > > /Ryan > > - -- > Ryan M. Harden, BS, KC9IHX Office: 217-265-5192 > CITES - Network Engineering Cell: 217-689-1363 > 2130 Digital Computer Lab Fax: 217-244-7089 > 1304 W. Springfield email: hardenrm at illinois.edu > Urbana, IL 61801 > > University of Illinois at Urbana/Champaign - AS38 > University of Illinois - ICCN - AS40387 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ > > iEYEARECAAYFAkuWo6EACgkQtuPckBBbXbrX/gCaA359X+PAWqOQug6LkVu3rZb5 > DtQAn1ohlgGlc5qU96DHODAM77KIEty2 > =js/V > -----END PGP SIGNATURE----- > > _______________________________________________ > 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 hardenrm at uiuc.edu Tue Mar 9 23:42:19 2010 From: hardenrm at uiuc.edu (Ryan Harden) Date: Tue, 09 Mar 2010 16:42:19 -0600 Subject: [smokeping-users] Alerts mailtemplate <##ALERT##> output In-Reply-To: References: <4B96A3A3.8090105@uiuc.edu> Message-ID: <4B96CECB.5000201@uiuc.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Tobi, On 03/09/2010 03:59 PM, Tobias Oetiker wrote: > Hi Ryan, > > Today Ryan Harden wrote: > > ## Resent from the address I'm actually subscribed by, so my apologies > if this is a duplicate. ## > > In setting up my mailtemplate for smokeping alerts I assumed that > <##ALERT##> would display the name of the "Target" that triggered the > alert. This is based on the documentation definition of "<##ALERT##> > - target name" > > Instead it prints the name of the Alert. > > Is there a variable that will display the information I'm looking for? > Right now I have to parse the URL to get the 'host' that triggered it. > > Smokeping 2.4.2 > >> I guess we have a little documentation deficit ... > >> this is the built-in template ... > >> Subject: [SmokeAlert] <##ALERT##> <##WHAT##> on <##LINE##> > >> <##STAMP##> > >> Alert "<##ALERT##>" <##WHAT##> for <##URL##> > >> Pattern >> ------- >> <##PAT##> > >> Data (old --> now) >> ------------------ >> <##LOSS##> >> <##RTT##> > >> Comment >> ------- >> <##COMMENT##> > > > >> does this help ? I guess you are looking for WHAT > Actually I'm not looking for WHAT as it just displays "is raised" or "is cleared" I was looking for something that would display a host as configured in the TARGETS section. I'm getting this info now using the <##LINE##>. /Ryan >> cheers >> tobi > > > > Thanks > > /Ryan > >> _______________________________________________ smokeping-users mailing list smokeping-users at lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users >> >> - -- Ryan M. Harden, BS, KC9IHX Office: 217-265-5192 CITES - Network Engineering Cell: 217-689-1363 2130 Digital Computer Lab Fax: 217-244-7089 1304 W. Springfield email: hardenrm at illinois.edu Urbana, IL 61801 University of Illinois at Urbana/Champaign - AS38 University of Illinois - ICCN - AS40387 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkuWzskACgkQtuPckBBbXbpREACgljjEUHK+0jHxoYygkgl5c21Z 12kAoJprcJvSBANZilulpGwd0OFNA6nB =W6Y1 -----END PGP SIGNATURE----- From tobi at oetiker.ch Wed Mar 10 06:45:43 2010 From: tobi at oetiker.ch (Tobias Oetiker) Date: Wed, 10 Mar 2010 06:45:43 +0100 (CET) Subject: [smokeping-users] Is there a probe that I can use to get RRT between 2 Cisco routes. In-Reply-To: <77AF43BAFA571044A7520788C54EDDEB02831E80D3@GLEXCH04401.GoldenLiving.Com> References: <77AF43BAFA571044A7520788C54EDDEB02831E80D3@GLEXCH04401.GoldenLiving.Com> Message-ID: Hi Bob, Yesterday Mersberger, Robert wrote: > Is this possible with Smokeping. > > I was wondering if you could provide me with answers and guidance > about using Smokeping. I am currently running version 20070126 on > Linux 2.2.11.4-21-bibsmp server using rrdtools. I would like to > upgrade to either the latest or newer version of Smokeping but > have limited experience working with any Unix. I took over this > server and application after the prior server owner left the > company. > > 1. What do I need to do to accomplish this upgrade and keep or > migrate my current data? * setup a new machine * install smokeping according to the instructions on the website * copy the config file * copy the data directory (see the config file for the location) * start smokeping at boot time note that my company does remote support, so if you want us to do the migration for you and can give us ssh access to the machines, I will be glad to make you an offer. Just mail me directly. > 2. Is there a probe that will allow me to capture RRT between two > remote routers. primary is in California and Other is in > OHIO. My server is in Arkansas and we use bgp and mpls for > our backbone. All router are Cisco 2811's the probes IOSPing and CiscoRTTMonEchoICMP should be able todo this for you. cheers tobi > I would appreciate any help or advice you could provide. > > Thanks > > > > Robert Mersberger > LAN Consultant, Information Technology > Phone 479-201-3442 > Fax 479-478-3837 > Email robert.mersberger at goldenliving.com > www.Goldenliving.com > Golden Living > 1000 Fianna Way > Fort Smith, AR 72919 > > > > > > ________________________________ > Please consider the environment before printing this e-mail. > > CONFIDENTIAL NOTICE: > This e-mail message and any attachment(s) (collectively, > this 'Email') are intended only for the confidential use of > the recipient(s) named above. If the reader of this message > is not the intended recipient named above or an agent > responsible for delivering it to the intended recipient > named above, you have received this Email in error. > Please notify the sender immediately and permanently delete > this Email and any copies thereof. > -- 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 Mar 10 06:47:04 2010 From: tobi at oetiker.ch (Tobias Oetiker) Date: Wed, 10 Mar 2010 06:47:04 +0100 (CET) Subject: [smokeping-users] CiscoRTTMonEchoICMP probe and IOS 15.x In-Reply-To: <383357751003091213t2ad5bee2hec532187ccfd3fe1@mail.gmail.com> References: <383357751003080233n12756926lb527eb173281baa7@mail.gmail.com> <383357751003081300v67621c9exf8d2360d51243663@mail.gmail.com> <383357751003090839v7ecf516fne618baa5a33bb7b1@mail.gmail.com> <383357751003091213t2ad5bee2hec532187ccfd3fe1@mail.gmail.com> Message-ID: Hi Mateusz, I set the timeout to 10, so that even when you had only a single ping it could never be a problem ... since normally you have more, 5 works too. cheers tobi Yesterday Mateusz Blaszczyk wrote: > On 9 March 2010 16:39, Mateusz Blaszczyk wrote: > > Tobias, > > > >> iiks, this is a bit twisted I see ... without going into brain > >> surgery, how about this: > >> > >> Index: CiscoRTTMonEchoICMP.pm > >> =================================================================== > > > > [...] > > > >> + ? ? ? ? ? ? _default => $pingtimeout+10, > >> + ? ? ? ? ? ? _doc => "How long a single RTTMonEcho ICMP 'ping' take at maximum plus 10 seconds to spare. Since we control our own timeout the only purpose of this is to not have us killed by the ping method from basefork.", > >> + > > > > I understand that this is a mistake, it should be > > > > + ? ? ? ? ? ? _default => $pingtimeout+5, > > + ? ? ? ? ? ? _doc => "How long a single RTTMonEcho ICMP 'ping' take > > at maximum plus 5 seconds to spare. Since we control our own timeout > > the only purpose of this is to not have us killed by the ping method > > from basefork.", > > > > according to the below: > > > >> the idea is to set the timeout 'per ping' to pingtimeout+5 seconds > >> ... this may be a bit of a long timeout but since we control our own time anyway it will never hit. > >> > > > > apart from that as I understand the code it looks ok. > > I will test it now and let you know the results > > > > works. the probe is not killed by basefork, without any timeout option > in config-file. > ... with "_default => $pingtimeout+5" settings. > > > Best Regards, > > -mat > > -- 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 Mar 10 06:58:30 2010 From: tobi at oetiker.ch (Tobias Oetiker) Date: Wed, 10 Mar 2010 06:58:30 +0100 (CET) Subject: [smokeping-users] Alerts mailtemplate <##ALERT##> output In-Reply-To: <4B96CECB.5000201@uiuc.edu> References: <4B96A3A3.8090105@uiuc.edu> <4B96CECB.5000201@uiuc.edu> Message-ID: Hi Ryan, Yesterday Ryan Harden wrote: [...] > Actually I'm not looking for WHAT as it just displays "is raised" or "is > cleared" I was looking for something that would display a host as > configured in the TARGETS section. > > I'm getting this info now using the <##LINE##>. > good ... glad I posted the whole template. 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 blahu77 at gmail.com Wed Mar 10 09:38:18 2010 From: blahu77 at gmail.com (Mateusz Blaszczyk) Date: Wed, 10 Mar 2010 08:38:18 +0000 Subject: [smokeping-users] CiscoRTTMonEchoICMP probe and IOS 15.x In-Reply-To: References: <383357751003080233n12756926lb527eb173281baa7@mail.gmail.com> <383357751003081300v67621c9exf8d2360d51243663@mail.gmail.com> <383357751003090839v7ecf516fne618baa5a33bb7b1@mail.gmail.com> <383357751003091213t2ad5bee2hec532187ccfd3fe1@mail.gmail.com> Message-ID: <383357751003100038w2f7eac2fr1cf660044b5ec4d7@mail.gmail.com> Hi Tobias, Good thinking. Best Regards -mat On 10 March 2010 05:47, Tobias Oetiker wrote: > Hi Mateusz, > > I set the timeout to 10, so that even when you had only a single > ping it could never be a problem ... > > since normally you have more, 5 works too. > > cheers > tobi > > Yesterday Mateusz Blaszczyk wrote: > >> On 9 March 2010 16:39, Mateusz Blaszczyk wrote: >> > Tobias, >> > >> >> iiks, this is a bit twisted I see ... without going into brain >> >> surgery, how about this: >> >> >> >> Index: CiscoRTTMonEchoICMP.pm >> >> =================================================================== >> > >> > [...] >> > >> >> + ? ? ? ? ? ? _default => $pingtimeout+10, >> >> + ? ? ? ? ? ? _doc => "How long a single RTTMonEcho ICMP 'ping' take at maximum plus 10 seconds to spare. Since we control our own timeout the only purpose of this is to not have us killed by the ping method from basefork.", >> >> + >> > >> > I understand that this is a mistake, it should be >> > >> > + ? ? ? ? ? ? _default => $pingtimeout+5, >> > + ? ? ? ? ? ? _doc => "How long a single RTTMonEcho ICMP 'ping' take >> > at maximum plus 5 seconds to spare. Since we control our own timeout >> > the only purpose of this is to not have us killed by the ping method >> > from basefork.", >> > >> > according to the below: >> > >> >> the idea is to set the timeout 'per ping' to pingtimeout+5 seconds >> >> ... this may be a bit of a long timeout but since we control our own time anyway it will never hit. >> >> >> > >> > apart from that as I understand the code it looks ok. >> > I will test it now and let you know the results >> > >> >> works. the probe is not killed by basefork, without any timeout option >> in config-file. >> ... with "_default => $pingtimeout+5" settings. >> >> >> Best Regards, >> >> -mat >> >> > > -- > 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 robert.mersberger at goldenliving.com Wed Mar 10 16:18:36 2010 From: robert.mersberger at goldenliving.com (Mersberger, Robert) Date: Wed, 10 Mar 2010 09:18:36 -0600 Subject: [smokeping-users] Is there a probe that I can use to get RRT between 2 Cisco routes. In-Reply-To: References: <77AF43BAFA571044A7520788C54EDDEB02831E80D3@GLEXCH04401.GoldenLiving.Com> Message-ID: <77AF43BAFA571044A7520788C54EDDEB02831E80D8@GLEXCH04401.GoldenLiving.Com> Thanks for the reply. Is it possible to do the upgrade to the same machine I am currently using for Smokeping? -----Original Message----- From: Tobias Oetiker [mailto:tobi at oetiker.ch] Sent: Tuesday, March 09, 2010 11:46 PM To: Mersberger, Robert Cc: 'smokeping-users at lists.oetiker.ch' Subject: Re: [smokeping-users] Is there a probe that I can use to get RRT between 2 Cisco routes. Hi Bob, Yesterday Mersberger, Robert wrote: > Is this possible with Smokeping. > > I was wondering if you could provide me with answers and guidance > about using Smokeping. I am currently running version 20070126 on > Linux 2.2.11.4-21-bibsmp server using rrdtools. I would like to > upgrade to either the latest or newer version of Smokeping but have > limited experience working with any Unix. I took over this server and > application after the prior server owner left the company. > > 1. What do I need to do to accomplish this upgrade and keep or migrate > my current data? * setup a new machine * install smokeping according to the instructions on the website * copy the config file * copy the data directory (see the config file for the location) * start smokeping at boot time note that my company does remote support, so if you want us to do the migration for you and can give us ssh access to the machines, I will be glad to make you an offer. Just mail me directly. > 2. Is there a probe that will allow me to capture RRT between two > remote routers. primary is in California and Other is in > OHIO. My server is in Arkansas and we use bgp and mpls for > our backbone. All router are Cisco 2811's the probes IOSPing and CiscoRTTMonEchoICMP should be able todo this for you. cheers tobi > I would appreciate any help or advice you could provide. > > Thanks > > > > Robert Mersberger > LAN Consultant, Information Technology Phone 479-201-3442 Fax > 479-478-3837 Email robert.mersberger at goldenliving.com > www.Goldenliving.com > Golden Living > 1000 Fianna Way > Fort Smith, AR 72919 > > > > > > ________________________________ > Please consider the environment before printing this e-mail. > > CONFIDENTIAL NOTICE: > This e-mail message and any attachment(s) (collectively, this 'Email') > are intended only for the confidential use of the recipient(s) named > above. If the reader of this message is not the intended recipient > named above or an agent responsible for delivering it to the intended > recipient named above, you have received this Email in error. > Please notify the sender immediately and permanently delete this Email > and any copies thereof. > -- 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 Please consider the environment before printing this e-mail. CONFIDENTIAL NOTICE: This e-mail message and any attachment(s) (collectively, this 'Email') are intended only for the confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient named above or an agent responsible for delivering it to the intended recipient named above, you have received this Email in error. Please notify the sender immediately and permanently delete this Email and any copies thereof. From bastien at yousaas.com Wed Mar 10 18:19:19 2010 From: bastien at yousaas.com (Bastien LAMOUREUX) Date: Wed, 10 Mar 2010 18:19:19 +0100 Subject: [smokeping-users] Smoketrace In-Reply-To: <77AF43BAFA571044A7520788C54EDDEB02831E80D8@GLEXCH04401.GoldenLiving.Com> References: <77AF43BAFA571044A7520788C54EDDEB02831E80D3@GLEXCH04401.GoldenLiving.Com> <77AF43BAFA571044A7520788C54EDDEB02831E80D8@GLEXCH04401.GoldenLiving.Com> Message-ID: Actually using smokeping 2.3.6 on Debian Lenny with great success (thanks to Tobi and community for this tool) I am actually trying to add smoketrace to my setup I followed instructions given here http://oss.oetiker.ch/smokeping/doc/smoketrace.en.html I feel I do not succeed to understand this part. I added this to the Targets file in /etc/smokeping/config.d but as soon as I restart smokeping "Starting latency logger daemon: smokeping" ERROR: /etc/smokeping/config.d/Targets, line 6: unknown variable 'menuextra' 6.Edit your config file and add the line: menuextra = *to your *** Targets *** section. It will make a * appear next to each host name, and when you click on it, the SmokeTrace window will open. Any idea Tobi or someone else? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 4987 bytes Desc: not available Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100310/7ead18ab/attachment.bin From tobi at oetiker.ch Wed Mar 10 22:47:26 2010 From: tobi at oetiker.ch (Tobias Oetiker) Date: Wed, 10 Mar 2010 22:47:26 +0100 (CET) Subject: [smokeping-users] Smoketrace In-Reply-To: References: <77AF43BAFA571044A7520788C54EDDEB02831E80D3@GLEXCH04401.GoldenLiving.Com> <77AF43BAFA571044A7520788C54EDDEB02831E80D8@GLEXCH04401.GoldenLiving.Com> Message-ID: Hi Bastien, Today Bastien LAMOUREUX wrote: > Actually using smokeping 2.3.6 on Debian Lenny with great success (thanks to > Tobi and community for this tool) > I am actually trying to add smoketrace to my setup > > > I followed instructions given here > http://oss.oetiker.ch/smokeping/doc/smoketrace.en.html > > I feel I do not succeed to understand this part. I added this to the Targets > file in /etc/smokeping/config.d but as soon as I restart smokeping > > "Starting latency logger daemon: smokeping" > ERROR: /etc/smokeping/config.d/Targets, line 6: unknown variable 'menuextra' > > 6.Edit your config file and add the line: > menuextra = onclick="window.open(this.href,this.target, \ > 'width=800,height=500,toolbar=no,location=no,status=no,scrollbars=no'); > \ > return false;">*to your *** Targets *** section. It will make a * > appear next to each host name, and when you click on it, the SmokeTrace > window will open. > > > Any idea Tobi or someone else? you need a newer version of smokeping I think ... note though that I am going to remove smoketrace from smokeping and will replace it with http://tobi.oetiker.ch/test/remocular if you want to test it, let me know ... 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 machfrey at yahoo.com Fri Mar 12 16:44:23 2010 From: machfrey at yahoo.com (max frey) Date: Fri, 12 Mar 2010 07:44:23 -0800 (PST) Subject: [smokeping-users] Smokeping Message-ID: <606653.40693.qm@web53507.mail.re2.yahoo.com> Hi to all. I am new to linux. I installed smokeping on my ubuntu 9.04 and configured the alerts, general, targets and probes but I can't view it on the browser. Below are some of the details: -------------------------------------------------------------------------------------------------------------------------------- smokeping --debug Smokeping version 2.003006 successfully launched. Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for that. FPing: probing 3 targets with step 300 s and offset 24 s. FPing: Executing /usr/bin/fping -C 20 -q -B1 -r1 -i10 www.brainpop.com www.yahoo.com localhost FPing: Got fping output: 'www.brainpop.com : 251.58 251.50 251.57 251.61 251.56 251.37 251.47 251.59 251.44 251.49 251.61 251.59 251.44 251.99 251.60 251.46 251.47 252.49 251.58 251.39' FPing: Got fping output: 'www.yahoo.com??? : 210.28 205.87 205.77 205.72 205.75 205.74 205.76 205.85 205.78 206.75 205.77 212.91 205.99 205.85 207.76 205.96 205.71 215.56 208.96 206.25' FPing: Got fping output: 'localhost??????? : 0.03 0.02 0.02 0.02 0.03 0.02 0.02 0.02 0.02 0.02 0.02 0.02 0.02 0.02 0.02 0.02 0.02 0.02 0.02 0.02' Calling RRDs::update(/var/lib/smokeping/World/Yahoo.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1268408376:U:0:2.0587000000e-01:2.0571000000e-01:2.0572000000e-01:2.0574000000e-01:2.0575000000e-01:2.0576000000e-01:2.0577000000e-01:2.0577000000e-01:2.0578000000e-01:2.0585000000e-01:2.0585000000e-01:2.0587000000e-01:2.0596000000e-01:2.0599000000e-01:2.0625000000e-01:2.0675000000e-01:2.0776000000e-01:2.0896000000e-01:2.1028000000e-01:2.1291000000e-01:2.1556000000e-01) RRDs::update ERROR: opening '/var/lib/smokeping/World/Yahoo.rrd': Permission denied Calling RRDs::update(/var/lib/smokeping/World/Brainpop.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1268408376:U:0:2.5157000000e-01:2.5137000000e-01:2.5139000000e-01:2.5144000000e-01:2.5144000000e-01:2.5146000000e-01:2.5147000000e-01:2.5147000000e-01:2.5149000000e-01:2.5150000000e-01:2.5156000000e-01:2.5157000000e-01:2.5158000000e-01:2.5158000000e-01:2.5159000000e-01:2.5159000000e-01:2.5160000000e-01:2.5161000000e-01:2.5161000000e-01:2.5199000000e-01:2.5249000000e-01) RRDs::update ERROR: opening '/var/lib/smokeping/World/Brainpop.rrd': Permission denied Calling RRDs::update(/var/lib/smokeping/Local/LocalMachine.rrd --template uptime:loss:median:ping1:ping2:ping3:ping4:ping5:ping6:ping7:ping8:ping9:ping10:ping11:ping12:ping13:ping14:ping15:ping16:ping17:ping18:ping19:ping20 1268408376:U:0:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:2.0000000000e-05:3.0000000000e-05:3.0000000000e-05) RRDs::update ERROR: opening '/var/lib/smokeping/Local/LocalMachine.rrd': Permission denied can't create /var/lib/smokeping/__sortercache/new: Permission denied at /usr/share/perl5/smokeping/Smokeping.pm line 1710 -------------------------------------------------------------------------------------------------------------------- /etc/init.d/smokeping restart ?* Shutting down latency logger daemon smokeping????????????????????????????????????????????????????????????????????????????????????????????????????? [ OK ] ?* Starting latency logger daemon smokeping?????????????????????????????????????????????????????????????????????????????????????????????????????????? [ OK ] ----------------------------------------------------------------------------------------------------------------------- Not Found The requested URL /cgi-bin/smokeping.cgi was not found on this server. Apache/2.2.12 (Ubuntu) Server at 116.93.86.2 Port 80 Can someone help me on this. I am a new linux user. Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100312/34ffa9be/attachment-0001.htm From chris+smokeping at aptivate.org Fri Mar 12 17:12:38 2010 From: chris+smokeping at aptivate.org (Chris Wilson) Date: Fri, 12 Mar 2010 17:12:38 +0100 (CET) Subject: [smokeping-users] Smokeping Message-ID: Hi Max, On Fri, 12 Mar 2010, max frey wrote: > I am new to linux. I installed smokeping on my ubuntu 9.04 and > configured the alerts, general, targets and probes but I can't view it > on the browser. Below are some of the details: > > Not Found > The requested URL /cgi-bin/smokeping.cgi was not found on this server. Did you follow this part of the installation instructions carefully? Please could you recheck it step by step? "htdocs/smokeping.cgi Edit the smokeping.cgi analog to the smokeping script above. Make sure the first line of the script is pointing to your freshly installed copy of Speedy CGI. Store the script in a directory of your weberver where CGIs get executed. You also have to edit the use lib line similar to what you did to smokeping." [http://oss.oetiker.ch/smokeping/doc/smokeping_install.en.html] (note: you can ignore the "speedy cgi" and change the first line of htdocs/smokeping.cgi to #!/usr/bin/perl). Cheers, Chris. -- Aptivate | http://www.aptivate.org | Phone: +44 1223 760887 The Humanitarian Centre, Fenner's, Gresham Road, Cambridge CB1 2ES Aptivate is a not-for-profit company registered in England and Wales with company number 04980791. From hardenrm at illinois.edu Tue Mar 9 18:46:25 2010 From: hardenrm at illinois.edu (Ryan Harden) Date: Tue, 9 Mar 2010 11:46:25 -0600 Subject: [smokeping-users] Alerts mailtemplate <##ALERT##> output Message-ID: <4B968971.7020301@illinois.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In setting up my mailtemplate for smokeping alerts I assumed that <##ALERT##> would display the name of the "Target" that triggered the alert. This is based on the documentation definition of "<##ALERT##> - - target name" Instead it prints the name of the Alert. Is there a variable that will display the information I'm looking for? Thanks /Ryan - -- Ryan M. Harden, BS, KC9IHX Office: 217-265-5192 CITES - Network Engineering Cell: 217-689-1363 2130 Digital Computer Lab Fax: 217-244-7089 1304 W. Springfield email: hardenrm at illinois.edu Urbana, IL 61801 University of Illinois - Urbana/Champaign - AS38 University of Illinois - ICCN - AS40387 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuWiXEACgkQtuPckBBbXbpuYACfUfhSJgYSWlZZwuwp410fJxgr eoYAn1lOHcQp6ovWJ8fBgp3qZKArIi5L =x2L/ -----END PGP SIGNATURE----- From wkstill at franz-family.com Wed Mar 17 14:22:25 2010 From: wkstill at franz-family.com (William Stillwell - KI4SWY) Date: Wed, 17 Mar 2010 09:22:25 -0400 Subject: [smokeping-users] Zoom/Firefox Message-ID: <039f01cac5d4$e2bbfd70$a833f850$@com> Looks like Zoom issue is fixed in Firefox 3.6 Bill- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100317/7bb5c5a7/attachment-0001.htm From ged at jubileegroup.co.uk Wed Mar 17 14:46:01 2010 From: ged at jubileegroup.co.uk (G.W. Haywood) Date: Wed, 17 Mar 2010 13:46:01 +0000 (GMT) Subject: [smokeping-users] Multiple much delayed messages. Message-ID: Hi there, Please note the original submission dates on the recent flurry of messages. Looks like the list server threw a fit. -- 73, Ged. From Al_Sorrell at troweprice.com Wed Mar 17 15:08:39 2010 From: Al_Sorrell at troweprice.com (Sorrell, Al) Date: Wed, 17 Mar 2010 10:08:39 -0400 Subject: [smokeping-users] smokeping curl specifiying proxy In-Reply-To: <8DA11B342D7A5643A515ACBF8B72D9875FD4ED38@IMCMBX3.MITRE.ORG> References: <8DA11B342D7A5643A515ACBF8B72D9875FD4ED38@IMCMBX3.MITRE.ORG> Message-ID: ________________________________ From: smokeping-users-bounces+al_sorrell=troweprice.com at lists.oetiker.ch [mailto:smokeping-users-bounces+al_sorrell=troweprice.com at lists.oetiker. ch] On Behalf Of Lee, Tony Sent: Thursday, June 11, 2009 12:24 PM To: smokeping-users at lists.oetiker.ch Subject: [smokeping-users] smokeping curl specifiying proxy Hi. Is there a way to pass the proxy variable or other variables into curl smokeping from curl? The versions running: curl --version curl 7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 Protocols: tftp ftp telnet dict ldap http file https ftps Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz smokeping --version 2.003006 --- Sample configuration: + Curl # Curl probe-specific variables binary = /usr/bin/curl step = 60 #curl probe target-specific variables urlformat = -x proxy:80 http://%host/ <<< This might be the wrong syntax trying to pass -x here. Try using the "extraargs" flag like this: + Curl binary = /usr/local/bin/curl pings=20 extraargs = --proxy myproxy:8080 --proxy-user "myuser:mypass" urlformat = http://%host% T. Rowe Price (including T. Rowe Price Group, Inc. and its affiliates) and its associates do not provide legal or tax advice. Any tax-related discussion contained in this e-mail, including any attachments, is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding any tax penalties or (ii) promoting, marketing, or recommending to any other party any transaction or matter addressed herein. Please consult your independent legal counsel and/or professional tax advisor regarding any legal or tax issues raised in this e-mail. The contents of this e-mail and any attachments are intended solely for the use of the named addressee(s) and may contain confidential and/or privileged information. Any unauthorized use, copying, disclosure, or distribution of the contents of this e-mail is strictly prohibited by the sender and may be unlawful. If you are not the intended recipient, please notify the sender immediately and delete this e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100317/c054690e/attachment.html From tobi at oetiker.ch Thu Mar 18 08:33:09 2010 From: tobi at oetiker.ch (Tobias Oetiker) Date: Thu, 18 Mar 2010 08:33:09 +0100 (CET) Subject: [smokeping-users] Multiple much delayed messages. In-Reply-To: References: Message-ID: Hi Ged, Yesterday G.W. Haywood wrote: > Hi there, > > Please note the original submission dates on the recent flurry of messages. > > Looks like the list server threw a fit. that was me spring cleaning the moderation queue ... :-) 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 tobi at oetiker.ch Mon Mar 22 08:03:21 2010 From: tobi at oetiker.ch (Tobias Oetiker) Date: Mon, 22 Mar 2010 08:03:21 +0100 (CET) Subject: [smokeping-users] Multihost graph for same target but with different probes? In-Reply-To: References: Message-ID: Hi Richard, Jan 15 RICHARD wrote: > Hello! > I wonder if there is a way to monitor multiple QoS classes in one > graph? What I would like to do is to send multiple probes (EF, > Afxx, AFyy, BE) to the same target host. I can do that today but > then I got separate graphs. > > I looked at the multihost feature but it looks to have a > different approach with combining same probe to many > destinations, not different probes to same destination. > > I run a Smokeping 2.4.2 server with ToS capable FPing. It work very nice so far. if you use multiple probes there would probably be a presentation problem in the legend ... time to dig into the code I'd say :-) cheers tobi > Best regards > Richard > > > ? > > > -- 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 cmathis at wsii.com Tue Mar 23 22:50:08 2010 From: cmathis at wsii.com (cmathis) Date: Tue, 23 Mar 2010 17:50:08 -0400 Subject: [smokeping-users] (no subject) Message-ID: I just discovered smokeping, so I gave it a 24 hour run. Boy am I concered, confused. Can anyone give me an idea here: http://www.dslreports.com/r3/smokeping.cgi?target=network.351bf3e5b53fb4a2e22013bcfc7cd925 I think my connection has a serious problem. I have a biz account with Cox Cable. Any ideas? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100323/5ba00e0c/attachment-0001.htm From josh at imaginenetworksllc.com Tue Mar 23 23:00:34 2010 From: josh at imaginenetworksllc.com (Josh Luthman) Date: Tue, 23 Mar 2010 18:00:34 -0400 Subject: [smokeping-users] (no subject) In-Reply-To: References: Message-ID: <961092e11003231500o2f6ad435m9db74f653425adf7@mail.gmail.com> It will probably help to share your relevant configuration. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 ?Success is not final, failure is not fatal: it is the courage to continue that counts.? --- Winston Churchill On Tue, Mar 23, 2010 at 5:50 PM, cmathis wrote: > I just discovered smokeping, so I gave it a 24 hour run. Boy am I concered, > confused. Can anyone give me an idea here: > > http://www.dslreports.com/r3/smokeping.cgi?target=network.351bf3e5b53fb4a2e22013bcfc7cd925 > > I think my connection has a serious problem. I have a biz account with Cox > Cable. Any ideas? > > _______________________________________________ > smokeping-users mailing list > smokeping-users at lists.oetiker.ch > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users > > From josh at imaginenetworksllc.com Wed Mar 24 04:08:10 2010 From: josh at imaginenetworksllc.com (Josh Luthman) Date: Tue, 23 Mar 2010 23:08:10 -0400 Subject: [smokeping-users] (no subject) In-Reply-To: References: <961092e11003231500o2f6ad435m9db74f653425adf7@mail.gmail.com> Message-ID: <961092e11003232008k5e52caf4r44746dfc9c151e2b@mail.gmail.com> What are you pinging? Try pinging the first route out and then the last router before you peer with the next peer. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 ?Success is not final, failure is not fatal: it is the courage to continue that counts.? --- Winston Churchill On Tue, Mar 23, 2010 at 10:55 PM, cmathis wrote: > Sorry all. Attached is a jpg of the last 30 hours. It looks like every two > hours or so my connection just dies. I have done tests on speedtest.net and > when the smokeping is showing my connection is poor, the speedtest confirms > it. I have no idea why this is happening. My ISP ( Cox ) said my business > high speed is fine, but how can this be. Please see attached pic. If anyone > has any ideas, I would be most greatful. > > Thank you, > > Chris > > > > It will probably help to share your relevant configuration. > > Josh Luthman > > On Tue, Mar 23, 2010 at 5:50 PM, cmathis wrote: >> I just discovered smokeping, so I gave it a 24 hour run. Boy am I >> concered, >> confused. Can anyone give me an idea here: >> >> >> http://www.dslreports.com/r3/smokeping.cgi?target=network.351bf3e5b53fb4a2e22013bcfc7cd925 >> >> I think my connection has a serious problem. I have a biz account with Cox >> Cable. Any ideas? >> >> _______________________________________________ >> smokeping-users mailing list >> smokeping-users at lists.oetiker.ch >> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users >> >> > From james.cornick at jchost.net Thu Mar 25 16:50:45 2010 From: james.cornick at jchost.net (James Cornick - JCHost.net) Date: Thu, 25 Mar 2010 10:50:45 -0500 Subject: [smokeping-users] startloss,bigloss,endloss Message-ID: <4BAB8655.3050808@jchost.net> Hello all I'm new here however I have been using smokeping for quite some time. I was curious if anyone had come up with way to get an email alert on 'endloss'. For example smokeping detects bigloss on a host and then 10 minutes later the host comes up again. I'm almost certain there would be a way to configure this but all my attempts so far have failed. If anyone has any ideas that would be much appreciated. Best Regards, James From alter3d at alter3d.ca Thu Mar 25 17:21:23 2010 From: alter3d at alter3d.ca (Peter Kristolaitis) Date: Thu, 25 Mar 2010 12:21:23 -0400 Subject: [smokeping-users] startloss,bigloss,endloss In-Reply-To: <4BAB8655.3050808@jchost.net> References: <4BAB8655.3050808@jchost.net> Message-ID: <4BAB8D83.4000706@alter3d.ca> Look at the 'edgetrigger' option for alerts. This will cause alerts to send out 2 emails -- one when the trigger is 'true', then another when it becomes 'not true'. - Peter On 3/25/2010 11:50 AM, James Cornick - JCHost.net wrote: > Hello all I'm new here however I have been using smokeping for quite > some time. I was curious if anyone had come up with way to get an email > alert on 'endloss'. For example smokeping detects bigloss on a host and > then 10 minutes later the host comes up again. I'm almost certain there > would be a way to configure this but all my attempts so far have > failed. If anyone has any ideas that would be much appreciated. > > Best Regards, > > James > > _______________________________________________ > smokeping-users mailing list > smokeping-users at lists.oetiker.ch > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6444 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100325/ba8deddd/attachment.bin From james.cornick at jchost.net Thu Mar 25 17:50:11 2010 From: james.cornick at jchost.net (James Cornick - JCHost.net) Date: Thu, 25 Mar 2010 11:50:11 -0500 Subject: [smokeping-users] startloss,bigloss,endloss In-Reply-To: <4BAB8D83.4000706@alter3d.ca> References: <4BAB8655.3050808@jchost.net> <4BAB8D83.4000706@alter3d.ca> Message-ID: <4BAB9443.705@jchost.net> Peter thank you I have tried this and it is 'kind of working' here is my bigloss alert config currently. +bigloss type = loss # in percent pattern = ==0%,==0%,==0%,>50%,>50%,>50%,>50% comment = Suddenly there is some packet loss! edgetrigger = yes However the alert seems to immediately clear even when the host does not come back online? Do you know if I am doing something incorrectly here? Regards, James Peter Kristolaitis wrote: > Look at the 'edgetrigger' option for alerts. This will cause alerts > to send out 2 emails -- one when the trigger is 'true', then another > when it becomes 'not true'. > > - Peter > > On 3/25/2010 11:50 AM, James Cornick - JCHost.net wrote: >> Hello all I'm new here however I have been using smokeping for quite >> some time. I was curious if anyone had come up with way to get an email >> alert on 'endloss'. For example smokeping detects bigloss on a host and >> then 10 minutes later the host comes up again. I'm almost certain there >> would be a way to configure this but all my attempts so far have >> failed. If anyone has any ideas that would be much appreciated. >> >> Best Regards, >> >> James >> >> _______________________________________________ >> smokeping-users mailing list >> smokeping-users at lists.oetiker.ch >> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users >> > > > ------------------------------------------------------------------------ > > _______________________________________________ > smokeping-users mailing list > smokeping-users at lists.oetiker.ch > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users > From alter3d at alter3d.ca Thu Mar 25 18:03:18 2010 From: alter3d at alter3d.ca (Peter Kristolaitis) Date: Thu, 25 Mar 2010 13:03:18 -0400 Subject: [smokeping-users] startloss,bigloss,endloss In-Reply-To: <4BAB9443.705@jchost.net> References: <4BAB8655.3050808@jchost.net> <4BAB8D83.4000706@alter3d.ca> <4BAB9443.705@jchost.net> Message-ID: <4BAB9756.9040504@alter3d.ca> Yeah, your pattern isn't written properly for edgetrigger use. The thing to understand here is that the values you provide in your pattern are the number of previous samples to look at in the history. The last pattern argument you list is the 'current' sample, then as you move backwards in the list, Smokeping examines more and more historical data. There's no additional logic here -- you're simply matching current data against a pattern, and seeing if it matches or not. So what your pattern is saying here is "This alert is TRUE when you see exactly 3 samples with 0% packet loss followed by exactly 4 samples with more than 50% packet loss". Note that it's NOT "4 or more samples with >50% packet loss". If the alert triggers at some point, but the host continues to be down (i.e. >50% loss), you will be matching the data "100% 100% 100% 100% 100% 100% 100%" against the rule -- but since the first 3 samples are NOT 0% loss, you no longer match the pattern, and the alert un-triggers itself! The proper way to write edgetriggers is simply ">50%,>50%,>50%,>50%". Because edgetriggers only send you an email when the event happens, then again when it stops happening, there is no need to check for 0% packet loss at the beginning of the pattern. Checking for 0% loss at the beginning of patterns is useful when you're NOT using edgetrigger -- otherwise you'll get an alert for every sample! - Peter On 3/25/2010 12:50 PM, James Cornick - JCHost.net wrote: > Peter thank you I have tried this and it is 'kind of working' here is > my bigloss alert config currently. > > +bigloss > type = loss > # in percent > pattern = ==0%,==0%,==0%,>50%,>50%,>50%,>50% > comment = Suddenly there is some packet loss! > edgetrigger = yes > > However the alert seems to immediately clear even when the host does > not come back online? Do you know if I am doing something incorrectly > here? > > Regards, > > James > > Peter Kristolaitis wrote: >> Look at the 'edgetrigger' option for alerts. This will cause alerts >> to send out 2 emails -- one when the trigger is 'true', then another >> when it becomes 'not true'. >> >> - Peter >> >> On 3/25/2010 11:50 AM, James Cornick - JCHost.net wrote: >>> Hello all I'm new here however I have been using smokeping for quite >>> some time. I was curious if anyone had come up with way to get an >>> email >>> alert on 'endloss'. For example smokeping detects bigloss on a host >>> and >>> then 10 minutes later the host comes up again. I'm almost certain >>> there >>> would be a way to configure this but all my attempts so far have >>> failed. If anyone has any ideas that would be much appreciated. >>> >>> Best Regards, >>> >>> James >>> >>> _______________________________________________ >>> 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 > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6444 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100325/f0e6d7f5/attachment-0001.bin From james.cornick at jchost.net Thu Mar 25 19:31:18 2010 From: james.cornick at jchost.net (James Cornick - JCHost.net) Date: Thu, 25 Mar 2010 13:31:18 -0500 Subject: [smokeping-users] startloss,bigloss,endloss In-Reply-To: <4BAB9756.9040504@alter3d.ca> References: <4BAB8655.3050808@jchost.net> <4BAB8D83.4000706@alter3d.ca> <4BAB9443.705@jchost.net> <4BAB9756.9040504@alter3d.ca> Message-ID: <4BABABF6.80007@jchost.net> Peter, Thanks for your explanation this makes perfect sense and works as expected! Peter Kristolaitis wrote: > Yeah, your pattern isn't written properly for edgetrigger use. > > The thing to understand here is that the values you provide in your > pattern are the number of previous samples to look at in the history. > The last pattern argument you list is the 'current' sample, then as > you move backwards in the list, Smokeping examines more and more > historical data. There's no additional logic here -- you're simply > matching current data against a pattern, and seeing if it matches or not. > > So what your pattern is saying here is "This alert is TRUE when you > see exactly 3 samples with 0% packet loss followed by exactly 4 > samples with more than 50% packet loss". Note that it's NOT "4 or > more samples with >50% packet loss". If the alert triggers at some > point, but the host continues to be down (i.e. >50% loss), you will be > matching the data "100% 100% 100% 100% 100% 100% 100%" against the > rule -- but since the first 3 samples are NOT 0% loss, you no longer > match the pattern, and the alert un-triggers itself! > > The proper way to write edgetriggers is simply > ">50%,>50%,>50%,>50%". Because edgetriggers only send you an email > when the event happens, then again when it stops happening, there is > no need to check for 0% packet loss at the beginning of the pattern. > Checking for 0% loss at the beginning of patterns is useful when > you're NOT using edgetrigger -- otherwise you'll get an alert for > every sample! > > - Peter > > > On 3/25/2010 12:50 PM, James Cornick - JCHost.net wrote: >> Peter thank you I have tried this and it is 'kind of working' here is >> my bigloss alert config currently. >> >> +bigloss >> type = loss >> # in percent >> pattern = ==0%,==0%,==0%,>50%,>50%,>50%,>50% >> comment = Suddenly there is some packet loss! >> edgetrigger = yes >> However the alert seems to immediately clear even when the host does >> not come back online? Do you know if I am doing something >> incorrectly here? >> >> Regards, >> >> James >> >> Peter Kristolaitis wrote: >>> Look at the 'edgetrigger' option for alerts. This will cause >>> alerts to send out 2 emails -- one when the trigger is 'true', then >>> another when it becomes 'not true'. >>> >>> - Peter >>> >>> On 3/25/2010 11:50 AM, James Cornick - JCHost.net wrote: >>>> Hello all I'm new here however I have been using smokeping for quite >>>> some time. I was curious if anyone had come up with way to get an >>>> email >>>> alert on 'endloss'. For example smokeping detects bigloss on a >>>> host and >>>> then 10 minutes later the host comes up again. I'm almost certain >>>> there >>>> would be a way to configure this but all my attempts so far have >>>> failed. If anyone has any ideas that would be much appreciated. >>>> >>>> Best Regards, >>>> >>>> James >>>> >>>> _______________________________________________ >>>> smokeping-users mailing list >>>> smokeping-users at lists.oetiker.ch >>>> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users >>> >>> >>> ------------------------------------------------------------------------ >>> >>> >>> _______________________________________________ >>> smokeping-users mailing list >>> smokeping-users at lists.oetiker.ch >>> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users >> > > From liviumey at gmail.com Sun Mar 28 21:01:34 2010 From: liviumey at gmail.com (Liviu Poenaru) Date: Sun, 28 Mar 2010 22:01:34 +0300 Subject: [smokeping-users] sort Message-ID: Hello, Is there any way to change "charts" in smokeping so it sorts from lowest to highest? I'm trying to sort hosts from best to worst and display top 10 bests. Best host means lowest lost, lowest max, median, deviation. Thanks, Poenaru Liviu TeenTelecom Bucharest, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100328/d6d1f932/attachment.htm From tobi at oetiker.ch Mon Mar 29 07:24:40 2010 From: tobi at oetiker.ch (Tobias Oetiker) Date: Mon, 29 Mar 2010 07:24:40 +0200 (CEST) Subject: [smokeping-users] sort In-Reply-To: References: Message-ID: Hi Liviu, Yesterday Liviu Poenaru wrote: > Hello, > > Is there any way to change "charts" in smokeping so it sorts from lowest to > highest? I'm trying to sort hosts from best to worst and display top 10 > bests. Best host means lowest lost, lowest max, median, deviation. there is curently no such function since normally there are many 'good' hosts ... so top 10 would make for a rather boring chart. cheers tobi > > > Thanks, > Poenaru Liviu > TeenTelecom > Bucharest, Romania > -- 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 bgcladd at gmail.com Tue Mar 30 09:13:03 2010 From: bgcladd at gmail.com (Joshua Smith) Date: Tue, 30 Mar 2010 00:13:03 -0700 Subject: [smokeping-users] graphing traceroutes possible? Message-ID: Hello everyone, i recently stumbled upon smokeping looking for an alternative to pingplotter pro which i currently use. I purchased pingplotter so i would be able to keep detailed logs of mtr-like traceroutes to and from all of my remote servers to help identify any network issues and so that i have some ammunition when dealing with the colo's about possible problems. While pingplotter accomplishes this, it is extremely resource hungry both on the host machine (windows only, that alone is huge drawback) and on any remote linux machine as it relies on a perl script to call traceroute, which somehow uses an incredible amount of resources when querying many hosts at once. Long story short after configuring smokeping and digging everywhere i'm unable to tell if smokeping offers this same functionality? An help would be greatly appreciated and i apologise for the back story. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100330/db15ce70/attachment.htm From tobi at oetiker.ch Tue Mar 30 09:52:25 2010 From: tobi at oetiker.ch (Tobias Oetiker) Date: Tue, 30 Mar 2010 09:52:25 +0200 (CEST) Subject: [smokeping-users] graphing traceroutes possible? In-Reply-To: References: Message-ID: Hi Joshua, curently smokeping has no functionality for running background traceroutes and recording of that information ... but if you have a budget, I'll be glad to make you an offer for developing such a feature. If you program yourself I'll be glad todo some chaperoning ... cheers tobi Today Joshua Smith wrote: > Hello everyone, i recently stumbled upon smokeping looking for an > alternative to pingplotter pro which i currently use. I purchased > pingplotter so i would be able to keep detailed logs of mtr-like traceroutes > to and from all of my remote servers to help identify any network issues and > so that i have some ammunition when dealing with the colo's about possible > problems. While pingplotter accomplishes this, it is extremely resource > hungry both on the host machine (windows only, that alone is huge drawback) > and on any remote linux machine as it relies on a perl script to call > traceroute, which somehow uses an incredible amount of resources when > querying many hosts at once. Long story short after configuring smokeping > and digging everywhere i'm unable to tell if smokeping offers this same > functionality? An help would be greatly appreciated and i apologise for the > back story. > -- 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 rjd at merit.edu Tue Mar 30 15:55:04 2010 From: rjd at merit.edu (Russell Dwarshuis) Date: Tue, 30 Mar 2010 09:55:04 -0400 (EDT) Subject: [smokeping-users] graphing traceroutes possible? In-Reply-To: References: Message-ID: And of course smokeping can be configured to run a script when a loss trigger is tripped. For awhile I had a little script run traceroute and email the results to me when loss was seen on a particular host. It's not exactly what Joshua was looking for but it's another less-resource intensive possibility. -Russell Dwarshuis On Tue, 30 Mar 2010, Tobias Oetiker wrote: > Hi Joshua, > > curently smokeping has no functionality for running background > traceroutes and recording of that information ... > > but if you have a budget, I'll be glad to make you an offer for > developing such a feature. > > If you program yourself I'll be glad todo some chaperoning ... > > cheers > tobi > > > > Today Joshua Smith wrote: > >> Hello everyone, i recently stumbled upon smokeping looking for an >> alternative to pingplotter pro which i currently use. I purchased >> pingplotter so i would be able to keep detailed logs of mtr-like traceroutes >> to and from all of my remote servers to help identify any network issues and >> so that i have some ammunition when dealing with the colo's about possible >> problems. While pingplotter accomplishes this, it is extremely resource >> hungry both on the host machine (windows only, that alone is huge drawback) >> and on any remote linux machine as it relies on a perl script to call >> traceroute, which somehow uses an incredible amount of resources when >> querying many hosts at once. Long story short after configuring smokeping >> and digging everywhere i'm unable to tell if smokeping offers this same >> functionality? An help would be greatly appreciated and i apologise for the >> back story. >> > > -- > 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 > > _______________________________________________ > smokeping-users mailing list > smokeping-users at lists.oetiker.ch > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users > From josh at imaginenetworksllc.com Tue Mar 30 16:12:13 2010 From: josh at imaginenetworksllc.com (Josh Luthman) Date: Tue, 30 Mar 2010 10:12:13 -0400 Subject: [smokeping-users] graphing traceroutes possible? In-Reply-To: References: Message-ID: <961092e11003300712l2f3b92f0u3d5985c0304f7022@mail.gmail.com> You can use Xymon to get a ping email alert. At this time it's simply up or down. Future plans are for so much loss or high values. No function for traceroutes that I am aware. On 3/30/10, Russell Dwarshuis wrote: > And of course smokeping can be configured to run a script when a loss > trigger is tripped. For awhile I had a little script run traceroute > and email the results to me when loss was seen on a particular host. > > It's not exactly what Joshua was looking for but it's another > less-resource intensive possibility. > > > -Russell Dwarshuis > > On Tue, 30 Mar 2010, Tobias Oetiker wrote: > >> Hi Joshua, >> >> curently smokeping has no functionality for running background >> traceroutes and recording of that information ... >> >> but if you have a budget, I'll be glad to make you an offer for >> developing such a feature. >> >> If you program yourself I'll be glad todo some chaperoning ... >> >> cheers >> tobi >> >> >> >> Today Joshua Smith wrote: >> >>> Hello everyone, i recently stumbled upon smokeping looking for an >>> alternative to pingplotter pro which i currently use. I purchased >>> pingplotter so i would be able to keep detailed logs of mtr-like >>> traceroutes >>> to and from all of my remote servers to help identify any network issues >>> and >>> so that i have some ammunition when dealing with the colo's about >>> possible >>> problems. While pingplotter accomplishes this, it is extremely resource >>> hungry both on the host machine (windows only, that alone is huge >>> drawback) >>> and on any remote linux machine as it relies on a perl script to call >>> traceroute, which somehow uses an incredible amount of resources when >>> querying many hosts at once. Long story short after configuring smokeping >>> and digging everywhere i'm unable to tell if smokeping offers this same >>> functionality? An help would be greatly appreciated and i apologise for >>> the >>> back story. >>> >> >> -- >> 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 >> >> _______________________________________________ >> 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 > -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 ?Success is not final, failure is not fatal: it is the courage to continue that counts.? --- Winston Churchill From rjd at merit.edu Tue Mar 30 21:01:08 2010 From: rjd at merit.edu (Russell Dwarshuis) Date: Tue, 30 Mar 2010 15:01:08 -0400 (EDT) Subject: [smokeping-users] graphing traceroutes possible? In-Reply-To: <961092e11003300712l2f3b92f0u3d5985c0304f7022@mail.gmail.com> References: <961092e11003300712l2f3b92f0u3d5985c0304f7022@mail.gmail.com> Message-ID: Since someone asked and others may want it, here's (more or less) the script I cobbled together to run traceroute on a slave and mtr on the master, then email the results when a smokeping loss trigger happens. It will need customization for your environment but should get you started. -Russell Dwarshuis ------------------------------------------------------------ #!/usr/bin/perl # this script would be run when smokeping detects some loss. The # smokeping trigger could look like: # # +highLossTwice # type = loss # pattern = >70%,>70% # to = |/usr/local/smokeping/contrib/mtr_email.pl # comment = 10 minutes of high loss # this runs mtr on master and traceroute on a slave and emails results # to an address hardcoded below. It was a throw-away so I didn't spend # any time making it user or developer friendly. use Net::SMTP; use English; my ($name_of_alert,$target,$loss_pattern,$rtt_pattern,$hostname) = @ARGV; # change smokeping host name to dotted quad IP address if it isn't one already if ($hostname !~ /^\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}$/) { ($name,$aliases,$addrtype,$length, at addrs)=gethostbyname($hostname); ($a,$b,$c,$d)=unpack("C4",$addrs[0]); $hostname="$a.$b.$c.$d"; } if ($hostname !~ /^\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}$/) { print "invalid IP address $hostname\n"; exit; } push @mtr_results, "To: someonewhocares\@yourcompany.com\n"; push @mtr_results, "Subject: smokeping detected loss to $hostname\n"; push @mtr_results, "smokeping detected loss to $target.\n\n"; push @mtr_results, "mtr was then run on the smokeping host and the results were:\n"; open MTR, ("/usr/local/sbin/mtr --report --report-cycles 10 --no-dns $hostname |"); push @mtr_results, (); close MTR; push @mtr_results, "\n\ntraceroute was then run on smokeping slave and the results were:\n"; # Now trying traceroute on slave via ssh open SSH, ("/usr/bin/ssh -o 'UserKnownHostsFile /usr/local/smokeping/.ssh/KnownHosts' -i /usr/local/smokeping/.ssh/id_rsa slaveuser\@slave.smokeping.yourcompany.com /usr/sbin/traceroute -w 3 -m 10 $hostname |"); push @mtr_results,(); close SSH; # send the email. $smtp = Net::SMTP->new('mail.yourcompany.com', Timeout => 5); $smtp->mail('smokeping at master.smokeping.yourcompany.com'); $smtp->to('someonewhocares at yourcompany.com'); $smtp->data(); foreach (@mtr_results) { $smtp->datasend($_) } $smtp->dataend(); $smtp->quit; > > On 3/30/10, Russell Dwarshuis wrote: >> And of course smokeping can be configured to run a script when a loss >> trigger is tripped. For awhile I had a little script run traceroute >> and email the results to me when loss was seen on a particular host. >> >> It's not exactly what Joshua was looking for but it's another >> less-resource intensive possibility. >> >> >> -Russell Dwarshuis >> >> On Tue, 30 Mar 2010, Tobias Oetiker wrote: >> >>> Hi Joshua, >>> >>> curently smokeping has no functionality for running background >>> traceroutes and recording of that information ... >>> >>> but if you have a budget, I'll be glad to make you an offer for >>> developing such a feature. >>> >>> If you program yourself I'll be glad todo some chaperoning ... >>> >>> cheers >>> tobi >>> >>> >>> >>> Today Joshua Smith wrote: >>> >>>> Hello everyone, i recently stumbled upon smokeping looking for an >>>> alternative to pingplotter pro which i currently use. I purchased >>>> pingplotter so i would be able to keep detailed logs of mtr-like >>>> traceroutes >>>> to and from all of my remote servers to help identify any network issues >>>> and >>>> so that i have some ammunition when dealing with the colo's about >>>> possible >>>> problems. While pingplotter accomplishes this, it is extremely resource >>>> hungry both on the host machine (windows only, that alone is huge >>>> drawback) >>>> and on any remote linux machine as it relies on a perl script to call >>>> traceroute, which somehow uses an incredible amount of resources when >>>> querying many hosts at once. Long story short after configuring smokeping >>>> and digging everywhere i'm unable to tell if smokeping offers this same >>>> functionality? An help would be greatly appreciated and i apologise for >>>> the >>>> back story. >>>> >>> >>> -- >>> 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 >>> >>> _______________________________________________ >>> 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 >> > > > -- > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > ?Success is not final, failure is not fatal: it is the courage to > continue that counts.? > --- Winston Churchill > > _______________________________________________ > smokeping-users mailing list > smokeping-users at lists.oetiker.ch > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users > From support at zenith-net.co.uk Wed Mar 31 11:53:55 2010 From: support at zenith-net.co.uk (support at zenith-net.co.uk) Date: Wed, 31 Mar 2010 05:53:55 -0400 Subject: [smokeping-users] Add-Remove targets from web interface? Message-ID: <380-22010333195355842@M2W116.mail2web.com> Hi guys, I've been looking around but can?t find anything like this. Is there any way/method out there for adding and removing targets/restarting the service etc via a web interface? The reason I ask is that I need to add lots of targets for short periods of time, the requests come in from other people, so ether I give everyone SSH access to edit the targets file or give them a simple interface. I've looked at possibly replacing smokeping with cacti but that?s drastically over complicated for just a ping graph for 24 hours etc. If there?s nothing out there I guess I could try and knock something up myself, but I was hoping something already existed. If one doesn't exists does anyone know if its possible to get smokeping to query a sql database for list of targets? Thanks Aaron -------------------------------------------------------------------- mail2web.com ? What can On Demand Business Solutions do for you? http://link.mail2web.com/Business/SharePoint From ssuetstudent at yahoo.com Wed Mar 31 19:27:09 2010 From: ssuetstudent at yahoo.com (Muhammad Asif Rao) Date: Wed, 31 Mar 2010 10:27:09 -0700 (PDT) Subject: [smokeping-users] problem with smokeping Message-ID: <813301.96881.qm@web33001.mail.mud.yahoo.com> Hi List, I just installed smokeping with all dependencies and smokeping process running fine on fedora 10. but when try to access via webpage, getting following error. Welcome to the SmokePing website of xxx Company. Here you will learn all about the latency of our network. ERROR: Could not save png to '/usr/local/smokedata/imgcache/Yahoo_mini.png' 'DEF:median1=/usr/local/smokedata/Yahoo.rrd:median:AVERAGE' 'DEF:loss1=/usr/local/smokedata/Yahoo.rrd:loss:AVERAGE' 'CDEF:ploss1=loss1,20,/,100,*' 'CDEF:dm1=median1,0,100000,LIMIT' 'DEF:pin1p1=/usr/local/smokedata/Yahoo.rrd:ping1:AVERAGE' 'CDEF:p1p1=pin1p1,UN,0,pin1p1,IF' 'DEF:pin1p2=/usr/local/smokedata/Yahoo.rrd:ping2:AVERAGE' 'CDEF:p1p2=pin1p2,UN,0,pin1p2,IF' 'DEF:pin1p3=/usr/local/smokedata/Yahoo.rrd:ping3:AVERAGE' 'CDEF:p1p3=pin1p3,UN,0,pin1p3,IF' 'DEF:pin1p4=/usr/local/smokedata/Yahoo.rrd:ping4:AVERAGE' 'CDEF:p1p4=pin1p4,UN,0,pin1p4,IF' 'DEF:pin1p5=/usr/local/smokedata/Yahoo.rrd:ping5:AVERAGE' 'CDEF:p1p5=pin1p5,UN,0,pin1p5,IF' 'DEF:pin1p6=/usr/local/smokedata/Yahoo.rrd:ping6:AVERAGE' 'CDEF:p1p6=pin1p6,UN,0,pin1p6,IF' 'DEF:pin1p7=/usr/local/smokedata/Yahoo.rrd:ping7:AVERAGE' 'CDEF:p1p7=pin1p7,UN,0,pin1p7,IF' 'DEF:pin1p8=/usr/local/smokedata/Yahoo.rrd:ping8:AVERAGE' 'CDEF:p1p8=pin1p8,UN,0,pin1p8,IF' 'DEF:pin1p9=/usr/local/smokedata/Yahoo.rrd:ping9:AVERAGE' 'CDEF:p1p9=pin1p9,UN,0,pin1p9,IF' 'DEF:pin1p10=/usr/local/smokedata/Yahoo.rrd:ping10:AVERAGE' 'CDEF:p1p10=pin1p10,UN,0,pin1p10,IF' 'DEF:pin1p11=/usr/local/smokedata/Yahoo.rrd:ping11:AVERAGE' 'CDEF:p1p11=pin1p11,UN,0,pin1p11,IF' 'DEF:pin1p12=/usr/local/smokedata/Yahoo.rrd:ping12:AVERAGE' 'CDEF:p1p12=pin1p12,UN,0,pin1p12,IF' 'DEF:pin1p13=/usr/local/smokedata/Yahoo.rrd:ping13:AVERAGE' 'CDEF:p1p13=pin1p13,UN,0,pin1p13,IF' 'DEF:pin1p14=/usr/local/smokedata/Yahoo.rrd:ping14:AVERAGE' 'CDEF:p1p14=pin1p14,UN,0,pin1p14,IF' 'DEF:pin1p15=/usr/local/smokedata/Yahoo.rrd:ping15:AVERAGE' 'CDEF:p1p15=pin1p15,UN,0,pin1p15,IF' 'DEF:pin1p16=/usr/local/smokedata/Yahoo.rrd:ping16:AVERAGE' 'CDEF:p1p16=pin1p16,UN,0,pin1p16,IF' 'DEF:pin1p17=/usr/local/smokedata/Yahoo.rrd:ping17:AVERAGE' 'CDEF:p1p17=pin1p17,UN,0,pin1p17,IF' 'DEF:pin1p18=/usr/local/smokedata/Yahoo.rrd:ping18:AVERAGE' 'CDEF:p1p18=pin1p18,UN,0,pin1p18,IF' 'DEF:pin1p19=/usr/local/smokedata/Yahoo.rrd:ping19:AVERAGE' 'CDEF:p1p19=pin1p19,UN,0,pin1p19,IF' 'DEF:pin1p20=/usr/local/smokedata/Yahoo.rrd:ping20:AVERAGE' 'CDEF:p1p20=pin1p20,UN,0,pin1p20,IF' 'CDEF:pings1=20,p1p1,UN,p1p2,UN,+,p1p3,UN,+,p1p4,UN,+,p1p5,UN,+,p1p6,UN,+,p1p7,UN,+,p1p8,UN,+,p1p9,UN,+,p1p10,UN,+,p1p11,UN,+,p1p12,UN,+,p1p13,UN,+,p1p14,UN,+,p1p15,UN,+,p1p16,UN,+,p1p17,UN,+,p1p18,UN,+,p1p19,UN,+,p1p20,UN,+,-' 'CDEF:m1=p1p1,p1p2,+,p1p3,+,p1p4,+,p1p5,+,p1p6,+,p1p7,+,p1p8,+,p1p9,+,p1p10,+,p1p11,+,p1p12,+,p1p13,+,p1p14,+,p1p15,+,p1p16,+,p1p17,+,p1p18,+,p1p19,+,p1p20,+,pings1,/' 'CDEF:sdev1=p1p1,m1,-,DUP,*,p1p2,m1,-,DUP,*,+,p1p3,m1,-,DUP,*,+,p1p4,m1,-,DUP,*,+,p1p5,m1,-,DUP,*,+,p1p6,m1,-,DUP,*,+,p1p7,m1,-,DUP,*,+,p1p8,m1,-,DUP,*,+,p1p9,m1,-,DUP,*,+,p1p10,m1,-,DUP,*,+,p1p11,m1,-,DUP,*,+,p1p12,m1,-,DUP,*,+,p1p13,m1,-,DUP,*,+,p1p14,m1,-,DUP,*,+,p1p15,m1,-,DUP,*,+,p1p16,m1,-,DUP,*,+,p1p17,m1,-,DUP,*,+,p1p18,m1,-,DUP,*,+,p1p19,m1,-,DUP,*,+,p1p20,m1,-,DUP,*,+,pings1,/,SQRT' 'CDEF:dmlow1=dm1,sdev1,2,/,-' 'CDEF:s2d1=sdev1' 'AREA:dmlow1' 'AREA:s2d1#00458630::STACK' 'LINE1:dm1#004586:med RTT' 'VDEF:avmed1=median1,AVERAGE' 'VDEF:avsd1=sdev1,AVERAGE' 'CDEF:msr1=median1,POP,avmed1,avsd1,/' 'VDEF:avmsr1=msr1,AVERAGE' 'GPRINT:avmed1:%5.1lf %ss av md ' 'GPRINT:ploss1:AVERAGE:%5.1lf %% av ls' 'GPRINT:avsd1:%5.1lf %ss av sd' 'GPRINT:avmsr1:%5.1lf %s am/as\l' HTTP error Logs shows [Wed Mar 31 22:21:54 2010] [error] [client 203.130.2.152] File does not exist: /????????????????????????????????????????????? snmp/data/mrtg/snmp, referer: http://nms.super.net.pk/cgi-bin/smokeping.cgi [Wed Mar 31 22:21:54 2010] [error] [client 203.130.2.152] File does not exist: /????????????????????????????????????????????? snmp/data/mrtg/snmp, referer: http://nms.super.net.pk/cgi-bin/smokeping.cgi [Wed Mar 31 22:21:54 2010] [error] [client 203.130.2.152] (8)Exec format error:?????????????????????????????????????????????? exec of '/snmp/data/mrtg/cgi-bin/cropper/cropper.js' failed, referer: http://nms????????????????????????????????????????????? .super.net.pk/cgi-bin/smokeping.cgi [Wed Mar 31 22:21:54 2010] [error] [client 203.130.2.152] (8)Exec format error:?????????????????????????????????????????????? exec of '/snmp/data/mrtg/cgi-bin/cropper/smokeping-zoom.js' failed, referer: htt????????????????????????????????????????????? p://nms.super.net.pk/cgi-bin/smokeping.cgi [Wed Mar 31 22:21:54 2010] [error] [client 203.130.2.152] Premature end of scrip????????????????????????????????????????????? t headers: cropper.js, referer: http://nms.super.net.pk/cgi-bin/smokeping.cgi [Wed Mar 31 22:21:54 2010] [error] [client 203.130.2.152] Premature end of scrip????????????????????????????????????????????? t headers: smokeping-zoom.js, referer: http://nms.super.net.pk/cgi-bin/smokeping????????????????????????????????????????????? .cgi I would appreciate if could have any insight to problem. Regards, Napizter -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20100331/672ca232/attachment.htm