[smokeping-users] empty graphs
gabster at lelutin.ca
Thu Jul 11 06:37:08 CEST 2019
On 2019-06-24 11:28 p.m., Gregory Guthrie wrote:
> Yes - I have the latest Debian release (9.9), and have full apt updates & upgrades.
> Yes; 2.6.11 is their most recent release, and I've been running on their ported releases all along.
yep indeed, the smokeping debian package lacked a bit of love for some
time, mostly due to the package manager being too busy, which is why I
started to do some work with them.
for what it's worth, the new debian release that just got out has 2.7.3
> Yes; RRd's are getting updated. I checked the file timestamps, and also the system logs show the updates, and I ran smokeping with a -debug flag and it showed the updates. (below)
[... and also in your previous email you showed that image files in
/var/cache/smokeping/www were up to date]
this is good, so your data is there at least, but it's not showing up.
so I think it might narrow things down to debugging your apache
configuration, which is usually pretty annoying :|
> Checking the Apache issue it notes; I get this:
> root at alpha:/var/lib/smokeping/World/MUM# apachectl -V | grep SERVER_CONFIG
> [Mon Jun 24 19:07:02.540073 2019] [alias:warn] [pid 46591] AH00671: The ScriptAlias directive in /etc/apache2/conf-enabled/smokeping.conf at line 3 will probably never match because it overlaps an earlier ScriptAlias.
> [Mon Jun 24 19:07:02.540635 2019] [alias:warn] [pid 46591] AH00671: The Alias directive in /etc/apache2/conf-enabled/smokeping.conf at line 4 will probably never match because it overlaps an earlier ScriptAlias.
> AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
> -D SERVER_CONFIG_FILE="apache2.conf"
those are just warnings so in theory they shouldn't be a problem.
however they seem to indicate that you're either loading the file twice
or you might have two configuration files being loaded. If it's the
latter, it might give a clue to what's happening.
the debian package deploys a file in /etc/smokeping/apache2.conf and
makes a symlink to it inside conf-enabled:
root at debian-9-amd64:~# ls -l /etc/apache2/conf-enabled/ | grep smokeping
lrwxrwxrwx 1 root root 32 Jul 11 04:28 smokeping.conf ->
If you've created another config file (e.g. that file in conf-available
is probably a manual creation), it might be symlinked inside
conf-enabled, too. use ls -l in /etc/apache2/conf-enabled to figure out
if you have two symlinks to smokeping configuration or maybe one symlink
and one plain file.
> root at alpha:/etc/apache2/conf-available# cat smokeping.conf
> ## GRG:
> ScriptAlias /smokeping /usr/lib/cgi-bin/smokeping.cgi
> ScriptAlias /smokeping/smokeping.cgi /usr/lib/cgi-bin/smokeping.cgi
> Alias /smokeping /usr/share/smokeping/www
> <Directory "/usr/share/smokeping/www">
> Options FollowSymLinks
> Require all granted
the weird thing is that if the content above is your second
configuration, it should work since it's almost identical to the one
deployed by the package. maybe there's even a third one?
lastly, on a new install there's a symlink from
/usr/share/smokeping/www/images to /var/cache/smokeping/images:
lrwxrwxrwx 1 root root 27 May 18 2016 /usr/share/smokeping/www/images
is this maybe not setup the same on your machine?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the smokeping-users