[Bug 1774788] Re: Daemon won't start at boot up (18LTS fully patched)

[Andreas Hasenack]

Thanks for filing this bug in Ubuntu.

The scenario is confirmed: when specifying an address to bind to, rsync will fail if that address is not available:
/var/log/syslog:Jun  4 21:12:27 bionic-rsync-1774788 rsyncd[269]: rsyncd version 3.1.2 starting, listening on port 873
/var/log/syslog:Jun  4 21:12:27 bionic-rsync-1774788 rsyncd[269]: bind() failed: Cannot assign requested address (address-family 2)
/var/log/syslog:Jun  4 21:12:27 bionic-rsync-1774788 rsyncd[269]: unable to bind any inbound sockets on port 873
/var/log/syslog:Jun  4 21:12:27 bionic-rsync-1774788 rsyncd[269]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2]

The solution seems to be for rsync to adopt the socket option
IP_FREEBIND.

>From the ip(7) manpage:
IP_FREEBIND (since Linux 2.4)
If enabled, this boolean option allows binding to an IP
address that is nonlocal or does not (yet) exist.  This per‐
mits listening on a socket, without requiring the underlying
network interface or the specified dynamic IP address to be up
at the time that the application is trying to bind to it.
This option is the per-socket equivalent of the ip_nonlo‐ 
cal_bind /proc interface described below.

Until then, one workaround would be to configure the service file for
rsyncd to wait for the network to be online.

If you run:
sudo systemctl edit rsync.service

It will open an editor. Put these lines in:
[Unit]
After=network.target,network-online.target

Then save. That will create
/etc/systemd/system/rsync.service.d/override.conf with the two lines
above. Alternatively you can just create the file above directly with
the specified content without going through "systemctl edit".

You can then reboot and see if that helps. Note that the job will fail,
after reaching the network-online target, if you specify an IP address
that doesn't exist at that stage.

Another option I saw in https://unix.stackexchange.com/questions/442181
/sshd-failed-due-to-network-not-yet-available but haven't tested is to
make a system-wide change in /proc.

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1774788

Title:
  Daemon won't start at boot up   (18LTS fully patched)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1774788/+subscriptions