From Hans-Peter.Rienecker at kion-ims.com Wed Jan 8 09:46:00 2014 From: Hans-Peter.Rienecker at kion-ims.com (Rienecker, Hans-Peter) Date: Wed, 8 Jan 2014 08:46:00 +0000 Subject: [smokeping-users] How to disable email alerts Message-ID: <0EA07EA508FBDF408998F66E584EB61C62DADFD9@DEFRKIM0005.d400.MH.GRP> Hello all, first of all happy new year to all of you. I'm looking for a way to completely disable email alerting in smokeping. We're using smokeping for a couple of year and in our case we do need any email alerting within smokeping. Unfortunately i did not find out how to disable it. Many thanks for any help. Best regards Hans-Peter Rienecker KION Information Management Services GmbH, Sitz der Gesellschaft: Wiesbaden, Registergericht: Wiesbaden HRB 22949, USt-Id-Nr. DE 254777238, Gesch?ftsf?hrung: Dr. Walter Gr?ner (Vorsitzender), Bart Wijnen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20140108/e343b8a5/attachment.htm From tobi at oetiker.ch Wed Jan 8 10:29:19 2014 From: tobi at oetiker.ch (Tobias Oetiker) Date: Wed, 8 Jan 2014 10:29:19 +0100 (CET) Subject: [smokeping-users] How to disable email alerts In-Reply-To: <0EA07EA508FBDF408998F66E584EB61C62DADFD9@DEFRKIM0005.d400.MH.GRP> References: <0EA07EA508FBDF408998F66E584EB61C62DADFD9@DEFRKIM0005.d400.MH.GRP> Message-ID: Hi Hans-Peter, Today Rienecker, Hans-Peter wrote: > Hello all, > > first of all happy new year to all of you. > I'm looking for a way to completely disable email alerting in smokeping. > We're using smokeping for a couple of year and in our case we do need > any email alerting within smokeping. > Unfortunately i did not find out how to disable it. > Many thanks for any help. > > Best regards > > Hans-Peter Rienecker if you do not need alerts, just remove the alert settings from the config file cheers tobi > > > KION Information Management Services GmbH, Sitz der Gesellschaft: Wiesbaden, Registergericht: Wiesbaden HRB 22949, USt-Id-Nr. DE 254777238, Gesch?ftsf?hrung: Dr. Walter Gr?ner (Vorsitzender), Bart Wijnen > -- 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 Hans-Peter.Rienecker at kion-ims.com Wed Jan 8 10:39:55 2014 From: Hans-Peter.Rienecker at kion-ims.com (Rienecker, Hans-Peter) Date: Wed, 8 Jan 2014 09:39:55 +0000 Subject: [smokeping-users] How to disable email alerts In-Reply-To: References: <0EA07EA508FBDF408998F66E584EB61C62DADFD9@DEFRKIM0005.d400.MH.GRP> Message-ID: <0EA07EA508FBDF408998F66E584EB61C62DAE0DE@DEFRKIM0005.d400.MH.GRP> Hello Tobi, many thanks for this really fast reply. Maybe i'm to stupid to get it working but what should be removed ? Here is the Alert-part of our config. Should i simply exclude the pattern lines ? Btw. we're running 2.0.9 Again many thanks. *** Alerts *** to = smokeping at our-company.com from = smokealert-new at our-company.com +bigloss type = loss # in percent pattern = ==0%,==0%,==0%,==0%,>0%,>0%,>0% comment = suddenly there is packet loss +someloss type = loss # in percent pattern = >0%,*12*,>0%,*12*,>0% comment = loss 3 times in a row +startloss type = loss # in percent pattern = ==S,>0%,>0%,>0% comment = loss at startup +rttdetect type = rtt # in milli seconds pattern = <10,<10,<10,<10,<10,<100,>100,>100,>100 comment = routing mesed up again ? Best regards Hans-Peter Rienecker -----Urspr?ngliche Nachricht----- Von: Tobias Oetiker [mailto:tobi at oetiker.ch] Gesendet: Mittwoch, 8. Januar 2014 10:29 An: Rienecker, Hans-Peter Cc: smokeping-users at lists.oetiker.ch Betreff: Re: [smokeping-users] How to disable email alerts Hi Hans-Peter, Today Rienecker, Hans-Peter wrote: > Hello all, > > first of all happy new year to all of you. > I'm looking for a way to completely disable email alerting in smokeping. > We're using smokeping for a couple of year and in our case we do need > any email alerting within smokeping. > Unfortunately i did not find out how to disable it. > Many thanks for any help. > > Best regards > > Hans-Peter Rienecker if you do not need alerts, just remove the alert settings from the config file cheers tobi > > > KION Information Management Services GmbH, Sitz der Gesellschaft: > Wiesbaden, Registergericht: Wiesbaden HRB 22949, USt-Id-Nr. DE > 254777238, Gesch?ftsf?hrung: Dr. Walter Gr?ner (Vorsitzender), Bart > Wijnen > -- 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 KION Information Management Services GmbH, Sitz der Gesellschaft: Wiesbaden, Registergericht: Wiesbaden HRB 22949, USt-Id-Nr. DE 254777238, Gesch?ftsf?hrung: Dr. Walter Gr?ner (Vorsitzender), Bart Wijnen From tobi at oetiker.ch Wed Jan 8 11:42:48 2014 From: tobi at oetiker.ch (Tobi Oetiker) Date: Wed, 8 Jan 2014 11:42:48 +0100 Subject: [smokeping-users] How to disable email alerts In-Reply-To: <0EA07EA508FBDF408998F66E584EB61C62DAE0DE@DEFRKIM0005.d400.MH.GRP> References: <0EA07EA508FBDF408998F66E584EB61C62DADFD9@DEFRKIM0005.d400.MH.GRP> <0EA07EA508FBDF408998F66E584EB61C62DAE0DE@DEFRKIM0005.d400.MH.GRP> Message-ID: <50E4D77B-76E0-4109-B9A6-34C14300F2D0@oetiker.ch> Hans-Peter you have to remove the alert settings in the target section cheers Tobias Oetiker tobi at oetiker.ch 062 775 9902 > On 08.01.2014, at 10:39, "Rienecker, Hans-Peter" wrote: > > Hello Tobi, > > many thanks for this really fast reply. > Maybe i'm to stupid to get it working but what should be removed ? > Here is the Alert-part of our config. > Should i simply exclude the pattern lines ? > Btw. we're running 2.0.9 > Again many thanks. > > *** Alerts *** > to = smokeping at our-company.com > from = smokealert-new at our-company.com > > +bigloss > type = loss > # in percent > pattern = ==0%,==0%,==0%,==0%,>0%,>0%,>0% > comment = suddenly there is packet loss > > +someloss > type = loss > # in percent > pattern = >0%,*12*,>0%,*12*,>0% > comment = loss 3 times in a row > > +startloss > type = loss > # in percent > pattern = ==S,>0%,>0%,>0% > comment = loss at startup > > +rttdetect > type = rtt > # in milli seconds > pattern = <10,<10,<10,<10,<10,<100,>100,>100,>100 > comment = routing mesed up again ? > > > Best regards > > Hans-Peter Rienecker > > -----Urspr?ngliche Nachricht----- > Von: Tobias Oetiker [mailto:tobi at oetiker.ch] > Gesendet: Mittwoch, 8. Januar 2014 10:29 > An: Rienecker, Hans-Peter > Cc: smokeping-users at lists.oetiker.ch > Betreff: Re: [smokeping-users] How to disable email alerts > > Hi Hans-Peter, > > Today Rienecker, Hans-Peter wrote: > >> Hello all, >> >> first of all happy new year to all of you. >> I'm looking for a way to completely disable email alerting in smokeping. >> We're using smokeping for a couple of year and in our case we do need >> any email alerting within smokeping. >> Unfortunately i did not find out how to disable it. >> Many thanks for any help. >> >> Best regards >> >> Hans-Peter Rienecker > > if you do not need alerts, just remove the alert settings from the config file > > cheers > tobi > >> >> >> KION Information Management Services GmbH, Sitz der Gesellschaft: >> Wiesbaden, Registergericht: Wiesbaden HRB 22949, USt-Id-Nr. DE >> 254777238, Gesch?ftsf?hrung: Dr. Walter Gr?ner (Vorsitzender), Bart >> Wijnen > > -- > 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 > KION Information Management Services GmbH, Sitz der Gesellschaft: Wiesbaden, Registergericht: Wiesbaden HRB 22949, USt-Id-Nr. DE 254777238, Gesch?ftsf?hrung: Dr. Walter Gr?ner (Vorsitzender), Bart Wijnen From Hans-Peter.Rienecker at kion-ims.com Wed Jan 8 14:46:12 2014 From: Hans-Peter.Rienecker at kion-ims.com (Rienecker, Hans-Peter) Date: Wed, 8 Jan 2014 13:46:12 +0000 Subject: [smokeping-users] How to disable email alerts In-Reply-To: <50E4D77B-76E0-4109-B9A6-34C14300F2D0@oetiker.ch> References: <0EA07EA508FBDF408998F66E584EB61C62DADFD9@DEFRKIM0005.d400.MH.GRP> <0EA07EA508FBDF408998F66E584EB61C62DAE0DE@DEFRKIM0005.d400.MH.GRP> <50E4D77B-76E0-4109-B9A6-34C14300F2D0@oetiker.ch> Message-ID: <0EA07EA508FBDF408998F66E584EB61C62DAE4EE@DEFRKIM0005.d400.MH.GRP> Hello Tobi, this did the trick - many thanks. Mit freundlichen Gr??en / Best regards /? Meilleures Salutations Hans-Peter Rienecker Dipl.Inf. (FH) TCC WAN & Security KION Information Management Services GmbH c/o Linde Material Handling GmbH Carl-von-Linde-Platz | 63743 Aschaffenburg | Germany Phone: +49 (0) 6021 99-1491 | Fax.: +49 (0) 6021 99-8-1491 Mobile: +49 (0)160 532 6477 eMail: hans-peter.rienecker at kion-ims.com -----Urspr?ngliche Nachricht----- Von: Tobi Oetiker [mailto:tobi at oetiker.ch] Gesendet: Mittwoch, 8. Januar 2014 11:43 An: Rienecker, Hans-Peter Cc: smokeping-users at lists.oetiker.ch Betreff: Re: AW: [smokeping-users] How to disable email alerts Hans-Peter you have to remove the alert settings in the target section cheers Tobias Oetiker tobi at oetiker.ch 062 775 9902 > On 08.01.2014, at 10:39, "Rienecker, Hans-Peter" wrote: > > Hello Tobi, > > many thanks for this really fast reply. > Maybe i'm to stupid to get it working but what should be removed ? > Here is the Alert-part of our config. > Should i simply exclude the pattern lines ? > Btw. we're running 2.0.9 > Again many thanks. > > *** Alerts *** > to = smokeping at our-company.com > from = smokealert-new at our-company.com > > +bigloss > type = loss > # in percent > pattern = ==0%,==0%,==0%,==0%,>0%,>0%,>0% comment = suddenly there is > packet loss > > +someloss > type = loss > # in percent > pattern = >0%,*12*,>0%,*12*,>0% > comment = loss 3 times in a row > > +startloss > type = loss > # in percent > pattern = ==S,>0%,>0%,>0% > comment = loss at startup > > +rttdetect > type = rtt > # in milli seconds > pattern = <10,<10,<10,<10,<10,<100,>100,>100,>100 > comment = routing mesed up again ? > > > Best regards > > Hans-Peter Rienecker > > -----Urspr?ngliche Nachricht----- > Von: Tobias Oetiker [mailto:tobi at oetiker.ch] > Gesendet: Mittwoch, 8. Januar 2014 10:29 > An: Rienecker, Hans-Peter > Cc: smokeping-users at lists.oetiker.ch > Betreff: Re: [smokeping-users] How to disable email alerts > > Hi Hans-Peter, > > Today Rienecker, Hans-Peter wrote: > >> Hello all, >> >> first of all happy new year to all of you. >> I'm looking for a way to completely disable email alerting in smokeping. >> We're using smokeping for a couple of year and in our case we do need >> any email alerting within smokeping. >> Unfortunately i did not find out how to disable it. >> Many thanks for any help. >> >> Best regards >> >> Hans-Peter Rienecker > > if you do not need alerts, just remove the alert settings from the > config file > > cheers > tobi > >> >> >> KION Information Management Services GmbH, Sitz der Gesellschaft: >> Wiesbaden, Registergericht: Wiesbaden HRB 22949, USt-Id-Nr. DE >> 254777238, Gesch?ftsf?hrung: Dr. Walter Gr?ner (Vorsitzender), Bart >> Wijnen > > -- > 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 KION Information Management Services GmbH, Sitz der Gesellschaft: Wiesbaden, Registergericht: Wiesbaden HRB 22949, USt-Id-Nr. DE 254777238, Gesch?ftsf?hrung: Dr. Walter Gr?ner (Vorsitzender), Bart Wijnen KION Information Management Services GmbH, Sitz der Gesellschaft: Wiesbaden, Registergericht: Wiesbaden HRB 22949, USt-Id-Nr. DE 254777238, Gesch?ftsf?hrung: Dr. Walter Gr?ner (Vorsitzender), Bart Wijnen From gert at space.net Mon Jan 13 12:19:30 2014 From: gert at space.net (Gert Doering) Date: Mon, 13 Jan 2014 12:19:30 +0100 Subject: [smokeping-users] AnotherDNS acting up with Net::DNS 0.73 Message-ID: <20140113111930.GA98687@Space.Net> Hi, I've recently upgraded perl and all perl modules on my Smokeping host (due to FreeBSD urging me to it). It's now perl 5.14.4 and Net::DNS 0.73, smokeping 2.6.9. Smokeping itself seems to work nicely, but AnotherDNS is failing in funny ways - specifically, it's claiming 4/5 loss for all DNS tests, even though I can see DNS queries going out and replies coming back (5+5, in the proper intervals as configured). In parallel, these error messages are showing up in the smokeping log: Mon Jan 13 12:05:43 2014 - *** FATAL PROGRAM ERROR!! Unknown method 'default' *** which the program has attempted to call for the object: *** *** . 0 IN OPT \# 0 *** *** This object does not have a method 'default'. THIS IS A BUG *** IN THE CALLING SOFTWARE, which incorrectly assumes that the *** object would be of a particular type. The type of an object *** should be checked before calling any of its methods. at /usr/local/lib/perl5/site_perl/5.14.2/mach/Net/DNS/Packet.pm line 183 Net::DNS::Packet::data('Net::DNS::Packet=HASH(0x90464b4)') called at /usr/local/smokeping/lib/Smokeping/probes/AnotherDNS.pm line 75 Smokeping::probes::AnotherDNS::pingone('Smokeping::probes::AnotherDNS=HASH(0x914e810)', 'HASH(0x896e6dc)') called at /usr/local/smokeping/lib/Smokeping/probes/basefork.pm line 204 Smokeping::probes::basefork::ping('Smokeping::probes::AnotherDNS=HASH(0x914e810)') called at /usr/local/smokeping/lib/Smokeping.pm line 1719 Smokeping::run_probes('HASH(0x8d39a34)', 'AnotherDNS') called at /usr/local/smokeping/lib/Smokeping.pm line 4382 Smokeping::main('/usr/local/etc/smokeping/config') called at /usr/local/bin/smokeping line 13 ... always 4 messages for each test cycle, so it seems all packet but the first are eaten by Net::DNS interactions. The line numbers in the backtrace are off, though I have no idea how *that* happened - the line that is triggering it seems to be line *76*, which is my $packet = Net::DNS::Packet->new( $lookuphost, $recordtype )->data; Before I now go and debug this: does this ring a bell for anyone? Is this a known issue, and the patch has just not been merged yet? Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 From gert at space.net Mon Jan 13 13:18:39 2014 From: gert at space.net (Gert Doering) Date: Mon, 13 Jan 2014 13:18:39 +0100 Subject: [smokeping-users] AnotherDNS acting up with Net::DNS 0.73 In-Reply-To: <20140113111930.GA98687@Space.Net> References: <20140113111930.GA98687@Space.Net> Message-ID: <20140113121839.GF40453@Space.Net> Hi, On Mon, Jan 13, 2014 at 12:19:30PM +0100, Gert Doering wrote: > I've recently upgraded perl and all perl modules on my Smokeping host > (due to FreeBSD urging me to it). It's now perl 5.14.4 and Net::DNS 0.73, > smokeping 2.6.9. [..] > Before I now go and debug this: does this ring a bell for anyone? Is this > a known issue, and the patch has just not been merged yet? Ignore that, and sorry for the noise... It turns out that there was a SmokePing instance still running from before the perl upgrade, and a second instance on the new perl - which explained the line number differences, and obviously the old instance was interfering with the new instance in some way. After killing everything and ensuring that only one instance runs, the errors in the log are gone, and the results are fine again. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 From mhaney at practichem.com Tue Jan 14 18:01:20 2014 From: mhaney at practichem.com (Mark Haney) Date: Tue, 14 Jan 2014 12:01:20 -0500 Subject: [smokeping-users] Successful install, but no graphs. Message-ID: <52D56D60.60105@practichem.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I just got started with Smokeping and I'm having what I hope is a simple issue. I followed the instructions to install smokeping here: https://www.3noled.in.th/network/install-smokeping-on-centos and did manage get a web interface. I'm testing one a single host at the moment, but while I have a web interface, I have no graphs showing in the display. I get the broken image icon. I've checked the image cache and the graphs are there, but they aren't showing up. Any ideas on the problem? I'll be glad to offer anything to help debug. The instructions above I followed exactly. I'm thinking there is a configuration error in one of the instructions, but I can't seem to find it. - -- Mark Haney Network Administrator/IT Support Practichem W:919-714-8428 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS1W1gAAoJEDgEuzPE0JQvSDQH/1KsxZbzxwX66AV/ERubvJSt F16KoPBSZPFneXX5jVADno+ywx3oZkcORcbfDqzx6uUO/dAf5kbt3LitwTLp+cmA SorPRPcIOpoksdzXtUPRxKo3adpUYCUVjjezA3FAZGg1JZ4xYUmn9LLnGAWyNZgE 7xEeOQHsA8qIZwkPIt/sgkZRGgGG++cegWUwQCxF55QJuyv5p1O7b+HW6Y+atuZ1 vAoAzt/YhIaDpsJx9cMr8wLwqLFsGVqo7T9yxZ6S+RY30JD/nEcgoj0o5/dwVnuS Utsv2elTFvVSLbBAsvF0w1USM7MeETQ53CiAxam+puSFMLbO861/Vao5QwcBCVA= =r2Nq -----END PGP SIGNATURE----- From mhaney at practichem.com Tue Jan 14 19:29:34 2014 From: mhaney at practichem.com (Mark Haney) Date: Tue, 14 Jan 2014 13:29:34 -0500 Subject: [smokeping-users] Successful install, but no graphs. -- update In-Reply-To: <52D56D60.60105@practichem.com> References: <52D56D60.60105@practichem.com> Message-ID: <52D5820E.60306@practichem.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/14/2014 12:01 PM, Mark Haney wrote: > Hi all, I just got started with Smokeping and I'm having what I > hope is a simple issue. I followed the instructions to install > smokeping here: > https://www.3noled.in.th/network/install-smokeping-on-centos and > did manage get a web interface. I'm testing one a single host at > the moment, but while I have a web interface, I have no graphs > showing in the display. I get the broken image icon. > > I've checked the image cache and the graphs are there, but they > aren't showing up. Any ideas on the problem? I'll be glad to offer > anything to help debug. > > The instructions above I followed exactly. I'm thinking there is > a configuration error in one of the instructions, but I can't seem > to find it. > Okay, I made a couple of changes to the configuration (based on this: http://www.wedebugyou.com/2012/11/how-to-install-and-configure-smokeping-on-centos-6/) and can /sort of/ get graphs. I still get the 'broken image' icon on the various pages, however, when I drill down to the only host I am monitoring (pinging only for now) instead of just getting the broken image icon I get a '+' when I move my mouse over where the graph would be and can drag through the image to (presumably) zoom down to a tighter time range and I get a graph. Why am I not getting graphs anyway else? - -- Mark Haney Network Administrator/IT Support Practichem W:919-714-8428 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS1YIOAAoJEDgEuzPE0JQvSlcIAMlVwO6raqL0aVXkK8oBWBrD yqXDz93a6hKu14/yoxwvyyRcmbdbUfqdwTA7wor1UL3oqFhishNDVw3MDLs5saj6 gfv/QP5mMB4NjwzqQewFRYHds5rKrwQBevHvIU8hiv//N8/sAB0FTQC0fmMrief4 K/BrqY9pKYqVeRTo2Aow49cMz2+9rSDlosx+8Gdys3cUKtFN0xzQF7cYgxI3CE1J QcR3RX+EGYGCrysz3U7kt7xuMxeHkYniPsY3J8+tonWow24xx3RO2nTck8O5e4kO RAsCiWZigjBCamvT3oFrp9M7MoTD/sQJDGOIQ8hKZVpWzyhoN/4SAgzKPuktkus= =I2ue -----END PGP SIGNATURE----- From gregs at sloop.net Tue Jan 14 22:03:34 2014 From: gregs at sloop.net (Gregory Sloop) Date: Tue, 14 Jan 2014 13:03:34 -0800 Subject: [smokeping-users] Successful install, but no graphs. -- update In-Reply-To: <52D5820E.60306@practichem.com> References: <52D56D60.60105@practichem.com> <52D5820E.60306@practichem.com> Message-ID: <383017278.20140114130334@sloop.net> [Top posting] Here's the FAQ: https://github.com/oetiker/SmokePing/issues/11 --- I'll cut and paste from my "usual" spiel. Assuming the isn't a master/slave setup. [I'm not sure why you get a graph on drill-down - that doesn't seem right, but the initial thought matches the FAQ. See if this helps. --- Graphs are empty! These have two root causes: 1) Data not reaching the RRD [round robin databases] Run smokeping in debug mode and watch what it says - you'll probably find some good reasons stuff isn't working and be able to fix it yourself. Like this: smokeping --debug 2) Data is hitting the RRD's as confirmed by --debug. However, you still get an empty graph from the browser. You see: the user smokeping is running as, is writing the data - that's often root or smokeping. However, the thing that's creating the graphs has to read the data - and that's whatever process your web-server is running as. That's often apache or www, httpd or www-data. [It depends on the apache [or how your distro sets it] configuration - or whatever other web-server you're using.] So, make sure that both the user smokeping is running as, as well as the user the web-server is running as, both have rights to the RRD's. [If you aren't sure what apache is running at, have a look at the apache config files. For example Ubuntu 12.04 has the user in /etc/apache2/envvars - and the user is www-data.] So, to spoon-feed you - you'll need to chown the files to something like: chown smokeping:www-data some-rrd-files*.rrd -Greg --- MH> -----BEGIN PGP SIGNED MESSAGE----- MH> Hash: SHA1 MH> On 1/14/2014 12:01 PM, Mark Haney wrote: >> Hi all, I just got started with Smokeping and I'm having what I >> hope is a simple issue. I followed the instructions to install >> smokeping here: >> https://www.3noled.in.th/network/install-smokeping-on-centos and >> did manage get a web interface. I'm testing one a single host at >> the moment, but while I have a web interface, I have no graphs >> showing in the display. I get the broken image icon. >> >> I've checked the image cache and the graphs are there, but they >> aren't showing up. Any ideas on the problem? I'll be glad to offer >> anything to help debug. >> >> The instructions above I followed exactly. I'm thinking there is >> a configuration error in one of the instructions, but I can't seem >> to find it. >> MH> Okay, I made a couple of changes to the configuration (based on this: MH> http://www.wedebugyou.com/2012/11/how-to-install-and-configure-smokeping-on-centos-6/) MH> and can /sort of/ get graphs. MH> I still get the 'broken image' icon on the various pages, however, MH> when I drill down to the only host I am monitoring (pinging only for MH> now) instead of just getting the broken image icon I get a '+' when I MH> move my mouse over where the graph would be and can drag through the MH> image to (presumably) zoom down to a tighter time range and I get a MH> graph. MH> Why am I not getting graphs anyway else? -- Gregory Sloop, Principal: Sloop Network & Computer Consulting Voice: 503.251.0452 x82 EMail: gregs at sloop.net http://www.sloop.net --- From jonesamu at isu.edu Wed Jan 15 05:23:13 2014 From: jonesamu at isu.edu (Samuel Jones) Date: Tue, 14 Jan 2014 21:23:13 -0700 Subject: [smokeping-users] Smokeping.fcgi permission denied for smokeping_cgi Message-ID: I currently have a new first time install of smokeping and I am trying to get the Web interface to display something. When I request the Web page on a browser I get in the Apache error log, permission denied on line 2 of the smokeping.fcgi file. The permissions on both smokeping.fcgi and smokping_cgi are a 755. When I run the files from the command line they produce output on the terminal that looks correct. Any assistance is appreciated. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20140114/dcac896c/attachment.htm From paul.mansfield+smokeping at grapeshot.co.uk Wed Jan 15 12:46:52 2014 From: paul.mansfield+smokeping at grapeshot.co.uk (Paul Mansfield) Date: Wed, 15 Jan 2014 11:46:52 +0000 Subject: [smokeping-users] Smokeping.fcgi permission denied for smokeping_cgi In-Reply-To: References: Message-ID: when you say you run them on the command line, are you doing so as the apache/httpd user, or as root? it could be an selinux problem? From mhaney at practichem.com Wed Jan 15 15:15:08 2014 From: mhaney at practichem.com (Mark Haney) Date: Wed, 15 Jan 2014 09:15:08 -0500 Subject: [smokeping-users] Successful install, but no graphs. -- update In-Reply-To: <383017278.20140114130334@sloop.net> References: <52D56D60.60105@practichem.com> <52D5820E.60306@practichem.com> <383017278.20140114130334@sloop.net> Message-ID: <52D697EC.9050806@practichem.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/14/2014 4:03 PM, Gregory Sloop wrote: > [Top posting] > > Here's the FAQ: > > https://github.com/oetiker/SmokePing/issues/11 > > 1) Data not reaching the RRD [round robin databases] Run smokeping > in debug mode and watch what it says - you'll probably find some > good reasons stuff isn't working and be able to fix it yourself. > Like this: smokeping --debug > > 2) Data is hitting the RRD's as confirmed by --debug. However, you > still get an empty graph from the browser. > > You see: the user smokeping is running as, is writing the data - > that's often root or smokeping. However, the thing that's creating > the graphs has to read the data - and that's whatever process your > web-server is running as. That's often apache or www, httpd or > www-data. > > [It depends on the apache [or how your distro sets it] > configuration - or whatever other web-server you're using.] > > So, make sure that both the user smokeping is running as, as well > as the user the web-server is running as, both have rights to the > RRD's. [If you aren't sure what apache is running at, have a look > at the apache config files. For example Ubuntu 12.04 has the user > in /etc/apache2/envvars - and the user is www-data.] > > So, to spoon-feed you - you'll need to chown the files to something > like: chown smokeping:www-data some-rrd-files*.rrd > > -Greg First off, it's not just the images of the graphs I'm not getting, I'm also not getting the counter image, nor the RRDtool image. I get the same broken image in their place. So it's not a read/write issue with only the graphs. Let me show you what I have setup: (smokeping is run as root and apache is the httpd user (I'm on CentOS 6.5). [root at mon smokeping]# ls -l total 36 drwxr-xr-x. 2 root root 4096 Jan 14 09:58 bin lrwxrwxrwx. 1 apache root 20 Jan 14 10:07 cache -> /var/www/html/cache/ drwxrwxrw-. 5 apache root 4096 Jan 14 10:27 data drwxr-xr-x. 3 root root 4096 Jan 14 13:02 etc drwxr-xr-x. 3 root root 4096 Jan 14 09:58 htdocs drwxr-xr-x. 3 root root 4096 Jan 14 09:58 lib drwxr-xr-x. 3 root root 4096 Jan 14 09:58 share - -rw-r--r--. 1 root root 302 Jan 14 13:06 smoke.log drwxr-xr-x. 6 root root 4096 Jan 14 09:57 thirdparty drwxr-xr-x. 2 root root 4096 Jan 14 10:07 var When I run smokeping with --debug I get this: [root at mon smokeping]# ./bin/smokeping --debug ### Compiling alert detector pattern 'someloss' ### >0%,*12*,>0%,*12*,>0% sub { my $d = shift; my $y = $d->{loss}; for(1){ my $imax2 = min(@$y - 3, 12); my $imax1 = min(@$y - 3, 12); my $minlength = 3; my $maxlength = 27; next if scalar @$y < $minlength ; my $i1; for($i1=0; $i1 < min($maxlength,$imax1); $i1++){ my $i2; for($i2=0; $i2 < min($maxlength-$i1,$imax2); $i2++){ next unless defined $y->[-3-$i1-$i2] and $y->[-3-$i1-$i2] =~ /^\d/ and $y->[-3-$i1-$i2] > 0 ; last; } return 0 if $i2 >= min($maxlength-$i1-$i2,$imax2); next unless defined $y->[-2-$i1] and $y->[-2-$i1] =~ /^\d/ and $y->[-2-$i1] > 0 ; last; } return 0 if $i1 >= min($maxlength-$i1,$imax1); next unless defined $y->[-1] and $y->[-1] =~ /^\d/ and $y->[-1] > 0 ; return 1; } return 0; } Smokeping version 2.006009 successfully launched. Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for that. FPing: probing 1 targets with step 300 s and offset 241 s. FPing: Executing /usr/sbin/fping -C 20 -q -B1 -r1 -i10 66.188.99.174 FPing: Got fping output: '66.188.99.174 : 269.98 183.10 81.46 118.87 82.20 79.97 85.42 81.77 82.68 82.11 82.29 87.19 80.58 82.50 82.84 82.56 80.92 80.20 81.37 104.47' Calling RRDs::update(/opt/smokeping/data/MTC/ASUSWifi.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 1389793594:U:0:8.2500000000e-02:7.9970000000e-02:8.0200000000e-02:8.0580000000e-02:8.0920000000e-02:8.1370000000e-02:8.1460000000e-02:8.1770000000e-02:8.2110000000e-02:8.2200000000e-02:8.2290000000e-02:8.2500000000e-02:8.2560000000e-02:8.2680000000e-02:8.2840000000e-02:8.5420000000e-02:8.7190000000e-02:1.0447000000e-01:1.1887000000e-01:1.8310000000e-01:2.6998000000e-01) So it certainly looks like the RRDs are being written: [root at mon smokeping]# ls -l cache/MTC/ total 132 - -rw-r--r--. 1 apache apache 29323 Jan 15 08:43 ASUSWifi_last_108000.png - -rw-r--r--. 1 apache apache 26737 Jan 15 08:43 ASUSWifi_last_10800.png - -rw-r--r--. 1 apache apache 26326 Jan 15 08:43 ASUSWifi_last_34560000.png - -rw-r--r--. 1 apache apache 26224 Jan 15 08:43 ASUSWifi_last_864000.png - -rw-r--r--. 1 apache apache 44 Jan 15 08:43 ASUSWifi.maxheight - -rw-r--r--. 1 apache apache 11742 Jan 15 08:59 ASUSWifi_mini.png 8:43 being the time I ran that command this morning. Here's the listing in /var/www/: [root at mon var]# ls www/html/cache/ -l total 28 drwxr-xr-x. 2 apache root 4096 Jan 14 13:08 __chartscache drwxr-xr-x. 2 apache root 4096 Jan 14 10:27 MTC drwxr-xr-x. 2 apache root 4096 Jan 15 09:07 __navcache - -rw-r--r--. 1 apache root 3908 Jan 14 10:15 rrdtool.png - -rw-r--r--. 1 apache root 4382 Jan 14 10:15 smokeping.png drwxr-xr-x. 2 apache root 4096 Jan 14 10:15 Test [root at mon var]# ls www/html/cache/MTC/ ASUSWifi_last_108000.png ASUSWifi_last_10800.png ASUSWifi_last_34560000.png ASUSWifi_last_864000.png ASUSWifi.maxheight ASUSWifi_mini.png [root at mon var]# ls www/html/cache/MTC/ -l total 132 - -rw-r--r--. 1 apache root 29191 Jan 15 09:07 ASUSWifi_last_108000.png - -rw-r--r--. 1 apache root 28220 Jan 15 09:07 ASUSWifi_last_10800.png - -rw-r--r--. 1 apache root 25284 Jan 15 09:07 ASUSWifi_last_34560000.png - -rw-r--r--. 1 apache root 26784 Jan 15 09:07 ASUSWifi_last_864000.png - -rw-r--r--. 1 apache root 42 Jan 15 09:07 ASUSWifi.maxheight - -rw-r--r--. 1 apache root 11542 Jan 15 09:07 ASUSWifi_mini.png Now, by all rights, the apache user /should/ be able to read and display the PNG file for the RRDtool and the SmokePing counter. But they are not showing up. I'm at a loss and getting in credibly frustrated by this. It should not be that hard to make this work. I've used and configured apache dozens of times and this makes no sense at all. - -- Mark Haney Network Administrator/IT Support Practichem W:919-714-8428 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS1pfsAAoJEDgEuzPE0JQvQMcH+gOWr6ZXL1GxtBvR37ecQHdq V7QyrwBKc9vd5ebRx6b9Z3wpmuJIs/Ts77m8djZCiw1ILw+xOCj2SeShU60DjsZ5 D5vHhnwhTrrleqmoRF0p4hQ40WoEj+aKLm5y/qssB08Q73sgDDH6okKuRlaI3NKv VJIQJWJBMmNHSs/G2sd8jB7rzSiRm8RtGygN3TFTLhjAdCs8IAPhbKRK9nYwxS5f nDqwZZEUc2ii2CAPT0oVrfI1edYAxfQZEZ82ehOxLwML5EwskTBynsib05V4zweg KHfvET98wYmisQCGkW8pAIkxPR8NNluPOwGu9bYpK7cRwYXcEdBvf0ZXDNWFjt8= =McCX -----END PGP SIGNATURE----- From gregs at sloop.net Wed Jan 15 15:53:25 2014 From: gregs at sloop.net (Greg Sloop ) Date: Wed, 15 Jan 2014 06:53:25 -0800 Subject: [smokeping-users] Successful install, but no graphs. -- update In-Reply-To: <52D697EC.9050806@practichem.com> References: <52D56D60.60105@practichem.com> <52D5820E.60306@practichem.com> <383017278.20140114130334@sloop.net> <52D697EC.9050806@practichem.com> Message-ID: What do the apache logs show? On Jan 15, 2014 6:15 AM, "Mark Haney" wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 1/14/2014 4:03 PM, Gregory Sloop wrote: > > [Top posting] > > > > Here's the FAQ: > > > > https://github.com/oetiker/SmokePing/issues/11 > > > > > 1) Data not reaching the RRD [round robin databases] Run smokeping > > in debug mode and watch what it says - you'll probably find some > > good reasons stuff isn't working and be able to fix it yourself. > > Like this: smokeping --debug > > > > 2) Data is hitting the RRD's as confirmed by --debug. However, you > > still get an empty graph from the browser. > > > > You see: the user smokeping is running as, is writing the data - > > that's often root or smokeping. However, the thing that's creating > > the graphs has to read the data - and that's whatever process your > > web-server is running as. That's often apache or www, httpd or > > www-data. > > > > [It depends on the apache [or how your distro sets it] > > configuration - or whatever other web-server you're using.] > > > > So, make sure that both the user smokeping is running as, as well > > as the user the web-server is running as, both have rights to the > > RRD's. [If you aren't sure what apache is running at, have a look > > at the apache config files. For example Ubuntu 12.04 has the user > > in /etc/apache2/envvars - and the user is www-data.] > > > > So, to spoon-feed you - you'll need to chown the files to something > > like: chown smokeping:www-data some-rrd-files*.rrd > > > > -Greg > > First off, it's not just the images of the graphs I'm not getting, I'm > also not getting the counter image, nor the RRDtool image. I get the > same broken image in their place. So it's not a read/write issue with > only the graphs. > > Let me show you what I have setup: (smokeping is run as root and > apache is the httpd user (I'm on CentOS 6.5). > > > [root at mon smokeping]# ls -l > total 36 > drwxr-xr-x. 2 root root 4096 Jan 14 09:58 bin > lrwxrwxrwx. 1 apache root 20 Jan 14 10:07 cache -> /var/www/html/cache/ > drwxrwxrw-. 5 apache root 4096 Jan 14 10:27 data > drwxr-xr-x. 3 root root 4096 Jan 14 13:02 etc > drwxr-xr-x. 3 root root 4096 Jan 14 09:58 htdocs > drwxr-xr-x. 3 root root 4096 Jan 14 09:58 lib > drwxr-xr-x. 3 root root 4096 Jan 14 09:58 share > - -rw-r--r--. 1 root root 302 Jan 14 13:06 smoke.log > drwxr-xr-x. 6 root root 4096 Jan 14 09:57 thirdparty > drwxr-xr-x. 2 root root 4096 Jan 14 10:07 var > > When I run smokeping with --debug I get this: > > [root at mon smokeping]# ./bin/smokeping --debug > ### Compiling alert detector pattern 'someloss' > ### >0%,*12*,>0%,*12*,>0% > sub { > my $d = shift; > my $y = $d->{loss}; > for(1){ > my $imax2 = min(@$y - 3, 12); > my $imax1 = min(@$y - 3, 12); > my $minlength = 3; > my $maxlength = 27; > next if scalar @$y < $minlength ; > my $i1; > for($i1=0; $i1 < min($maxlength,$imax1); $i1++){ > my $i2; > for($i2=0; $i2 < min($maxlength-$i1,$imax2); $i2++){ > next unless defined $y->[-3-$i1-$i2] > and $y->[-3-$i1-$i2] =~ /^\d/ > and $y->[-3-$i1-$i2] > 0 > ; last; > } > return 0 if $i2 >= min($maxlength-$i1-$i2,$imax2); > next unless defined $y->[-2-$i1] > and $y->[-2-$i1] =~ /^\d/ > and $y->[-2-$i1] > 0 > ; last; > } > return 0 if $i1 >= min($maxlength-$i1,$imax1); > next unless defined $y->[-1] > and $y->[-1] =~ /^\d/ > and $y->[-1] > 0 > ; return 1; > } > return 0; > } > > > > Smokeping version 2.006009 successfully launched. > Not entering multiprocess mode with '--debug'. Use '--debug-daemon' > for that. > FPing: probing 1 targets with step 300 s and offset 241 s. > FPing: Executing /usr/sbin/fping -C 20 -q -B1 -r1 -i10 66.188.99.174 > FPing: Got fping output: '66.188.99.174 : 269.98 183.10 81.46 118.87 > 82.20 79.97 85.42 81.77 82.68 82.11 82.29 87.19 80.58 82.50 82.84 > 82.56 80.92 80.20 81.37 104.47' > Calling RRDs::update(/opt/smokeping/data/MTC/ASUSWifi.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 > > 1389793594:U:0:8.2500000000e-02:7.9970000000e-02:8.0200000000e-02:8.0580000000e-02:8.0920000000e-02:8.1370000000e-02:8.1460000000e-02:8.1770000000e-02:8.2110000000e-02:8.2200000000e-02:8.2290000000e-02:8.2500000000e-02:8.2560000000e-02:8.2680000000e-02:8.2840000000e-02:8.5420000000e-02:8.7190000000e-02:1.0447000000e-01:1.1887000000e-01:1.8310000000e-01:2.6998000000e-01) > > So it certainly looks like the RRDs are being written: > > [root at mon smokeping]# ls -l cache/MTC/ > total 132 > - -rw-r--r--. 1 apache apache 29323 Jan 15 08:43 ASUSWifi_last_108000.png > - -rw-r--r--. 1 apache apache 26737 Jan 15 08:43 ASUSWifi_last_10800.png > - -rw-r--r--. 1 apache apache 26326 Jan 15 08:43 ASUSWifi_last_34560000.png > - -rw-r--r--. 1 apache apache 26224 Jan 15 08:43 ASUSWifi_last_864000.png > - -rw-r--r--. 1 apache apache 44 Jan 15 08:43 ASUSWifi.maxheight > - -rw-r--r--. 1 apache apache 11742 Jan 15 08:59 ASUSWifi_mini.png > > 8:43 being the time I ran that command this morning. > > Here's the listing in /var/www/: > > [root at mon var]# ls www/html/cache/ -l > total 28 > drwxr-xr-x. 2 apache root 4096 Jan 14 13:08 __chartscache > drwxr-xr-x. 2 apache root 4096 Jan 14 10:27 MTC > drwxr-xr-x. 2 apache root 4096 Jan 15 09:07 __navcache > - -rw-r--r--. 1 apache root 3908 Jan 14 10:15 rrdtool.png > - -rw-r--r--. 1 apache root 4382 Jan 14 10:15 smokeping.png > drwxr-xr-x. 2 apache root 4096 Jan 14 10:15 Test > [root at mon var]# ls www/html/cache/MTC/ > ASUSWifi_last_108000.png ASUSWifi_last_10800.png > ASUSWifi_last_34560000.png ASUSWifi_last_864000.png > ASUSWifi.maxheight ASUSWifi_mini.png > [root at mon var]# ls www/html/cache/MTC/ -l > total 132 > - -rw-r--r--. 1 apache root 29191 Jan 15 09:07 ASUSWifi_last_108000.png > - -rw-r--r--. 1 apache root 28220 Jan 15 09:07 ASUSWifi_last_10800.png > - -rw-r--r--. 1 apache root 25284 Jan 15 09:07 ASUSWifi_last_34560000.png > - -rw-r--r--. 1 apache root 26784 Jan 15 09:07 ASUSWifi_last_864000.png > - -rw-r--r--. 1 apache root 42 Jan 15 09:07 ASUSWifi.maxheight > - -rw-r--r--. 1 apache root 11542 Jan 15 09:07 ASUSWifi_mini.png > > Now, by all rights, the apache user /should/ be able to read and > display the PNG file for the RRDtool and the SmokePing counter. But > they are not showing up. I'm at a loss and getting in credibly > frustrated by this. It should not be that hard to make this work. > I've used and configured apache dozens of times and this makes no > sense at all. > > > > > - -- > Mark Haney > Network Administrator/IT Support > Practichem > W:919-714-8428 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (MingW32) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJS1pfsAAoJEDgEuzPE0JQvQMcH+gOWr6ZXL1GxtBvR37ecQHdq > V7QyrwBKc9vd5ebRx6b9Z3wpmuJIs/Ts77m8djZCiw1ILw+xOCj2SeShU60DjsZ5 > D5vHhnwhTrrleqmoRF0p4hQ40WoEj+aKLm5y/qssB08Q73sgDDH6okKuRlaI3NKv > VJIQJWJBMmNHSs/G2sd8jB7rzSiRm8RtGygN3TFTLhjAdCs8IAPhbKRK9nYwxS5f > nDqwZZEUc2ii2CAPT0oVrfI1edYAxfQZEZ82ehOxLwML5EwskTBynsib05V4zweg > KHfvET98wYmisQCGkW8pAIkxPR8NNluPOwGu9bYpK7cRwYXcEdBvf0ZXDNWFjt8= > =McCX > -----END PGP SIGNATURE----- > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20140115/cddb2b22/attachment-0001.htm From jonesamu at isu.edu Wed Jan 15 16:46:33 2014 From: jonesamu at isu.edu (Samuel Jones) Date: Wed, 15 Jan 2014 08:46:33 -0700 Subject: [smokeping-users] Smokeping.fcgi permission denied for smokeping_cgi In-Reply-To: References: Message-ID: selinux was the issue thanks for the help On Wed, Jan 15, 2014 at 4:46 AM, Paul Mansfield < paul.mansfield+smokeping at grapeshot.co.uk> wrote: > when you say you run them on the command line, are you doing so as the > apache/httpd user, or as root? > > it could be an selinux problem? > -- *Sam Jones *|| CCNA Network Administrator || Idaho State University jonesamu at isu.edu || (208) 282-4525 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20140115/47c4a70c/attachment.htm From rb14060 at gmail.com Wed Jan 15 16:57:52 2014 From: rb14060 at gmail.com (Ryan Becker) Date: Wed, 15 Jan 2014 10:57:52 -0500 Subject: [smokeping-users] Successful install, but no graphs. -- update In-Reply-To: <52D697EC.9050806@practichem.com> References: <52D56D60.60105@practichem.com> <52D5820E.60306@practichem.com> <383017278.20140114130334@sloop.net> <52D697EC.9050806@practichem.com> Message-ID: Make sure that your Apache and SmokePing users can read/write the directory where the data is stored. There was just some discussion about a day ago on this list about that very issue. Look back and I'm sure you can find it ;) On Jan 15, 2014 9:15 AM, "Mark Haney" wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 1/14/2014 4:03 PM, Gregory Sloop wrote: > > [Top posting] > > > > Here's the FAQ: > > > > https://github.com/oetiker/SmokePing/issues/11 > > > > > 1) Data not reaching the RRD [round robin databases] Run smokeping > > in debug mode and watch what it says - you'll probably find some > > good reasons stuff isn't working and be able to fix it yourself. > > Like this: smokeping --debug > > > > 2) Data is hitting the RRD's as confirmed by --debug. However, you > > still get an empty graph from the browser. > > > > You see: the user smokeping is running as, is writing the data - > > that's often root or smokeping. However, the thing that's creating > > the graphs has to read the data - and that's whatever process your > > web-server is running as. That's often apache or www, httpd or > > www-data. > > > > [It depends on the apache [or how your distro sets it] > > configuration - or whatever other web-server you're using.] > > > > So, make sure that both the user smokeping is running as, as well > > as the user the web-server is running as, both have rights to the > > RRD's. [If you aren't sure what apache is running at, have a look > > at the apache config files. For example Ubuntu 12.04 has the user > > in /etc/apache2/envvars - and the user is www-data.] > > > > So, to spoon-feed you - you'll need to chown the files to something > > like: chown smokeping:www-data some-rrd-files*.rrd > > > > -Greg > > First off, it's not just the images of the graphs I'm not getting, I'm > also not getting the counter image, nor the RRDtool image. I get the > same broken image in their place. So it's not a read/write issue with > only the graphs. > > Let me show you what I have setup: (smokeping is run as root and > apache is the httpd user (I'm on CentOS 6.5). > > > [root at mon smokeping]# ls -l > total 36 > drwxr-xr-x. 2 root root 4096 Jan 14 09:58 bin > lrwxrwxrwx. 1 apache root 20 Jan 14 10:07 cache -> /var/www/html/cache/ > drwxrwxrw-. 5 apache root 4096 Jan 14 10:27 data > drwxr-xr-x. 3 root root 4096 Jan 14 13:02 etc > drwxr-xr-x. 3 root root 4096 Jan 14 09:58 htdocs > drwxr-xr-x. 3 root root 4096 Jan 14 09:58 lib > drwxr-xr-x. 3 root root 4096 Jan 14 09:58 share > - -rw-r--r--. 1 root root 302 Jan 14 13:06 smoke.log > drwxr-xr-x. 6 root root 4096 Jan 14 09:57 thirdparty > drwxr-xr-x. 2 root root 4096 Jan 14 10:07 var > > When I run smokeping with --debug I get this: > > [root at mon smokeping]# ./bin/smokeping --debug > ### Compiling alert detector pattern 'someloss' > ### >0%,*12*,>0%,*12*,>0% > sub { > my $d = shift; > my $y = $d->{loss}; > for(1){ > my $imax2 = min(@$y - 3, 12); > my $imax1 = min(@$y - 3, 12); > my $minlength = 3; > my $maxlength = 27; > next if scalar @$y < $minlength ; > my $i1; > for($i1=0; $i1 < min($maxlength,$imax1); $i1++){ > my $i2; > for($i2=0; $i2 < min($maxlength-$i1,$imax2); $i2++){ > next unless defined $y->[-3-$i1-$i2] > and $y->[-3-$i1-$i2] =~ /^\d/ > and $y->[-3-$i1-$i2] > 0 > ; last; > } > return 0 if $i2 >= min($maxlength-$i1-$i2,$imax2); > next unless defined $y->[-2-$i1] > and $y->[-2-$i1] =~ /^\d/ > and $y->[-2-$i1] > 0 > ; last; > } > return 0 if $i1 >= min($maxlength-$i1,$imax1); > next unless defined $y->[-1] > and $y->[-1] =~ /^\d/ > and $y->[-1] > 0 > ; return 1; > } > return 0; > } > > > > Smokeping version 2.006009 successfully launched. > Not entering multiprocess mode with '--debug'. Use '--debug-daemon' > for that. > FPing: probing 1 targets with step 300 s and offset 241 s. > FPing: Executing /usr/sbin/fping -C 20 -q -B1 -r1 -i10 66.188.99.174 > FPing: Got fping output: '66.188.99.174 : 269.98 183.10 81.46 118.87 > 82.20 79.97 85.42 81.77 82.68 82.11 82.29 87.19 80.58 82.50 82.84 > 82.56 80.92 80.20 81.37 104.47' > Calling RRDs::update(/opt/smokeping/data/MTC/ASUSWifi.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 > > 1389793594:U:0:8.2500000000e-02:7.9970000000e-02:8.0200000000e-02:8.0580000000e-02:8.0920000000e-02:8.1370000000e-02:8.1460000000e-02:8.1770000000e-02:8.2110000000e-02:8.2200000000e-02:8.2290000000e-02:8.2500000000e-02:8.2560000000e-02:8.2680000000e-02:8.2840000000e-02:8.5420000000e-02:8.7190000000e-02:1.0447000000e-01:1.1887000000e-01:1.8310000000e-01:2.6998000000e-01) > > So it certainly looks like the RRDs are being written: > > [root at mon smokeping]# ls -l cache/MTC/ > total 132 > - -rw-r--r--. 1 apache apache 29323 Jan 15 08:43 ASUSWifi_last_108000.png > - -rw-r--r--. 1 apache apache 26737 Jan 15 08:43 ASUSWifi_last_10800.png > - -rw-r--r--. 1 apache apache 26326 Jan 15 08:43 ASUSWifi_last_34560000.png > - -rw-r--r--. 1 apache apache 26224 Jan 15 08:43 ASUSWifi_last_864000.png > - -rw-r--r--. 1 apache apache 44 Jan 15 08:43 ASUSWifi.maxheight > - -rw-r--r--. 1 apache apache 11742 Jan 15 08:59 ASUSWifi_mini.png > > 8:43 being the time I ran that command this morning. > > Here's the listing in /var/www/: > > [root at mon var]# ls www/html/cache/ -l > total 28 > drwxr-xr-x. 2 apache root 4096 Jan 14 13:08 __chartscache > drwxr-xr-x. 2 apache root 4096 Jan 14 10:27 MTC > drwxr-xr-x. 2 apache root 4096 Jan 15 09:07 __navcache > - -rw-r--r--. 1 apache root 3908 Jan 14 10:15 rrdtool.png > - -rw-r--r--. 1 apache root 4382 Jan 14 10:15 smokeping.png > drwxr-xr-x. 2 apache root 4096 Jan 14 10:15 Test > [root at mon var]# ls www/html/cache/MTC/ > ASUSWifi_last_108000.png ASUSWifi_last_10800.png > ASUSWifi_last_34560000.png ASUSWifi_last_864000.png > ASUSWifi.maxheight ASUSWifi_mini.png > [root at mon var]# ls www/html/cache/MTC/ -l > total 132 > - -rw-r--r--. 1 apache root 29191 Jan 15 09:07 ASUSWifi_last_108000.png > - -rw-r--r--. 1 apache root 28220 Jan 15 09:07 ASUSWifi_last_10800.png > - -rw-r--r--. 1 apache root 25284 Jan 15 09:07 ASUSWifi_last_34560000.png > - -rw-r--r--. 1 apache root 26784 Jan 15 09:07 ASUSWifi_last_864000.png > - -rw-r--r--. 1 apache root 42 Jan 15 09:07 ASUSWifi.maxheight > - -rw-r--r--. 1 apache root 11542 Jan 15 09:07 ASUSWifi_mini.png > > Now, by all rights, the apache user /should/ be able to read and > display the PNG file for the RRDtool and the SmokePing counter. But > they are not showing up. I'm at a loss and getting in credibly > frustrated by this. It should not be that hard to make this work. > I've used and configured apache dozens of times and this makes no > sense at all. > > > > > - -- > Mark Haney > Network Administrator/IT Support > Practichem > W:919-714-8428 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (MingW32) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJS1pfsAAoJEDgEuzPE0JQvQMcH+gOWr6ZXL1GxtBvR37ecQHdq > V7QyrwBKc9vd5ebRx6b9Z3wpmuJIs/Ts77m8djZCiw1ILw+xOCj2SeShU60DjsZ5 > D5vHhnwhTrrleqmoRF0p4hQ40WoEj+aKLm5y/qssB08Q73sgDDH6okKuRlaI3NKv > VJIQJWJBMmNHSs/G2sd8jB7rzSiRm8RtGygN3TFTLhjAdCs8IAPhbKRK9nYwxS5f > nDqwZZEUc2ii2CAPT0oVrfI1edYAxfQZEZ82ehOxLwML5EwskTBynsib05V4zweg > KHfvET98wYmisQCGkW8pAIkxPR8NNluPOwGu9bYpK7cRwYXcEdBvf0ZXDNWFjt8= > =McCX > -----END PGP SIGNATURE----- > > _______________________________________________ > 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/20140115/49f4b3a0/attachment.htm From vrc.vlm at gmail.com Mon Jan 20 14:53:20 2014 From: vrc.vlm at gmail.com (=?ISO-8859-1?Q?Victor_Rafael_Rodriguez_Cort=E9s?=) Date: Mon, 20 Jan 2014 14:53:20 +0100 Subject: [smokeping-users] Permanently store/archive historical data Message-ID: Hello, I have a set of routers monitored with smokeping for a couple of years. Now, I'm going to replace them with new equipment with new IP addresses. I've searched unsuccessfully to find a way to make Smokeping stop testing the old IPs but still allow access to the data and graphs it has collected until now from the web interface. I would like to be able to view those graphs but not waste resources checking IP's that will no longer exists in my network. Is there a way to accomplish that? Thanks! Victor. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20140120/e3a0fa46/attachment.html From gregs at sloop.net Tue Jan 21 00:39:23 2014 From: gregs at sloop.net (Gregory Sloop) Date: Mon, 20 Jan 2014 15:39:23 -0800 Subject: [smokeping-users] Permanently store/archive historical data In-Reply-To: References: Message-ID: <981231810.20140120153923@sloop.net> An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20140120/87188f19/attachment.htm From vrc.vlm at gmail.com Tue Jan 21 09:12:59 2014 From: vrc.vlm at gmail.com (=?ISO-8859-1?Q?Victor_Rafael_Rodriguez_Cort=E9s?=) Date: Tue, 21 Jan 2014 09:12:59 +0100 Subject: [smokeping-users] Permanently store/archive historical data In-Reply-To: <981231810.20140120153923@sloop.net> References: <981231810.20140120153923@sloop.net> Message-ID: Changing the IP address is ok for some devices, but others will be simply removed (I will have less devices monitored). One option might be to replace the old IP with i.e. 127.0.0.1: testing would be fast and produce minimum resource utilization and the very low ping times would mark the date of replacement. Should I take any special any special care to avoid Smokeping to delete rrd data with more than 400 days? Thank you! 2014/1/21 Gregory Sloop > I don't know of a way to solve your problem the way you want, but what > about simply pointing the same RRD/Target at the new IP. > > You'll be able to look at historical data, as well as not having no > superfluous data/bandwidth. You'll have to keep track of the "change" date, > but that's pretty trivial - you could even simply edit the descriptive name > to put in that info... > > But I don't believe there's a way to do exactly what you want. > > -Greg > > > > Hello, > > I have a set of routers monitored with smokeping for a couple of years. > Now, I'm going to replace them with new equipment with new IP addresses. > > I've searched unsuccessfully to find a way to make Smokeping stop testing > the old IPs but still allow access to the data and graphs it has collected > until now from the web interface. I would like to be able to view those > graphs but not waste resources checking IP's that will no longer exists in > my network. > > Is there a way to accomplish that? > > Thanks! > Victor. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20140121/2f26c163/attachment.htm From paul.mansfield+smokeping at grapeshot.co.uk Tue Jan 21 12:16:08 2014 From: paul.mansfield+smokeping at grapeshot.co.uk (Paul Mansfield) Date: Tue, 21 Jan 2014 11:16:08 +0000 Subject: [smokeping-users] Permanently store/archive historical data In-Reply-To: References: <981231810.20140120153923@sloop.net> Message-ID: On 21 January 2014 08:12, Victor Rafael Rodriguez Cort?s wrote: > Changing the IP address is ok for some devices, but others will be simply removed (I will have less devices monitored). One option might be to replace the old IP with i.e. 127.0.0.1: testing would be fast and produce minimum resource utilization and the very low ping times would mark the date of replacement. > > Should I take any special any special care to avoid Smokeping to delete rrd data with more than 400 days? you could amend the RRD file to change the way old data is combined/smoothed. it's probably also worth doing an rrd dump archive so that you can recover the historic data if you need to create a new .RRD file from it with different settings. From ok.aless at gmail.com Thu Jan 23 17:30:53 2014 From: ok.aless at gmail.com (Alessandro Palermo) Date: Thu, 23 Jan 2014 14:30:53 -0200 Subject: [smokeping-users] Trying to modify the smokeping web interface Message-ID: Hi list. I was working on a bash script to save the change of routes on smokeping Target devices. The script is quite simple, It's read the Target file and get the IP address and the check if the device is reachable, if so, then it's make and mtr and store the route in a database (mysql) This script runs on cron each 5 minutes. Also I wrote a php web that recives an IP address as a parameter and show the changes of routes for these IP. I want to add this php web as a link in the title of the detailed graphs. So I edited the Target file and add in the title variable something like this: menu = Some place title= Some place 192.168.2.234 host= 192.168.2.234 <#> This works so so, because the links appear ok in the detailed graphs as a title (html title) but in the main view of the smokeping the graphs generated by rrdtool show as a title this: Some place 192.168.2.234 And so the graph It's look no good. Then I edit the Smokeping.pm and this block of code ------------------------------------------------ my ($graphret,$xs,$ys) = RRDs::graph ($cfg->{General}{imgcache}.$dir."/${prop}_mini.png", # '--lazy', '--start','-'.exp2seconds($cfg->{Presentation}{overview}{range}), '--title',$phys_tree->{title}, '--height',$cfg->{Presentation}{overview}{height}, '--width',$cfg->{Presentation}{overview}{width}, '--vertical-label', $ProbeUnit, '--imgformat','PNG', '--alt-autoscale-max', '--alt-y-grid', '--rigid', '--lower-limit','0', @G, "COMMENT:$date\\r"); my $ERROR = RRDs::error(); $page .= "
"; ------------------------------------------------ I've changed the line '--title',$phys_tree->{title}, for this line '--title',$phys_tree->{mytitle}, With this change It's work so so, because in the rrdtool main graph It's appear no title. Trying to solve this, in the file Targets I've add a new variable defined on this way menu = Some place title= Some place 192.168.2.234 mytitle= Some place 192.168.2.234 host= 192.168.2.234 But with this change when I restart smokeping I've an error. Unknown variable mytitle. Any ideas? Thanks in advance and sorry for my english :( -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20140123/a74e4bde/attachment.html From rjd at merit.edu Thu Jan 23 18:35:33 2014 From: rjd at merit.edu (Russell Dwarshuis) Date: Thu, 23 Jan 2014 12:35:33 -0500 (EST) Subject: [smokeping-users] Trying to modify the smokeping web interface In-Reply-To: References: Message-ID: <131053981.985531.1390498533253.JavaMail.zimbra@merit.edu> It looks like mytitle in the configuration file is not being put into $phys_tree->{mytitle} I have not checked the code, but this is probably because mytitle is not considered a valid variable name in the configuration file. I recall that the author is using a perl module to read the configuration file, that module probably has a constructor that states what the valid variable names are so you would need to track that down and add mytitle there, too. Alternatively, you could further modify Smokeping.pm to create mytitle there by parsing title with a regular expression (and forget about adding mytitle to the configuration file): ########## my $mytitle = $phys_tree->{title}; if ($phys_tree->{title} =~ /(.*)<.*ip=(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})//) { $mytitle = "$1 $2"; } my ($graphret,$xs,$ys) = RRDs::graph( $cfg->{General}{imgcache}.$dir."/${prop}_mini.png", # '--lazy', '--start','-'.exp2seconds($cfg->{Presentation}{overview}{range}), '--title',$mytitle, '--height',$cfg->{Presentation}{overview}{height}, '--width',$cfg->{Presentation}{overview}{width}, '--vertical-label', $ProbeUnit, '--imgformat','PNG', '--alt-autoscale-max', '--alt-y-grid', '--rigid', '--lower-limit','0', @G, "COMMENT:$date\\r"); ########## This would require your title to have a certain format to detect the IPv4 (IPv6 would fail) in the URL so it could create problems later, though. -Russell Dwarshuis ----- Original Message ----- From: "Alessandro Palermo" To: "smokeping-users" Sent: Thursday, January 23, 2014 11:30:53 AM Subject: [smokeping-users] Trying to modify the smokeping web interface Hi list. I was working on a bash script to save the change of routes on smokeping Target devices. The script is quite simple, It's read the Target file and get the IP address and the check if the device is reachable, if so, then it's make and mtr and store the route in a database (mysql) This script runs on cron each 5 minutes. Also I wrote a php web that recives an IP address as a parameter and show the changes of routes for these IP. I want to add this php web as a link in the title of the detailed graphs. So I edited the Target file and add in the title variable something like this: menu = Some place title= Some place 192.168.2.234 host= 192.168.2.234 This works so so, because the links appear ok in the detailed graphs as a title (html title) but in the main view of the smokeping the graphs generated by rrdtool show as a title this: Some place 192.168.2.234 And so the graph It's look no good. Then I edit the Smokeping.pm and this block of code ------------------------------------------------ my ($graphret,$xs,$ys) = RRDs::graph ($cfg->{General}{imgcache}.$dir."/${prop}_mini.png", # '--lazy', '--start','-'.exp2seconds($cfg->{Presentation}{overview}{range}), '--title',$phys_tree->{title}, '--height',$cfg->{Presentation}{overview}{height}, '--width',$cfg->{Presentation}{overview}{width}, '--vertical-label', $ProbeUnit, '--imgformat','PNG', '--alt-autoscale-max', '--alt-y-grid', '--rigid', '--lower-limit','0', @G, "COMMENT:$date\\r"); my $ERROR = RRDs::error(); $page .= "
"; ------------------------------------------------ I've changed the line '--title',$phys_tree->{title}, for this line '--title',$phys_tree->{mytitle}, With this change It's work so so, because in the rrdtool main graph It's appear no title. Trying to solve this, in the file Targets I've add a new variable defined on this way menu = Some place title= Some place 192.168.2.234 mytitle= Some place 192.168.2.234 host= 192.168.2.234 But with this change when I restart smokeping I've an error. Unknown variable mytitle. Any ideas? Thanks in advance and sorry for my english :( _______________________________________________ smokeping-users mailing list smokeping-users at lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users From ok.aless at gmail.com Fri Jan 24 09:55:16 2014 From: ok.aless at gmail.com (Alessandro Palermo) Date: Fri, 24 Jan 2014 06:55:16 -0200 Subject: [smokeping-users] Trying to modify the smokeping web interface In-Reply-To: <131053981.985531.1390498533253.JavaMail.zimbra@merit.edu> References: <131053981.985531.1390498533253.JavaMail.zimbra@merit.edu> Message-ID: Thanks Russell I will try on this way. Regards. El ene 23, 2014 3:35 PM, "Russell Dwarshuis" escribi?: > It looks like mytitle in the configuration file is not being put into > $phys_tree->{mytitle} > I have not checked the code, but this is probably because mytitle is not > considered a valid variable name in the configuration file. I recall that > the author is using a perl module to read the configuration file, that > module probably has a constructor that states what the valid variable names > are so you would need to track that down and add mytitle there, too. > > Alternatively, you could further modify Smokeping.pm to create mytitle > there by parsing title with a regular expression (and forget about adding > mytitle to the configuration file): > > ########## > my $mytitle = $phys_tree->{title}; > if ($phys_tree->{title} =~ > /(.*)<.*ip=(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})//) { > $mytitle = "$1 $2"; > } > my ($graphret,$xs,$ys) = RRDs::graph( > $cfg->{General}{imgcache}.$dir."/${prop}_mini.png", > # '--lazy', > '--start','-'.exp2seconds($cfg->{Presentation}{overview}{range}), > '--title',$mytitle, > '--height',$cfg->{Presentation}{overview}{height}, > '--width',$cfg->{Presentation}{overview}{width}, > '--vertical-label', $ProbeUnit, > '--imgformat','PNG', > '--alt-autoscale-max', > '--alt-y-grid', > '--rigid', > '--lower-limit','0', > @G, > "COMMENT:$date\\r"); > ########## > > This would require your title to have a certain format to detect the IPv4 > (IPv6 would fail) in the URL so it could create problems later, though. > > > -Russell Dwarshuis > > ----- Original Message ----- > From: "Alessandro Palermo" > To: "smokeping-users" > Sent: Thursday, January 23, 2014 11:30:53 AM > Subject: [smokeping-users] Trying to modify the smokeping web interface > > Hi list. > > I was working on a bash script to save the change of routes on smokeping > Target devices. > The script is quite simple, It's read the Target file and get the IP > address and the check if the device is reachable, if so, then it's make and > mtr and store the route in a database (mysql) > This script runs on cron each 5 minutes. > Also I wrote a php web that recives an IP address as a parameter and show > the changes of routes for these IP. > I want to add this php web as a link in the title of the detailed graphs. > So I edited the Target file and add in the title variable something like > this: > > menu = Some place > title= Some place href=/ruteo/search.php?ip=192.168.2.234>192.168.2.234 > host= 192.168.2.234 > > This works so so, because the links appear ok in the detailed graphs as a > title (html title) but in the main view of the smokeping the graphs > generated by rrdtool show as a title this: > > Some place 192.168.2.234 > > And so the graph It's look no good. > > Then I edit the Smokeping.pm and this block of code > ------------------------------------------------ > my ($graphret,$xs,$ys) = RRDs::graph > ($cfg->{General}{imgcache}.$dir."/${prop}_mini.png", > # '--lazy', > '--start','-'.exp2seconds($cfg->{Presentation}{overview}{range}), > '--title',$phys_tree->{title}, > '--height',$cfg->{Presentation}{overview}{height}, > '--width',$cfg->{Presentation}{overview}{width}, > '--vertical-label', $ProbeUnit, > '--imgformat','PNG', > '--alt-autoscale-max', > '--alt-y-grid', > '--rigid', > '--lower-limit','0', > @G, > "COMMENT:$date\\r"); > my $ERROR = RRDs::error(); > $page .= "
"; > > ------------------------------------------------ > > I've changed the line '--title',$phys_tree->{title}, > for this line '--title',$phys_tree->{mytitle}, > > With this change It's work so so, because in the rrdtool main graph It's > appear no title. > Trying to solve this, in the file Targets I've add a new variable defined > on this way > > menu = Some place > title= Some place href=/ruteo/search.php?ip=192.168.2.234>192.168.2.234 > mytitle= Some place 192.168.2.234 > host= 192.168.2.234 > > But with this change when I restart smokeping I've an error. Unknown > variable mytitle. > > Any ideas? > > Thanks in advance and sorry for my english :( > > > > > > > > > > > > > > _______________________________________________ > 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/20140124/c3bbbcd2/attachment.htm From ok.aless at gmail.com Fri Jan 24 13:26:37 2014 From: ok.aless at gmail.com (Alessandro Palermo) Date: Fri, 24 Jan 2014 10:26:37 -0200 Subject: [smokeping-users] Trying to modify the smokeping web interface In-Reply-To: References: <131053981.985531.1390498533253.JavaMail.zimbra@merit.edu> Message-ID: Russell, thank you very much. It's work perfect! Regards 2014/1/24 Alessandro Palermo > Thanks Russell I will try on this way. > > Regards. > El ene 23, 2014 3:35 PM, "Russell Dwarshuis" escribi?: > > It looks like mytitle in the configuration file is not being put into >> $phys_tree->{mytitle} >> I have not checked the code, but this is probably because mytitle is not >> considered a valid variable name in the configuration file. I recall that >> the author is using a perl module to read the configuration file, that >> module probably has a constructor that states what the valid variable names >> are so you would need to track that down and add mytitle there, too. >> >> Alternatively, you could further modify Smokeping.pm to create mytitle >> there by parsing title with a regular expression (and forget about adding >> mytitle to the configuration file): >> >> ########## >> my $mytitle = $phys_tree->{title}; >> if ($phys_tree->{title} =~ >> /(.*)<.*ip=(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})//) { >> $mytitle = "$1 $2"; >> } >> my ($graphret,$xs,$ys) = RRDs::graph( >> $cfg->{General}{imgcache}.$dir."/${prop}_mini.png", >> # '--lazy', >> '--start','-'.exp2seconds($cfg->{Presentation}{overview}{range}), >> '--title',$mytitle, >> '--height',$cfg->{Presentation}{overview}{height}, >> '--width',$cfg->{Presentation}{overview}{width}, >> '--vertical-label', $ProbeUnit, >> '--imgformat','PNG', >> '--alt-autoscale-max', >> '--alt-y-grid', >> '--rigid', >> '--lower-limit','0', >> @G, >> "COMMENT:$date\\r"); >> ########## >> >> This would require your title to have a certain format to detect the IPv4 >> (IPv6 would fail) in the URL so it could create problems later, though. >> >> >> -Russell Dwarshuis >> >> ----- Original Message ----- >> From: "Alessandro Palermo" >> To: "smokeping-users" >> Sent: Thursday, January 23, 2014 11:30:53 AM >> Subject: [smokeping-users] Trying to modify the smokeping web interface >> >> Hi list. >> >> I was working on a bash script to save the change of routes on smokeping >> Target devices. >> The script is quite simple, It's read the Target file and get the IP >> address and the check if the device is reachable, if so, then it's make and >> mtr and store the route in a database (mysql) >> This script runs on cron each 5 minutes. >> Also I wrote a php web that recives an IP address as a parameter and show >> the changes of routes for these IP. >> I want to add this php web as a link in the title of the detailed graphs. >> So I edited the Target file and add in the title variable something like >> this: >> >> menu = Some place >> title= Some place > href=/ruteo/search.php?ip=192.168.2.234>192.168.2.234 >> host= 192.168.2.234 >> >> This works so so, because the links appear ok in the detailed graphs as a >> title (html title) but in the main view of the smokeping the graphs >> generated by rrdtool show as a title this: >> >> Some place 192.168.2.234 >> >> And so the graph It's look no good. >> >> Then I edit the Smokeping.pm and this block of code >> ------------------------------------------------ >> my ($graphret,$xs,$ys) = RRDs::graph >> ($cfg->{General}{imgcache}.$dir."/${prop}_mini.png", >> # '--lazy', >> '--start','-'.exp2seconds($cfg->{Presentation}{overview}{range}), >> '--title',$phys_tree->{title}, >> '--height',$cfg->{Presentation}{overview}{height}, >> '--width',$cfg->{Presentation}{overview}{width}, >> '--vertical-label', $ProbeUnit, >> '--imgformat','PNG', >> '--alt-autoscale-max', >> '--alt-y-grid', >> '--rigid', >> '--lower-limit','0', >> @G, >> "COMMENT:$date\\r"); >> my $ERROR = RRDs::error(); >> $page .= "
"; >> >> ------------------------------------------------ >> >> I've changed the line '--title',$phys_tree->{title}, >> for this line '--title',$phys_tree->{mytitle}, >> >> With this change It's work so so, because in the rrdtool main graph It's >> appear no title. >> Trying to solve this, in the file Targets I've add a new variable defined >> on this way >> >> menu = Some place >> title= Some place > href=/ruteo/search.php?ip=192.168.2.234>192.168.2.234 >> mytitle= Some place 192.168.2.234 >> host= 192.168.2.234 >> >> But with this change when I restart smokeping I've an error. Unknown >> variable mytitle. >> >> Any ideas? >> >> Thanks in advance and sorry for my english :( >> >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> 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/20140124/41237955/attachment.htm From paul.mansfield+smokeping at grapeshot.co.uk Mon Jan 27 14:42:10 2014 From: paul.mansfield+smokeping at grapeshot.co.uk (Paul Mansfield) Date: Mon, 27 Jan 2014 13:42:10 +0000 Subject: [smokeping-users] mod_fcgid: HTTP request length xxx (so far) exceeds MaxRequestLen (yyyy) Message-ID: We have had a significant number of problems with smokeping client consuming all the memory on a server, we've had these grow to 12GB in the worst case! There appear to be two problems, probably related. * One is that the slave can't communicate with the master for a while and the smokeping slave cache builds up a backlog of work, and then it is unable to send the data. * The other problem is that the slave process, e.g. usually FPing, gets wedged and becomes larger and larger. the clue to the first problem are lines like this in the Apache error log: [Mon Jan 27 12:12:42 2014] [warn] [client w.x.y.z] mod_fcgid: HTTP request length 394304 (so far) exceeds MaxRequestLen (393216) To resolve this, you have to kill-9 the smokeping slave, and any child processes like FPing, then remove everything in the ~smokeping/cache directory. Then it's safe to restart. It's probably worth setting a larger number than the default in apache config anyway to allow slaves to catch up... e.g. FcgidMaxRequestLen 131072 but if you find anything larger than that it probably means something else has gone wrong.