[Bug 1814124] Re: sshd does not start after update

[Robie Basak]

> The entry in /usr/lib/tmpfiles.d/sshd.conf SHOULD be...

I don't agree, even if this happens to work for you. It's valid for it
to be /var/run/sshd provided that your system is properly up-to-date
(see related bug 1804847). If you're using some environment that is
broken, please ask the people who develop that environment to fix the
problem.

I'm reluctant to "just" proposed to change it the other way in a stable
release, because other users may be regressed in other ways by that
change. If your system is broken in this behaviour, it may be broken in
other ways too that will manifest later.

Since there's no action planned to be taken in Ubuntu for this
behaviour, I'm marking the bug status Invalid to make this clear to
users.

For users with broken systems, the workaround for this specific symptom
(rather than the general problem) is to override your tmpfiles.d entry
in /etc/tmpfiles.d. DO NOT EDIT /usr/lib/tmpfiles.d/sshd.conf since this
will be overwritten in a future package update. The right way to make
local configuration changes is in /etc/tmpfiles.d/. See tmpfiles.d(5)
for details. I'd appreciate if somebody could test and provide step-by-
step instructions to help other users.

** Changed in: openssh (Ubuntu)
       Status: Incomplete => Invalid

** Description changed:

+ [Triage Notes]
+ 
+ This issue is caused on Ubuntu derivatives due to problematic symlink
+ handling on those systems. See bug 1804847 for details, and comment 10
+ below for details.
+ 
+ Proper Ubuntu systems do not appear to be affected.
+ 
+ [Original Description]
+ 
  After processing system update by:
  apt-get clean && apt-get autoclean && apt-get autoremove && apt-get update && apt-get upgrade && apt-get dist-upgrade && reboot
  
  ssh server stops starting at system boot.
  
  It starts after doing:
  mkdir /var/run/sshd
  chmod 0755 /var/run/sshd
  service ssh start
  
  It happens on fresh Ubuntu-16.04 installs on every VPS provide I have
  tested so far.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.6
  Uname: Linux 2.6.32-042stab127.2 x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Jan 31 10:18:56 2019
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
+  TERM=xterm
+  PATH=(custom, no user)
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  [Triage Notes]
  
  This issue is caused on Ubuntu derivatives due to problematic symlink
  handling on those systems. See bug 1804847 for details, and comment 10
- below for details.
+ below for details and a workaround.
  
  Proper Ubuntu systems do not appear to be affected.
  
  [Original Description]
  
  After processing system update by:
  apt-get clean && apt-get autoclean && apt-get autoremove && apt-get update && apt-get upgrade && apt-get dist-upgrade && reboot
  
  ssh server stops starting at system boot.
  
  It starts after doing:
  mkdir /var/run/sshd
  chmod 0755 /var/run/sshd
  service ssh start
  
  It happens on fresh Ubuntu-16.04 installs on every VPS provide I have
  tested so far.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.6
  Uname: Linux 2.6.32-042stab127.2 x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Jan 31 10:18:56 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- sshd does not start after update
+ sshd does not start after update on non-Ubuntu kernels where fchownat() is broken

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

Title:
  sshd does not start after update on non-Ubuntu kernels where
  fchownat() is broken

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  [Triage Notes]

  This issue is caused on Ubuntu derivatives due to problematic symlink
  handling on those systems. See bug 1804847 for details, and comment 10
  below for details and a workaround.

  Proper Ubuntu systems do not appear to be affected.

  [Original Description]

  After processing system update by:
  apt-get clean && apt-get autoclean && apt-get autoremove && apt-get update && apt-get upgrade && apt-get dist-upgrade && reboot

  ssh server stops starting at system boot.

  It starts after doing:
  mkdir /var/run/sshd
  chmod 0755 /var/run/sshd
  service ssh start

  It happens on fresh Ubuntu-16.04 installs on every VPS provide I have
  tested so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.6
  Uname: Linux 2.6.32-042stab127.2 x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Jan 31 10:18:56 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1814124/+subscriptions