librelist archives

« back to archive

m2 log warning

m2 log warning

From:
Matt Towers
Date:
2011-05-05 @ 18:07
Anyone seen this before?  The favicon.ico 404 makes sense but I'm not sure
how to interpret the warning.  

[ERROR] (src/connection.c:107: errno: Resource temporarily unavailable) 
Handler not found: /favicon.ico
[WARN] (src/register.c:312: errno: Resource temporarily unavailable) 
Connection fd=4:conn_id=2 write rate lower than allowed: 0 < 300


✈ Matt


Re: [mongrel2] m2 log warning

From:
Zed A. Shaw
Date:
2011-05-05 @ 19:03
On Thu, May 05, 2011 at 11:07:06AM -0700, Matt Towers wrote:
> Anyone seen this before?  The favicon.ico 404 makes sense but I'm not 
sure how to interpret the warning.  
> 
> [ERROR] (src/connection.c:107: errno: Resource temporarily unavailable) 
Handler not found: /favicon.ico
> [WARN] (src/register.c:312: errno: Resource temporarily unavailable) 
Connection fd=4:conn_id=2 write rate lower than allowed: 0 < 300

That's the new timeout code.  I threw in over abundant logging so that
people can watch it work and report if it's wrong before I finalize it.
Stay tuned for a more detailed description, but basically it by default
kills connections that aren't active enough.  That's telling you that it
found a connection that hasn't written any data in the last 10 seconds
or so.

-- 
Zed A. Shaw
http://zedshaw.com/

Re: [mongrel2] m2 log warning

From:
Matt Towers
Date:
2011-05-05 @ 20:44
Here's another one.  This one is being repeatedly dumped to the output.  I
think the environment where this is occurring is one in which m2 reloaded 
it's config but one or more handlers were not running at reload time?  
Still working to isolate further.

[WARN] (src/handler.c:286: errno: Resource temporarily unavailable) Failed
to bind send socket trying again for: tcp://127.0.0.1:10010

✈ Matt



On May 5, 2011, at 12:03 , Zed A. Shaw wrote:

> On Thu, May 05, 2011 at 11:07:06AM -0700, Matt Towers wrote:
>> Anyone seen this before?  The favicon.ico 404 makes sense but I'm not 
sure how to interpret the warning.  
>> 
>> [ERROR] (src/connection.c:107: errno: Resource temporarily unavailable)
Handler not found: /favicon.ico
>> [WARN] (src/register.c:312: errno: Resource temporarily unavailable) 
Connection fd=4:conn_id=2 write rate lower than allowed: 0 < 300
> 
> That's the new timeout code.  I threw in over abundant logging so that
> people can watch it work and report if it's wrong before I finalize it.
> Stay tuned for a more detailed description, but basically it by default
> kills connections that aren't active enough.  That's telling you that it
> found a connection that hasn't written any data in the last 10 seconds
> or so.
> 
> -- 
> Zed A. Shaw
> http://zedshaw.com/

Re: [mongrel2] m2 log warning

From:
Zed A. Shaw
Date:
2011-05-05 @ 21:54
On Thu, May 05, 2011 at 01:44:13PM -0700, Matt Towers wrote:
> Here's another one.  This one is being repeatedly dumped to the
> output.  I think the environment where this is occurring is one in
> which m2 reloaded it's config but one or more handlers were not
> running at reload time?  Still working to isolate further.
> 
> [WARN] (src/handler.c:286: errno: Resource temporarily unavailable)
> Failed to bind send socket trying again for: tcp://127.0.0.1:10010

You'll get this if:

1. Port 10010 is already taken by something else.
2. You accidentally configured a new handler that's slightly different
in the same server.  Like the old one is tcp://localhost:10010/ and then
you change it to tcp://127.0.0.1:10010/ or change the UUID but not the
port, etc.

Let me know if it's one of those two.

-- 
Zed A. Shaw
http://zedshaw.com/