[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

[Bill Gradwohl]

I installed version 16LTS recently and just upgraded the box to 18LTS
and both display the error.

I have 2 NICs (Private / Public) with an sshd config file set to only
listen to the private side. It appears sshd attempt to start after the
Public NIC is up, but before the private NIC is available. The Private
NIC becomes available several seconds after sshd is initiated according
to journalctl.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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