headers
benedict | 1 Dec 2004 09:35
Picon
Favicon

problem with smokeping CGI


I am new to smoke and have recently installed it

OS linux Red Hat 8

smokeping 1.31
apache version httpd-2.0.40-8

i have installed and setup smokeping with the other required software but
now when I try to use the browser and try to open the smokeping.cgi

it says

Access forbiden

you dont have permission to acces the requested object it is either read
protected or not readable by the server

my imgcache directory is /var/www/html/smokecache and the permissions are
defult as i have created this directory as user root.

appreciate if you could help me

any other info required kindly let me know

thanks n regards

--
Unsubscribe mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=unsubscribe
Help        mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=help
(Continue reading)

Permalink | Reply | 0 comments |
headers
Keith Redfield | 2 Dec 2004 00:53

Re: problem with smokeping CGI

"Linux FAQ #1 : It's always permissions".

This sounds like an apache config problem, not a problem with smokeping. Unless you are running apache as
suid root (a bad idea I hear), it might not be able to read all the data files - so find out what user apache is
runnng under (usually 'apache') and chown/chgrp all the files to that uid. A simple test would be to create
a small perl script like:
-------------
#!/usr/bin/perl <---or wherever your perl is

print "Content-type text/html\n\n";
print "Hello World";
-------------
chmod 774 it and call it 'test.cgi' and put it in the same dir as smokeping.cgi. If it works, you know apache
can handle CGI's correctly, and so the permissions issue is the more likely candidate. 

Cheers,

-Keith
________________________________

From: smokeping-users-bounce <at> list.ee.ethz.ch on behalf of benedict <at> kmun.gov.kw
Sent: Wed 12/1/2004 12:35 AM
To: smokeping-users <at> list.ee.ethz.ch
Subject: [smokeping-users] problem with smokeping CGI

I am new to smoke and have recently installed it

OS linux Red Hat 8

smokeping 1.31
(Continue reading)

Permalink | Reply | 0 comments |
headers
Keith Redfield | 2 Dec 2004 01:07

RRD data and 'step' config parameter

I am trying to understand how the RRD files generated by smokeping correspond to the polling interval. I
simulated an outage by re-booting a monitored box and wanted to look at the raw data to see how it appeared
there (smokeping.cgi shows a few ping losses, but I wanted to see timestamps). Step and pings are set to 90
and 20 in smokeping.conf.

I dumped the data using 'rrdtool dump' and it appears to only be stored as 5-min intervals [corresponding to
the graph]. There are 20 data elements which appear to be latency readings for the 20 pings. However, I have
'step' configured for 90 seconds, not 300, so I would have expected to see 90-sec intervals (20
pings/interval) in the datafile. 

Is rrdtool/smokeping only storing selected readings regardless of the step interval? Or is the problem
because I started this RRD file on 300sec orginally and did a 'smokeping --restart' when I later changed
step to 90? (I would consider that a bug). Or am I just completely clueless as to what the raw data is actually showing?

I am using the CiscoRTTMonEchoICMP probe for this.

TIA

-Keith
--
Unsubscribe mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=unsubscribe
Help        mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/smokeping-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
Permalink | Reply | 1 comment |
headers
Keith Redfield | 2 Dec 2004 05:13

Re: RRD data and 'step' config parameter

Further to this: created a new host entry in the same config file, ran it for a bit and the dump on that file
shows 90-sec intervals. So I think indeed this represents an undocumented feature ;)
-Keith

-----Original Message-----
From: smokeping-users-bounce <at> list.ee.ethz.ch on behalf of Keith Redfield
Sent: Wed 12/1/2004 4:07 PM
To: smokeping-users <at> list.ee.ethz.ch
Subject: [smokeping-users] RRD data and 'step' config parameter

I am trying to understand how the RRD files generated by smokeping correspond to the polling interval. I
simulated an outage by re-booting a monitored box and wanted to look at the raw data to see how it appeared
there (smokeping.cgi shows a few ping losses, but I wanted to see timestamps). Step and pings are set to 90
and 20 in smokeping.conf.

I dumped the data using 'rrdtool dump' and it appears to only be stored as 5-min intervals [corresponding to
the graph]. There are 20 data elements which appear to be latency readings for the 20 pings. However, I have
'step' configured for 90 seconds, not 300, so I would have expected to see 90-sec intervals (20
pings/interval) in the datafile. 

Is rrdtool/smokeping only storing selected readings regardless of the step interval? Or is the problem
because I started this RRD file on 300sec orginally and did a 'smokeping --restart' when I later changed
step to 90? (I would consider that a bug). Or am I just completely clueless as to what the raw data is actually showing?

I am using the CiscoRTTMonEchoICMP probe for this.

TIA

-Keith
--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tobias Oetiker | 2 Dec 2004 08:06
Picon
Picon
Favicon

Re: RRD data and 'step' config parameter

Yesterday Keith Redfield wrote:

