Hi there, I'm having some trouble getting the web interface to smokeping going, The daemon is fine and appears to run 100% However when I try to access the Web interface I get the following error: "speedy[16214]: Cannot spawn backend process" Has anyone had this before ? Thanks and Regards NIc
Good Morning, Yesterday I have released SmokePing 2. It includes a revamped Plugin-Interface written by Niko Tyni as well as updates to all the monitoring plug-ins. The new plugin system provides better config file integration for plugin specific directives as well as improved documentation. Niko has ported all the existing plugins to the new architecture and made several updates to the plugins in the process. There was also the odd stability fix and an all new website that went along with the update. Note that you may have to update your config file to work with the new version. You find all the documentation online on http://people.ee.ethz.ch/~oetiker/webtools/smokeping cheers tobi -- -- ______ __ _ /_ __/_ / / (_) Oetiker <at> ISG.EE, ETL F24.2, ETH, CH-8092 Zurich / // _ \/ _ \/ / System Manager, Time Lord, Coder, Designer, Coach /_/ \.__/_.__/_/ http://people.ee.ethz.ch/oetiker +41(0)44-632-5286(Continue reading)
Hello, I have started playing with sending alerts from my already working SmokePing installation. I use the latest-and-greatest version 2.0.1 (thanks for the great work!) and I have a problem with the alert called someloss in the distributed sample configuration file. It looks like this: +someloss type = loss # in percent pattern = >0%,*12*,>0%,*12*,>0% comment = loss 3 times in a row When I interpret it according to the documentation at http://people.ee.ethz.ch/~oetiker/webtools/smokeping/doc/smokeping_config.en.html - especially this part: ----------------------------------------------------------------------- Sometimes it may be that conditions occur at irregular intervals. But still you only want to throw an alert if they occur several times within a certain amount of times. The operator *X* will ignore up to X values and still let the pattern match: >10%,*10*,>10% will fire if more than 10% of the packets have been lost at least twice over the last 10 samples. ----------------------------------------------------------------------- I would expect that for a host which is down (100% packet loss all the(Continue reading)
When accessing http://<hostname>/cgi-bin/smokeping.cgi Apache returns the following error ERROR: /var/www/cgi-bin/smokeping.cgi, line 3: table syntax error Smokeping.cgi is located in the Apache cgi-bin directory. Httpd.conf has this Directory configured for Exec CGI. The only error in the httpd logs is the one displayed to the user above.... Apache User is 'apache', and member of apache group. /var/www/cgi-bin [root <at> home cgi-bin]# ls -la drwxr-xr-x 2 root apache 4096 Sep 7 14:05 . drwxr-xr-x 9 root root 4096 Sep 6 15:21 .. -rwxr-xr-x 1 root apache 2464 Sep 7 14:05 smokeping.cgi [root <at> home cgi-bin]# /usr/bin [root <at> home bin]# ls -la | grep speedy -r-xr-xr-x 1 root apache 57977 Sep 6 13:08 speedy -r-xr-xr-x 1 root apache 109516 Sep 6 13:08 speedy_backend [root <at> home bin]# Smokeping.cgi contains the following: #!/usr/bin/speedy -w # -*-(Continue reading)perl-*- use lib qw "/usr/local/rrdtool-1.2.10/lib/perl/5.8.5"; <<-- Presumably the problem line ## I've also tried use lib qw
On Wed, Sep 07, 2005 at 04:02:08PM -0400, Ian Fraser wrote: > > When accessing http://<hostname>/cgi-bin/smokeping.cgi Apache returns > the following error > > ERROR: /var/www/cgi-bin/smokeping.cgi, line 3: table syntax error Hi, this looks like smokeping.cgi is trying to use itself as its configuration file. The path to the configuration file is specified inside smokeping.cgi on the 'Smokeping::cgi(<pathname>)' line. Make sure that points to the right place. HTH, -- -- Niko
Excellent that's what it was. I mistook the ::cgi to be the path to the .cgi script, not the config file. Thanks -----Original Message----- From: Niko Tyni [mailto:ntyni+smokeping-users <at> mappi.helsinki.fi] Sent: Wednesday, September 07, 2005 5:03 PM To: Fraser, Ian [CAR:W669:EXCH] Cc: smokeping-users <at> list.ee.ethz.ch Subject: Re: [smokeping-users] Problem smokeping.cgi, line 3: table syntax error On Wed, Sep 07, 2005 at 04:02:08PM -0400, Ian Fraser wrote: > > When accessing http://<hostname>/cgi-bin/smokeping.cgi Apache returns > the following error > > ERROR: /var/www/cgi-bin/smokeping.cgi, line 3: table syntax error Hi, this looks like smokeping.cgi is trying to use itself as its configuration file. The path to the configuration file is specified inside smokeping.cgi on the 'Smokeping::cgi(<pathname>)' line. Make sure that points to the right place. HTH,(Continue reading)
Hello list, I use Smokeping since 1 year now and I've to say that it's a very nice tool to get information about latency for all devices on the network. From my experience I've remarked that if we can have a top 10 list of devices generating most latency, then Smokeping will become better again and more complete. A top 10 list allow us to get quick view and information on devices having most latency. This is especially usefull when you monitor lot of devices (>=50) because passing through all graph to check for this information will take lot of time (as you can imagine). This is my 2 cent recomendation for future version or maybe some one already know how to do it with version 2.0.1. Gerhard,
Hi Gerhard, please note that smokeping development is mostly driven by Nikos and my spare time interests. So as such, your suggestion will certainly make it into the TODO list, but if you want to ensure implementation, we are most interested in people, putting their code or their money where their wishes point. contact me for an offer cheers tobi > Hello list, > > I use Smokeping since 1 year now and I've to say that it's a very nice > tool to get information about latency for all devices on the network. From > my experience I've remarked that if we can have a top 10 list of devices > generating most latency, then Smokeping will become better again and more > complete. > > A top 10 list allow us to get quick view and information on devices having > most latency. This is especially usefull when you monitor lot of devices > (>=50) because passing through all graph to check for this information > will take lot of time (as you can imagine). This is my 2 cent > recomendation for future version or maybe some one already know how to do > it with version 2.0.1. > > Gerhard, >(Continue reading)
On Thu, 2005-09-08 at 08:53 -0400, gmourani <at> privalodc.com wrote: > Hello list, > > I use Smokeping since 1 year now and I've to say that it's a very nice > tool to get information about latency for all devices on the network. From > my experience I've remarked that if we can have a top 10 list of devices > generating most latency, then Smokeping will become better again and more > complete. > > A top 10 list allow us to get quick view and information on devices having > most latency. This is especially usefull when you monitor lot of devices > (>=50) because passing through all graph to check for this information > will take lot of time (as you can imagine). This is my 2 cent > recomendation for future version or maybe some one already know how to do > it with version 2.0.1. > > Gerhard, > > -- > Unsubscribe mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=unsubscribe > Help mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=help > Archive http://lists.ee.ethz.ch/smokeping-users > WebAdmin http://lists.ee.ethz.ch/lsg2.cgi > I'm using not some kind of 'TOP10', but it is report with defined max values of packet loss or rtt, every device that overstep this limits is reported. It is possible to define several reports, with diferent limits.(Continue reading)
On Tue, Sep 06, 2005 at 03:40:44PM +0200, Leos Bitto wrote: > +someloss > type = loss > # in percent > pattern = >0%,*12*,>0%,*12*,>0% > comment = loss 3 times in a row > I would expect that for a host which is down (100% packet loss all the > time) this alert would send me an e-mail after three testing iterations. > That does not happen. I have to wait for 27 iterations until I get the > first e-mail. After that I get an additional e-mail every iteration, but > that's understandable. > > So what's wrong - the behaviour, or the documentation? Should the > documenation be corrected to have "The operator *X* will ignore exactly > X values..."? Hi, I'd say this is a bug, or at least a shortcut in the code :) Could you please try the attached patch (or the development snapshot version from http://people.ee.ethz.ch/~oetiker/webtools/smokeping/pub/trunk/ in a few hours) and tell me if it works for you? I haven't played with the alerts much before, and I may well have broken something... Cheers,(Continue reading)
RSS Feed22 | |
|---|---|
54 | |
10 | |
18 | |
27 | |
38 | |
24 | |
24 | |
42 | |
32 | |
121 | |
30 | |
33 | |
25 | |
28 | |
39 | |
28 | |
42 | |
42 | |
62 | |
29 | |
14 | |
39 | |
14 | |
21 | |
15 | |
16 | |
6 | |
21 | |
14 | |
29 | |
35 | |
26 | |
16 | |
16 | |
15 | |
27 | |
12 | |
52 | |
27 | |
59 | |
26 | |
55 | |
3 | |
21 | |
20 | |
20 | |
43 | |
32 | |
46 | |
55 | |
47 | |
54 | |
30 | |
38 | |
20 | |
42 | |
64 | |
79 | |
159 | |
62 | |
106 | |
104 | |
64 | |
44 | |
47 | |
52 | |
84 | |
78 | |
30 | |
12 | |
26 | |
16 | |
34 | |
26 | |
21 | |
46 | |
53 | |
23 | |
40 | |
30 | |
65 | |
61 | |
26 | |
30 | |
21 | |
36 | |
22 | |
22 | |
48 | |
19 | |
31 | |
34 | |
61 | |
60 | |
44 | |
57 | |
29 | |
32 | |
33 | |
40 | |
27 | |
36 | |
32 | |
32 | |
27 | |
34 | |
59 | |
48 | |
23 | |
23 | |
56 | |
49 | |
47 | |
32 | |
33 | |
43 | |
56 | |
24 | |
28 | |
39 | |
42 | |
36 | |
45 | |
14 | |
30 | |
13 | |
34 | |
51 | |
14 | |
30 | |
24 | |
23 | |
31 | |
30 | |
41 | |
72 | |
15 | |
3 | |
1 |
