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

2022-03-30 Thread Simon Déziel
When rsyncd cannot find the address it was told to bind to, it exits with rc=10 and systemd doesn't even attempt a restart. To make it restart on such condition, the systemd unit should have `Restart=on-failure` added. -- You received this bug notification because you are a member of Ubuntu

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

2022-03-30 Thread Andreas Hasenack
This is a class[1] of bugs for which we cannot come up with a general solution that will safely and sanely apply to all scenarios. For such cases, local configuration changes should be made to accommodate the intended behavior in each case. We believe that, in this particular case, since the

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

2022-03-30 Thread Robie Basak
** Tags added: network-online-ordering -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1774788 Title: Daemon won't start at boot up (18LTS fully patched) Status in rsync:

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

2022-03-01 Thread Athos Ribeiro
Upstream seems to disagree with the IP_FREEBIND implementation, as per https://bugzilla.samba.org/show_bug.cgi?id=13463. The reason behind it is that the daemon should fail for invalid ip addresses. Adding After=network-online.target is frowned upon by systemd upstream. Following up with

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

2018-06-04 Thread Andreas Hasenack
The default behaviour of these services is to bind to "0.0.0.0", which means "any IP" essentially. That means they will work even when the nic isn't there yet, because localhost is. It also means that once a new nic comes up, they will listen on all its addresses too, without any other changes in

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

2018-06-04 Thread Bill Gradwohl
I'm a recent convert to Ubuntu, having been on Fedora from FC2 through F26; quite a long time. Over the last few years, their support became nonexistent. Bugs reported would not even be acknowledged, much less worked on. To have someone actually respond to a bug report is so unusual in my

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

2018-06-04 Thread Andreas Hasenack
** Bug watch added: Samba Bugzilla #13463 https://bugzilla.samba.org/show_bug.cgi?id=13463 ** Also affects: rsync via https://bugzilla.samba.org/show_bug.cgi?id=13463 Importance: Unknown Status: Unknown ** Changed in: rsync (Ubuntu) Status: New => Triaged ** Changed in:

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

2018-06-04 Thread Bill Gradwohl
I'm impressed! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1774788 Title: Daemon won't start at boot up (18LTS fully patched) Status in rsync: Unknown Status in

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

2018-06-04 Thread 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