Am 06.08.19 um 09:15 schrieb Michael Biebl:
> Am 06.08.19 um 04:48 schrieb Debian Bug Tracking System:
>>  rpcbind (1.2.5-5) unstable; urgency=medium
>>  .
>>    * debian/rules: Add --no-restart-after-upgrade option to
>>      dh_installsystemd to avoid race condition at rpcbind.socket
>>      initialization (Closes: #933268)
> 
> https://salsa.debian.org/debian/rpcbind/commit/6bdd9256f811ed312173eeb9e9ca7f600720769b
> 
> I don't think this is a proper fix. After all, you typically want a
> daemon to be restarted after upgrades so (security) fixes are applied.
> I also notice, that the above commit contains other (unrelated) changes
> which are not mentioned in the changelog.
> 
> 
> A quick test shows, that debhelper creates the following code and
> executing that manually triggers the same error:
> 
> # systemctl restart rpcbind.service rpcbind.socket
> 
> Job for rpcbind.socket failed.
> See "systemctl status rpcbind.socket" and "journalctl -xe" for details.
> A dependency job for rpcbind.service failed. See 'journalctl -xe' for
> details.
> 
> This needs further investigation, where the underlying problem is.
> For the time being, I would suggest a different workaround, ie.
> restarting rpcbind.service and rpcbind.socket sequentially (or only
> rpcbind.service, I think that should be sufficient)
> 
> 
> So somehting like this:
> override_dh_installsystemd:
>      dh_installsystemd rpcbind.socket
>       dh_installsystemd rpcbind.service
> 
> 
> I'm not yet sure if this is a bug in systemd itself, in rpcbind or
> debhelper for generating such a code sequence, so CCing all affected
> parties.
> 

I've filed https://github.com/systemd/systemd/issues/13271 in the mean
time, asking for input from systemd upstream.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to