From cholam20 at yahoo.co.in  Thu Dec  1 01:33:50 2011
From: cholam20 at yahoo.co.in (revathi ganesh)
Date: Thu, 1 Dec 2011 06:03:50 +0530 (IST)
Subject: [smokeping-users] Hey there How are you!!
Message-ID: <1322699630.51396.androidMobile@web137306.mail.in.yahoo.com>

<p>Hola<br>I wanted to prove I could amount to something there is  nothing else like this out here this was more than effective just imagine what it could do for you <br><a href="http://bluecat.x.fc2.com/profile/92MartinJames/">http://bluecat.x.fc2.com/profile/92MartinJames/</a><br>ttyl.</p>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20111201/55e8b371/attachment.htm 

From newsboonie at gmail.com  Thu Dec  1 18:22:18 2011
From: newsboonie at gmail.com (Boonie)
Date: Thu, 1 Dec 2011 18:22:18 +0100
Subject: [smokeping-users] centos 6 instruction
Message-ID: <CAJ9oaKtsVJ-muGqX19_mgRixFm5p653qxf=2t3MLUNsEm9J-mQ@mail.gmail.com>

Hi,

Can anyone point me to a step by step instruction on how to install
smokeping on centos 6?

I tried and got stuck while it is a rather simple thing to do on
Ubuntu. But I have a centos 6 VPS on which I'd like to have it run.

Thanks,

Dave


From mgd at interbaun.com  Thu Dec  1 20:37:02 2011
From: mgd at interbaun.com (mgd at interbaun.com)
Date: Thu, 01 Dec 2011 11:37:02 -0800
Subject: [smokeping-users] inconsistencies in smokeping_config documentation
 ***Targets*** section
Message-ID: <20111201113702.21064ri103k1f80u@webmail.uniserve.com>

At the beginning of the ***Targets***, just after the statement  
beginning with "The following variables can be set in this section:",  
the "alerts" are described as:

A comma separated list of alerts to check for this target. The alerts  
have to be setup in the Alerts section. Alerts are inherited by child  
nodes. Use an empty alerts definition to remove inherited alerts from  
the current target and its children.

Then in the Level 1 section that follows a few sentences later, it is  
written for alerts that:

     Comma separated list of alert names

     This variable inherits its value from the parent section if  
nothing is specified here.

So, the first statement says that "use an empty alert definition to  
remove inherited alerts from the current target and its children".  
Then in the section for configured targets it says: "This variable  
inherits its value from the parent section if nothing is specified  
here". These two statements clash, only one can be true. So, what is  
the true statement?


From gregs at sloop.net  Thu Dec  1 21:39:39 2011
From: gregs at sloop.net (Gregory Sloop)
Date: Thu, 1 Dec 2011 12:39:39 -0800
Subject: [smokeping-users] inconsistencies in smokeping_config
	documentation ***Targets*** section
In-Reply-To: <20111201113702.21064ri103k1f80u@webmail.uniserve.com>
References: <20111201113702.21064ri103k1f80u@webmail.uniserve.com>
Message-ID: <78838250.20111201123939@sloop.net>

See comments following...

mic> At the beginning of the ***Targets***, just after the statement
mic> beginning with "The following variables can be set in this section:",
mic> the "alerts" are described as:

mic> A comma separated list of alerts to check for this target. The alerts
mic> have to be setup in the Alerts section. Alerts are inherited by child
mic> nodes. Use an empty alerts definition to remove inherited alerts from
mic> the current target and its children.

mic> Then in the Level 1 section that follows a few sentences later, it is
mic> written for alerts that:

mic>      Comma separated list of alert names

mic>      This variable inherits its value from the parent section if  
mic> nothing is specified here.

mic> So, the first statement says that "use an empty alert definition to  
mic> remove inherited alerts from the current target and its children".  
mic> Then in the section for configured targets it says: "This variable  
mic> inherits its value from the parent section if nothing is specified  
mic> here". These two statements clash, only one can be true. So, what is  
mic> the true statement?

[Provided I understand your question...]
I think what it's saying is:

If you leave a child section without any *explicitly* defined alerts, it
will get the alerts from its parent.

If you want to cancel/remove an alert for a child section, then define an
"empty" alert with the same name in the child and you don't get that
alert from the parent. If there are other alerts, you'll get those.

[And I'm pretty sure it works that way. I don't have any currently
configured child sections using this, but did one a while back and it
functioned as specified here - at least IIRC it did. I was using
2.4.something - but I haven't heard of any different behavior in
2.6.x]

-Greg


From mgd at interbaun.com  Fri Dec  2 00:29:30 2011
From: mgd at interbaun.com (mgd at interbaun.com)
Date: Thu, 01 Dec 2011 15:29:30 -0800
Subject: [smokeping-users] inconsistencies in smokeping_config
 documentation ***Targets*** section
In-Reply-To: <78838250.20111201123939@sloop.net>
References: <20111201113702.21064ri103k1f80u@webmail.uniserve.com>
	<78838250.20111201123939@sloop.net>
Message-ID: <20111201152930.21131b8pjqsi0xy2@webmail.uniserve.com>

Thank you, Greg

Yes, I ended up defining all my parent alerts in one line in the Targets file:

alerts =  
bigloss,someloss,startloss,rttdetect,anydelay,rttdetectbccable,rttdetectcube

Then, for each target, I defined alerts uniquely, such as:

++ SquarePE
menu = SquarePE
title = SquarePE
host = 1.2.3.4
alerts = bigloss

++ CubeCE
menu = CubeCE
title = CubeCE
host = 4.3.2.1
alerts = rttdetectcube

But, as you suggest, I could also have created a dummy or do nothing  
alert and assigned that to Targets for which I do not need email alerts.


Quoting Gregory Sloop <gregs at sloop.net>:

> See comments following...
>
> mic> At the beginning of the ***Targets***, just after the statement
> mic> beginning with "The following variables can be set in this section:",
> mic> the "alerts" are described as:
>
> mic> A comma separated list of alerts to check for this target. The alerts
> mic> have to be setup in the Alerts section. Alerts are inherited by child
> mic> nodes. Use an empty alerts definition to remove inherited alerts from
> mic> the current target and its children.
>
> mic> Then in the Level 1 section that follows a few sentences later, it is
> mic> written for alerts that:
>
> mic>      Comma separated list of alert names
>
> mic>      This variable inherits its value from the parent section if
> mic> nothing is specified here.
>
> mic> So, the first statement says that "use an empty alert definition to
> mic> remove inherited alerts from the current target and its children".
> mic> Then in the section for configured targets it says: "This variable
> mic> inherits its value from the parent section if nothing is specified
> mic> here". These two statements clash, only one can be true. So, what is
> mic> the true statement?
>
> [Provided I understand your question...]
> I think what it's saying is:
>
> If you leave a child section without any *explicitly* defined alerts, it
> will get the alerts from its parent.
>
> If you want to cancel/remove an alert for a child section, then define an
> "empty" alert with the same name in the child and you don't get that
> alert from the parent. If there are other alerts, you'll get those.
>
> [And I'm pretty sure it works that way. I don't have any currently
> configured child sections using this, but did one a while back and it
> functioned as specified here - at least IIRC it did. I was using
> 2.4.something - but I haven't heard of any different behavior in
> 2.6.x]
>
> -Greg
>
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>




From tobi at oetiker.ch  Fri Dec  2 07:07:44 2011
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Fri, 2 Dec 2011 07:07:44 +0100 (CET)
Subject: [smokeping-users] inconsistencies in smokeping_config
 documentation ***Targets*** section
In-Reply-To: <20111201152930.21131b8pjqsi0xy2@webmail.uniserve.com>
References: <20111201113702.21064ri103k1f80u@webmail.uniserve.com>
	<78838250.20111201123939@sloop.net>
	<20111201152930.21131b8pjqsi0xy2@webmail.uniserve.com>
Message-ID: <alpine.DEB.2.02.1112020704490.7523@engelberg.oetiker.ch>

> Quoting Gregory Sloop <gregs at sloop.net>:
>
> > See comments following...
> >
> > mic> At the beginning of the ***Targets***, just after the statement
> > mic> beginning with "The following variables can be set in this section:",
> > mic> the "alerts" are described as:
> >
> > mic> A comma separated list of alerts to check for this target. The alerts
> > mic> have to be setup in the Alerts section. Alerts are inherited by child
> > mic> nodes. Use an empty alerts definition to remove inherited alerts from
> > mic> the current target and its children.
> >
> > mic> Then in the Level 1 section that follows a few sentences later, it is
> > mic> written for alerts that:
> >
> > mic>      Comma separated list of alert names
> >
> > mic>      This variable inherits its value from the parent section if
> > mic> nothing is specified here.
> >
> > mic> So, the first statement says that "use an empty alert definition to
> > mic> remove inherited alerts from the current target and its children".
> > mic> Then in the section for configured targets it says: "This variable
> > mic> inherits its value from the parent section if nothing is specified
> > mic> here". These two statements clash, only one can be true. So, what is
> > mic> the true statement?
> >
> > [Provided I understand your question...]
> > I think what it's saying is:
> >
> > If you leave a child section without any *explicitly* defined alerts, it
> > will get the alerts from its parent.
> >
> > If you want to cancel/remove an alert for a child section, then define an
> > "empty" alert with the same name in the child and you don't get that
> > alert from the parent. If there are other alerts, you'll get those.
> >
> > [And I'm pretty sure it works that way. I don't have any currently
> > configured child sections using this, but did one a while back and it
> > functioned as specified here - at least IIRC it did. I was using
> > 2.4.something - but I haven't heard of any different behavior in
> > 2.6.x]
> >
Yesterday mgd at interbaun.com wrote:

