From: sonots@...
Date: 2014-03-06T18:44:21+00:00
Subject: [ruby-core:61337] [ruby-trunk - Bug #9525] Stuck with	Socket.pack_sockaddr_in

Issue #9525 has been updated by Naotoshi Seo.


Naotoshi Seo wrote:
> EDIT: In details, I met 3 times out of 36 times that process is stuck with this case too, but
> these processes were died after 300sec, 100sec, 300sec passed respectively. I am not sure what the second mean. 
> Actually, I sent CONT signal to get sigdump https://github.com/frsyuki/sigdump, and next tried to gcore, but the process was not lived any more at that time. So, I could not get core file. The result of sigdump is available at https://gist.github.com/sonots/9392668

I could reproduce the same thing by 4 additional restarts. In this time, I waited until the process terminates without sending CONT signal or gcore. Then, I found that the process does not die even after 300sec passed. I sent CONT signal, then the process died. 

So, `Stuck with Socket.pack_sockaddr_in` was resolved, but now Fluentd gets stuck at the different point. See https://gist.github.com/sonots/9392668

----------------------------------------
Bug #9525: Stuck with Socket.pack_sockaddr_in
https://bugs.ruby-lang.org/issues/9525#change-45660

* Author: Naotoshi Seo
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: REQUIRED, 2.0.0: REQUIRED, 2.1: REQUIRED
----------------------------------------
We met this trouble with Fluentd https://github.com/fluent/fluentd. 

Fluentd is sometimes stuck at `Socket.pack_sockaddr_in` line on shutdown. 
Here is the gist https://gist.github.com/sonots/9047653 to explain details. 





-- 
http://bugs.ruby-lang.org/