Ok, should be enough information for a local expert to begin to help. I am not so deeply familiar with libevent.
On Mon, Feb 22, 2010 at 10:49 AM, Beier <beier...@gmail.com> wrote: > Hi Aaron, > > libevent 1.4.13 > memcached 1.4.3 > > client library is libmemcached-0.35 > > what I mean by 'went down' is, the service is dead, I had to start > memcached again Ok, but did the process die, or did the process stay alive but become unresponsive to the network? > and here is the log file: > > [err] event_queue_remove: 0x62fad8(fd 27) not on queue 8 > [err] event_queue_remove: 0x62fad8(fd 27) not on queue 8 > > the service was dead twice, that's why you see two of the same > messages: > > these are the options when memcached is started > > -d > -m 2048 > -c 3000 > > Thanks! > > On Feb 22, 10:28 am, Aaron Stone <sodab...@gmail.com> wrote: >> Please include memcached and libevent versions and your client >> libraries (just for completeness). >> >> What do you mean by "went down"? Did it become unresponsive? Did the >> process die? Memory use spin out of control? Anything else catch on >> fire? >> >> >> >> On Mon, Feb 22, 2010 at 10:16 AM, Beier <beier...@gmail.com> wrote: >> > My memcached server has been running smoothly in the past few months, >> > but last Friday and this morning, during peak traffic time memcached >> > server went down without much error message. the only message logged >> > is: >> >> > [err] event_queue_remove: 0x62fad8(fd 27) not on queue 8 >> >> > my guess is something wrong with libevent? but no idea what made this >> > happening. any help will be really appreciated >
