[ruby-core:60801] [ruby-trunk - Bug #9525] [Open] Stuck with Socket.pack_sockaddr_in

[ruby-core:60801] [ruby-trunk - Bug #9525] [Open] Stuck with Socket.pack_sockaddr_in

[sonots]

Issue #9525 has been reported by Naotoshi Seo.

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

* Author: Naotoshi Seo
* Status: Open
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60802] [ruby-trunk - Bug #9525] [Feedback] Stuck with Socket.pack_sockaddr_in

[akr]

Issue #9525 has been updated by Akira Tanaka.

Status changed from Open to Feedback

Socket.pack_sockaddr_in can block with a name resolution.
If you think the name resolution doesn't block, please explain why.

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

* Author: Naotoshi Seo
* Status: Feedback
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60803] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[sonots]

Issue #9525 has been updated by Naotoshi Seo.


Are there any ways to timeout Socket.pack_sockaddr_in? 
If so, this problem should be resolved. 

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

* Author: Naotoshi Seo
* Status: Feedback
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60804] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[akr]

Issue #9525 has been updated by Akira Tanaka.


I think it is very difficult to add timeout to getaddrinfo() function in C.

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

* Author: Naotoshi Seo
* Status: Feedback
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60805] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[akr]

Issue #9525 has been updated by Akira Tanaka.


I guess getaddrinfo() doesn't block if an IP address is given.

At least, following command on Debian GNU/Linux (jessie) doesn't show anything.

    % strace -e socket ruby -rsocket -e 'Socket.pack_sockaddr_in(80, "192.168.1.1")'

It means the command create no socket and no communication to another site.


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

* Author: Naotoshi Seo
* Status: Feedback
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60806] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[sonots]

Issue #9525 has been updated by Naotoshi Seo.


Following command on CentOS release 6.2 x86_64 returned a line

    $ strace -e socket /usr/lib64/fluent/ruby/bin/ruby -rsocket -e 'Socket.pack_sockaddr_in(80, "192.168.1.1")'
    socket(PF_NETLINK, SOCK_RAW, 0)         = 5

/usr/lib64/fluent/ruby/bin/ruby -v #=> ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]

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

* Author: Naotoshi Seo
* Status: Feedback
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60807] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[akr]

Issue #9525 has been updated by Akira Tanaka.


I think that PF_NETLINK is not a socket to communicate to another host.

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

* Author: Naotoshi Seo
* Status: Feedback
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60809] [ruby-trunk - Bug #9525] [Third Party's Issue] Stuck with Socket.pack_sockaddr_in

[naruse]

Issue #9525 has been updated by Yui NARUSE.

Status changed from Feedback to Third Party's Issue

gdb says __check_pf is guilty.
https://gist.github.com/sonots/9047653#file-gistfile3-txt

    (gdb) bt
    #0  0x00000032f2ce659d in recvmsg () from /lib64/libc.so.6
    #1  0x00000032f2d0c2c5 in make_request () from /lib64/libc.so.6
    #2  0x00000032f2d0c6fa in __check_pf () from /lib64/libc.so.6
    #3  0x00000032f2ccfb47 in getaddrinfo () from /lib64/libc.so.6
    #4  0x00007fb3139d3818 in nogvl_getaddrinfo (arg=<value optimized out>) at raddrinfo.c:161
    #5  0x00000000004f600c in rb_thread_blocking_region (func=0x7fb3139d3800 <nogvl_getaddrinfo>, data1=0x7fb0d5dd0140, ubf=<value optimized out>, data2=<value optimized out>) at thread.c:1129
    #6  0x00007fb3139d2eaf in rb_getaddrinfo (node=<value optimized out>, service=<value optimized out>, hints=<value optimized out>, res=<value optimized out>) at raddrinfo.c:181
    #7  0x00007fb3139d2fcb in rsock_getaddrinfo (host=<value optimized out>, port=22017, hints=0x7fb0d5dd0600, socktype_hack=1) at raddrinfo.c:359
    #8  0x00007fb3139d37ed in rsock_addrinfo (host=0, port=140397479001552, socktype=<value optimized out>, flags=659) at raddrinfo.c:379
    #9  0x00007fb3139c939a in sock_s_pack_sockaddr_in (self=<value optimized out>, port=140397479001552, host=35158400) at socket.c:1307

By glibc's commits, once __check_pf is always called [6f3914d5a3269c00e70506bd95f816fef6b635ce](https://sourceware.org/git/?p=glibc.git;a=commit;f=sysdeps/posix/getaddrinfo.c;h=6f3914d5a3269c00e70506bd95f816fef6b635ce)
(it is fixed at [fa3fc0fe5f452d0aa7e435d8f32e992958683819](https://sourceware.org/git/?p=glibc.git;a=commit;f=sysdeps/posix/getaddrinfo.c;h=fa3fc0fe5f452d0aa7e435d8f32e992958683819))

The difference between akr's and sonots' seems because of this.

Therefore this is glibc's old bug and RHEL/CentOS's backport issue.

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

* Author: Naotoshi Seo
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60810] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[sonots]

Issue #9525 has been updated by Naotoshi Seo.


Thank you! Let me write a note here. 

On my current environment, the glibc version was glibc-2.12-1.47.el6.x86_64. 

I checked the latest centos rpm http://vault.centos.org/6.5/os/Source/SPackages/glibc-2.12-1.132.el6.src.rpm,
but it looked RHED/CentOS is not backporting it yet (cf. https://gist.github.com/sonots/9065060)

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

* Author: Naotoshi Seo
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60829] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[akr]

Issue #9525 has been updated by Akira Tanaka.


I think we can accept a workaround if there is a good patch.

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

* Author: Naotoshi Seo
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60830] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[kosaki.motohiro]

Issue #9525 has been updated by Motohiro KOSAKI.


I checked a glibc code. I don't think fa3fc0fe5f fixed this issue. It is a mere optimization patch.
I'm not sure why kernel's netlink doesn't reply anything. But it may be worth to try upgrade your kernel.

Thanks.



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

* Author: Naotoshi Seo
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60831] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[kosaki.motohiro]

