[Bug 1774788] Re: Daemon won't start at boot up (18LTS fully patched)
Bill Gradwohl
bill at ycc.com
Mon Jun 4 22:00:14 UTC 2018
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 experience that I'm pleasantly shocked. Thank You. Thank
You.
Shouldn't services (sshd, rsync, etc) that depend on a NIC being
available ALL wait till that's true? Shouldn't the fix presented for
this bug become SOP for all the control files for services that require
a NIC to be up?
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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 rsync package in Ubuntu:
Triaged
Bug description:
By adding the 'address=' option to the /etc/rsyncd.conf file, the
daemon fails at boot.
Once the NIC(s) is/are up, it will start fine when executed via
systemctl start rsync
● rsync.service - fast remote file copy program daemon
Loaded: loaded (/lib/systemd/system/rsync.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 52min ago
Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, status=10)
Main PID: 851 (code=exited, status=10)
Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file copy program daemon.
Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 starting, listening on port 873
Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot assign requested address (address-family 2)
Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main process exited, code=exited, status=10/n/a
Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any inbound sockets on port 873
Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with result 'exit-code'.
Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2]
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: rsync 3.1.2-2.1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jun 2 08:48:15 2018
InstallationDate: Installed on 2018-06-01 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: rsync
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/rsync/+bug/1774788/+subscriptions
More information about the foundations-bugs
mailing list