Hi, Ive tried both the youpper c handler at https://github.com/derdewey/mongrel2_c_handler/ and the cpp handler at https://github.com/akrennmair/mongrel2-cpp They both seem to be giving me the following error: [ERROR] (src/handler.c:173: errno: Resource temporarily unavailable) Failed to parse message from handler. [ERROR] (src/handler.c:173: errno: Resource temporarily unavailable) Failed to parse message from handler. based on the logging they are receiving the messages from mongrel2, and are attempting to respond. Are there recent changes that might cause both of those to fail, or am I just likely to be missing something? Thanks for any help - Andrew
2011/3/2 Andrew <andrew.bush@xtra.co.nz>: > Hi, > Ive tried both the youpper c handler > at https://github.com/derdewey/mongrel2_c_handler/ > and the cpp handler at https://github.com/akrennmair/mongrel2-cpp > They both seem to be giving me the following error: > [ERROR] (src/handler.c:173: errno: Resource temporarily unavailable) Failed > to parse message from handler. > [ERROR] (src/handler.c:173: errno: Resource temporarily unavailable) Failed > to parse message from handler. > The errno message "Resource temporarily unavailable" makes me think that mongrel2 didn't had the chance to start reading the handler response. I don't think that this error is a malformed handler message. This could be a misconfiguration in the socket that transports the messages back to mongrel2. Could you please post your mongrel2 config? Thanks. -- Dalton Barreto http://daltonmatos.wordpress.com
Andrew, I have updated the body_to_upper sample's documentation. You can use the config in deployment. Please see the README of my project to get a simple server up and running. Xavier On Wed, Mar 2, 2011 at 4:35 AM, Dalton Barreto <daltonmatos@gmail.com> wrote: > 2011/3/2 Andrew <andrew.bush@xtra.co.nz>: >> Hi, >> Ive tried both the youpper c handler >> at https://github.com/derdewey/mongrel2_c_handler/ >> and the cpp handler at https://github.com/akrennmair/mongrel2-cpp >> They both seem to be giving me the following error: >> [ERROR] (src/handler.c:173: errno: Resource temporarily unavailable) Failed >> to parse message from handler. >> [ERROR] (src/handler.c:173: errno: Resource temporarily unavailable) Failed >> to parse message from handler. >> > > The errno message "Resource temporarily unavailable" makes me think > that mongrel2 didn't had the chance to start > reading the handler response. I don't think that this error is a > malformed handler message. > > This could be a misconfiguration in the socket that transports the > messages back to mongrel2. > > Could you please post your mongrel2 config? > > Thanks. > > -- > Dalton Barreto > http://daltonmatos.wordpress.com >