@Andrew ran into this in https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/413490/ and I just ran into it on deployment-deploy02.deployment-prep.eqiad.wmflabs.
I found that the nutcracker binary would give up shortly after this:
bind(11, {sa_family=AF_UNIX, sun_path="/var/run/nutcracker/nutcracker.sock"}, 110) = -1 ENOENT (No such file or directory)
(another thing nutcracker appears to care about without erroring for, even with --verbose=11, is the file permissions)
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| systemd::tmpfile: apply changes when we change the files. | operations/puppet | production | +8 -0 |
Related Objects
Related Objects
- Mentioned In
- T201343: rack/setup/install mwmaint1002.eqiad.wmnet
Event Timeline
Comment Actions
The .sock file is created via systemd-tmpfiles, which is only read during boot, the socket will be created with the next restart
Comment Actions
FWIW this is also a shortcoming of our tmpfiles abstraction in puppet I think, namely we should be notifying in puppet systemd-tmpfiles --create when puppet changes/creates tmpfiles
Comment Actions
Change 527430 had a related patch set uploaded (by Giuseppe Lavagetto; owner: Giuseppe Lavagetto):
[operations/puppet@production] systemd::tmpfile: apply changes when we change the files.
Comment Actions
Change 527430 merged by Giuseppe Lavagetto:
[operations/puppet@production] systemd::tmpfile: apply changes when we change the files.