Version 1.2.8 is too old and is not supported, sorry! Newer versions do
not have that problem.
On Mon, 15 Oct 2018, huan ling wrote:
> Does the event_queue_remove problem resolved？
> My SUSE linux server with libevent 1.4 and memcached 1.2.8 have this problem
> too
>
> 在 2010年2月23日星期二
Does the event_queue_remove problem resolved？
My SUSE linux server with libevent 1.4 and memcached 1.2.8 have this
problem too
在 2010年2月23日星期二 UTC+8上午2:16:58，Beier写道：
>
> My memcached server has been running smoothly in the past few months,
> but last Friday and this morning, during peak
I tried to reproduce the error using Gear6's Brutis, but unfortunately
this time I'm getting too many connections error instead of event
queue error. It's hard to reproduce the exact environment when the
error occurred last week as our dev team has deployed new codes
including the fix for mysql
my web app opens a mysql and a memcached connection when php script
starts, and then close the database and memcached connection right
before php script finishes execution.
Based on the logging info I have, what happened was that there was
something wrong with mysql. queries were taking very
the memcached sever is hosted on a 64 bit Ubuntu8.0.4 distribution on
Amazon EC2, it was installed from source
max_connection was the default 1024. I suspect that the connection
might went over 1024 (at peak time the server deals with about 500
hits / sec), so now I set it to 5000 and it has been
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
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
and here is the log file:
[err] event_queue_remove: 0x62fad8(fd 27) not on queue 8
[err] event_queue_remove: 0x62fad8(fd 27
' 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
?
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
