> Robie: If the service offers a mechanism to set a specific NIC to listen on, then the service should make good on that offer when it's requested. Doesn't that make sense to you?
Correct. If you configure the service to listen on a specific NIC, you should also configure the service to wait for that NIC to be up before it attempts to start. > All services that require a NIC to function should wait for that NIC to come alive. Having a service start or attempt to start before what it needs for life support is available makes no sense. So don't configure it like that. > Allowing a service to start on a bogus IP address provides no "service". What's the point of having a service technically up if it's deaf to traffic? What you're asking for is the system to algorithmically detect when it has been configured this way and defer starting of the service. This isn't a feature that currently exists. The workaround is to adjust service dependencies at the same time as you change your service configuration to add that dependency. This problem is more complex than you might think. See https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ for some background. > I can't see where this qualifies as a wishlist item. The service advertises a feature and doesn't provide it. To me, that's a bug. Which service? This problem crosses an integration point: the upstream sshd daemon versus the service manager. In any case, arguing about whether it is a bug or a feature doesn't change anything. If you'd like to see this fixed properly, please volunteer your time upstream to implement the proposed solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in portable OpenSSH: New Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
