Re: Re: Re: website availability ping

I disagree. In his post he is trying to find problem determination by trying to retrieve a website. If by chance the http request is timing out (DOS, high traffic, etc) he will not receive an http error message besides "timed out". This just says that there was no reply to the request sent. If you read the original post I believe he is trying to get beyond the fact that the server is timing out.

Continue to use LWP::UserAgent, but dig deeper to see what the problem is. Is the server up? (ICMP call) Is the port listening? (TCP call) Has ICMP been shut down? (Another TCP Call) All which can be accomplished through NET::Ping.

The fact that an HTTP request times out does not mean that it is an HTTP problem.

Understand that the word "Ping" as the original author used does not only apply to ICMP packets.

The problem resolution is definately related.

Comment on Re: Re: Re: website availability ping

Replies are listed 'Best First'.
Re: Re: Re: Re: website availability ping by Lhamo Latso (Scribe) on Oct 29, 2003 at 06:23 UTC
I purposely left this ping idea vague. I wanted to see what ideas would come my way. I may incorporate both Net::Ping and LWP:UserAgent in a rewrite that tells me more. Possibly, I could get response time statistics by using a low timeout, and increment until I wait long enough. After too much wait, I could use Net::Ping to see if the network is down. Then maybe something in the middle, like reporting the HTTP errors. Two problems. I will need to open the firewall some, or run ICMP as root. The firewall currently doesn't let the udp/tcp packets through the echo port 7. Second. I must have an older version of LWP, because there is no get method. I need to work on it again tomorrow. Thanks.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: website availability ping
by Lhamo Latso (Scribe) on Oct 29, 2003 at 06:23 UTC

I purposely left this ping idea vague. I wanted to see what ideas would come my way. I may incorporate both Net::Ping and LWP:UserAgent in a rewrite that tells me more. Possibly, I could get response time statistics by using a low timeout, and increment until I wait long enough. After too much wait, I could use Net::Ping to see if the network is down. Then maybe something in the middle, like reporting the HTTP errors.

Two problems. I will need to open the firewall some, or run ICMP as root. The firewall currently doesn't let the udp/tcp packets through the echo port 7.

Second. I must have an older version of LWP, because there is no get method. I need to work on it again tomorrow.

Thanks.

[reply]