> Thank you, Greg
>
> Yes, I ended up defining all my parent alerts in one line in the Targets file:
>
> [...]

Now that you understood. Do you want to suggest changes to
Smokeping.pm (the documentation is in there ... just search for the
strings ... ).


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 gregs at sloop.net  Fri Dec  2 18:27:28 2011
From: gregs at sloop.net (Gregory Sloop)
Date: Fri, 2 Dec 2011 09:27:28 -0800
Subject: [smokeping-users] Broken graphs
Message-ID: <1644333141.20111202092728@sloop.net>


Ok, here's what I've got:

Ubuntu 10.4 LTS

My targets are all setup, and "smokeping --debug" shows everything is running fine.
My RRD's are getting created and populated.
www-data has read access to the RRD's.
www-data has write access to "imgcache = /var/cache/smokeping/images"

I get the base page, but if I go into any of the graph pages, I get
"broken" graphs.

I don't get any errors though.

If I were betting I'd guess it's probably a permissions issue, but I
can't see what.

Any ideas? I'm stumped.

-Greg
-- 
Gregory Sloop, Principal: Sloop Network & Computer Consulting
503.251.0452 x82 Voice | 503.251.0452 Fax
www.sloop.net
mailto:gregs at sloop.net


From gregs at sloop.net  Fri Dec  2 18:30:51 2011
From: gregs at sloop.net (Gregory Sloop)
Date: Fri, 2 Dec 2011 09:30:51 -0800
Subject: [smokeping-users] Broken graphs
In-Reply-To: <1644333141.20111202092728@sloop.net>
References: <1644333141.20111202092728@sloop.net>
Message-ID: <524444256.20111202093051@sloop.net>

I probably should have said this, I assumed it was obvious...but this
is a new setup.

-Greg

GS> Ok, here's what I've got:

GS> Ubuntu 10.4 LTS

GS> My targets are all setup, and "smokeping --debug" shows everything is running fine.
GS> My RRD's are getting created and populated.
GS> www-data has read access to the RRD's.
GS> www-data has write access to "imgcache = /var/cache/smokeping/images"

GS> I get the base page, but if I go into any of the graph pages, I get
GS> "broken" graphs.

GS> I don't get any errors though.

GS> If I were betting I'd guess it's probably a permissions issue, but I
GS> can't see what.

GS> Any ideas? I'm stumped.

GS> -Greg

-- 
Gregory Sloop, Principal: Sloop Network & Computer Consulting
Voice: 503.251.0452 x82
EMail: gregs at sloop.net
http://www.sloop.net
---


From newsboonie at gmail.com  Fri Dec  2 20:50:54 2011
From: newsboonie at gmail.com (Boonie)
Date: Fri, 2 Dec 2011 20:50:54 +0100
Subject: [smokeping-users] Broken graphs
References: <1644333141.20111202092728@sloop.net>
	<524444256.20111202093051@sloop.net>
Message-ID: <EC16715D28814C95AFD9E16D51BB06F6@AMD>

Did you put dots in the name of the items or menus? I did that a few days 
ago and that had the same result.

Regards,

Dave



----- Original Message ----- 
From: "Gregory Sloop" <gregs at sloop.net>
To: "Greg Sloop" <gregs at sloop.net>
Cc: <smokeping-users at lists.oetiker.ch>
Sent: Friday, December 02, 2011 6:30 PM
Subject: Re: [smokeping-users] Broken graphs


>I probably should have said this, I assumed it was obvious...but this
> is a new setup.
>
> -Greg
>
> GS> Ok, here's what I've got:
>
> GS> Ubuntu 10.4 LTS
>
> GS> My targets are all setup, and "smokeping --debug" shows everything is 
> running fine.
> GS> My RRD's are getting created and populated.
> GS> www-data has read access to the RRD's.
> GS> www-data has write access to "imgcache = /var/cache/smokeping/images"
>
> GS> I get the base page, but if I go into any of the graph pages, I get
> GS> "broken" graphs.
>
> GS> I don't get any errors though.
>
> GS> If I were betting I'd guess it's probably a permissions issue, but I
> GS> can't see what.
>
> GS> Any ideas? I'm stumped.
>
> GS> -Greg
>
> -- 
> Gregory Sloop, Principal: Sloop Network & Computer Consulting
> Voice: 503.251.0452 x82
> EMail: gregs at sloop.net
> http://www.sloop.net
> ---
>
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
> 


From chris at aptivate.org  Fri Dec  2 21:38:26 2011
From: chris at aptivate.org (Chris Wilson)
Date: Fri, 2 Dec 2011 20:38:26 +0000 (GMT)
Subject: [smokeping-users] Updated tcpping probe and script
Message-ID: <alpine.DEB.2.02.1112022038060.19049@lap-x201>

Dear Richard, Tobi and smokeping users,

I tried to use the tcpping probe but it didn't work for me (centos 5). It seems 
that the tcptraceroute output format has changed or there is a problem with the 
script's ability to parse options. It also doesn't report tcptraceroute errors 
properly or have much in the way of debugging support. And it required 
smokeping to be run as root.

I think I have fixed these issues, and posted updated versions here:

https://github.com/aptivate/network-scripts/blob/master/TCPPing.pm
https://github.com/aptivate/network-scripts/blob/master/tcpping

I hope that you will consider these for inclusion in your projects. Richard, 
are you still maintaining tcpping? If not, is it worth merging this 
functionality into the TCPPing module?

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 chris+smokeping at aptivate.org  Fri Dec  2 21:56:47 2011
From: chris+smokeping at aptivate.org (Chris Wilson)
Date: Fri, 2 Dec 2011 20:56:47 +0000 (GMT)
Subject: [smokeping-users] Updated tcpping probe and script
Message-ID: <alpine.DEB.2.02.1112022038510.19049@lap-x201>

Dear Richard, Tobi and smokeping users,

I tried to use the tcpping probe but it didn't work for me (centos 5). It seems 
that the tcptraceroute output format has changed or there is a problem with the 
script's ability to parse options. It also doesn't report tcptraceroute errors 
properly or have much in the way of debugging support. And it required 
smokeping to be run as root.

I think I have fixed these issues, and posted updated versions here:

https://github.com/aptivate/network-scripts/blob/master/TCPPing.pm
https://github.com/aptivate/network-scripts/blob/master/tcpping

I hope that you will consider these for inclusion in your projects. Richard, 
are you still maintaining tcpping? If not, is it worth merging this 
functionality into the TCPPing module?

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 tobi at oetiker.ch  Sat Dec  3 13:01:09 2011
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Sat, 3 Dec 2011 13:01:09 +0100 (CET)
Subject: [smokeping-users] Updated tcpping probe and script
In-Reply-To: <alpine.DEB.2.02.1112022038060.19049@lap-x201>
References: <alpine.DEB.2.02.1112022038060.19049@lap-x201>
Message-ID: <alpine.DEB.2.00.1112031300030.2800@johan.oetiker.ch>

Hi Chris,

Yesterday Chris Wilson wrote:

> Dear Richard, Tobi and smokeping users,
>
> I tried to use the tcpping probe but it didn't work for me (centos 5). It seems
> that the tcptraceroute output format has changed or there is a problem with the
> script's ability to parse options. It also doesn't report tcptraceroute errors
> properly or have much in the way of debugging support. And it required
> smokeping to be run as root.
>
> I think I have fixed these issues, and posted updated versions here:
>
> https://github.com/aptivate/network-scripts/blob/master/TCPPing.pm
> https://github.com/aptivate/network-scripts/blob/master/tcpping
>
> I hope that you will consider these for inclusion in your projects. Richard,
> are you still maintaining tcpping? If not, is it worth merging this
> functionality into the TCPPing module?

I have added your update for TPCPing.pm ... but integrating the
tcpping script functionality would certainly make sense ...

how about creating a new probe for this ?

cheers
tobi


> Cheers, Chris.
>

-- 
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 chris+smokeping at aptivate.org  Sat Dec  3 16:18:26 2011
From: chris+smokeping at aptivate.org (Chris Wilson)
Date: Sat, 3 Dec 2011 15:18:26 +0000 (GMT)
Subject: [smokeping-users] Updated tcpping probe and script
In-Reply-To: <4ED95E38.5070507@vdberg.org>
References: <alpine.DEB.2.02.1112022014390.19049@lap-x201>
	<4ED95E38.5070507@vdberg.org>
Message-ID: <alpine.LRH.2.02.1112031508590.26023@mail.aptivate.org>

Hi Richard,

Thanks for your prompt reply :)

On Sat, 3 Dec 2011, Richard van den Berg wrote:

> What version of tcptraceroute is included with CentOS 5? Before I could 
> get your version 1.8 of tcpping to work on Debian using tcptraceroute 
> 1.5beta7+debian-4 I had to fix some bugs:
>
> 1) You introduced a dependency on bash using the $[${ttl}-1] syntax on
>    line 58. This is fine, but then the shebang needs to be changed to
>    #!/bin/bash since #!/bin/sh cannot be assumed to be bash on all
>    systems.

Thanks for spotting that. I agree, but I'm surprised it didn't work on 
Debian. Does sh point to dash on that system, and doesn't dash support 
arithmetic?

> 2) You cannot put the stderr redirection 2>&1 inside the $cmd variable on 
> line 58. This needs to be placed after $cmd when called on line 68 instead.

Yes, you're right, thanks.

> After this the output is:
>
> $ /tmp/tcpping.1.8 -D www.cisco.com
> debug: tcptraceroute -f 254 -m 255 -q 1 -w 3 www.cisco.com
> Unexpected output from tcptraceroute: Selected device eth0, address 
> 94.142.246.140, port 59896 for outgoing packets
> Unexpected output from tcptraceroute: Tracing the path to www.cisco.com 
> (88.221.32.170) on TCP port 80 (www), 255 hops max
> Unexpected output from tcptraceroute: 254 
> a88-221-32-170.deploy.akamaitechnologies.com (88.221.32.170) [open]  4.238 ms
>
> I am very interested to see what the output of "tcptraceroute -f 254 -m 255 
> -q 1 -w 3 www.cisco.com" looks like on your system.