Issue #9525 has been updated by Motohiro KOSAKI.


Akr-san,

I'm not an expert this area. But I guess we don't need to call getaddrinfo() in this case
because the name was already resolved.
How about bypass to call getaddrinfo when 'host' is given by IP address?

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

* Author: Naotoshi Seo
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60846] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[akr]

Issue #9525 has been updated by Akira Tanaka.


Motohiro KOSAKI wrote:

> I'm not an expert this area. But I guess we don't need to call getaddrinfo() in this case
> because the name was already resolved.
> How about bypass to call getaddrinfo when 'host' is given by IP address?

Yes.  It is the workaround I said.


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

* Author: Naotoshi Seo
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60890] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[akr]

Issue #9525 has been updated by Akira Tanaka.


I tried to workaround this issue at r45047.
However I don't have an environment to reproduce the problem.

Would anyone test the problem at latest trunk?

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

* Author: Naotoshi Seo
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60891] Re: [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[Eric Wong]

akr@fsij.org wrote:
> I tried to workaround this issue at r45047.
> However I don't have an environment to reproduce the problem.

I don't know how to reproduce the problem, either.  netlink sockets
should not block like that.

r45047 looks correct.  A few minor comments:
* backwards for loop for list is confusing to me,
  any reason for not reversing list declaration?
* why xmalloc + MEMZERO?  xcalloc is shorter and generates smaller code

[ruby-core:60892] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[normalperson]

Issue #9525 has been updated by Eric Wong.


 akr@fsij.org wrote:
 > I tried to workaround this issue at r45047.
 > However I don't have an environment to reproduce the problem.
 
 I don't know how to reproduce the problem, either.  netlink sockets
 should not block like that.
 
 r45047 looks correct.  A few minor comments:
 * backwards for loop for list is confusing to me,
   any reason for not reversing list declaration?
 * why xmalloc + MEMZERO?  xcalloc is shorter and generates smaller code

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

* Author: Naotoshi Seo
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60894] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[kosaki.motohiro]

Issue #9525 has been updated by Motohiro KOSAKI.

Related to Backport #9538: backport r45047 added

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

* Author: Naotoshi Seo
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60896] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[kosaki.motohiro]

Issue #9525 has been updated by Motohiro KOSAKI.

Related to Backport #9536: backport r45047 added

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

* Author: Naotoshi Seo
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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/

