Re: [wmii] wmiirc Locking Up

On 6/28/06, Kris Maglione <bsdaemon_AT_comcast.net> wrote:
> On Wed, Jun 28, 2006 at 04:21:06PM +0200, W.P. van Paassen wrote:
> >On 6/28/06, Anselm R. Garbe <garbeam_AT_wmii.de> wrote:
> >>On Wed, Jun 28, 2006 at 09:22:26AM +0200, W.P. van Paassen wrote:
> >> > I'm having the same lock up problems.
> >> > I noticed however that in case of a lockup the following error
> >> > is constantly generated
> >> >
> >> > wmiir cannot connect to server
> >>
> >
> >>If that occures, no more connections attempting to connect to
> >>the server aren't enqueued by the OS.
> >
> >This is propably caused by the server not accepting connections any
> >longer (because it hangs?)
> >
> >>Could it be that you run
> >>several other servers which might be connected from other kinds
> >>of clients as well, that we get near to say 256 connections in
> >>average?
> >>
> >>
> >No, this is not the case
> >
> >By the way my /tmp is on nfs and the file's atime is not updated (for
> >performance reasons)
> >
> >I'll do some stracing and come back later
> It might be easier to attach to it with gdb and get a backtrace. The server
> hanging would not cause that error to be constantly generated, though. The
> only place that we loop if wmiir exits non-zero is in the first loop in the
> wmiirc (echo "Start wmiirc"), but that has stderr redirected to /dev/null, so
> it can't be the cause. Everywhere else we loop, we stop when wmii exits or
> exits non-zero (the event loop exits with wmii, the status script exits when
> wmiir exits non-zero). It seems likely to me that somehow, you've managed to
> cause an infinate loop in you wmiirc or status scripts which, possibly, forks
> enough wmiir instances to cause the socket to reject connections.
>

I'm using the default script of 3.0. I'll try the 3.1 version next

wmiirc is not hanging, I can still create a new client in the view by
either using Alt-Enter or Alt-P. I just can't change view and I can't
change client within the view using the keyboard, the mouse works
though

> The only other likely possibility is that the socket is somehow being closed
> or wmiir is dieing. Check with netstat that the socket is actually still open
> and listening for connections and how many open connections it has.

here's my netstat output

unix 3 [ ] STREAM CONNECTED 12210822
21532/wmiiwm /tmp/ns.username.:0/wmii
unix 3 [ ] STREAM CONNECTED 12210821 21560/wmiir
unix 3 [ ] STREAM CONNECTED 12210779 21532/wmiiwm

unix 2 [ ACC ] STREAM LISTENING 12210781
21532/wmiiwm /tmp/ns.username.:0/wmii

here's a tail of the strace of wmiir read /event

read(3, "u\377\377\16\0\0\0ClientFocus 6\n", 21) = 21
write(1, "ClientFocus 6\n", 14) = 14
write(3, "\27\0\0\0t\377\377\340P\1\0v\31\0\0\0\0\0\0\0\10\0\0", 23) = 23
read(3,
etc

wmiir is not dieing

Hope this helps

regards
WP
Received on Fri Jun 30 2006 - 10:42:31 UTC