[smokeping-users] debug of smokeping... and a suggestion.
murf at parsetree.com
Sat Jan 31 05:19:31 CET 2015
I've just spent two days playing with smokeping, getting myself
acquainted. And I thought I'd be helpful to those who come after me,
and share a few problems and solutions.
a. I spent over 4 hours trying to get the website to work. In the end,
I got a bunch of "500" result codes from the fcgid stuff in httpd,
and a bunch of broken links. So, I basically erased it all,
and started almost from scratch, and followed the instructions
very carefully at:
I also read some emails from here warning that following such
cookbooks can lead to disaster, but happily, for my situation, with
worked great. I was mostly up and running in less than an hour.
b. If you get this in your http error_log:
[Fri Jan 30 15:55:09 2015] [warn] [client 18.104.22.168] mod_fcgid: stderr:
[Fri Jan 30 15:55:09 2015] smokeping_cgi [client 22.214.171.124]: Can't call
" on an undefined value at /opt/smokeping/bin/../lib/Smokeping.pm line
[Fri Jan 30 15:55:15 2015] [warn] mod_fcgid: cleanup zombie process 19016
... You might seriously consider that you are making a reference to a
in a Multi-host graph. Make sure you spell your host names right!
c. If you see this:
[Fri Jan 30 10:27:25 2015] [error] [client 126.96.36.199] Premature end of
script headers: cropper.js, referer:
[Fri Jan 30 10:27:26 2015] [warn] [client 188.8.131.52] (104)Connection
reset by peer: mod_fcgid: error reading data from FastCGI server, referer:
... Again, make sure you all your refs will match a def!
And, so, having spent sooo much time on such trivial issues, I have two
implementation, I believe, might spare more than a few users some large
1. Please, add some code to do a quick check of every ref, to make sure the
it matches a def, and if not, returns the line number, and the ref
I ran with the --check option, and nothing popped up.
2. Some scripts for each major OS, to install the web interface, would be
very helpful. I fully notice and appreciate the fact that the web code
daemon code are irrevocably intermingled.... but I also see that they
so tied together, that it is a mistake to separate the two and let the
fend for themselves when it comes to installing the goodies in apache.
The "optimal" (or something as close as practical) way
to do the integration between the two needs some attention.
I'd help with either, but... no spare time right now. Others are closer to
and able to implement these kinds of things faster/better than I, lowly
newbie that I am.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the smokeping-users