From: Eric Wong <e@80x24.org>
To: Amir Yalon <amiryal@yxejamir.net>
Cc: unicorn-public@bogomips.org
Subject: Re: Systemd socket inheritance fails with “not a socket file descriptor”
Date: Wed, 9 Mar 2016 03:51:57 +0000 [thread overview]
Message-ID: <20160309035157.GA23507@dcvr.yhbt.net> (raw)
In-Reply-To: <1457469175.1318763.543399970.5DA44188@webmail.messagingengine.com>
Amir Yalon <amiryal@yxejamir.net> 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.
next prev parent reply other threads:[~2016-03-09 3:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 23:08 Systemd socket inheritance fails with “not a socket file descriptor” Amir Yalon
2016-03-08 3:31 ` Eric Wong
2016-03-08 7:45 ` Amir Yalon
2016-03-08 17:39 ` Eric Wong
2016-03-08 20:32 ` Amir Yalon
2016-03-09 3:51 ` Eric Wong [this message]
2016-03-09 13:19 ` Systemd socket inheritance fails with “not a socket file descriptor” [take2] Christos Trochalakis
2016-03-09 14:06 ` Systemd socket inheritance fails with “not a socket file descriptor” Christos Trochalakis
2016-03-10 9:48 ` Amir Yalon
2016-03-12 5:30 ` Eric Wong
2016-03-12 23:19 ` Amir Yalon
2016-03-17 0:27 ` [PATCH] doc: reference --keep-file-descriptors for "bundle exec" Eric Wong
2016-03-17 13:09 ` Amir Yalon
2016-03-17 16:37 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160309035157.GA23507@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=amiryal@yxejamir.net \
--cc=unicorn-public@bogomips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).