I created Bug 1774788 which is for rsyncd not starting at boot and was
provided with a fix by Andreas Hasenack that works. I tried using that
fix for ssh and it does not work.

Both services fail when an attempt is made to specify a particular NIC
via their respective config files. In the case of rsync, the fix was to
create the override.conf file containing:

[Unit]
After=network.target,network-online.target

via the command systemctl edit rsync.service

Using a similar procedure to create the override.conf file for ssh does
not fix the ssh daemon startup issue. I'm curious as to why that is.

-- 
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

Reply via email to