headers
Rob de Jong | 2 Dec 2005 04:18

Curl probe doesn't handle multiple url's

Hi all,

I'd like to measure the time taken to fetch multiple url's with curl, 
eg: urlformat = http://%host%/pdf[1-2].pdf
My problem is that SmokePing does not seem to handle the fact that curl 
is fetching multiple url's.
It just grabs the average Total Time of the second url in this case.
Is there a way I can achieve this?

Best regards,

Rob

>
>  
>
Permalink | Reply | 3 comments |
headers
Niko Tyni | 2 Dec 2005 12:11
Picon
Picon

Re: Curl probe doesn't handle multiple url's

On Fri, Dec 02, 2005 at 02:18:32PM +1100, Rob de Jong wrote:

> I'd like to measure the time taken to fetch multiple url's with curl, 
> eg: urlformat = http://%host%/pdf[1-2].pdf
> My problem is that SmokePing does not seem to handle the fact that curl 
> is fetching multiple url's.
> It just grabs the average Total Time of the second url in this case.
> Is there a way I can achieve this?

Hi,

I'm not quite sure if this is a good idea... the curl documentation
states that curl will re-use the same TCP connection when it can, so
you'll get kind of skewed results. What are you trying to measure
anyway? It seems to me that one file would be enough to measure
webserver responsiveness, and if you're trying to measure the bandwidth
of the connection (to see if it's saturated or something), you'd
probably be better off with big ICMP packets.

That said, here's a patch that makes multiple URLs (whether in the 
[]/{} notation or with separate arguments) possible. It needs
the 'redirect' patch I sent earlier to be applied first.

Cheers,
--

-- 
Niko
Permalink | Reply | 2 comments |
headers
Niko Tyni | 2 Dec 2005 12:14
Picon
Picon

Re: Curl probe doesn't handle multiple url's

On Fri, Dec 02, 2005 at 01:11:28PM +0200, Niko Tyni wrote:

> That said, here's a patch that makes multiple URLs (whether in the 
> []/{} notation or with separate arguments) possible. It needs
> the 'redirect' patch I sent earlier to be applied first.
Oops, forgot to attach the patch. Here we go again.

Cheers,
--

-- 
Niko

-- Attached file removed by Ecartis and put at URL below --
-- Type: text/plain
-- Size: 1k (1396 bytes)
-- URL : http://lists.ee.ethz.ch/p/curl-url-patch
Permalink | Reply | 0 comments |
headers
Niko Tyni | 2 Dec 2005 12:24
Picon
Picon

Re: DYNAMIC config help

On Wed, Nov 30, 2005 at 11:25:33AM -0500, Lemaire, David W. wrote:

> host = DYNAMIC/<password>
> email = Dave Lemaire <my <at> email.address>
> menu = Daves PC
> title = Daves PC
> 
>  in an fping probe group. 
> Also started smokeping  as 'smokeping --email'.
> It has not sent anything out.

Hi,

the idea is that you at first put the line

host = DYNAMIC

(without any password) to the target section, and then run 

# smokeping --email

which generates a password, inserts it (or rather a hash of it)
into the config file and sends the agent script containing the
password to the 'email' address.

If you already did this and 'smokeping --email' told you that it sent
the script, there might be something wrong with your sendmail setup.
You could to try the 'mailhost' variable to get smokeping to send the
message straight to a smarthost without using the local sendmail.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Priebe, Mike | 2 Dec 2005 16:59
Picon
Picon

smokeping.cgi webpage problems

Hello List!
I'm having a problem accessing the smokeping.cgi webpage on my Mandrake/Apache server. When I try to
access http://192.192.1.50/cgi-bin/smokeping.cgi, the browser displays the following message.........
"The Server encountered an internal error or misconfiguration and was unable to complete your request"

Checked the apache logs...

[Fri Dec 02 09:05:25 2005] [error] [client 192.192.1.33] Can't locate Smokeping.pm in  <at> INC ( <at> INC
contains: /home/mp/tmp/smokeping_stuff/smokeping-2.0.5/lib
/usr/local/rrdtool-1.2.6/lib/perl/5.8.5/i386-linux-thread-multi
/usr/local/rrdtool-1.2.6/lib/perl/5.8.5 /usr/lib/perl5/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/5.8.5 /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5
/usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4
/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3
/usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl .) at
/var/www/cgi-bin/smokeping.cgi line 7.
[Fri Dec 02 09:05:25 2005] [error] [client 192.192.1.33] BEGIN failed--compilation aborted at
/var/www/cgi-bin/smokeping.cgi line 7.
[Fri Dec 02 09:05:25 2005] [error] [client 192.192.1.33] speedy_backend[14737]: perl_parse error
[Fri Dec 02 09:05:26 2005] [error] [client 192.192.1.33] speedy[14735]: Cannot spawn backend process
[Fri Dec 02 09:05:26 2005] [error] [client 192.192.1.33] Premature end of script headers: smokeping.cgi

The smokeping.cgi is located in the default cgi directory /var/www/cgi-bin from which I can execute other
cgi's. 

When I execute the cgi manually, I do not see any errors.. /var/www/cgi-bin perl smokeping.cgi

The weblog states that it can't locate Smokeping.pm, but when I use the path mentioned in the error log from
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ian Fraser | 2 Dec 2005 17:36
Favicon

Using mutt rather than Sendmail?


