rick sunix | 1 Jul 2008 13:28
Picon

problem with smoketrace

Hi ,

I was compiling smokeping for my linux server, that i got to work. but i was trying to setup the smoketrace available in smokeping.
i follow the instructions for the smoketrace installation ,but at the end i ran into problem with JSON-RPC protocol setup .
I am getting "Your HTTP Client is not using the JSON-RPC protocol" whenever i try to run tr.cgi.
Can anybody help with this .
Is there anything else is additionally required ( perl module , java , ajax , php) for smoketrace to get it to work.


Ricky

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Tobias Oetiker | 1 Jul 2008 13:36
Picon
Gravatar

Re: problem with smoketrace

Hi Rick,

this error is actually a good thing. tr.cgi gets called by the
javascript which is loaded in the tr.html file ... so you must open
tr.html in your browser

cheers
tobi

Today rick sunix wrote:

> Hi ,
>
> I was compiling smokeping for my linux server, that i got to work. but i was
> trying to setup the smoketrace available in smokeping.
> i follow the instructions for the smoketrace installation ,but at the end i
> ran into problem with JSON-RPC protocol setup .
> I am getting "Your HTTP Client is not using the JSON-RPC protocol" whenever
> i try to run tr.cgi.
> Can anybody help with this .
> Is there anything else is additionally required ( perl module , java , ajax
> , php) for smoketrace to get it to work.
>
>
> Ricky
>

--

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi <at> oetiker.ch ++41 62 775 9902 / sb: -9900

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users

Schneider, Andreas | 1 Jul 2008 14:58
Favicon

Re: EchoPingHttp

Hello,
im not very familiar with the echoping stuff. But i found out that i use version 6.0.2 on Debian 4.0
I tried with the -R option but nothing changed. Still got "HTTP/1.1 401 Unauthorized".
Do i have to change the echoping.pm ? But what should i change?
 
Kind regards,
Andreas

 
Von: smokeping-users-bounces <at> lists.oetiker.ch im Auftrag von G.W. Haywood
Gesendet: Sa 28.06.2008 12:30
An: Schneider, Andreas
Cc: smokeping-users <at> lists.oetiker.ch
Betreff: Re: [smokeping-users] EchoPingHttp

Hi there,

On Fri, 27 Jun 2008, Schneider, Andreas wrote:

> i want to monitor a SharePoint Website with EchoPingHttp. But i always get 100% packet loss.
> When i run echoping from commandline with the -v switch i got message ...401 Unauthorized.
> OK, the SharePoint is a local Intranet and works together with ActiveDirectory authentication.
> So, is there a way to send authorization, so that echopinghttp is not refused?

If I were doing this I wouldn't want to send authorization, because it
might add a significant amount of unnecessary overhead.  Instead, I'd
request a URL which would cause a 301 response from the server.  I'd
use EchoPingHttp's 'accept_redirects' option so that a 301 is treated
as a normal respo nse, not an error.

The accept_redirects option gives the '-R' switch to echoping, so you
need a recent version of echoping which will understand it.  The version
that I use on Debi pm to
prevent the switch from being used.

--

73,
Ged.

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
G.W. Haywood | 1 Jul 2008 16:06
Picon
Favicon

Re: EchoPingHttp

Hi there,

On Tue, 1 Jul 2008, Schneider, Andreas wrote:

> im not very familiar with the echoping stuff. But i found out that i
> use version 6.0.2 on Debian 4.0

Debian 4.0 stable is known as 'Etch', which is what I'm using on my desktop.
I have version 5.2.0 of echoping on that system, not version 6.

> I tried with the -R option but nothing changed. Still got "HTTP/1.1 401 Unauthorized".

I'm not sure that you understood my suggestion.  My suggestion was to
ask for a different URL, one which would give you a 301 response, not
a 4xx response.

You could try

man echoping

to see if the -R flag is supported.

Here is the output of a couple of echoping commands on my desktop machine:

----------------------------------------------------------------------
tornado:~$ >>> echoping -R -v -h /smokeping oss.oetiker.ch
echoping: invalid option -- R
[...]
tornado:~$ >>> echoping -v -h /smokeping oss.oetiker.ch

This is echoping, version 5.2.0.

Trying to connect to internet address 213.144.138.195 80 to transmit 99 bytes...
Trying to send 256 bytes to internet address 213.144.138.195...
Connected...
TCP Latency: 0.054292 seconds
Sent (99 bytes)...
Application Latency: 0.066763 seconds
HTTP error "HTTP/1.1 301 Moved Permanently
"
----------------------------------------------------------------------

> Do i have to change the echoping.pm ? But what should i change?

Don't change anything until you understand what you're doing.

Lars Hecking | 2 Jul 2008 11:41
Picon