[ruby-core:60898] [ruby-trunk - Bug #9525] [Closed] Stuck with Socket.pack_sockaddr_in

[kosaki.motohiro]

Issue #9525 has been updated by Motohiro KOSAKI.

Status changed from Third Party's Issue to Closed
Backport changed from 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN to 1.9.3: REQUIRED, 2.0.0: REQUIRED, 2.1: REQUIRED

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

* 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/

[ruby-core:60907] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[akr]

Issue #9525 has been updated by Akira Tanaka.


Eric Wong wrote:

>  * backwards for loop for list is confusing to me,
>    any reason for not reversing list declaration?

I prefer ordering consistency between "list" and "res".

>  * why xmalloc + MEMZERO?  xcalloc is shorter and generates smaller code

xcalloc is good idea.



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

* 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/

[ruby-core:61276] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[sonots]

Issue #9525 has been updated by Naotoshi Seo.


Akira Tanaka wrote:
> Would anyone test the problem at latest trunk?

I had never ran fluentd with ruby 2.1.1, but now I am trying it. 
If it works well, I will try ruby-trunk next. 


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

* 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/

[ruby-core:61334] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[sonots]

Issue #9525 has been updated by Naotoshi Seo.


I applied following consecutive patches for ruby 2.1.1, and tried. 

https://github.com/ruby/ruby/commit/948ce9decb97e5ff0833e53a392aa9f1d42c9b0d
https://github.com/ruby/ruby/commit/dd1c3a75096b97c1ebcb8597c001761ddfb3c1bf
https://github.com/ruby/ruby/commit/2e6b97a45d077979121b29484a8831034d47ef50

Before (ruby 2.1.1): 

The stuck was able to be reproduced with ruby 2.1.1. 
I restarted my entire fluentd cluster 12 times, and it occurred at 4th and 12th, that is, 2 times out of 12. 

After (ruby 2.1.1 + patch)

I restarted the fluentd cluster 36 times, and got stuck 0 time. 

After all, it looks this patch fixed the issue. 

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

* 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/

[ruby-core:61335] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[sonots]

Issue #9525 has been updated by Naotoshi Seo.


Naotoshi Seo wrote:
> I applied following consecutive patches for ruby 2.1.1, and tried. 
> 
> https://github.com/ruby/ruby/commit/948ce9decb97e5ff0833e53a392aa9f1d42c9b0d
> https://github.com/ruby/ruby/commit/dd1c3a75096b97c1ebcb8597c001761ddfb3c1bf
> https://github.com/ruby/ruby/commit/2e6b97a45d077979121b29484a8831034d47ef50
> 
> Before (ruby 2.1.1): 
> 
> The stuck was able to be reproduced with ruby 2.1.1. 
> I restarted my entire fluentd cluster 12 times, and it occurred at 4th and 12th, that is, 2 times out of 12. 
> 
> After (ruby 2.1.1 + patch)
> 
> I restarted the fluentd cluster 36 times, and got stuck 0 time. 
> 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. Then these processes were not lived any more. 
> 
> After all, it looks this patch fixed the issue.


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

* 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/

[ruby-core:61337] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[sonots]

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/

[ruby-core:62241] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[usa]

Issue #9525 has been updated by Usaku NAKAMURA.


memo: related commits: 45046,45047,45063,45087,45150,45151,45152

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

* 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. 





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

[ruby-core:64545] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[nagachika00]

Issue #9525 has been updated by Tomoyuki Chikanaga.


Is there any progress?

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

* 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. 





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

[ruby-core:64792] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[nagachika00]

Issue #9525 has been updated by Tomoyuki Chikanaga.


I have confirmed that this issue is already fixed.

https://twitter.com/sonots/status/507804708153483264

Add related commits: r45146


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

* 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. 





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

[ruby-core:64793] [ruby-trunk - Bug #9525] Stuck with Socket.pack_sockaddr_in

[nagachika00]

Issue #9525 has been updated by Tomoyuki Chikanaga.

Backport changed from 1.9.3: REQUIRED, 2.0.0: REQUIRED, 2.1: REQUIRED to 1.9.3: REQUIRED, 2.0.0: REQUIRED, 2.1: DONE

r45046, r45047, r45063, r45087, r45146, r45150, r45151 and r45152 were backported into `ruby_2_1` branch at r47415.

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

* 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: DONE
----------------------------------------
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. 





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

[ruby-core:76359] [Ruby trunk Bug#9525] Stuck with Socket.pack_sockaddr_in

[sm]

Issue #9525 has been updated by maria katosvich.

Backport deleted (1.9.3: REQUIRED, 2.0.0: REQUIRED, 2.1: DONE)



Related issue: https://bugs.ruby-lang.org/issues/9536

This problem is a big issue for Fluentd.
We hope to backport this commit to Latest Rubies.

Thanks,
[sky contact number uk@fixithere.net](http://www.fixithere.net/sky-contact-number/)

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

* Author: Naotoshi Seo
* Status: Closed
* Priority: Normal
* Assignee: 
* ruby -v: 1.9.3p194
* Backport: 
----------------------------------------
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. 





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

[ruby-core:76363] [Ruby trunk Bug#9525] Stuck with Socket.pack_sockaddr_in

[nobu]

Issue #9525 has been updated by Nobuyoshi Nakada.

Backport set to 2.1: DONE

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

* Author: Naotoshi Seo
* Status: Closed
* Priority: Normal
* Assignee: 
* ruby -v: 1.9.3p194
* Backport: 2.1: DONE
----------------------------------------
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. 





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