If the files are there, doesn't that mean Smokeping is working?
Have you checked your Apache logs (or whatever http daemon you run)?
Jim
On Fri, Oct 31, 2014 at 09:51:40AM -0500, David Thompson wrote:
Just installed a fresh instance of Smokeping and none of my images are
loading for some
in the Apache log at least none that I
can see. It's just a 404 for some reason.
David Thompson
Network Services Support Technician
(O) 858.357.8794
(F) 858-225-1882
(E) dthomp...@esi-estech.com
(W)??www.esi-estech.com
-Original Message-
From: Jim Long [mailto:smokep...@museum.rain.com
The Smokeping user has to be able to WRITE to the in order
for updates to work. The Apache group needs to be able to
READ the file in order to display the image to a web browser.
chown smokeping:www-data foo-bar.rrd
is perhaps what you want.
Jim
On Mon, Apr 15, 2013 at 02:37:03PM +0200,
On Mon, Apr 15, 2013 at 06:54:52AM -0700, Jim Long wrote:
The Smokeping user has to be able to WRITE to the in order
Boss! The file, the file!
for updates to work. The Apache group needs to be able to
READ the file in order to display the image to a web browser.
chown smokeping:www-data
-
From: Jim Long [mailto:smokep...@museum.rain.com]
Sent: Wednesday, January 23, 2013 4:12 PM
To: Abello, Vinny
Cc: smokeping-users@lists.oetiker.ch
Subject: Re: [smokeping-users] ssh-keyscan error starting from boot only
On Wed, Jan 23, 2013 at 07:17:09PM +, vinny_abe...@dell.com wrote
On Wed, Feb 06, 2013 at 02:53:15AM +0100, Kris De Rocker wrote:
Dear,
I've followed a nice (and working!) how-to to install smokeping on a
CentOS system
(http://www.wedebugyou.com/2012/11/how-to-install-and-configure-smokeping-on-centos-6/)
At this moment, the smokeping URL is like
On Sun, Oct 21, 2012 at 04:53:58PM -0400, staticsafe wrote:
I have a Smokeping 2.6.7 install running over at
smokeping.asininetech.com/smokeping.cgi.
I am getting errors such as this:
ERROR: Could not save png to
'/usr/local/smokeping/htdocs/img/IRC/amy_mini.png'
Here it is:
that script as a
'wrapper' around the sudo call:
#!/bin/sh
sudo /home/pi/adsl_alert.py
Hope this helps,
Jim
xxx
On 27 July 2012 01:25, Jim Long smokep...@museum.rain.com wrote:
On Fri, Jul 27, 2012 at 12:42:23AM +0100, Andrew Pattison wrote:
I cannot su to the smokeping user for some
On Thu, Jul 26, 2012 at 11:56:41PM +0100, Andrew Pattison wrote:
I tried that but it still doesn't work. The alert is triggered as it is
logged in /var/messages but either smokeping is not calling the script or
the call is failing. Any ideas?
Andrew.
Once again, please pardon the basics.
run is
the alert script.
Jim
Thanks
Andrew.
On 27 July 2012 00:13, Jim Long smokep...@museum.rain.com wrote:
On Thu, Jul 26, 2012 at 11:56:41PM +0100, Andrew Pattison wrote:
I tried that but it still doesn't work. The alert is triggered as it is
logged in /var/messages
On Fri, Jul 06, 2012 at 11:38:46PM +, vinny_abe...@dell.com wrote:
Hi,
I'm having trouble upgrading Smokeping on FreeBSD from ports. Currently I'm
running Smokeping 2.4.2, specifically port smokeping-2.4.2_6 and am trying to
build smokeping-2.6.7.
I keep getting this error:
===
On Sun, Apr 15, 2012 at 01:27:47PM +0600, Smokeping slt wrote:
I think Apache cannot excute the .fcgi file properly.
But yet you have not provided any output from the Apache log
files. That's the first place to look when you suspect that
things work okay when you run them manually, but not
My FreeBSD system finds the source code at:
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/fping-2.4b2_to-ipv6.tar.gz
That should be the original tarball.
Jim
On Tue, Jan 31, 2012 at 10:10:37AM -0500, K. M. Peterson wrote:
Hi all,
I've just set up smokeping for the first time in quite a
:46, Jim Long wrote:
On Tue, Sep 06, 2011 at 10:30:29PM +0200, Ton Muller wrote:
rrd is building DB files.
but smoke isnt making its stats in htdocs..
I'm still stuck on the chroot option in Apache.
In my smokeping.cgi, on line 9 there is an explicit reference to
the smokeping
On Wed, Sep 07, 2011 at 06:06:53PM +0200, Ton Muller wrote:
On 6-9-2011 22:51, Jim Long wrote:
Once you get the big issues sorted, I strongly suggest you iron
out the logging for smokeping. In FreeBSD, the default log file
is /var/log/smokeping.log. I don't know whether OpenBSD has
more a pf guy,hehe..
On 6-9-2011 22:13, Jim Long wrote:
Just for good measure, I'd suggest stopping smokeping, and then
checking with ps to ensure that all smokeping processes have
terminated. Once all smokeping processes have terminated,
restart smokeping, to ensure
.
http://192.168.0.240/smokeping/test.html
says hello world.
Regards.
Ton.
... Feel the power of my shell !!
On 6-9-2011 20:31, Jim Long wrote:
Hi, Ton. I didn't notice that you were running BSD. I run smokeping
on FreeBSD, so perhaps I'll jump in here.
Gregory's line
On Tue, Sep 06, 2011 at 10:39:05PM +0200, Ton Muller wrote:
On 6-9-2011 22:13, Jim Long wrote:
SUBJECT TO CORRECTION, PLEASE:
It is my understanding that the graphic files and html are
created by the smokeping daemon, which is not subject to the
chrooted Apache configuration, because
Sounds like you're running on Linux, and I'm FreeBSD, but here is
a generic reply that I hope will be useful.
Figure out what GROUP the smokeping daemon is running as, and:
chgrp $GROUP /opt/smokeping/etc/secrets.conf
Group-read permissions for group root don't do any good if the
smokeping
/clipped4.png
http://www.umpquanet.com/james/clipped5.png
Please advise how I can fix or clarify this problem, and accept my
apologies if I have not provided sufficient information to diagnose.
Jim Long
___
smokeping-users mailing list
smokeping-users
20 matches
Mail list logo
