Issue 224 in memcached: memcached exits with code 0, under abnormal conditions

2011-09-29 Thread memcached
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 224 by antoun.k...@gmail.com: memcached exits with code 0, under abnormal conditions http://code.google.com/p/memcached/issues/detail?id=224 What steps will reproduce the problem? Arrange for event_base_loop to exit with a

Re: Issue 224 in memcached: memcached exits with code 0, under abnormal conditions

2011-09-29 Thread memcached
Comment #1 on issue 224 by dorma...@rydia.net: memcached exits with code 0, under abnormal conditions http://code.google.com/p/memcached/issues/detail?id=224 About as interesting as the error code being wrong, why is your instance exiting from the event loop abnormally and stopping?

Re: Issue 224 in memcached: memcached exits with code 0, under abnormal conditions

2011-09-30 Thread memcached
Comment #2 on issue 224 by anto...@gmail.com: memcached exits with code 0, under abnormal conditions http://code.google.com/p/memcached/issues/detail?id=224 The conditions are: a huge number of connections, exceeding the configured max. This stress is sustained. I suspect it's a epoll_wa

Re: Issue 224 in memcached: memcached exits with code 0, under abnormal conditions

2011-10-17 Thread memcached
Updates: Status: Fixed Comment #3 on issue 224 by dorma...@rydia.net: memcached exits with code 0, under abnormal conditions http://code.google.com/p/memcached/issues/detail?id=224 Fixed for the next release, thanks for the report! for what it's worth; the crash bug you're seeing is