headers
정현주 | 3 Jun 2009 10:45
Subject: smokeping doesn't read & make img file

smokeping doesn't read & make img file


 

 Hello~~

 

 I newly intalled Smokeping on  RHLinux .

 Debug shows no config errors. But Web page doesn't show smokeping graph.

 I guess smokeping cannot make and read img file where locate in imgcache directory.

 Imgche directory is owned by user "root" . can it be problem??

 Please advise me~ Thank you.

 
정현주 (JUNG HYUN JU)   대리
Samsung Networks   기술1팀
Tel: 070-7015-6889   Fax: 070-7016-0031
M.P: 016-244-5636   hj01.jung <at> samsung.com 
_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 0 comments |
headers
B. Cook | 3 Jun 2009 16:49
Favicon

500 Error all of a sudden..

Not that it should matter, but I have been running smokeping on this 
machine for over 45+ days on lighttpd and FreeBSD 7.2 (amd64).

Yesterday someone told me smokeping.cgi gave a 500 error, (they were 
right) and as far as I can see I can not find a problem.

if I run ./smokeping.cgi it does produce html output.

thinking for some odd reason there might be something up w/ lighttpd; i 
quickly compiled thttpd.  It to produces a white screen.

I just ran a rebuild of smokeping with portmaster, and same results.

(software versions)

smokeping-2.4.2_1   Latency logging and graphing system

This is perl, v5.10.0 built for amd64-freebsd

RRDtool 1.3.7  Copyright 1997-2009 by Tobias Oetiker <tobi <at> oetiker.ch>
                Compiled Jun  3 2009 07:34:00

lighttpd error log (fwiw)

2009-06-03 10:41:14: (server.c.1469) server stopped by UID = 0 PID = 0
2009-06-03 10:41:17: (log.c.97) server started
2009-06-03 10:41:20: (request.c.294) fd: 11 request-len: 452
GET /smokeping/ HTTP/1.1
Host: nms.domain.com
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; 
rv:1.9.0.12pre) Gecko/2009060209 Camino/2.0b3pre (like Firefox/3.0.12pre)
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: 
en-US,en;q=0.9,ja;q=0.8,fr;q=0.7,de;q=0.6,es;q=0.5,it;q=0.4,pt;q=0.3,pt-PT;q=0.2,nl;q=0.1
Accept-Encoding: gzip,deflate
Keep-Alive: 300
Connection: keep-alive

2009-06-03 10:41:20: (response.c.221) -- splitting Request-URI
2009-06-03 10:41:20: (response.c.222) Request-URI  :  /smokeping/
2009-06-03 10:41:20: (response.c.223) URI-scheme   :  https
2009-06-03 10:41:20: (response.c.224) URI-authority:  nms.domain.com
2009-06-03 10:41:20: (response.c.225) URI-path     :  /smokeping/
2009-06-03 10:41:20: (response.c.226) URI-query    :
2009-06-03 10:41:20: (response.c.276) -- sanatising URI
2009-06-03 10:41:20: (response.c.277) URI-path     :  /smokeping/
2009-06-03 10:41:20: (mod_access.c.135) -- mod_access_uri_handler called
2009-06-03 10:41:20: (response.c.391) -- before doc_root
2009-06-03 10:41:20: (response.c.392) Doc-Root     : /usr/local/www/data/
2009-06-03 10:41:20: (response.c.393) Rel-Path     : /smokeping/
2009-06-03 10:41:20: (response.c.394) Path         :
2009-06-03 10:41:20: (response.c.442) -- after doc_root
2009-06-03 10:41:20: (response.c.443) Doc-Root     : /usr/local/www/data/
2009-06-03 10:41:20: (response.c.444) Rel-Path     : /smokeping/
2009-06-03 10:41:20: (response.c.445) Path         : 
/usr/local/www/data/smokeping/
2009-06-03 10:41:20: (response.c.462) -- logical -> physical
2009-06-03 10:41:20: (response.c.463) Doc-Root     : /usr/local/www/data/
2009-06-03 10:41:20: (response.c.464) Rel-Path     : /smokeping/
2009-06-03 10:41:20: (response.c.465) Path         : 
/usr/local/smokeping/htdocs/
2009-06-03 10:41:20: (response.c.482) -- handling physical path
2009-06-03 10:41:20: (response.c.483) Path         : 
/usr/local/smokeping/htdocs/
2009-06-03 10:41:20: (response.c.490) -- file found
2009-06-03 10:41:20: (response.c.491) Path         : 
/usr/local/smokeping/htdocs/
2009-06-03 10:41:20: (response.c.640) -- handling subrequest
2009-06-03 10:41:20: (response.c.641) Path         : 
/usr/local/smokeping/htdocs/
2009-06-03 10:41:20: (mod_indexfile.c.151) -- handling the request as 
Indexfile
2009-06-03 10:41:20: (mod_indexfile.c.152) URI          : /smokeping/
2009-06-03 10:41:20: (mod_access.c.135) -- mod_access_uri_handler called
2009-06-03 10:41:20: (response.c.120) Response-Header:
HTTP/1.1 500 Internal Server Error
Content-Type: text/html
Content-Length: 369
Date: Wed, 03 Jun 2009 14:41:20 GMT
Server: lighttpd/1.4.22

