Re: What does this error really mean?

[Ben Hartshorne]

On Tue, Oct 18, 2005 at 01:41:42PM +0200, Jan-Henrik Haukeland wrote:
> 
> On 18. okt. 2005, at 02.05, Ben Hartshorne wrote:
> 
> >I've got this error sprinkled through my logs.  I'm curious what it
> >actually means.
> >
> >GENERIC: error receiving data -- Resource temporarily unavailable
> >
> >At what point did the test fail?  Did it...
> >*
> 
> It means that the connection end-point (the server) did not provide  
> data when monit was trying to read. It may help if you increase the  
> connection timeout from the default which is 5 sec.
> 
> >Here's the relevant section of the monit config file:
> >
> >check host Google with address www.google.com
> >        start program = "/bin/true"
> >        stop program = "/bin/true"
> >        if 3 restarts within 4 cycles then timeout
> >      if failed url http://www.google.com/
> >              then restart
> 
> This error should come from a send/expect statement, are sure you  
> don't have one of those in your config file?

Whoops!  Sorry, you're right.  That error was generated by the following
config section:

check host SearchDidntReturn with address www.simplyhired.com
        start program = "/bin/true"
        stop program = "/bin/true"
        if 2 restarts within 3 cycles then timeout
        if failed port 80 send
                "GET 
/index.php?dstate=searchresult&state=searchresult&miles=&sortby=date&keywords=pink+elephant&location=ca
 HTTP/1.0\r\nHost: www.simplyhired.com\r\n\r\n"
                expect "HTTP/1.1 200 OK.*\r\n"
                with timeout 10 seconds
                then restart
        depends on FrontApacheDown

The previous section generated:

HTTP: error receiving data -- Resource temporarily unavailable

Does that error mean basically the same thing (that the connection
endpoint did not send data that monit was expecting to recieve), but
over HTTP instead of send/expect?

How is this different from the "service timed out" error?  Does one
imply that it was never able to connect, and the other that a connection
was made but not completed?  Both of these scenarios are different from
getting the wrong data, right?

I'm getting these Resource temporarily unavailable errors in the middle
of the night (my tests go over a local ethernet network). I'm really not
sure why they're occuring.  

-ben

-- 
Ben Hartshorne
email: address@hidden
http://ben.hartshorne.net

signature.asc
Description: Digital signature