Completely different to the above :(

[chris at central-server-1 ~]$ sudo tcptraceroute -f 254 -m 255 -q 1 -w 3 
www.cisco.com
traceroute to www.cisco.com (72.163.4.161), 255 hops max, 40 byte packets
255  www1.cisco.com (72.163.4.161)  316.157 ms

[chris at central-server-1 ~]$ tcptraceroute -V
Modern traceroute for Linux, version 2.0.1, Feb 26 2009
Copyright (c) 2006  Dmitry Butskoy,   License: GPL

> Writing a perl module that calls a shell script that uses the 
> tcptraceroute executable really does not sound like the best approach. 
> In fact, when I wrote tcpping I was not aware there are much better ways 
> to measure tcp round trip times. I can recommend hping2 or hping3 (see 
> www.hping.org) which gives output like this:

Yes, I have used hping, and if I'd known it would be so much work to fix 
TCPPing.pm and tcpping to work on my system, I probably would have 
adapted the module to use hping instead :)

I think that I will do that now.

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 kdr at kdr.ms  Mon Dec  5 02:02:12 2011
From: kdr at kdr.ms (Kris De Rocker)
Date: Mon, 05 Dec 2011 02:02:12 +0100
Subject: [smokeping-users] Wanted : fresh install of smokeping (centos 6)
Message-ID: <4EDC1814.20501@kdr.ms>

Dear,

I'm looking for someone who wants to set up a smokeping application on a 
system (running centos 6) and that could give me a little howto he've 
done it (so i can do it by myself on another system).  I've tried some 
how-to's on the internet, but none seems to work for centos 6.


Cheers,
Kris


From ged at jubileegroup.co.uk  Mon Dec  5 08:16:01 2011
From: ged at jubileegroup.co.uk (G.W. Haywood)
Date: Mon, 5 Dec 2011 07:16:01 +0000 (GMT)
Subject: [smokeping-users] Wanted : fresh install of smokeping (centos 6)
In-Reply-To: <4EDC1814.20501@kdr.ms>
References: <4EDC1814.20501@kdr.ms>
Message-ID: <Pine.LNX.4.58.1112050713530.25813@mail3.jubileegroup.co.uk>

Hi there,

On Mon, 5 Dec 2011, Kris De Rocker wrote:

> I'm looking for someone who wants to set up a smokeping application on a
> system (running centos 6) and that could give me a little howto he've
> done it (so i can do it by myself on another system).  I've tried some
> how-to's on the internet, but none seems to work for centos 6.

Forget how-tos, they suck.  Spend some quality time learning about
what's going on, then you'll be able to do it anytime on any system.

Hint:

Centos may be using SELinux, which can cause permissions problems.

--

73,
Ged.


From tony at ai.net.nz  Wed Dec  7 21:10:49 2011
From: tony at ai.net.nz (Tony Arcus)
Date: Thu, 08 Dec 2011 09:10:49 +1300
Subject: [smokeping-users] For Boonie and also Help
Message-ID: <20111208091049.17356broffujmzih@mail.ai.net.nz>

Hi Boonie
I am getting together a how to on Centos 6 and Smokeping.
I have hit a road block that I hope to fix.
See here
http://ai.net.nz/gettinghelp/how-do-i/centos-servers/67-5-packages-04-smokeping.html


My question to the group is:

Having done all this I get error messages in my /var/log/httpd/error_log file

      (13)Permission denied: exec of  
'/var/www/cgi-bin/cropper/smokeping-zoom.js'

This is due to having the cropper dir in the /var/www/cgi-bin directory.

    1. So here is where I am at.
    2. I have previously had older versions of smokeping going fine on  
my servers.
    3. This new version has got me a bit lost.
    4. The web pages are forming, but with out graphs.
    5. Where should things live?
    6. I put smokeping.fcgi in to /var/www/cgi-bin (as I have in older  
versions)
    7. I can url to this fine and things appear, bit no graphs
    8. I have errors in my log relating to cropper


SO
    9. Where should cropper be put?
   10. Where should smokeping.fcgi put?
   11. What should the referencing url be?  
http:://me.com/cgi-bin/smokeping.fcgi

Thanks
-- 
Tony Arcus
Systems and Network Engineer
Access Information Limited
PO Box 122
Carterton
Wairarapa

Phone : 06-379-6668
Phone : 04-831-1401
Email : tony at ai.net.nz
Cell  : 021-827-660

This email and any accompanying documentation may contain privileged and
confidential information.  If you are not the intended recipient, your use
of the information is strictly prohibited.





----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


From alex.colonna at bjtmail.com  Wed Dec  7 22:24:00 2011
From: alex.colonna at bjtmail.com (Alexandre COLONNA)
Date: Wed, 7 Dec 2011 22:24:00 +0100
Subject: [smokeping-users] For Boonie and also Help
In-Reply-To: <20111208091049.17356broffujmzih@mail.ai.net.nz>
References: <20111208091049.17356broffujmzih@mail.ai.net.nz>
Message-ID: <CACG8jGxTh070KqNVx9RbemZ6jr8VKFpWhG4rfvgJpAMBrsQMsA@mail.gmail.com>

Hi
it's quite simple to install smokeping on centos 6, which version did you
install ?

For the latest version, you must follow the "install" tutorial on
http://oss.oetiker.ch/smokeping/doc/smokeping_install.en.html

After that you must allow cgi execution in your httpd.conf for the
directory /var/www/html and if you have an .htaccess add those lines to
allow cgi execution:

AddHandler cgi-script .cgi
Options +ExecCGI

If you use "fcgi" you must enable EPEL depot : yum --enablerepo epel
then install fast-cgi and httpd-devel : yum install mod_fcgid httpd-devel

After that you must edit your config file in /opt/smokeping/etc/config to
put the good link:
imgcache = /opt/smokeping/img
imgurl   = ../smokeping/img
datadir  = /opt/smokeping/data
piddir  = /opt/smokeping/var
cgiurl   = http://www.exemple.com/smokeping/smokeping.fcgi
smokemail = /opt/smokeping/etc/smokemail
tmail = /opt/smokeping/etc/tmail

After that don't forget to create some directories like /opt/smokeping/img
/opt/smokeping/img/data and /opt/smokeping/img/var

Now you could make symbolics links in your /var/www/html,  e.g :
ln -s /opt/smokeping/htdocs /var/www/html/smokeping
ln -s /opt/smokeping/img /var/www/html/smokeping

