I'm trying to get smokeping 2 working with the RADIUS probe - the daemon seems to handle the new conf syntax fine, but the cgi coughs up: ERROR: /etc/smokeping/smokeping.conf, line 127: unknown variable 'username' (and this repeats for every probe_conf variable - yes I removed + PROBE_CONF lines :) Thanks, -Keith
On Thu, Jun 02, 2005 at 09:43:44AM -0700, Keith Redfield wrote: > I'm trying to get smokeping 2 working with the RADIUS probe - the daemon seems to handle the new conf syntax fine, but the cgi coughs up: > > > ERROR: /etc/smokeping/smokeping.conf, line 127: unknown variable 'username' > (and this repeats for every probe_conf variable - yes I removed + PROBE_CONF lines :) Hi, sounds like the CGI might still be using the 1.x Smokeping.pm library. Check the 'use lib' lines in smokeping.cgi (and restart the speedyCGI process just in case). Another thing to check is the daemon's output; you can verify that it works with the '--debug-daemon' option. If that doesn't help, please send me your config file so I can test it. Cheers, -- -- Niko Tyni ntyni <at> iki.fi
I've installed smokeping (pkg_add) 1.31_1. The install process adds rrdtool-1.0.49 . I have perl-5.8.6_2 Freebsd 4.11 When I try to run smokeping error appears : Can't locate RRDs.pm in <at> INC ( <at> INC contains: /usr/local/smokeping/lib /usr/local/lib/perl5/site_perl/5.8.6/mach /usr/local/lib/perl5/site_perl/5.8.6 /usr/local/lib/perl5/site_perl/5.8.5 /usr/local/lib/perl5/site_perl/5.8.4 /usr/local/lib/perl5/site_perl/5.8.2 /usr/local/lib/perl5/site_perl/5.005 /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.6/BSDPAN /usr/local/lib/perl5/5.8.6/mach /usr/local/lib/perl5/5.8.6 .) at /usr/local/smokeping/lib/Smokeping.pm line 13. BEGIN failed--compilation aborted at /usr/local/smokeping/lib/Smokeping.pm line 13. Compilation failed in require at /usr/local/bin/smokeping line 6. BEGIN failed--compilation aborted at /usr/local/bin/smokeping line 6. I tried to link RRDs.pm from /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/RRDs.pm but then another error appears Can't locate loadable object for module RRDs in <at> INC ... What should I do to make it work ?(Continue reading)
On Fri, Jun 03, 2005 at 05:03:30PM +0200, Marcin Kmetko wrote: > I've installed smokeping (pkg_add) 1.31_1. > The install process adds rrdtool-1.0.49 . > > I have perl-5.8.6_2 > Freebsd 4.11 > > When I try to run smokeping error appears : > > Can't locate RRDs.pm in <at> INC ( <at> INC contains: /usr/local/smokeping/lib > I tried to link RRDs.pm from > /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/RRDs.pm > > but then another error appears > Can't locate loadable object for module RRDs in <at> INC ... Hi, I don't know much about FreeBSD, but the RRDs library installation is specific to the Perl version, and the problem is that they are mixed up on your system for some reason. The straightforward way to fix this would be to grab the rrdtool source, compile it against Perl 5.8.6 with a prefix like '/usr/local/rrdtool-1.0.49-perl-5.8.6' or something like that so that 'make install' doesn't overwrite the other rrdtool package. No promises, though :) You'll then have to point Smokeping to use the new library path, of course.(Continue reading)
On Wed, May 18, 2005 at 02:55:16PM -0700, Engle, Kurt wrote: > Is there any documentation regarding background colors on the graphs > produced by smokeping? Also, where can I find more information about > monitoring the uptime of a specific host or router? Hi, Smokeping isn't currently suitable for host uptime monitoring. The 'uptime' that it measures means how long a client with a dynamic IP address is able to keep its address. There's a description in the smokeping_config manual page under 'uptime_colors': "When monitoring a host with DYNAMIC addressing, SmokePing will keep track of how long the machine is able to keep the same IP address. This time is plotted as a color in the graphs background. SmokePing comes with a reasonable default setting, but you may choose to disagree. The table below lets you specify your own coloring" We do have some future plans of generalizing the uptime definition so that it could eg. be queried with SNMP or an external command. Kludge: if you really wanted to have this now, you could have a cronjob do its own stuff to notice a reboot and then update the timestamp of the .adr and .snmp files of the target in the Smokeping datadir. HTH -- -- Niko Tyni(Continue reading)
Hi, I use smokeping to monitor our DNS server service quality. I set up smokeping to query 4 domain names every 5 minutes, in which 20 queries are executed consequently. The configuration file looks alike: *** Database *** step = 300 pings = 20 + DNS binary = /usr/local/bin/dig forks = 40 timeout = 10 *** Targets *** probe = DNS ... I found that the result of monitoring result degrade apparentaly ( packet loss shown on the graph) after I add four testing items ( target with host option). The total number of target with host option is 45. What confused me is :(Continue reading)
Well, at the risk of self promoting, tSmoke (see the CONTRIB directory) does a pretty fair job of keeping my boss happy on measuring uptime for specific hosts as well as groups of hosts. The weekly summary shows availability (as opposed to uptime) over several durations in a nice HTML formatted mail. The downtime summary shows individual host downtime. One major drawback is that the round robin databases default consolidations cut off the five minute interval at 3 1/2 days so your accuracy for weekly measures suffers slightly. However, this evens out for monthly and quarterly measures since the consolidations relative to downtime tend to make shorter outages disappear and longer outages become multiples of half hour and hour measures. Showing host uptime vs. how long you had a dynamic IP address will be an interesting addition to Smokeping! Dan > -----Original Message----- > Smokeping isn't currently suitable for host uptime monitoring. The > 'uptime' that it measures means how long a client with a dynamic IP > address is able to keep its address. > > > We do have some future plans of generalizing the uptime definition so > that it could eg. be queried with SNMP or an external command. >(Continue reading)
On Mon, Jun 06, 2005 at 04:25:28AM -0400, Dan McGinn-Combs wrote: > Well, at the risk of self promoting, tSmoke (see the CONTRIB directory) > does a pretty fair job of keeping my boss happy on measuring uptime for > specific hosts as well as groups of hosts. > > The weekly summary shows availability (as opposed to uptime) over > several durations in a nice HTML formatted mail. The downtime summary > shows individual host downtime. Good point. I was only thinking of uptime in the sense of 'seconds since last reboot'. Uptime in the sense of 'availability', ie. the opposite of downtime, might well be closer what the original question was about. tSmoke is actually included in the 2.0rc5 tarball, since it needed a few modifications for 2.0 compatibility. > Showing host uptime vs. how long you had a dynamic IP address will be an > interesting addition to Smokeping! This should be implemented so that it's easy to add new 'uptime plugins'. An SNMP query for sysUptime and an ability to run an external command are the first things that come to mind, but perhaps there are others... like how long a DNS name has resolved to the same IP address, or a given URL has contained the same HTML code. Ideas welcome. Hm, as I think of these now, the latter seem probe-specific. Maybe a probe should be able to define its own uptime plugins in addition to the generic ones...(Continue reading)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
When using the new custom time resolution range (Smokeping 2.x rc), with
5x EchoPing every 60secs, I can view the complete 60 bars result over
the 1-hour period (see 1-hour-today.png, but when I zoom into the same
hour but 24hrs earlier (see 1-hour-yesterday.png) I've lost high def
results, and instead I'm seeing the 10min average (5 bars for the entire
hour).
I understand that this is a result of default smokeping RRD creation
specs and an expected way how RRD stores and averages data. In my
etc/config.dist, the RRD related parameters are as follows:
*** Database ***
step = 60 <-- every minute
pings = 5
# consfn mrhb steps total
AVERAGE 0.5 1 1008
AVERAGE 0.5 12 4320
MIN 0.5 12 4320
MAX 0.5 12 4320
AVERAGE 0.5 144 720
MAX 0.5 144 720
MIN 0.5 144 720
(Continue reading)
On Mon, Jun 06, 2005 at 10:30:29AM +0800, Joe Shen wrote: > I use smokeping to monitor our DNS server service > quality. I set up smokeping to query 4 domain names > every 5 minutes, in which 20 queries are executed > consequently. The configuration file looks alike: > > > *** Database *** > > step = 300 > pings = 20 > > + DNS > > binary = /usr/local/bin/dig > forks = 40 > timeout = 10 > I found that the result of monitoring result degrade > apparentaly ( packet loss shown on the graph) after I > add four testing items ( target with host option). The > total number of target with host option is 45. Hi, I'm afraid I don't quite understand. Maybe you're mixing up the 'host' variable (the DNS server to be probed) and the 'lookup' variable (the DNS name to be looked up)? If you are testing just a single server and 4 domain names, there should be just 4 targets (each having the same(Continue reading)
RSS Feed20 | |
|---|---|
22 | |
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 |
