Re: Any takers on Bug #1703? (diskd stuck at 100% CPU)

On Sat, 29 Jul 2006, Henrik Nordstrom wrote:

> lör 2006-07-29 klockan 23:16 +0800 skrev Steven:
>
> > I was seeing the msgrecv() calls while running strace, but it wasn't in
> > the same loop as reported in the bug. Looks like I just found another bug
> > while trying to reproduce this one :)
>
> Was not aware there was msgrcv() calls in pthreads.
>
> We don't have a backtrace in the bug, so it could be the same and I was
> chasing down the wrong path...
>
> Guess we gave to wait for Ralf to answer about the details of his setup.

I have just found another bug. I have ended up in the situation where
squid has not stared the diskd processes (because the binary is called
diskd-daemon not diskd_daemon). Squid is not serving any web pages,
and will not stop because of this, but is is stuck in a loop doing the
following:

epoll_wait(3, {}, 256, 10) = 0
gettimeofday({1154236711, 528040}, NULL) = 0
msgrcv(1409029, {0,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...}, 32, 0,
IPC_NOWAIT) = -1 ENOMSG (No message of desired type)
epoll_wait(3, {}, 256, 10) = 0

What would happen if the diskd process stopped too early on a busy
system. Is it possible that the diskd_daemon processes can stop without
processing all requests (which would leave the main squid process in an
endless loop).

Steven
Received on Sat Jul 29 2006 - 23:21:28 MDT