[smokeping-users] [Ticket #17] smokeping-users Digest, Vol 76, Issue 1

IT Department anghelflorin at globtel.ro
Tue Nov 12 18:31:58 CET 2013


This is a notification from the Help Desk.




On Nov 12, 2013 @ 05:31 pm, smokeping-users-request at lists.oetiker.ch wrote:
Send smokeping-users mailing list submissions to
	smokeping-users at lists.oetiker.ch

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
or, via email, send a message with subject or body 'help' to
	smokeping-users-request at lists.oetiker.ch

You can reach the person managing the list at
	smokeping-users-owner at lists.oetiker.ch

When replying, please edit your Subject line so it is more specific
than "Re: Contents of smokeping-users digest..."


Today's Topics:

   1. partially solved problem with tcpping probe on	centos6
      (Paul Mansfield)
   2. Re: error when slave connects to the master (Fligor, Debbie)
   3. units for rtt_max (Paul Mansfield)
   4. Sporadic crashes on reload in Smokeping.pm (Vinny_Abello at Dell.com)
   5. Re: Sporadic crashes on reload in Smokeping.pm (Paul Mansfield)
   6. Re: Sporadic crashes on reload in Smokeping.pm
      (Vinny_Abello at Dell.com)


----------------------------------------------------------------------

Message: 1
Date: Mon, 3 Jun 2013 12:59:55 +0100
From: Paul Mansfield <paul.mansfield+smokeping at grapeshot.co.uk>
Subject: [smokeping-users] partially solved problem with tcpping probe
	on	centos6
To: smokeping-users at lists.oetiker.ch
Message-ID:
	<CAHYeK0eBOy6EBeGFm4e+F0eXWewN=FBRvUMjh7AB2+-UFvvEuQ at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hello,
I am trying to use the tcpping probe with smokeping installed on centos6.

The first thing I had to fix was to put an explicit path in the
tcpping script to use /usr/bin/tcptraceroute, because centos stupidly
has a softlink at /bin/tcptraceroute to the standard system traceroute
binary!

I install smokeping into /usr/local/smokeping; the tcpping script is
in the bin directory.

If I run the master in debug mode, I see it is calling the plugin like this:

TCPPing: forks 5, timeout for each target 26
TCPPing: Executing /usr/local/smokeping/bin/tcpping -C -x 5 somehost 4949
TCPPing: Received: GLOB(0x24d0850)
TCPPing: somehost: got
Calling RRDs::update(/usr/local/smokeping/data/TCPPing/somehost.rrd
--template uptime:loss:median:ping1:ping2:ping3:ping4:ping5
1370260050:U:5:U:U:U:U:U:U)


However, if I execute the plugin at the command line, it works happily

# /usr/local/smokeping/bin/tcpping -C -x 5 somehost 4949
somehost : 0.391 0.269 0.301 0.281 0.315

I am running smokeping as the user/group smokeping; if I "su -
smokeping -s /bin/bash" and then try, tcptraceroute would complain
"Got root?"

The solution is to "chmod u+s /usr/bin/tcptraceroute".


I still see "TCPPing: Received: GLOB(0x24f12f8)", so I was wondering
if someone can suggest a way of fixing that?


I hope this helps someone as I spent quite a time tracking these two
problems down.

Paul



------------------------------

Message: 2
Date: Mon, 3 Jun 2013 13:00:24 -0500
From: "Fligor, Debbie" <fligor at illinois.edu>
Subject: Re: [smokeping-users] error when slave connects to the master
To: "smokeping-users at lists.oetiker.ch"
	<smokeping-users at lists.oetiker.ch>
Cc: Debbie Fligor <fligor at illinois.edu>
Message-ID: <505684DF-F117-42E5-92AF-8B541410F513 at illinois.edu>
Content-Type: text/plain; charset="us-ascii"



We finally solved this problem, it was all in fast cgi.  Either a default value changed, or we had just been lucky. Here are the details in case anyone else happens to hit this problem.

This site: http://foaa.de/old-blog/2010/11/php-apache-and-fastcgi-a-comprehensive-overview/trackback/index.html  was a big help

we needed to use -idle-timeout parameter on "FastCgiExternalServer"   ours is now set to 300, and it seems to be working.

if the idle timeout is too short, it cuts out the end of the headers, and you hit this from the FastCGI FAQ ( http://www.fastcgi.com/docs/faq.html#incomplete_headers ):

FastCGI: incomplete headers (d bytes) received from server "s"

The FastCGI application, s, didn't terminate the headers properly. A total of d bytes were recieved.

Headers are terminated by an empty line, e.g.

    printf("Content-type: text/html\r\nStatus: 200 OK\r\n\r\n");

See the CGI specification for more information.


-debbie


On Sep 17, 2012, at 17:01, G.W. Haywood <ged at jubileegroup.co.uk> wrote:

> Hi there,
> 
> On Mon, 17 Sep 2012, Debbie Fligor wrote:
> 
>> A few weeks ago our sysadmins patched our RHEL6 box that our
>> smokeping master runs on.. Since then none of the slaves have been
>> able to report.
> 
> I hate it when that happens. :(
> 
>> I get this error in our logs:
>> [Mon Sep 17 12:54:31 2012] [error] [client xxx.xxx.xxx.xxx] FastCGI: comm with (dynamic) server "/services/netmetrics/public_html/http/smokeping/smokeping.cgi" aborted: (first read) idle timeout (30 sec)
>> [Mon Sep 17 12:54:31 2012] [error] [client xxx.xxx.xxx.xxx] FastCGI: incomplete headers (0 bytes) received from server "/services/netmetrics/public_html/http/smokeping/smokeping.cgi"
>> 
>> but when I run this on the command line, or web to it with a browser, it works fine with no errors:
>> 
>> /services/netmetrics/public_html/http/smokeping/smokeping.cgi
> 
> Sounds like the master can connect to itself but the slaves are having
> problems.  I'd sniff the network traffic with tcpdump to a file for a
> while, and then run Wireshark on the file.  Something like
> 
> tcpdump -i eth0 -s 0 -Uw - 'tcp port 80' > /home/debbie/tcpdump.out.`date +"%Y%m%d%H%M%S"` &
> 
> I'd run tcpdump on both the master and a slave.  I'd hope that you
> have your system clocks all in sync to within a fraction of a second
> using ntpd so that you can compare the logs. :)
> 
>> ... here's the packages that they upgraded in case anyone knows of
>> anything in one of those: ...
> 
> My guess is that something else has been changed too.
> 
> --
> 
> 73,
> Ged.

-- 
-debbie
Debbie Fligor, n9dn       Lead Network Engineer, CITES, Univ. of Il
email: fligor at illinois.edu          
"Every keystroke can be monitored. And the computers never forget."



------------------------------

Message: 3
Date: Tue, 4 Jun 2013 10:47:10 +0100
From: Paul Mansfield <paul.mansfield+smokeping at grapeshot.co.uk>
Subject: [smokeping-users] units for rtt_max
To: smokeping-users at lists.oetiker.ch
Message-ID:
	<CAHYeK0eDOs8Cm=x1B0Q=dusxrxWx86o7YxTPQji=vzpwGdZv-w at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

please can someone update the page
http://oss.oetiker.ch/smokeping/doc/smokeping_config.en.html

and specify what the units are for rtt_max, and whether it needs to be
an integer or fixed value?

it's possible to work it out through trial and error, but having it
stated specifically would be more useful.

thanks
-- 
Paul Mansfield



------------------------------

Message: 4
Date: Tue, 4 Jun 2013 19:28:02 +0000
From: <Vinny_Abello at Dell.com>
Subject: [smokeping-users] Sporadic crashes on reload in Smokeping.pm
To: <smokeping-users at lists.oetiker.ch>
Message-ID:
	<FD9B2CB2B33E394FAE3B7466954760571D55F4EF at DFWX10HMPTC05.AMER.DELL.COM>
Content-Type: text/plain; charset="us-ascii"

Hello,

I've been noticing on one of our smokeping installations running smokeping 2.6.8 on FreeBSD 8.3 (from ports), that occasionally after a reload of smokeping, it will crash in the following manner according to the log:

Tue Jun  4 11:55:34 2013 - Reloading configuration.
Tue Jun  4 11:56:00 2013 - Got HUP signal, exiting gracefully.
Tue Jun  4 11:56:00 2013 - Got HUP signal, exiting gracefully.
Tue Jun  4 11:56:00 2013 - Exiting due to HUP signal.
Tue Jun  4 11:56:00 2013 - Exiting due to HUP signal.
Tue Jun  4 11:56:00 2013 - Got HUP signal, exiting gracefully.
Tue Jun  4 11:56:00 2013 - Exiting due to HUP signal.
Tue Jun  4 11:56:00 2013 - Got HUP signal, exiting gracefully.
Tue Jun  4 11:56:00 2013 - Exiting due to HUP signal.
Tue Jun  4 11:56:00 2013 - Got HUP signal, exiting gracefully.
Tue Jun  4 11:56:00 2013 - Exiting due to HUP signal.
Tue Jun  4 11:56:00 2013 - Waiting for child processes to terminate.
Tue Jun  4 11:56:00 2013 - Can't call method "step" on an undefined value at /usr/local/smokeping/lib/Smokeping.pm line 4284.

This definitely does not happen every time we reload it and we don't do anything to correct it other than start it back up again using the rc script and it runs fine. Any clues as to what might be causing this to happen on occasion and how to fix it? We currently have about 1067 targets defined and it normally finishes probing them all without issue every 300 seconds.

Thanks!

-Vinny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20130604/56c97770/attachment-0001.htm 

------------------------------

Message: 5
Date: Wed, 5 Jun 2013 10:10:09 +0100
From: Paul Mansfield <paul.mansfield+smokeping at grapeshot.co.uk>
Subject: Re: [smokeping-users] Sporadic crashes on reload in
	Smokeping.pm
To: smokeping-users at lists.oetiker.ch
Message-ID:
	<CAHYeK0ctZcFSZWefmYmYDEHbrJufSU85ikTmHQV9CetYHH5Sgw at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On 4 June 2013 20:28,  <Vinny_Abello at dell.com> wrote:
> 2.6.8 on FreeBSD 8.3 (from ports), that occasionally after a reload of
> smokeping, it will crash in the following manner according to the log:
>
I don't know if it's related but if the slave is running in debug
mode, it stops working when the master is restarted; this on centos6.4
x64.



------------------------------

Message: 6
Date: Thu, 6 Jun 2013 15:17:36 +0000
From: <Vinny_Abello at Dell.com>
Subject: Re: [smokeping-users] Sporadic crashes on reload in
	Smokeping.pm
To: <paul.mansfield+smokeping at grapeshot.co.uk>,
	<smokeping-users at lists.oetiker.ch>
Message-ID:
	<FD9B2CB2B33E394FAE3B7466954760571D561C35 at DFWX10HMPTC05.AMER.DELL.COM>
Content-Type: text/plain; charset="us-ascii"

No slave servers currently... I'm wondering if it's some sort of timing issue with when the reload done. I saw code that looks like it handles it when a probe dies on its own, but that was my other thought... I'm not sure. I'm just taking guesses.

-Vinny

-----Original Message-----
From: smokeping-users-bounces+vinny_abello=dell.com at lists.oetiker.ch [mailto:smokeping-users-bounces+vinny_abello=dell.com at lists.oetiker.ch] On Behalf Of Paul Mansfield
Sent: Wednesday, June 05, 2013 5:10 AM
To: smokeping-users at lists.oetiker.ch
Subject: Re: [smokeping-users] Sporadic crashes on reload in Smokeping.pm

On 4 June 2013 20:28,  <Vinny_Abello at dell.com> wrote:
> 2.6.8 on FreeBSD 8.3 (from ports), that occasionally after a reload of
> smokeping, it will crash in the following manner according to the log:
>
I don't know if it's related but if the slave is running in debug
mode, it stops working when the master is restarted; this on centos6.4
x64.

_______________________________________________
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


End of smokeping-users Digest, Vol 76, Issue 1
**********************************************

------
This is an automated response.  Your issue has been noted.  We'll be in touch soon.



Please reply to this email or visit the URL below with any additional details.

http://florin-pc/portal/view-help-request/17


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


More information about the smokeping-users mailing list