> Is rrdtool/smokeping only storing selected readings regardless of
> the step interval? Or is the problem because I started this RRD
> file on 300sec orginally and did a 'smokeping --restart' when I
> later changed step to 90? (I would consider that a bug). Or am I
> just completely clueless as to what the raw data is actually
> showing?

this exactly is the problem ... smokeping does not somehow
magically alter the resolution of the rrdfiles later on .. it might
generate some warning if it finds an rrdfile that does not match
though ... patches welcome ...

cheers
tobi

--

-- 
  ______    __   _
/_  __/_  / /  (_) Oetiker  <at>  ISG.EE, ETL F24.2, ETH, CH-8092 Zurich
  / // _ \/ _ \/ /  System Manager, Time Lord, Coder, Designer, Coach
/_/ \.__/_.__/_/   http://people.ee.ethz.ch/oetiker +41(0)44-632-5286

--
Unsubscribe mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=unsubscribe
Help        mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/smokeping-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
(Continue reading)

Permalink | Reply | 0 comments |
headers
Keith Redfield | 2 Dec 2004 08:23

Re: RRD data and 'step' config parameter

Well, it was probably covered in this comment:

Note that it is not possible to edit existing RRDs
by changeing the entries in the cfg file.

but I didn't fully grasp the consequences. I'm happy to contribute an FAQ, but my perl code is renowned for
it's resemblence to BASIC.

Cheers,

-Keith
________________________________

From: Tobias Oetiker [mailto:oetiker <at> ee.ethz.ch]
Sent: Wed 12/1/2004 11:06 PM
To: Keith Redfield
Cc: smokeping-users <at> list.ee.ethz.ch
Subject: Re: [smokeping-users] RRD data and 'step' config parameter

Yesterday Keith Redfield wrote:

> Is rrdtool/smokeping only storing selected readings regardless of
> the step interval? Or is the problem because I started this RRD
> file on 300sec orginally and did a 'smokeping --restart' when I
> later changed step to 90? (I would consider that a bug). Or am I
> just completely clueless as to what the raw data is actually
> showing?

this exactly is the problem ... smokeping does not somehow
magically alter the resolution of the rrdfiles later on .. it might
(Continue reading)

Permalink | Reply | 1 comment |
headers
Nic le Roux | 2 Dec 2004 09:11

Time zone incorrect

Good Morning all.

Have mandrake 9.2 setup with smokeping 1.31
I'm in time zone GMT +2 and clock is not set to GMT.

However the graphs are showing what appears to be GMT time.

Is there a config setting for this somewhere ?

Thanks and Regards
Nic

--
Unsubscribe mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=unsubscribe
Help        mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/smokeping-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
Permalink | Reply | 0 comments |
headers
Dan McGinn-Combs | 9 Dec 2004 15:56

ISG::ParseConfig - Parsing a Table

Sorry if this is a bit off-topic! I'm not sure where else to ask and
since Smokeping uses ParseConfig, I thought I'd start here.

I was perusing my Smokeping config file and matching it up against the
parser in Smokeping.pm when I noticed that there was apparently only one
array called _table field permitted by the parser per section. Is this
true?

Thanks,

Dan

---

Dan McGinn-Combs

--
Unsubscribe mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=unsubscribe
Help        mailto:smokeping-users-request <at> list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/smokeping-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
Permalink | Reply | 0 comments |
headers
Tobias Oetiker | 9 Dec 2004 23:33
Picon
Picon
Favicon

Re: ISG::ParseConfig - Parsing a Table

Today Dan McGinn-Combs wrote:

> Sorry if this is a bit off-topic! I'm not sure where else to ask and
> since Smokeping uses ParseConfig, I thought I'd start here.
> 
> 
> I was perusing my Smokeping config file and matching it up against the
> parser in Smokeping.pm when I noticed that there was apparently only one
> array called _table field permitted by the parser per section. Is this
> true?

Hi Dan,

yes this is true ... how should the parser distinguisch between
different tables ?

*** section ***

a b c
1 2 3

g k
1 1

how about this ?

*** another ***
+table1

l n p
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dan McGinn-Combs | 10 Dec 2004 21:23

Re: ISG::ParseConfig - Parsing a Table

Honest! I wasn't trying to make trouble! :)
I just wanted to make sure my understanding was correct. I reckon it
isn't a limitation as long as the application knows to access _table
rather than a hash.

The reason I was curious is that the DESCRIPTION at
http://isg.ee.ethz.ch/tools/realmen/down/data/ParseConfig.html shows
what looks like a section of hosts where the pointer to the array has
the same names as the contents of first column. But I may not have
understood relationship between the input and the output.

Dan

-----Original Message-----
Today Dan McGinn-Combs wrote:

> I noticed that there was apparently only one
> array called _table field permitted by the parser per section. Is this
> true?

yes this is true ... how should the parser distinguisch between
different tables ?

*** section ***

a b c
1 2 3

g k
1 1
(Continue reading)

Permalink | Reply | 1 comment |

Gmane