And normally (maybe i'm going too fast) it's done !
maybe you will encountered some trouble about permissions.
In my case iput the file img in chmod 777 and the htdoc in 755

Good luck and tell me if it's ok

cheers

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

From alex.colonna at bjtmail.com  Wed Dec  7 22:32:41 2011
From: alex.colonna at bjtmail.com (Alexandre COLONNA)
Date: Wed, 7 Dec 2011 22:32:41 +0100
Subject: [smokeping-users] For Boonie and also Help
In-Reply-To: <CACG8jGxTh070KqNVx9RbemZ6jr8VKFpWhG4rfvgJpAMBrsQMsA@mail.gmail.com>
References: <20111208091049.17356broffujmzih@mail.ai.net.nz>
	<CACG8jGxTh070KqNVx9RbemZ6jr8VKFpWhG4rfvgJpAMBrsQMsA@mail.gmail.com>
Message-ID: <CACG8jGzFUeS+CA+FeOz2CDPo6kiP0WYmMs+5jE-AMLXdCS6wCA@mail.gmail.com>

Hi I forgot !

With centos you could encountered some trouble with selinux try make a
setenforce 0 or use semanage command
*
*
*Cheers*
*
*
*Alex*


2011/12/7 Alexandre COLONNA <alex.colonna at bjtmail.com>

> Hi
> it's quite simple to install smokeping on centos 6, which version did you
> install ?
>
> For the latest version, you must follow the "install" tutorial on
> http://oss.oetiker.ch/smokeping/doc/smokeping_install.en.html
>
> After that you must allow cgi execution in your httpd.conf for the
> directory /var/www/html and if you have an .htaccess add those lines to
> allow cgi execution:
>
> AddHandler cgi-script .cgi
> Options +ExecCGI
>
> If you use "fcgi" you must enable EPEL depot : yum --enablerepo epel
> then install fast-cgi and httpd-devel : yum install mod_fcgid httpd-devel
>
> After that you must edit your config file in /opt/smokeping/etc/config to
> put the good link:
> imgcache = /opt/smokeping/img
> imgurl   = ../smokeping/img
> datadir  = /opt/smokeping/data
> piddir  = /opt/smokeping/var
> cgiurl   = http://www.exemple.com/smokeping/smokeping.fcgi
> smokemail = /opt/smokeping/etc/smokemail
> tmail = /opt/smokeping/etc/tmail
>
> After that don't forget to create some directories like /opt/smokeping/img
> /opt/smokeping/img/data and /opt/smokeping/img/var
>
> Now you could make symbolics links in your /var/www/html,  e.g :
> ln -s /opt/smokeping/htdocs /var/www/html/smokeping
> ln -s /opt/smokeping/img /var/www/html/smokeping
>
> And normally (maybe i'm going too fast) it's done !
> maybe you will encountered some trouble about permissions.
> In my case iput the file img in chmod 777 and the htdoc in 755
>
> Good luck and tell me if it's ok
>
> cheers
>
> Alex
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20111207/96f70afc/attachment.htm 

From brian at iptelecom.ie  Thu Dec  8 01:02:18 2011
From: brian at iptelecom.ie (Brian Chamberlain)
Date: Thu, 8 Dec 2011 00:02:18 +0000
Subject: [smokeping-users] Question about Database Config.
Message-ID: <B5D71B17-CB3F-4A9E-85E1-ABD8856EEFA3@iptelecom.ie>

Hi All,

Thank you for amazing piece of software!

I had to very aggressively test packet loss to some servers so I made the following changes to the Database config.

*** Database ***

step     = 60
pings    = 20

# consfn mrhb steps total

AVERAGE  0.5   1  5040  #1008
AVERAGE  0.5  12  21600 #4320
    MIN  0.5  12  21600 #4320
    MAX  0.5  12  21600 #4320
AVERAGE  0.5 144   3600 #720
    MAX  0.5 144   3600 #720
    MIN  0.5 144   3600 #720


Basically I multiplied the steps in the config below by 5 as I was reducing the step period by a factor of 5.

Should I do this or should I just leave the bits below at their default values?

Thanks in advance.
Brian

From gregs at sloop.net  Thu Dec  8 01:40:56 2011
From: gregs at sloop.net (Gregory Sloop)
Date: Wed, 7 Dec 2011 16:40:56 -0800
Subject: [smokeping-users] Question about Database Config.
In-Reply-To: <B5D71B17-CB3F-4A9E-85E1-ABD8856EEFA3@iptelecom.ie>
References: <B5D71B17-CB3F-4A9E-85E1-ABD8856EEFA3@iptelecom.ie>
Message-ID: <214496458.20111207164056@sloop.net>

Provided I understand these configs right, you've got:

BC> AVERAGE  0.5   1  5040  #1008
5040 minutes of 1 min resolution data. (i.e. 84 hours or 3.5 days)

BC> AVERAGE  0.5  12  21600 #4320
BC>     MIN  0.5  12  21600 #4320
BC>     MAX  0.5  12  21600 #4320

Then the next set is 12 minute steps, and you've got 180 days of 12min
data.

[These compress the prior 1 min steps by a factor or 1:12.
Again, provided I understand correctly. This seems excessive - I'd
probably keep 30 - 90 days of 12 min data. But I'm not sure what your
goals are - perhaps that 12 minute data is more important than I
realize. But I think I should catch most important stuff in 3 days,
and after 30 days, the data's not terribly important for higher
resolution needs.]

BC> AVERAGE  0.5 144   3600 #720
BC>     MAX  0.5 144   3600 #720
BC>     MIN  0.5 144   3600 #720
Then 360 days of 144 minute (~2.3 hr resolution) data.

---
Here's what I do:

I keep one minute data too, and I use
BC> AVERAGE  0.5   1  4320  #3 days, 60 sec resolution

BC> AVERAGE  0.5  10  4320 #30 days at 10 min resolution
BC>     MIN  0.5  10  4320 #
BC>     MAX  0.5  10  4320 #
[90 days might be better, but I don't often wish for more than 30-60
days]

BC> AVERAGE  0.5 144   2400 #400 days at 2 hr resolution
BC>     MAX  0.5 144   2400 #
BC>     MIN  0.5 144   2400 #

IIRC, this results in about 8.5MB rrd files for each monitored device.
This seems like a pretty reasonable file size for me.

I just calculated it, and this appears to use roughly 0.77 KB per row of
data. [~770KB per 1000 RRD rows or ~1300 rows/MB.]

HTH

-Greg




BC> Hi All,

BC> Thank you for amazing piece of software!

BC> I had to very aggressively test packet loss to some servers so I
BC> made the following changes to the Database config.

BC> *** Database ***

BC> step     = 60
BC> pings    = 20

BC> # consfn mrhb steps total


BC> AVERAGE  0.5  12  21600 #4320
BC>     MIN  0.5  12  21600 #4320
BC>     MAX  0.5  12  21600 #4320
BC> AVERAGE  0.5 144   3600 #720
BC>     MAX  0.5 144   3600 #720
BC>     MIN  0.5 144   3600 #720


BC> Basically I multiplied the steps in the config below by 5 as I
BC> was reducing the step period by a factor of 5.

BC> Should I do this or should I just leave the bits below at their default values?

BC> Thanks in advance.
BC> Brian
BC> _______________________________________________
BC> smokeping-users mailing list
BC> smokeping-users at lists.oetiker.ch
BC> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users

-- 
Gregory Sloop, Principal: Sloop Network & Computer Consulting
Voice: 503.251.0452 x82
EMail: gregs at sloop.net
http://www.sloop.net
---


From darren at victoriajd.com  Thu Dec  8 03:43:55 2011
From: darren at victoriajd.com (Darren Murphy)
Date: Thu, 8 Dec 2011 10:43:55 +0800
Subject: [smokeping-users] Question about Database Config.
In-Reply-To: <214496458.20111207164056@sloop.net>
References: <B5D71B17-CB3F-4A9E-85E1-ABD8856EEFA3@iptelecom.ie>
	<214496458.20111207164056@sloop.net>
Message-ID: <CAJYt4JuuwUR1RybsqSaJvk4PaqmYWMzfrJC15uOuZGobzyGS5Q@mail.gmail.com>

Somewhat tangentially related (and apologies in advance for the
shameless personal plug)...

I once found the need to do a mass resize of my RRD files.
This was complicated somewhat by the fact that my existing RRD's were
of varying sizes (due to an earlier resizing exercise).

So I knocked up a script to handle this, which did the job rather well.

A copy is at http://perlmonks.org/?node_id=874274

cheers,
Darren

On 8 December 2011 08:40, Gregory Sloop <gregs at sloop.net> wrote:
> Provided I understand these configs right, you've got:
>
> BC> AVERAGE ?0.5 ? 1 ?5040 ?#1008
> 5040 minutes of 1 min resolution data. (i.e. 84 hours or 3.5 days)
>
> BC> AVERAGE ?0.5 ?12 ?21600 #4320
> BC> ? ? MIN ?0.5 ?12 ?21600 #4320
> BC> ? ? MAX ?0.5 ?12 ?21600 #4320
>
> Then the next set is 12 minute steps, and you've got 180 days of 12min
> data.
>
> [These compress the prior 1 min steps by a factor or 1:12.
> Again, provided I understand correctly. This seems excessive - I'd
> probably keep 30 - 90 days of 12 min data. But I'm not sure what your
> goals are - perhaps that 12 minute data is more important than I
> realize. But I think I should catch most important stuff in 3 days,
> and after 30 days, the data's not terribly important for higher
> resolution needs.]
>
> BC> AVERAGE ?0.5 144 ? 3600 #720
> BC> ? ? MAX ?0.5 144 ? 3600 #720
> BC> ? ? MIN ?0.5 144 ? 3600 #720
> Then 360 days of 144 minute (~2.3 hr resolution) data.
>
> ---
> Here's what I do:
>
> I keep one minute data too, and I use
> BC> AVERAGE ?0.5 ? 1 ?4320 ?#3 days, 60 sec resolution
>
> BC> AVERAGE ?0.5 ?10 ?4320 #30 days at 10 min resolution
> BC> ? ? MIN ?0.5 ?10 ?4320 #
> BC> ? ? MAX ?0.5 ?10 ?4320 #
> [90 days might be better, but I don't often wish for more than 30-60
> days]
>
> BC> AVERAGE ?0.5 144 ? 2400 #400 days at 2 hr resolution
> BC> ? ? MAX ?0.5 144 ? 2400 #
> BC> ? ? MIN ?0.5 144 ? 2400 #
>
> IIRC, this results in about 8.5MB rrd files for each monitored device.
> This seems like a pretty reasonable file size for me.
>
> I just calculated it, and this appears to use roughly 0.77 KB per row of
> data. [~770KB per 1000 RRD rows or ~1300 rows/MB.]
>
> HTH
>
> -Greg
>
>
>
>
> BC> Hi All,
>
> BC> Thank you for amazing piece of software!
>
> BC> I had to very aggressively test packet loss to some servers so I
> BC> made the following changes to the Database config.
>
> BC> *** Database ***
>
> BC> step ? ? = 60
> BC> pings ? ?= 20
>
> BC> # consfn mrhb steps total
>
>
> BC> AVERAGE ?0.5 ?12 ?21600 #4320
> BC> ? ? MIN ?0.5 ?12 ?21600 #4320
> BC> ? ? MAX ?0.5 ?12 ?21600 #4320
> BC> AVERAGE ?0.5 144 ? 3600 #720
> BC> ? ? MAX ?0.5 144 ? 3600 #720
> BC> ? ? MIN ?0.5 144 ? 3600 #720
>
>
> BC> Basically I multiplied the steps in the config below by 5 as I
> BC> was reducing the step period by a factor of 5.
>
> BC> Should I do this or should I just leave the bits below at their default values?
>
> BC> Thanks in advance.
> BC> Brian
> BC> _______________________________________________
> BC> smokeping-users mailing list
> BC> smokeping-users at lists.oetiker.ch
> BC> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>
> --
> Gregory Sloop, Principal: Sloop Network & Computer Consulting
> Voice: 503.251.0452 x82
> EMail: gregs at sloop.net
> http://www.sloop.net
> ---
>
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


From gregs at sloop.net  Thu Dec  8 05:07:16 2011
From: gregs at sloop.net (Gregory Sloop)
Date: Wed, 7 Dec 2011 20:07:16 -0800
Subject: [smokeping-users] Question about Database Config.
In-Reply-To: <CAJYt4JuuwUR1RybsqSaJvk4PaqmYWMzfrJC15uOuZGobzyGS5Q@mail.gmail.com>
References: <B5D71B17-CB3F-4A9E-85E1-ABD8856EEFA3@iptelecom.ie>
	<214496458.20111207164056@sloop.net>
	<CAJYt4JuuwUR1RybsqSaJvk4PaqmYWMzfrJC15uOuZGobzyGS5Q@mail.gmail.com>
Message-ID: <1301471122.20111207200716@sloop.net>

Hey, as long I'm wasting bandwidth... :)

It just occurred to me that my calculations prior on the number of KB
per row(s) was wrong.

The calculation I used was
8.5MB / (4300 + 4300 + 2400) = MB / RRD row

But after looking at the details of the RRD file, it appears I'm
wrong, and the calc should look something like this:

8.5MB / (4300 + (4300*3) + (2400 * 3)) = MB / RRD row

So, provided my new calculations are right, the general rough estimate
for number of rows per MB is really something different.

Also, I'm using 40 pings, rather than 20, so I have twice as many
values as the default.

So, it's probably really something like this
8.5MB / ((4300 + (4300*3) + (2400 * 3)*# of pings)) = MB / RRD row

So, really, my calculations are pretty much bollocks. I'm sure there's
a better formula - but it's probably just a whole heap easier just to
create the dang thing and see how big it is. :)

Which reminds me of that Calvin and Hobbes strip...
http://www.s-anand.net/blog/calvin-and-hobbes-dad-explains-science/

"How do they know the load limit on bridges Dad??
?They drive bigger and bigger trucks over the bridge until it breaks. Then they weigh the last truck and rebuild the bridge.?
?Oh. I should?ve guessed.

-Greg


From newsboonie at gmail.com  Thu Dec  8 08:11:21 2011
From: newsboonie at gmail.com (Boonie)
Date: Thu, 8 Dec 2011 08:11:21 +0100
Subject: [smokeping-users] For Boonie and also Help
References: <20111208091049.17356broffujmzih@mail.ai.net.nz>
Message-ID: <676129384BA34F29B3E0A5B5188FE7F7@AMD>

Hi Tony,

Thanks a lot. I'll test this weekend. I'll give feeback then.

Regards,

Dave


----- Original Message ----- 
From: "Tony Arcus" <tony at ai.net.nz>
To: <smokeping-users at lists.oetiker.ch>
Sent: Wednesday, December 07, 2011 9:10 PM
Subject: [smokeping-users] For Boonie and also Help


> Hi Boonie
> I am getting together a how to on Centos 6 and Smokeping.
> I have hit a road block that I hope to fix.
> See here
> http://ai.net.nz/gettinghelp/how-do-i/centos-servers/67-5-packages-04-smokeping.html
>
>
> My question to the group is:
>
> Having done all this I get error messages in my /var/log/httpd/error_log 
> file
>
>      (13)Permission denied: exec of
> '/var/www/cgi-bin/cropper/smokeping-zoom.js'
>
> This is due to having the cropper dir in the /var/www/cgi-bin directory.
>
>    1. So here is where I am at.
>    2. I have previously had older versions of smokeping going fine on
> my servers.
>    3. This new version has got me a bit lost.
>    4. The web pages are forming, but with out graphs.
>    5. Where should things live?
>    6. I put smokeping.fcgi in to /var/www/cgi-bin (as I have in older
> versions)
>    7. I can url to this fine and things appear, bit no graphs
>    8. I have errors in my log relating to cropper
>
>
> SO
>    9. Where should cropper be put?
>   10. Where should smokeping.fcgi put?
>   11. What should the referencing url be?
> http:://me.com/cgi-bin/smokeping.fcgi
>
> Thanks
> -- 
> Tony Arcus
> Systems and Network Engineer
> Access Information Limited
> PO Box 122
> Carterton
> Wairarapa
>
> Phone : 06-379-6668
> Phone : 04-831-1401
> Email : tony at ai.net.nz
> Cell  : 021-827-660
>
> This email and any accompanying documentation may contain privileged and
> confidential information.  If you are not the intended recipient, your use
> of the information is strictly prohibited.
>
>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
> 


From cholam20 at yahoo.co.in  Thu Dec  8 21:04:24 2011
From: cholam20 at yahoo.co.in (revathi ganesh)
Date: Fri, 9 Dec 2011 01:34:24 +0530 (IST)
Subject: [smokeping-users] Your question...
Message-ID: <1323374664.78082.androidMobile@web137314.mail.in.yahoo.com>

<p>Hola!<br>don't let insufficient funds hold you back in life<br><a href="http://www.curtain-plage.co.jp/profile/75NicholasWilliams/">http://www.curtain-plage.co.jp/profile/75NicholasWilliams/</a><br>goodbye.</p>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20111209/a2bc3a1b/attachment.htm 

From brian at iptelecom.ie  Thu Dec  8 21:39:28 2011
From: brian at iptelecom.ie (Brian Chamberlain)
Date: Thu, 8 Dec 2011 20:39:28 +0000
Subject: [smokeping-users] Question about Database Config.
In-Reply-To: <214496458.20111207164056@sloop.net>
References: <B5D71B17-CB3F-4A9E-85E1-ABD8856EEFA3@iptelecom.ie>
	<214496458.20111207164056@sloop.net>
Message-ID: <AAA136FF-4D4F-48F5-92C0-F84ED3096364@iptelecom.ie>


On 8 Dec 2011, at 00:40, Gregory Sloop wrote:

> Provided I understand these configs right, you've got:
> 
> BC> AVERAGE  0.5   1  5040  #1008
> 5040 minutes of 1 min resolution data. (i.e. 84 hours or 3.5 days)
> 
> BC> AVERAGE  0.5  12  21600 #4320
> BC>     MIN  0.5  12  21600 #4320
> BC>     MAX  0.5  12  21600 #4320
> 
> Then the next set is 12 minute steps, and you've got 180 days of 12min
> data.
> 
> [These compress the prior 1 min steps by a factor or 1:12.
> Again, provided I understand correctly. This seems excessive - I'd
> probably keep 30 - 90 days of 12 min data. But I'm not sure what your
> goals are - perhaps that 12 minute data is more important than I
> realize. But I think I should catch most important stuff in 3 days,
> and after 30 days, the data's not terribly important for higher
> resolution needs.]
> 
> BC> AVERAGE  0.5 144   3600 #720
> BC>     MAX  0.5 144   3600 #720
> BC>     MIN  0.5 144   3600 #720
> Then 360 days of 144 minute (~2.3 hr resolution) data.
> 
> ---
> Here's what I do:
> 
> I keep one minute data too, and I use
> BC> AVERAGE  0.5   1  4320  #3 days, 60 sec resolution
> 
> BC> AVERAGE  0.5  10  4320 #30 days at 10 min resolution
> BC>     MIN  0.5  10  4320 #
> BC>     MAX  0.5  10  4320 #
> [90 days might be better, but I don't often wish for more than 30-60
> days]
> 
> BC> AVERAGE  0.5 144   2400 #400 days at 2 hr resolution
> BC>     MAX  0.5 144   2400 #
> BC>     MIN  0.5 144   2400 #
> 
> IIRC, this results in about 8.5MB rrd files for each monitored device.
> This seems like a pretty reasonable file size for me.
> 
> I just calculated it, and this appears to use roughly 0.77 KB per row of
> data. [~770KB per 1000 RRD rows or ~1300 rows/MB.]
> 
> HTH
> 
> -Greg




Hi Greg,

Many thanks for this excellent reply. I can't find documentation that answers this question:

If I adjust:

*** Database ***

step     = 60
pings    = 20


to different values do I have to adjust the 

# consfn mrhb steps total


lines in step with the adjustments made to the step and pings?

Thanks
Brian

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

From gregs at sloop.net  Thu Dec  8 21:55:24 2011
From: gregs at sloop.net (Gregory Sloop)
Date: Thu, 8 Dec 2011 12:55:24 -0800
Subject: [smokeping-users] Question about Database Config.
In-Reply-To: <AAA136FF-4D4F-48F5-92C0-F84ED3096364@iptelecom.ie>
References: <B5D71B17-CB3F-4A9E-85E1-ABD8856EEFA3@iptelecom.ie>
	<214496458.20111207164056@sloop.net>
	<AAA136FF-4D4F-48F5-92C0-F84ED3096364@iptelecom.ie>
Message-ID: <328225251.20111208125524@sloop.net>

An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20111208/e5d5791b/attachment.htm 

From tony at ai.net.nz  Tue Dec 13 21:30:21 2011
From: tony at ai.net.nz (Tony Arcus)
Date: Wed, 14 Dec 2011 09:30:21 +1300
Subject: [smokeping-users] For Boonie and also Help
In-Reply-To: <CACG8jGzFUeS+CA+FeOz2CDPo6kiP0WYmMs+5jE-AMLXdCS6wCA@mail.gmail.com>
References: <20111208091049.17356broffujmzih@mail.ai.net.nz>
	<CACG8jGxTh070KqNVx9RbemZ6jr8VKFpWhG4rfvgJpAMBrsQMsA@mail.gmail.com>
	<CACG8jGzFUeS+CA+FeOz2CDPo6kiP0WYmMs+5jE-AMLXdCS6wCA@mail.gmail.com>
Message-ID: <20111214093021.61903i86824wco9p@mail.ai.net.nz>

Right I think I may be getting things to work.

Thanks Alexandre for your email I think I have all the bits finally  
worked out.

I am running a centos 6 server for a customer, with MailScanner,  
ClamAV, Spamassassin as a firewall and internal network monitor  
therefore my desire to have smokeping running.

Previously under Centos 5 my howto worked find and every things  
installed in a snap.
Since moving to Centos 6 I have been working though a heap of problems.
So my how to for Smokeping is here:

http://ai.net.nz/gettinghelp/how-do-i/centos-servers/67-5-packages-04-smokeping.html

-- 
Tony Arcus
Systems and Network Engineer
Access Information Limited
PO Box 122
Carterton
Wairarapa

Phone : 06-379-6668
Phone : 04-831-1401
Email : tony at ai.net.nz
Cell  : 021-827-660

This email and any accompanying documentation may contain privileged and
confidential information.  If you are not the intended recipient, your use
of the information is strictly prohibited.


Quoting Alexandre COLONNA <alex.colonna at bjtmail.com>:

> Hi I forgot !
>
> With centos you could encountered some trouble with selinux try make a
> setenforce 0 or use semanage command
> *
> *
> *Cheers*
> *
> *
> *Alex*
>
>
> 2011/12/7 Alexandre COLONNA <alex.colonna at bjtmail.com>
>
>> Hi
>> it's quite simple to install smokeping on centos 6, which version did you
>> install ?
>>
>> For the latest version, you must follow the "install" tutorial on
>> http://oss.oetiker.ch/smokeping/doc/smokeping_install.en.html
>>
>> After that you must allow cgi execution in your httpd.conf for the
>> directory /var/www/html and if you have an .htaccess add those lines to
>> allow cgi execution:
>>
>> AddHandler cgi-script .cgi
>> Options +ExecCGI
>>
>> If you use "fcgi" you must enable EPEL depot : yum --enablerepo epel
>> then install fast-cgi and httpd-devel : yum install mod_fcgid httpd-devel
>>
>> After that you must edit your config file in /opt/smokeping/etc/config to
>> put the good link:
>> imgcache = /opt/smokeping/img
>> imgurl   = ../smokeping/img
>> datadir  = /opt/smokeping/data
>> piddir  = /opt/smokeping/var
>> cgiurl   = http://www.exemple.com/smokeping/smokeping.fcgi
>> smokemail = /opt/smokeping/etc/smokemail
>> tmail = /opt/smokeping/etc/tmail
>>
>> After that don't forget to create some directories like /opt/smokeping/img
>> /opt/smokeping/img/data and /opt/smokeping/img/var
>>
>> Now you could make symbolics links in your /var/www/html,  e.g :
>> ln -s /opt/smokeping/htdocs /var/www/html/smokeping
>> ln -s /opt/smokeping/img /var/www/html/smokeping
>>
>> And normally (maybe i'm going too fast) it's done !
>> maybe you will encountered some trouble about permissions.
>> In my case iput the file img in chmod 777 and the htdoc in 755
>>
>> Good luck and tell me if it's ok
>>
>> cheers
>>
>> Alex
>>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


From gregs at sloop.net  Tue Dec 13 22:39:52 2011
From: gregs at sloop.net (Greg Sloop)
Date: Tue, 13 Dec 2011 13:39:52 -0800
Subject: [smokeping-users] For Boonie and also Help
In-Reply-To: <20111214093021.61903i86824wco9p@mail.ai.net.nz>
References: <20111208091049.17356broffujmzih@mail.ai.net.nz>
	<CACG8jGxTh070KqNVx9RbemZ6jr8VKFpWhG4rfvgJpAMBrsQMsA@mail.gmail.com>
	<CACG8jGzFUeS+CA+FeOz2CDPo6kiP0WYmMs+5jE-AMLXdCS6wCA@mail.gmail.com>
	<20111214093021.61903i86824wco9p@mail.ai.net.nz>
Message-ID: <B81B19DB-63CE-422C-9927-610ECA715D67@sloop.net>

I had had the same problem with graphs under ubuntu, and my lazy/desperate method to fix it was to simply copy the whole HTML directory structure to /var/www (or wherever ubuntu's default apache www dir is)

I assume is was a permissions issues, either with the apache config, or in the directories themselves. (I would guess the former). But once I got it working, I gave up trying to figure the rest of it out and left it as is now.
 -Greg


On Dec 13, 2011, at 12:30 PM, Tony Arcus <tony at ai.net.nz> wrote:

> Right I think I may be getting things to work.
> 
> Thanks Alexandre for your email I think I have all the bits finally  
> worked out.
> 
> I am running a centos 6 server for a customer, with MailScanner,  
> ClamAV, Spamassassin as a firewall and internal network monitor  
> therefore my desire to have smokeping running.
> 
> Previously under Centos 5 my howto worked find and every things  
> installed in a snap.
> Since moving to Centos 6 I have been working though a heap of problems.
> So my how to for Smokeping is here:
> 
> http://ai.net.nz/gettinghelp/how-do-i/centos-servers/67-5-packages-04-smokeping.html
> 
> -- 
> Tony Arcus
> Systems and Network Engineer
> Access Information Limited
> PO Box 122
> Carterton
> Wairarapa
> 
> Phone : 06-379-6668
> Phone : 04-831-1401
> Email : tony at ai.net.nz
> Cell  : 021-827-660
> 
> This email and any accompanying documentation may contain privileged and
> confidential information.  If you are not the intended recipient, your use
> of the information is strictly prohibited.
> 
> 
> Quoting Alexandre COLONNA <alex.colonna at bjtmail.com>:
> 
>> Hi I forgot !
>> 
>> With centos you could encountered some trouble with selinux try make a
>> setenforce 0 or use semanage command
>> *
>> *
>> *Cheers*
>> *
>> *
>> *Alex*
>> 
>> 
>> 2011/12/7 Alexandre COLONNA <alex.colonna at bjtmail.com>
>> 
>>> Hi
>>> it's quite simple to install smokeping on centos 6, which version did you
>>> install ?
>>> 
>>> For the latest version, you must follow the "install" tutorial on
>>> http://oss.oetiker.ch/smokeping/doc/smokeping_install.en.html
>>> 
>>> After that you must allow cgi execution in your httpd.conf for the
>>> directory /var/www/html and if you have an .htaccess add those lines to
>>> allow cgi execution:
>>> 
>>> AddHandler cgi-script .cgi
>>> Options +ExecCGI
>>> 
>>> If you use "fcgi" you must enable EPEL depot : yum --enablerepo epel
>>> then install fast-cgi and httpd-devel : yum install mod_fcgid httpd-devel
>>> 
>>> After that you must edit your config file in /opt/smokeping/etc/config to
>>> put the good link:
>>> imgcache = /opt/smokeping/img
>>> imgurl   = ../smokeping/img
>>> datadir  = /opt/smokeping/data
>>> piddir  = /opt/smokeping/var
>>> cgiurl   = http://www.exemple.com/smokeping/smokeping.fcgi
>>> smokemail = /opt/smokeping/etc/smokemail
>>> tmail = /opt/smokeping/etc/tmail
>>> 
>>> After that don't forget to create some directories like /opt/smokeping/img
>>> /opt/smokeping/img/data and /opt/smokeping/img/var
>>> 
>>> Now you could make symbolics links in your /var/www/html,  e.g :
>>> ln -s /opt/smokeping/htdocs /var/www/html/smokeping
>>> ln -s /opt/smokeping/img /var/www/html/smokeping
>>> 
>>> And normally (maybe i'm going too fast) it's done !
>>> maybe you will encountered some trouble about permissions.
>>> In my case iput the file img in chmod 777 and the htdoc in 755
>>> 
>>> Good luck and tell me if it's ok
>>> 
>>> cheers
>>> 
>>> Alex
>>> 
>> 
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>> 
>> 
> 
> 
> 
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
> 
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


From spirrello at gmail.com  Wed Dec 14 04:13:45 2011
From: spirrello at gmail.com (Stefano Pirrello)
Date: Tue, 13 Dec 2011 22:13:45 -0500
Subject: [smokeping-users] Installing Smokeping 2.2.6 on CentOS 5.7
Message-ID: <CAJ_tR7U7tMdzfT=8CY4u8-p5q_Qy_JQWU5AHeqX4T=oJ6r3H8w@mail.gmail.com>

Hi,

Can someone point me to a guide for installing Smokeping 2.6.6 on a
new CentOS 5.7 installation?  There doesn't seem to be anything out
there yet.

Thank you,
Stefano


From gregs at sloop.net  Wed Dec 14 19:04:50 2011
From: gregs at sloop.net (Gregory Sloop)
Date: Wed, 14 Dec 2011 10:04:50 -0800
Subject: [smokeping-users] Alerts
Message-ID: <557569534.20111214100450@sloop.net>


I'm having some problems with alerts on a new installation.

I see in the syslog messages like this:
"... ubuntu smokeping[30041]: Alert loss-moderate was raised for xyz"

This should mean, to my understanding that the alert flag was raised,
and if email alerts are defined properly, I should get an alert email,
which I don't.

===
But I also see messages like this in the debug trace.
---
Alert "loss-small": no match for target /var/lib/smokeping/rrd/xyz
Alert "loss-moderate": no match for target /var/lib/smokeping/rrd/xyz
Alert "loss-massive": no match for target /var/lib/smokeping/rrd/xyz

---
What do the "no match for target" messages mean?

===
So, I'm working to figure out why I'm not getting email.
Anyone have any helpful tips to get more logging/debug info so I can
see what's failing?

I've reviewed my config files carefully and I don't see any errors
there, but without any debug info, finding what's wrong is a bit
difficult - esp when you don't know where to look.

Thoughts/suggestions welcome! <beg> Please! </beg>

-Greg

-- 
Gregory Sloop, Principal: Sloop Network & Computer Consulting
503.251.0452 x82 Voice | 503.251.0452 Fax
www.sloop.net
mailto:gregs at sloop.net


From gregs at sloop.net  Wed Dec 14 19:10:07 2011
From: gregs at sloop.net (Gregory Sloop)
Date: Wed, 14 Dec 2011 10:10:07 -0800
Subject: [smokeping-users] Paging Mark Perry!
Message-ID: <161251310.20111214101007@sloop.net>

... Paging Mark Perry!
Please pick up the white paging telephone for an urgent message...

---
Dang - I've subscribed to the SP list for quite a while, and I'm not
sure that Mark Perry has EVER actually been *in* the office.

He's never posted to the list, at least not that I can tell from any
searches of the archives, etc.

Is there any reason to leave him subscribed?

:-\

-Greg


From cholam20 at yahoo.co.in  Wed Dec 14 19:18:19 2011
From: cholam20 at yahoo.co.in (revathi ganesh)
Date: Wed, 14 Dec 2011 23:48:19 +0530 (IST)
Subject: [smokeping-users] try it out for yourself
Message-ID: <1323886699.73967.androidMobile@web137306.mail.in.yahoo.com>

<p>Hola.<br>im finally turning my life around since I found this ive never had a late payment now im on top of my game imagine the possibilities<br><a href="http://serviciogamo.com/profile/23DarrenBrown/">http://serviciogamo.com/profile/23DarrenBrown/</a><br>goodbye.</p>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20111214/b6cdaf56/attachment-0001.htm 

From gregs at sloop.net  Wed Dec 14 21:43:43 2011
From: gregs at sloop.net (Gregory Sloop)
Date: Wed, 14 Dec 2011 12:43:43 -0800
Subject: [smokeping-users] Alerts pt 2
Message-ID: <1805539254.20111214124343@sloop.net>

Tobi...
Possible semi-bug [I hesitate to say it - because I code horribly and
don't know perl very well at all, but think so. Please don't flame me
if I'm wrong! :) ]

I see that in both 2.4.2 and 2.6.6 I get that message on every
target - at least in my installation. [My 2.4.2 install is working
fine, my new 2.6.6 is not.]

Perhaps there's a semi-bug in the code.

I'm using a "to = |" for my destination - since I'm using my own perl
module to send mail. I'm also using the edgetrigger option.

I'd assume that it shouldn't generate any message like the above in
this case, but it does.

[It seems like it should only generate that message if there's nothing
in the "to=" section in the config file. [Provided I'm reading the
perl correctly, which isn't at all certain.]
See - {if (@to) - line 1897 in smokeping.pm}

[It looks like it should break out of the whole routine once it finds
it's using SNPP or the "|" and not check the following IF. [If you're
doing a pipe or SNPP, you're not doing the code under the @if (I
think)]


I'm still not sure why I'm not getting messages, but perhaps I'm
getting closer.

Again, I welcome any thoughts/suggestions.

-Greg

-- 
Gregory Sloop, Principal: Sloop Network & Computer Consulting
503.251.0452 x82 Voice | 503.251.0452 Fax
www.sloop.net
mailto:gregs at sloop.net


From gregs at sloop.net  Wed Dec 14 21:55:53 2011
From: gregs at sloop.net (Gregory Sloop)
Date: Wed, 14 Dec 2011 12:55:53 -0800
Subject: [smokeping-users] Alerts pt 2
In-Reply-To: <1805539254.20111214124343@sloop.net>
References: <1805539254.20111214124343@sloop.net>
Message-ID: <69364957.20111214125553@sloop.net>

I'm sorry, I left out critical information in my prior post, let me re-post.
I've clarified a bit too.

---
Tobi...
Possible semi-bug [I hesitate to say it - because I code horribly and
don't know perl very well at all, but think so. Please don't flame me
if I'm wrong! :) ]

I get this message.
---
Alert "loss-small": no match for target /var/lib/smokeping/rrd/xyz
Alert "loss-moderate": no match for target /var/lib/smokeping/rrd/xyz
Alert "loss-massive": no match for target /var/lib/smokeping/rrd/xyz

---
I see that in both 2.4.2 and 2.6.6 I get that message on every
target - at least in my installation. [My 2.4.2 install is working
fine, my new 2.6.6 is not.]

I believe I get the message every pass [step], regardless of an actual alert being
raised or not.

Perhaps there's a semi-bug in the code.

I'm using a "to = |" for my destination - since I'm using my own perl
module to send mail. I'm also using the edgetrigger option.

I'd assume that it shouldn't generate any message like the above in
this case, but it does.

[It seems like it should only generate that message if there's nothing
in the "to=" section in the config file. [Provided I'm reading the
perl correctly, which isn't at all certain.

See - {if (@to) - line 1897 in smokeping.pm}

It looks like it should break out of the whole routine once it finds
it's using SNPP or the "|" and not check the following IF. If you're
doing a pipe or SNPP, you're not doing the code under the "if (@to)" (I
think)]


I'm still not sure why I'm not getting messages, but perhaps I'm
getting closer.

Again, I welcome any thoughts/suggestions.

-Greg
---


From gregs at sloop.net  Wed Dec 14 23:13:41 2011
From: gregs at sloop.net (Gregory Sloop)
Date: Wed, 14 Dec 2011 14:13:41 -0800
Subject: [smokeping-users] Alerts pt 3
Message-ID: <83210705.20111214141341@sloop.net>

My prior complaint of a bug still stands, but I did resolve my problem.
[If those messages *are* bugs, they can cause someone to spend time
chasing them down when they're phantom problems.]

My problem wasn't related to those messages.

I had a syntax problem on the Alert configs, and thus my perl script to
email me wasn't running properly. [D'oh]

Once I fixed that, I do get email, but the log/debug messages still
occur.

[i.e.
Alert "loss-small": no match for target /var/lib/smokeping/rrd/xyz
Alert "loss-moderate": no match for target /var/lib/smokeping/rrd/xyz
Alert "loss-massive": no match for target /var/lib/smokeping/rrd/xyz]

And these occur regardless of an alert state being raised or not.
They occur every step right after the RRD:Update call for that target


-Greg

-- 
Gregory Sloop, Principal: Sloop Network & Computer Consulting
503.251.0452 x82 Voice | 503.251.0452 Fax
www.sloop.net
mailto:gregs at sloop.net


From darren at victoriajd.com  Thu Dec 15 04:21:18 2011
From: darren at victoriajd.com (Darren Murphy)
Date: Thu, 15 Dec 2011 11:21:18 +0800
Subject: [smokeping-users] Paging Mark Perry!
In-Reply-To: <161251310.20111214101007@sloop.net>
References: <161251310.20111214101007@sloop.net>
Message-ID: <CAJYt4Jue2WrSoXPNoJQv5VhPfYChwgdFYW2StEMKTtSoOzB_pQ@mail.gmail.com>

Greg,

I'm not quite sure what you're getting at here.
As far as I'm aware, active participation is not (and never has been)
a prerequisite for belonging to a mailing list.
I'd imagine that there are lots of people that have subscribed to the
list, but never posted.

So what?

cheers,
Darren

On 15 December 2011 02:10, Gregory Sloop <gregs at sloop.net> wrote:
> ... Paging Mark Perry!
> Please pick up the white paging telephone for an urgent message...
>
> ---
> Dang - I've subscribed to the SP list for quite a while, and I'm not
> sure that Mark Perry has EVER actually been *in* the office.
>
> He's never posted to the list, at least not that I can tell from any
> searches of the archives, etc.
>
> Is there any reason to leave him subscribed?
>
> :-\
>
> -Greg
>
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


From david at schweikert.ch  Fri Dec 16 22:43:50 2011
From: david at schweikert.ch (David Schweikert)
Date: Fri, 16 Dec 2011 22:43:50 +0100
Subject: [smokeping-users] fping 3: new version with improved performance,
	please test
Message-ID: <20111216214350.GA16939@schweikert.ch>

Dear SmokePing community:

I am about to announce fping version 3 (see the announcement text that I
prepared for it below). Before releasing it officially and calling it
"3.0", I'd like to ask for any volunteer to test a release candidate,
available here: http://fping.org/dist/

This new version includes a completely reworked main loop, which should
really make a difference in the total run time of fping. I am interested
to hear if it works well for you and if you get similar results as
before.

Thanks
David

------ DRAFT ANNOUNCEMENT FOR FPING 3.0 --------

     _                 _  
   _|_ ._  o ._   _    _) 
    |  |_) | | | (_|   _) 
       |          _|     

    (fping version 3.0-rc2)

What is fping?

    fping is a program to send ICMP echo probes to network hosts, similar
    to ping, but much better performing when pinging multiple hosts.

    fping has a long long story: Roland Schemers did publish a first
    version of it in 1992 and it has established itself since then as
    a standard tool.

Announcing version 3

    There has been no official fping release since 2002. Various patches
    exist, but were never integrated "upstream". Also, the current
    maintainer doesn't answer emails, so I decided to just step up and
    take over maintenanceship. If you disagree, please contact me.

    To mark this change of maintenance, and avoid confusion, I have
    decided to call it version 3. Besides a new maintainer, fping now also
    features a completely rewritten main loop implementation which
    improves performance significantly. The run time is now close to the
    theoretical time required to send and receive the pings under the
    specified parameters.

Included changes

    fping 3.0 includes the following changes, compared to the last
    released version 2.4b2-to-ipv6:

    - Debian patches until version 2.4b2-to-ipv6-16.
    - Modifications by Tobias Oetiker for SmokePing (2.4b2-to4)
    - Reimplemented main loop for improved performance (me)

Where to get

    http://fping.org/

    (see also that link for any feedback)


From ged at jubileegroup.co.uk  Fri Dec 16 23:19:30 2011
From: ged at jubileegroup.co.uk (G.W. Haywood)
Date: Fri, 16 Dec 2011 22:19:30 +0000 (GMT)
Subject: [smokeping-users] fping 3: new version with improved
 performance, please test
In-Reply-To: <20111216214350.GA16939@schweikert.ch>
References: <20111216214350.GA16939@schweikert.ch>
Message-ID: <Pine.LNX.4.58.1112162217320.15295@mail3.jubileegroup.co.uk>

Hi there,
On Fri, 16 Dec 2011, David Schweikert wrote:

> I am about to announce fping version 3 ...

Thanks, and well done!

I haven't done a lot with your version yet, but I have at least
compiled it on AMD64 (Debian Squeeze) with no issues.

At first glance your version seems to accept -T but doesn't mention it
in the usage output.

--

73,
Ged.


From david at schweikert.ch  Sun Dec 18 00:22:28 2011
From: david at schweikert.ch (David Schweikert)
Date: Sun, 18 Dec 2011 00:22:28 +0100
Subject: [smokeping-users] fping 3: new version with improved
 performance, please test
In-Reply-To: <Pine.LNX.4.58.1112162217320.15295@mail3.jubileegroup.co.uk>
References: <20111216214350.GA16939@schweikert.ch>
	<Pine.LNX.4.58.1112162217320.15295@mail3.jubileegroup.co.uk>
Message-ID: <20111217232228.GC29358@schweikert.ch>

Hi Ged,

On Fri, Dec 16, 2011 at 22:19:30 +0000, G.W. Haywood wrote:
> At first glance your version seems to accept -T but doesn't mention it
> in the usage output.

The -T option was actually one of the main motivations for me to rewrite
some part of fping: "select timeout"? Worst parameter description ever :-)

My implementation will still accept that parameter for compatibility
reasons, but will ignore it. The internal select statement now uses a
dynamic timeout value based on when it expects the next event.

Still, you are probably right that it should be mentioned in the usage
output with something like: ignored (for compatibility reasons). I will
do that.

Cheers
David


From newsboonie at gmail.com  Sun Dec 18 16:11:04 2011
From: newsboonie at gmail.com (Boonie)
Date: Sun, 18 Dec 2011 16:11:04 +0100
Subject: [smokeping-users] For Boonie and also Help
References: <20111208091049.17356broffujmzih@mail.ai.net.nz>
	<CACG8jGxTh070KqNVx9RbemZ6jr8VKFpWhG4rfvgJpAMBrsQMsA@mail.gmail.com>
	<CACG8jGzFUeS+CA+FeOz2CDPo6kiP0WYmMs+5jE-AMLXdCS6wCA@mail.gmail.com>
	<20111214093021.61903i86824wco9p@mail.ai.net.nz>
Message-ID: <ACDFF57BB27748F3BCC807A97D249C58@AMD>

I tried and failed again.

I've replied off-list with more info.

Thanks,

Dave


----- Original Message ----- 
From: "Tony Arcus" <tony at ai.net.nz>
To: "Boonie" <newsboonie at gmail.com>
Cc: <smokeping-users at lists.oetiker.ch>
Sent: Tuesday, December 13, 2011 9:30 PM
Subject: Re: [smokeping-users] For Boonie and also Help


> Right I think I may be getting things to work.
>
> Thanks Alexandre for your email I think I have all the bits finally 
> worked out.
>
> I am running a centos 6 server for a customer, with MailScanner,  ClamAV, 
> Spamassassin as a firewall and internal network monitor  therefore my 
> desire to have smokeping running.
>
> Previously under Centos 5 my howto worked find and every things  installed 
> in a snap.
> Since moving to Centos 6 I have been working though a heap of problems.
> So my how to for Smokeping is here:
>
> http://ai.net.nz/gettinghelp/how-do-i/centos-servers/67-5-packages-04-smokeping.html
>
> -- 
> Tony Arcus
> Systems and Network Engineer
> Access Information Limited
> PO Box 122
> Carterton
> Wairarapa
>
> Phone : 06-379-6668
> Phone : 04-831-1401
> Email : tony at ai.net.nz
> Cell  : 021-827-660
>
> This email and any accompanying documentation may contain privileged and
> confidential information.  If you are not the intended recipient, your use
> of the information is strictly prohibited.
>
>
> Quoting Alexandre COLONNA <alex.colonna at bjtmail.com>:
>
>> Hi I forgot !
>>
>> With centos you could encountered some trouble with selinux try make a
>> setenforce 0 or use semanage command
>> *
>> *
>> *Cheers*
>> *
>> *
>> *Alex*
>>
>>
>> 2011/12/7 Alexandre COLONNA <alex.colonna at bjtmail.com>
>>
>>> Hi
>>> it's quite simple to install smokeping on centos 6, which version did 
>>> you
>>> install ?
>>>
>>> For the latest version, you must follow the "install" tutorial on
>>> http://oss.oetiker.ch/smokeping/doc/smokeping_install.en.html
>>>
>>> After that you must allow cgi execution in your httpd.conf for the
>>> directory /var/www/html and if you have an .htaccess add those lines to
>>> allow cgi execution:
>>>
>>> AddHandler cgi-script .cgi
>>> Options +ExecCGI
>>>
>>> If you use "fcgi" you must enable EPEL depot : yum --enablerepo epel
>>> then install fast-cgi and httpd-devel : yum install mod_fcgid 
>>> httpd-devel
>>>
>>> After that you must edit your config file in /opt/smokeping/etc/config 
>>> to
>>> put the good link:
>>> imgcache = /opt/smokeping/img
>>> imgurl   = ../smokeping/img
>>> datadir  = /opt/smokeping/data
>>> piddir  = /opt/smokeping/var
>>> cgiurl   = http://www.exemple.com/smokeping/smokeping.fcgi
>>> smokemail = /opt/smokeping/etc/smokemail
>>> tmail = /opt/smokeping/etc/tmail
>>>
>>> After that don't forget to create some directories like 
>>> /opt/smokeping/img
>>> /opt/smokeping/img/data and /opt/smokeping/img/var
>>>
>>> Now you could make symbolics links in your /var/www/html,  e.g :
>>> ln -s /opt/smokeping/htdocs /var/www/html/smokeping
>>> ln -s /opt/smokeping/img /var/www/html/smokeping
>>>
>>> And normally (maybe i'm going too fast) it's done !
>>> maybe you will encountered some trouble about permissions.
>>> In my case iput the file img in chmod 777 and the htdoc in 755
>>>
>>> Good luck and tell me if it's ok
>>>
>>> cheers
>>>
>>> Alex
>>>
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> 


From david at schweikert.ch  Wed Dec 28 15:00:47 2011
From: david at schweikert.ch (David Schweikert)
Date: Wed, 28 Dec 2011 15:00:47 +0100
Subject: [smokeping-users] ANNOUNCE: fping 3.0 (better performance,
	new maintainer)
Message-ID: <20111228140047.GA31670@schweikert.ch>

Dear SmokePing community:

I'd like to announce a new version of the popular fping tool:

     _                 _  
   _|_ ._  o ._   _    _) 
    |  |_) | | | (_|   _) 
       |          _|     

    (fping version 3.0)

What is fping?

    fping is a program to send ICMP echo probes to network hosts, similar
    to ping, but much better performing when pinging multiple hosts.

    fping has a long long story: Roland Schemers did publish a first
    version of it in 1992 and it has established itself since then as
    a standard tool.

Announcing version 3

    There has been no official fping release since 2002. Various patches
    exist, but were never integrated "upstream". Also, the current
    maintainer doesn't answer emails, so I decided to just step up and
    take over maintenance. If you disagree, please contact me.

    To mark this change of maintenance, and avoid confusion, I have
    decided to call it version 3. Besides a new maintainer, fping now also
    features a completely rewritten main loop implementation which
    improves performance significantly. The run time is now close to the
    theoretical time required to send and receive the pings under the
    specified parameters.

Included changes

    fping 3.0 includes the following changes, compared to the last
    released version 2.4b2-to-ipv6:

    - Debian patches until version 2.4b2-to-ipv6-16.
    - Modifications by Tobias Oetiker for SmokePing (2.4b2-to4)
    - Reimplemented main loop for improved performance (me)

Where to get it

    http://fping.org/

    (see also that link for any feedback)


From lb at mpexnet.de  Fri Dec 30 10:32:40 2011
From: lb at mpexnet.de (Lars Braeuer)
Date: Fri, 30 Dec 2011 10:32:40 +0100
Subject: [smokeping-users] Mail timestamps end up as 01/01/1970 at mail
 recipient in 2.6.3-5 (Debian) [SOLVED]
Message-ID: <4EFD8538.3090409@mpexnet.de>

Hi,

we are using the Debian stable version 2.3.6-5, which is indeed a bit old compared to the current
version 2.6.6.

At some point we started receiving smokeping mails with a date of 01.01.1970, although the date line
seemed to be present in the mail header.

After some debugging I found out that this is a locales problem which is not corrected by smokeping
setting LC_NUMERIC to 'C' in lib/Smokeping.pm.

$rfc2822stamp, which is used when sending mails, ends up to be something like "Fr, 30 Dez 2011
09:57:08 +0100" (note the "Dez", which is German and not intepreted by the mailserver as a valid date).

As I have no time to test 2.6.6 at the moment, my workaround for the Debian version is to include
"LC_TIME=C" in /etc/default/smokeping (restart smokeping afterwards).

I actually searched through the 2.6.6 code but found no mention of LC_TIME. So if the problem still
persists with 2.6.6, this could be fixed in future releases by not only setting LC_NUMERIC but also
LC_TIME to 'C'.

Best regards

Lars Br?uer
-- 
MPeX.net GmbH / Werner-Vo?-Damm 62 / D-12101 Berlin / Germany
MPeXnetworks / www.mpexnetworks.de
Tel: ++49-30-78097 180 / Fax: ++49-30-78097 181

Sitz, Registergericht: Berlin, Amtsgericht Charlottenburg, HRB 76688
Gesch?ftsf?hrer: Lars Br?uer, Gregor Rex-Lawatscheck