(smokeping log..)

Jun  3 10:15:13 nms smokeping[7931]: Starting syslog logging
Jun  3 10:15:13 nms smokeping[28513]: Smokeping version 2.004002 
successfully launched.
Jun  3 10:15:13 nms smokeping[28513]: Entering multiprocess mode.
Jun  3 10:15:14 nms smokeping[28513]: Child process 95763 started for 
probe FPing.
Jun  3 10:15:14 nms smokeping[95763]: FPing: probing 57 targets with 
step 300 s and offset 148 s.
Jun  3 10:15:14 nms smokeping[28513]: Child process 61506 started for 
probe EchoPingSmtp.
Jun  3 10:15:14 nms smokeping[61506]: EchoPingSmtp: probing 6 targets 
with step 300 s and offset 150 s.
Jun  3 10:15:14 nms smokeping[28513]: All probe processes started 
successfully.

(first few lines of smokeping.cgi being executed)

root <at> nms [/usr/local/smokeping/htdocs]# 69 > ./smokeping.cgi
Expires: Wed, 03 Jun 2009 14:49:49 GMT
Date: Wed, 03 Jun 2009 14:44:49 GMT
Content-length: 4446
Content-Type: text/html; charset=iso-8859-15

<?xml version="1.0" encoding="iso-8859-15"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<HTML>
<HEAD>
<META HTTP-EQUIV="Cache-Control" content="no-cache">
<META HTTP-EQUIV="Pragma" CONTENT="no-cache">
<META HTTP-EQUIV="Refresh" CONTENT="300">
<link rel="shortcut icon" href="/smokeping/favicon.ico" type="image/x-icon">
<link rel="icon" href="/smokeping/favicon.ico" type="image/x-icon">
<TITLE>SmokePing Latency Page for Network Latency Grapher</TITLE>
<STYLE type="text/css">

root <at> nms [/usr/local/smokeping/htdocs]# 70 > pkg_info -W smokeping.cgi
/usr/local/smokeping/htdocs/smokeping.cgi was installed by package 
smokeping-2.4.2_1

Anyone have a clue where I could/should start?

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 0 comments |
headers
BREUVART Jean-Jacques | 10 Jun 2009 13:10

Problem this Smoketrace

Hi,
 I've installed Smoketrace like describ in the documentation and when I try it, I receive the following message in a popup windows from IE.

Line : 16844
Char : 9
Error '$5' as a Null value or is not an object.
Code : 0
URL: http://srvstats/smokeping/tr.html

Any ideas ?

Cordialement, greatings.
Jean-Jacques Breuvart

Ce message contient des informations confidentielles protegees par le secret professionnel. Au cas ou il ne vous serait pas destine, nous vous remercions de bien vouloir nous en aviser immediatement et de le supprimer. This e-mail is sent by a law firm and may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately. 
_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 0 comments |
headers
Eric Chatham | 10 Jun 2009 17:31
Favicon

Master/Slave configuration trouble

Hello Smokeping Users,

 

I am having some difficulty daemonizing the slave servers for Smokeping.  I created the secrets.conf file and the secret answer file on each of the slaves, but when I daemonize them, I get an HTTP 500 error (at least I believe it’s HTTP error.  I didn’t see it appear in the apache logs):

 

