Comment #14 on issue 363 by [email protected]: MemcachePool::get(): Server
127.0.0.1 (tcp 11211, udp 0) failed with: Network timeout
http://code.google.com/p/memcached/issues/detail?id=363
heh.. if I'm not in IRC you might want to update here :P
I made a few more mistakes... I should've asked you to save a core, and
also run gdb a few times.
However from what I see in backlog is useful: there's a line number!
That line is:
switch(c->state) {
... which might seem useless, and would be a lot better with some stepping
or printing of variables (really wishing I knew what c->state is..). GDB is
a skill you should pick up.
Anyway, between 1.4.17 and 1.4.18 one new c->state was added to the
routine, conn_closed. Under the debug binary that assert's. Under the
non-debug binary however it'll endlessly loop. So pretty high odds a
connection is ending up in conn_closed state within there.
Find me in IRC and we'll walk through a quick patch to confirm this. (or if
it happens again before you see this, try to find me).
thanks!
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
