Bug#555728: smokeping: does not show graphs for the new configuration
Francesco Potortì
Version: 2.3.6-4
Severity: normal
I have a trivial smokeping configuration, with just some hosts checked
using fping. I set up a configuration for monitoring five hosts.
Everything is well and has built graphs for more than 10 hours.
Now I change the configuration, add a menu and two hosts. Apparently
smokeping reads the new configuration, because in the syslog it reports:
smokeping[27324]: Starting syslog logging
smokeping: Note: logging to syslog as local0/info.
smokeping: Daemonizing /usr/sbin/smokeping ...
smokeping[27328]: Smokeping version 2.003006 successfully launched.
smokeping[27328]: Not entering multiprocess mode for just a single probe.
smokeping[27328]: FPing: probing 7 targets with step 300 s and offset 82 s.
But the web page keeps showing the same five hosts as before, and the
same single menu as before. I have no speedy_backend processes
running, and I tried this even after restarting both Apache2 and Smokeping.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-proposed-updates')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages smokeping depends on:
ii adduser 3.111 add and remove users and groups
ii debianutils 3.2.1 Miscellaneous utilities specific t
ii fping 2.4b2-to-ipv6-16 sends ICMP ECHO_REQUEST packets to
ii libconfig-grammar-perl 1.10-1 grammar-based user-friendly config
ii libdigest-hmac-perl 1.01-7 create standard message integrity
ii libjs-cropper 1.2.0-2 JavaScript image cropper UI
ii libjs-prototype 1.6.1-1 JavaScript Framework for dynamic w
ii libjs-scriptaculous 1.8.3-1 JavaScript library for dynamic web
ii librrds-perl 1.3.8-1 Time-series data storage and displ
ii libsnmp-session-perl 1.13-1 Perl support for accessing SNMP-aw
ii liburi-perl 1.37+dfsg-1 Manipulates and accesses URI strin
ii libwww-perl 5.833-1 Perl HTTP/WWW client/server librar
ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip
ii perl 5.10.1-5 Larry Wall's Practical Extraction
ii speedy-cgi-perl 2.22-11 speed up perl scripts by making th
ii ucf 3.0024 Update Configuration File: preserv
Versions of packages smokeping recommends:
ii apache2 2.2.14-1 Apache HTTP Server metapackage
ii apache2-mpm-prefork [h 2.2.14-1 Apache HTTP Server - traditional n
ii dnsutils 1:9.6.1.dfsg.P1-3 Clients provided with BIND
ii echoping 6.0.2-3 A small test tool for TCP servers
ii libsocket6-perl 0.20-1 Perl extensions for IPv6
Versions of packages smokeping suggests:
ii curl 7.19.5-1.1 Get a file from an HTTP, HTTPS or
ii exim4 4.69-11 metapackage to ease Exim MTA (v4)
ii exim4-daemon-light [mail-tran 4.69-11+b1 lightweight Exim MTA (v4) daemon
pn libauthen-radius-perl <none> (no description available)
ii libio-socket-ssl-perl 1.31-1 Perl module implementing object or
ii libnet-dns-perl 0.65-1 Perform DNS queries from a Perl sc
pn libnet-ldap-perl <none> (no description available)
pn libnet-telnet-perl <none> (no description available)
ii openssh-client 1:5.1p1-8 secure shell client, an rlogin/rsh
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Francesco Potortì
my part.
On the other hand, I am subject to the speedy_backend bug: it is
perfectly reproducible and manifests itself with the trivial
configuration I sent in the bug report, so if this can be of any help to
tray and correct it, just ask.
Niko Tyni
found 555728 2.3.6-4
thanks
On Thu, Nov 12, 2009 at 12:45:01AM +0100, Francesco Potortì wrote:
> >Hm, thanks but that's not necessary. I see the move to the
> >split configuration files in /etc/smokeping/config.d already
> >deprecated the README.Debian note: the persistent CGI just checks if
> >/etc/smokeping/config has been modified but not the separate files
> >@included from it.
>
> Well, I'd say this is a bug...
Fair enough. I doubt it will be fixed though, I think getting automatic
reloading is not worth the effort (particularly because the original
problem described #397609 is so hard to reproduce.)
> >So having to kill speedy_backends is now expected behaviour and not a bug.
> >I'll update the init.d message and README.Debian.
>
> In fact, /etc/init.d/smokeping could do it itself. Here is what I do to
> reload the smokeping configuration:
>
> /etc/init.d/smokeping reload && killall speedy_backend
Yeah, combined with some more checks for just those speedy_backends
related to smokeping would make this an adequate solution.
I'm reopening this bug to track this.
Thanks for caring,
--
Niko Tyni nt...@debian.org