LAXVPN ATTEMPTING TO DAEMONIZE:

[root <at> laxvpn001 ~]# /opt/smokeping/bin/smokeping --master-url=http://server02.domain.net/smokeping/smokeping.cgi --shared-secret=/opt/smokeping/secret.txt --cache-dir=/var/tmp/

WARNING Master said 500 Can't connect to server02.domain.net:80 (connect: timeout)

ERROR: we did not get config form the master. Maybe we are not configured as a slave for any of the targets on the master ?

 

One thing I should point out.  The slaves were former slaves of “derelict” copy of smokeping that we no longer use.  That is why I called it “server02.domain.net.”  We no longer use “server01.domain.net.”  Here is my config file of the current master Smokeping:

 

CONFIG FILE:

 

*** Probes ***

 

+ FPing

 

binary = /usr/local/sbin/fping

 

++ FPing_default

 

++ FPing_I

 

offset = 0%

 

++ FPing_II

 

offset = 10%

 

++ FPing_III

 

offset = 20%

 

++ FPing_IV

 

offset = 30%

 

 

*** Slaves ***

 

#secrets=/home/oetiker/checkouts/smokeping/trunk/software/etc/smokeping_secrets.dist

#+boomer

#display_name=boomer

#color=0000ff

 

secrets=/opt/smokeping/etc/secrets.conf

 

+nycvpn001

display_name=NYC VPN

color=ff3300

 

#+slave2

#display_name=another

#color=00ff00

 

+laxvpn001

display_name=LAX VPN

color=00ff00

.

.

.

*** Targets ***

slaves=nycvpn001 laxvpn001

 

# probe = FPing

probe = FPing_default

.

.

.

 

Thank you for any assistance,

 

Eric Chatham

 

 


CONFIDENTIAL. This e-mail and any attached files are confidential and should be destroyed and/or returned if you are not the intended and proper recipient.
_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 503 comments |
headers
Eric Chatham | 10 Jun 2009 18:38
Favicon

Re: Master/Slave configuration trouble

> I am having some difficulty daemonizing the slave servers for Smokeping.  I created the secrets.conf file
and the secret answer file on each of > the slaves, but when I daemonize them, I get an HTTP 500 error (at least
I believe it's HTTP error.  I didn't see it appear in the apache logs):

I fixed part of this problem.  The original problem was an error in routing.  BUT, I'm now seeing a new error:

.::---::.
SLAVE SERVER:
[root <at> laxvpn001 ~]# /opt/smokeping/bin/smokeping
--master-url=http://dalnag02.broadvox.net/smokeping/smokeping.cgi
--shared-secret=/opt/smokeping/secret.txt --cache-dir=/var/tmp/
WARNING: Opening secrets file /opt/smokeping/etc/secrets.conf: Permission denied

ERROR: we did not get config form the master. Maybe we are not configured as a slave for any of the targets on
the master ?
'::---::'

When I try to give "read" permissions to the secrets file to group and everyone, I get an error when I try to
daemonize the master server.

.::---::.
MASTER SERVER:
[root <at> dalimnag02 ~]# chmod 700 /opt/smokeping/etc/secrets.conf
[root <at> dalimnag02 ~]# /opt/smokeping/bin/smokeping -restart
Note: logging to syslog as local0/info.
Daemonizing /opt/smokeping/bin/smokeping ...

[root <at> dalimnag02 ~]# chmod 722 /opt/smokeping/etc/secrets.conf
[root <at> dalimnag02 ~]# /opt/smokeping/bin/smokeping -restart
ERROR: /opt/smokeping/etc/config, line 137: File '/opt/smokeping/etc/secrets.conf' is
world-readable or writable, refusing it

[root <at> dalimnag02 ~]# chmod 711 /opt/smokeping/etc/secrets.conf
[root <at> dalimnag02 ~]# /opt/smokeping/bin/smokeping -restart
Note: logging to syslog as local0/info.
Daemonizing /opt/smokeping/bin/smokeping ...
[root <at> dalimnag02 ~]
'::---::'

CONFIDENTIAL.  This e-mail and any attached files are confidential and should be destroyed and/or
returned if you are not the intended and proper recipient.

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 502 comments |
headers
G.W. Haywood | 10 Jun 2009 18:50
Picon
Favicon

