On Wed, Mar 09, 2016 at 03:51:57AM +0000, Eric Wong wrote:
Amir Yalon <[email protected]> wrote:Yes, everything looks as expected, one inherited socket starting at fd number 3:I=[3] PID=4869 FDS=1 Also tried with Ruby 2.2.1, same results. FWIW, my rubies are compiled by system-wide RVM with no special options given to it.Interesting. Can you try using some other non-Ruby daemon which uses sd_listen_fds, too? I can't think of any off the top of my head, but I'm sure there's some. It seems like systemd is mis-setting FD_CLOEXEC on socket, even.Thanks for taking the time to investigate, really appreciated.No problem. I wonder if something else is broken in your systemd config... Again, I'll take a harder look at newer systemd later this week unless somebody beats me to it.
I was also unable to reproduce it in:
* debian stretch, ruby2.2 / systemd 229
* ubuntu wily, ruby2.{1,2} / systemd 225
I used system rubies for all the experments, not rvm.
Amir, could you also send us for completeness your unicorn config and
the output of systemctl cat unicorn.socket & systemctl cat
[email protected] ?