Slave loss computation broken?


 Take a look at the attached graph from a smokeping slave. Although there
 clearly are more than two dozen periods of packet loss, the legend says
 0.00% for avg/max/min/now packet loss. I've not seen this for any master
 graphs.

 Out of 30 slave graphs, only 8 or so show the problem, but the probe in
 question is always AnotherDNS with a record type of MX. Not all probes
 of this type exhibit the problem. E.g. for one particular probe:

 - overview/3h/30h graph wrong
 - 10day/400day graph correct (non-zero loss)

 All graphs based on a plain DNS probe seem to be correct.

 Config:

+ AnotherDNS

offset = 50%
step = 300
pings = 5

+++ FOO_DNS_MX

probe = AnotherDNS
menu = foo_dns_mx
title = DNS MX on FOO
host = 1.2.3.4
lookup = bar.company.com
recordtype = MX
slaves = host.sub.company.com

 smokeping 2.4.1
 rrdtool 1.2.27 (1.3 doesn't build on RHEL3)

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Jan Rockstedt | 2 Jul 2008 14:36
Picon

Segmentation fault

 
Hi all,
 
After runing portupgrade -a we have problem to start smokeping.
Segmentation fault
 
/usr/local/smokeping/htdocs/smokeping.cgi
speedy[62572]: Cannot spawn backend process
 
FreeBSD freebsd 7.0-STABLE FreeBSD 7.0-STABLE #4: Wed Jul  2 12:06:59 CEST 2008     root <at> freebsd:/usr/obj/usr/src/sys/GENERIC  i386
Any sugestion?
 
Jan Rockstedt
_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Tobias Oetiker | 2 Jul 2008 15:24
Picon
Gravatar

Re: Slave loss computation broken?

Lars,

note that the orange stripes are not packet loss, but 'NO DATA' it
means that smokeping has not been running at these times or it has
not completed the polling round in this periode. Check the logfile.

cheers
tobi

Today Lars Hecking wrote:

>
>  Take a look at the attached graph from a smokeping slave. Although there
>  clearly are more than two dozen periods of packet loss, the legend says
>  0.00% for avg/max/min/now packet loss. I've not seen this for any master
>  graphs.
>
>  Out of 30 slave graphs, only 8 or so show the problem, but the probe in
>  question is always AnotherDNS with a record type of MX. Not all probes
>  of this type exhibit the problem. E.g. for one particular probe:
>
>  - overview/3h/30h graph wrong
>  - 10day/400day graph correct (non-zero loss)
>
>  All graphs based on a plain DNS probe seem to be correct.
>
>  Config:
>
> + AnotherDNS
>
> offset = 50%
> step = 300
> pings = 5
>
> +++ FOO_DNS_MX
>
> probe = AnotherDNS
> menu = foo_dns_mx
> title = DNS MX on FOO
> host = 1.2.3.4
> lookup = bar.company.com
> recordtype = MX
> slaves = host.sub.company.com
>
>  smokeping 2.4.1
>  rrdtool 1.2.27 (1.3 doesn't build on RHEL3)
>
>

--

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi <at> oetiker.ch ++41 62 775 9902 / sb: -9900

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users

Lars Hecking | 2 Jul 2008 16:09
Picon

Re: Slave loss computation broken?

Tobias Oetiker writes:
> Lars,
> 
> note that the orange stripes are not packet loss, but 'NO DATA' it
> means that smokeping has not been running at these times or it has
> not completed the polling round in this periode. Check the logfile.

 I actually thought of that later ...

 I will revisit this issue once the slave instance has been running
 for a longer period of time. Nothing in the logs, and I am pretty
 sure that both master and slave instances were running continuously
 for at least the overnight 'NO DATA' periods. The network between
 the two may have a few quirks ...

 Thanks :)

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users

Tobias Oetiker | 2 Jul 2008 16:20
Picon
Gravatar

Re: Slave loss computation broken?

Hi Lars,

Today Lars Hecking wrote:

> Tobias Oetiker writes:
> > Lars,
> >
> > note that the orange stripes are not packet loss, but 'NO DATA' it
> > means that smokeping has not been running at these times or it has
> > not completed the polling round in this periode. Check the logfile.
>
>  I actually thought of that later ...
>
>  I will revisit this issue once the slave instance has been running
>  for a longer period of time. Nothing in the logs, and I am pretty
>  sure that both master and slave instances were running continuously
>  for at least the overnight 'NO DATA' periods. The network between
>  the two may have a few quirks ...

network outages between master and slave are no problem. the slave
will spool its updates until the net is back ... if the slave does
not manage to do a round, you have to check the log on the  slave.

cheers
tobi
>
>  Thanks :)
>
>
> _______________________________________________
> smokeping-users mailing list
> smokeping-users <at> lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>
>

--

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi <at> oetiker.ch ++41 62 775 9902 / sb: -9900

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users

Lars Hecking | 2 Jul 2008 16:24
Picon

Re: Slave loss computation broken?


> network outages between master and slave are no problem. the slave
> will spool its updates until the net is back ... if the slave does
> not manage to do a round, you have to check the log on the  slave.

 I set up proper logging only now, but there's a possibility the probes
 were timing out.

_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


Gmane