I don't have sendmail installed on the machine running smokeping. I do
have mutt, with LIBeSMTP and the patch to allow Mutt to talk directly to
the SMTP server,  I know mutt works ok as I can send email from the CLI
and GUI. My SMTP server requires non-standard ports and SMTP_AUTH, so
mutt's easier to use for this purpose than sendmail or postfix etc....

Is it possible to have smokeping send email using mutt instead of
sendmail ? I've modified the config to point sendmail=/usr/bin/mutt but
when I run tSmoke --testmail I see nothing going to the SMTP server (I
should shouldn't I ?)

Thanks,
Ian
Permalink | Reply | 1 comment |
headers
Ian Fraser | 2 Dec 2005 17:41
Favicon

Re: smokeping.cgi webpage problems


Try to start smokeping like this (assuming the smokeping script is in
/usr/local/smokeping/bin)

cd /usr/local/smokeping  

./bin/smokeping 

I found on apache that if I called smokeping directly it would then have
problems finding the pm's.

May help

-----Original Message-----
From: smokeping-users-bounce <at> list.ee.ethz.ch
[mailto:smokeping-users-bounce <at> list.ee.ethz.ch] On Behalf Of Priebe,
Mike
Sent: Friday, December 02, 2005 10:59 AM
To: smokeping-users <at> list.ee.ethz.ch
Subject: [smokeping-users] smokeping.cgi webpage problems

Hello List!
I'm having a problem accessing the smokeping.cgi webpage on my
Mandrake/Apache server. When I try to access
http://192.192.1.50/cgi-bin/smokeping.cgi, the browser displays the
following message.........
"The Server encountered an internal error or misconfiguration and was
unable to complete your request"

Checked the apache logs...
(Continue reading)

Permalink | Reply | 0 comments |
headers
Niko Tyni | 2 Dec 2005 19:09
Picon
Picon

Re: Using mutt rather than Sendmail?

On Fri, Dec 02, 2005 at 11:36:32AM -0500, Ian Fraser wrote:

> Is it possible to have smokeping send email using mutt instead of
> sendmail ? I've modified the config to point sendmail=/usr/bin/mutt but
> when I run tSmoke --testmail I see nothing going to the SMTP server (I
> should shouldn't I ?)

Hi,

I suppose mutt should work, if it supports sendmail-style options.
Smokeping calls sendmail as

# <sendmail-program> -f <from-address> <to-address>

so there's nothing fancy there.

The tSmoke '--testmail' option is unfortunately misnamed. It apparently
doesn't really send anything, just tells where the mail would go.
I think I'll fix this for the next release. Meanwhile, I guess you
can test with eg. '--morning' just as well.

Cheers,
--

-- 
Niko
Permalink | Reply | 0 comments |
headers
Niko Tyni | 2 Dec 2005 19:18
Picon
Picon

Re: smokeping.cgi webpage problems

On Fri, Dec 02, 2005 at 09:59:24AM -0600, Priebe, Mike wrote:

> [Fri Dec 02 09:05:25 2005] [error] [client 192.192.1.33] Can't locate Smokeping.pm in  <at> INC ( <at> INC
contains: /home/mp/tmp/smokeping_stuff/smokeping-2.0.5/lib
/usr/local/rrdtool-1.2.6/lib/perl/5.8.5/i386-linux-thread-multi
/usr/local/rrdtool-1.2.6/lib/perl/5.8.5 /usr/lib/perl5/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/5.8.5 /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5
/usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4
/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3
/usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl .) at
/var/www/cgi-bin/smokeping.cgi line 7.

Hi,

this is indeed a permission problem, although they do seem to be OK in
your 'ls' output. The last time somebody had this kind of a problem, the
culprit turned out to be SELinux. If that's the case, 'setenforce 0'
should help.

(I don't know much about SELinux, but this fix sounds a bit crude...
suggestions for a finer-granularity fix are welcome.)

Cheers,
--

-- 
Niko
Permalink | Reply | 0 comments |
headers
Ian Fraser | 2 Dec 2005 19:19
Favicon

Re: Using mutt rather than Sendmail?

 Ahh.. Yes so I invoked --morning instead and it does appear to use
mutt, but mutt bypassed the SMTP_AUTH portion so the server rejects the
connection... It DID use the alternate SMTP Port though, so it's
something in the mutt backend it would seem now.. Interesting. Thanks!

-----Original Message-----
From: Niko Tyni [mailto:ntyni+smokeping-users <at> mappi.helsinki.fi] 
Sent: Friday, December 02, 2005 1:09 PM
To: Fraser, Ian [CAR:W669:EXCH]
Cc: smokeping-users <at> list.ee.ethz.ch
Subject: Re: [smokeping-users] Using mutt rather than Sendmail?

On Fri, Dec 02, 2005 at 11:36:32AM -0500, Ian Fraser wrote:

> Is it possible to have smokeping send email using mutt instead of 
> sendmail ? I've modified the config to point sendmail=/usr/bin/mutt 
> but when I run tSmoke --testmail I see nothing going to the SMTP 
> server (I should shouldn't I ?)

Hi,

I suppose mutt should work, if it supports sendmail-style options.
Smokeping calls sendmail as

# <sendmail-program> -f <from-address> <to-address>

so there's nothing fancy there.

The tSmoke '--testmail' option is unfortunately misnamed. It apparently
doesn't really send anything, just tells where the mail would go.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane