Subject: [sup-talk] Sup locking up

From: [email-masked] (Marcus Williams)
Date: Thu, 11 Jun 2009 10:05:38 +0100

Hi -

Something new has started happening in sup ? I think this is what
Edward was talking about, but it appears to lock up every now and
again in a way that it never used to.

Once its locked up it doesnt come back and I dont seem to be able to
ctrl-c/d/z out of it. Its only started in the last few days and I dont
think its my IMAP server.

Oddly its breaking my screen session as well which is odder still -
the screen with sup running is locked completely (I can create new
shells from screen and use them fine, its just the sup session within
screen).

Anyone else seeing this (running next branch)?

Marcus

---

From: [email-masked] (Ben Walton)
Date: Thu, 11 Jun 2009 07:23:49 -0400

> Anyone else seeing this (running next branch)?

No...and I'm running from the most recent next with a few local
patches (message bouncing, currently).  I run in screen as well.

Is there anything constant about when the lockup occurs?  Has anything
else about your system/setup changed that could impact this?

Thanks
-Ben
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090611/8810e1f0/attachment.bin>

---

From: [email-masked] (Marcus Williams)
Date: Thu, 11 Jun 2009 15:23:28 +0100

> patches (message bouncing, currently).  I run in screen as well.

Mmmmm. Strange.

> else about your system/setup changed that could impact this?

I _think_ it occurs during a poll for new messages. Its difficult to
tell though because like I say that "window" in screen gets completely
blocked, only killing sup will get out of it (kill -9 rather than a
ctrl-c/z/d). Its very odd.

Nothing has changed on my box bar sup in recent weeks.

Marcus

---

From: [email-masked] (Ben Walton)
Date: Thu, 11 Jun 2009 11:46:19 -0400

> ctrl-c/z/d). Its very odd.

Can you strace/truss/whatever the ruby process running sup to see what
it's doing?

> Nothing has changed on my box bar sup in recent weeks.

...ok.  At least that rules out most external interference.

Thanks
-Ben

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090611/7f2e26e6/attachment.bin>

---

From: [email-masked] (Andrei Thorp)
Date: Thu, 11 Jun 2009 13:58:26 -0400

Yeah...

I have a theory. Have you learned some new stuff about screen lately?
Screen has this binding that pretty much makes it freeze up. I guess
I'm talking about http://savannah.gnu.org/bugs/?11610 which applies to
screen 4.0.0, which is the one people have.

Try maybe running sup out of screen for a while and see if it can happen then.

Another test: if screen locks up but sup respects regular kill (not
-9), sup's not locked up itself.

-AT

---

From: [email-masked] (Marcus Williams)
Date: Thu, 11 Jun 2009 20:09:19 +0100

> screen 4.0.0, which is the one people have.

I dont think debian has this problem, although I may have hit ctrl-a
and then s by accident (I actually tried ctrl-q thinking that I had
hit ctrl-s by accident when it hung but nothing happened... forgetting
that I was in screen so would need to prepend ctrl-a). Its a bit wierd
that its happened to me recently and not before though if this is what
it was - I leave sup running in screen as it makes imap bearable and
havnt run into this problem until recently when its happened a couple
of times. I'll keep an eye on it and see if it happens again.

Marcus

---

From: [email-masked] (Edward Z. Yang)
Date: Fri, 12 Jun 2009 00:38:42 -0400

> Can you strace/truss/whatever the ruby process running sup to see what

Seconded. You can attach strace to Sup while it's running, and it
will give you a good fingerprint for what the process is doing when
it locks up.

Cheers,
Edward