Re: Master/Slave configuration trouble

Hi there,

On Wed, 10 Jun 2009, Eric Chatham wrote:

> [root <at> dalimnag02 ~]# chmod 700 /opt/smokeping/etc/secrets.conf
> [root <at> dalimnag02 ~]# chmod 722 /opt/smokeping/etc/secrets.conf
> [root <at> dalimnag02 ~]# chmod 711 /opt/smokeping/etc/secrets.conf

You're going to need to do some reading about filesystem things.  You
gave the file various nonsensical permissions.  That last one for
example was owner read, write and execute, group and world execute
only (not read, not write).  You would normally use something like 640
(to put it another way, owner read+write, group read only, world none).
A configuration file almost never needs any execute permissions.

I'd probably make the file owned by the same user that's running the
daemon which needs to read the file, and make the permissions 600
(rw,none,none).

http://www.zzee.com/solutions/linux-permissions.shtml
Permalink | Reply | 11 comments |
headers
Eric Chatham | 10 Jun 2009 18:54
Favicon

Re: Master/Slave configuration trouble

On Wednesday, June 10, 2009 12:50, Ged wrote,

> You're going to need to do some reading about filesystem things.  You
> gave the file various nonsensical permissions.  That last one for
> example was owner read, write and execute, group and world execute
> only (not read, not write).  You would normally use something like 640
> (to put it another way, owner read+write, group read only, world none).
> A configuration file almost never needs any execute permissions.
>
> I'd probably make the file owned by the same user that's running the
> daemon which needs to read the file, and make the permissions 600
> (rw,none,none).
>
> http://www.zzee.com/solutions/linux-permissions.shtml

Hi Ged.  Would this work?

# chmod og=r /opt/smokeping/etc/secrets.conf

Would this allow the file to be read publically?

CONFIDENTIAL.  This e-mail and any attached files are confidential and should be destroyed and/or
returned if you are not the intended and proper recipient.

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 1 comment |
headers
Eric Chatham | 10 Jun 2009 19:03
Favicon

Re: Master/Slave configuration trouble

On Wednesday, June 10, 2009 12:50, Ged wrote,

> I'd probably make the file owned by the same user that's running the
> daemon which needs to read the file, and make the permissions 600
> (rw,none,none).

When I try the last one you mentioned, I still get permission denied on the slave servers.  Originally, I had
700 as the permissions when I first started trying this.  What user is trying to read the master from the
slave?  The smokeping process is run by root on both slaves and the master.  Does the apache user/group try to
read the master config from the slaves?

CONFIDENTIAL.  This e-mail and any attached files are confidential and should be destroyed and/or
returned if you are not the intended and proper recipient.

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 6 comments |
headers
Nathan Long | 10 Jun 2009 19:21
Picon

Re: Master/Slave configuration trouble

The command and error you posted doesn't match up.  I'm not sure if it's a typo or not.  The command lists a secrets.txt while the error shows secrets.conf.  Anyways.  The slaves do not read the master's config file, and the slaves do not have a config of their own.  When contact is made, the master will send the slave it's config.  

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 3 comments |
headers
Eric Chatham | 10 Jun 2009 19:30
Favicon

Re: Master/Slave configuration trouble

On Wednesday, June 10, 2009 13:22, Nathan Long wrote,

> The command and error you posted doesn't match up.  I'm not sure if it's a typo or not.  The command lists a
secrets.txt while the error shows
> secrets.conf.  Anyways.  The slaves do not read the master's config file, and the slaves do not have a config
of their own.  When contact is
> made, the master will send the slave it's config.

If I'm understanding this right the "--shared-secret" switch is the "answer" file for
/opt/smokeping/etc/secrets.conf file on the master server.  Is that correct?  Locally, I have
secrets.txt with the "answer" that is on the master server.

SECRET.TXT
--shared-secret=/opt/smokeping/secret.txt for laxvpn001

<password1>

SECRETS.CONF
/opt/smokeping/etc/secrets.conf

host1:<password1>
host2:<password1>
nycvpn001:<password1>
laxvpn001:<password1>

<password1> is the same all around.

CONFIDENTIAL.  This e-mail and any attached files are confidential and should be destroyed and/or
returned if you are not the intended and proper recipient.

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Permalink | Reply | 2 comments |

Gmane