sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd

[JakFrost]

Symptom: ssh.service is not running and not accepting new SSH connections and returns socket closed error upon attempted connection. ssh.service shows a failed with error message "Missing privilege separation directory: /run/sshd".

The following line is needed in the SystemD Unit configuration of the ssh.service file for the openssh-server package to fix what appears to be a race condition when ssh.service is sometimes started before systemd-tmpfiles-setup.service is finished processing the file in /usr/lib/tmpfiles.d/openssh.server.conf that is required to create the /run/sshd directory that is required by ssh.service to start property.

There might be more depth or an alternative reason to why /run/sshd/ still didn't exist after using ```systemctl reset-failed ssh.service```. So more investigation is needed by someone with more background in systemd-tmpfiles-setup.service and openssh-server package after it when to socket activation.

= Error Messages =

```
$journalctl -u ssh.service -b-1

Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 21:30:56 server sshd[1271]: Missing privilege separation directory: /run/sshd
Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1.
Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 21:30:56 server sshd[1369]: Missing privilege separation directory: /run/sshd
Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 2.
Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 21:30:56 server sshd[1454]: Missing privilege separation directory: /run/sshd
Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 3.
Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 21:30:57 server sshd[1465]: Missing privilege separation directory: /run/sshd
Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 4.
Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 21:30:57 server sshd[1475]: Missing privilege separation directory: /run/sshd
Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5.
Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 21:30:57 server systemd[1]: ssh.service: Start request repeated too quickly.
Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:25 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 22:19:25 server sshd[47238]: Missing privilege separation directory: /run/sshd
Mar 02 22:19:25 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 22:19:25 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 22:19:25 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:25 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1.
Mar 02 22:19:25 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:25 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 22:19:25 server sshd[47240]: Missing privilege separation directory: /run/sshd
Mar 02 22:19:25 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 22:19:25 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 22:19:25 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:26 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 2.
Mar 02 22:19:26 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:26 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 22:19:26 server sshd[47241]: Missing privilege separation directory: /run/sshd
Mar 02 22:19:26 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 22:19:26 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 22:19:26 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:26 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 3.
Mar 02 22:19:26 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:26 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 22:19:26 server sshd[47242]: Missing privilege separation directory: /run/sshd
Mar 02 22:19:26 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 22:19:26 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 22:19:26 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:26 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 4.
Mar 02 22:19:26 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:26 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 22:19:26 server sshd[47243]: Missing privilege separation directory: /run/sshd
Mar 02 22:19:26 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 22:19:26 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 22:19:26 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:26 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5.
Mar 02 22:19:26 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:26 server systemd[1]: ssh.service: Start request repeated too quickly.
Mar 02 22:19:26 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 22:19:26 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:37 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 22:19:37 server sshd[47253]: Missing privilege separation directory: /run/sshd
Mar 02 22:19:37 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 22:19:37 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 22:19:37 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:37 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1.
Mar 02 22:19:37 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:37 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 22:19:37 server sshd[47254]: Missing privilege separation directory: /run/sshd
Mar 02 22:19:37 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 22:19:37 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 22:19:37 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:37 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 2.
Mar 02 22:19:37 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:37 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 22:19:37 server sshd[47255]: Missing privilege separation directory: /run/sshd
Mar 02 22:19:37 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 22:19:37 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 22:19:37 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:38 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 3.
Mar 02 22:19:38 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:38 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 22:19:38 server sshd[47256]: Missing privilege separation directory: /run/sshd
Mar 02 22:19:38 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 22:19:38 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 22:19:38 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:38 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 4.
Mar 02 22:19:38 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:38 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Mar 02 22:19:38 server sshd[47257]: Missing privilege separation directory: /run/sshd
Mar 02 22:19:38 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Mar 02 22:19:38 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 22:19:38 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:38 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5.
Mar 02 22:19:38 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:38 server systemd[1]: ssh.service: Start request repeated too quickly.
Mar 02 22:19:38 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 22:19:38 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Mar 02 22:19:45 server systemd[1]: ssh.service: Start request repeated too quickly.
Mar 02 22:19:45 server systemd[1]: ssh.service: Failed with result 'exit-code'.
Mar 02 22:19:45 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
```

Note: Errors showed up a total of 3x5 times because the ```systemctl reset-failed ssh.service``` command was used and it still showed up.

= Add to Package SystemD Unit File =

```
''/lib/systemd/system/ssh.service''

[Unit]
After=systemd-tmpfiles-setup.service
```

= System Configuration =

```
''lsb_release -rd''

No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
```

```
''cat /etc/lsb-release''

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=23.10
DISTRIB_CODENAME=mantic
DISTRIB_DESCRIPTION="Ubuntu 23.10"
```

```
''apt-cache policy openssh-server''

openssh-server:
  Installed: 1:9.3p1-1ubuntu3.2
  Candidate: 1:9.3p1-1ubuntu3.2
  Version table:
 *** 1:9.3p1-1ubuntu3.2 500
        500 http://us.archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1:9.3p1-1ubuntu3 500
        500 http://us.archive.ubuntu.com/ubuntu mantic/main amd64 Packages
```

= Package Configuration Problems =

```
''systemctl --property=After show ssh.service''

After=network.target sysinit.target basic.target auditd.service system.slice ssh.socket pollinate.service systemd-journald.socket
```

```
''systemctl --no-pager --property=Before show systemd-tmpfiles-setup.service''

Before=ssh.service man-db.service logrotate.service systemd-timesyncd.service vgauth.service ModemManager.service fwupd.service e2scrub_reap.service initrd-switch-root.target systemd-update-utmp.service bluetooth.service open-vm-tools.service systemd-resolved.service polkit.service systemd-logind.service cockpit.service sysinit.target upower.service shutdown.target
```

**Note: ssh.service needs to be in the Before= clause above to fix the race condition of the ssh.service starting before the /usr/lib/tmpfiles.d/openssh-server.conf is processed by systemd-tmpfiles-setup.service during start-up sequence otherwise /run/sshd directory won't exist.**

```
''cat /usr/lib/tmpfiles.d/openssh-server.conf''

#Type Path Mode UID GID Age Arguments
D /run/sshd 0755 root root - -
```

= Temporary Solution =

Create the directory and the Unit file with the After= clause to populate the Before= clause for systemd-tmpfiles-setup.service

```
''mkdir -p /etc/systemd/system/ssh.service.d''

cat >/etc/systemd/system/ssh.service.d/after.conf <<EOF
[Unit]
After=systemd-tmpfiles-setup.service
EOF

```

Verify the file.

```
''cat /etc/systemd/system/ssh.service.d/after.conf''

[Unit]
After=systemd-tmpfiles-setup.service
```

```

Reload SystemD config

```
systemctl daemon-reload
```

Verify new active config.

```
''systemctl --no-pager --property=Before show systemd-tmpfiles-setup.service''

Before=... ssh.service ...
```

```
''systemctl --property=After show ssh.service''

After=... systemd-tmpfiles-setup.service ...```

=== End of Bug Report ===

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: openssh-server 1:9.3p1-1ubuntu3.2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sun Mar 3 02:22:39 2024
InstallationDate: Installed on 2020-12-14 (1174 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=putty
SourcePackage: openssh
UpgradeStatus: Upgraded to mantic on 2024-02-26 (6 days ago)

[JakFrost (jakfrost273)]

This is a follow-up to the problems reported in the following thread that already discussed an issue with socket activation for the ssh.service.

SSHd now uses socket-based activation (Ubuntu 22.10 and later)
https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-ubuntu-22-10-and-later/30189/4

[JakFrost (jakfrost273)]

Found this reference also to this folder.

```
''man sshd''

/run/sshd
               chroot(2) directory used by sshd during privilege separation in the pre‐authentication phase. The directory should not contain any files and must be owned by root and not group or world‐writable.
```

[JakFrost (jakfrost273)]

More discussion threads regarding this issue.

This is an old one from 16.04 before ssh socket activation.

https://askubuntu.com/questions/1110828/ssh-failed-to-start-missing-privilege-separation-directory-var-run-sshd

Another older report from 5-years ago from 16.04.05 again.
https://askubuntu.com/questions/1109934/ssh-server-stops-working-after-reboot-caused-by-missing-var-run-sshd/1110843#1110843

Below is an older report from 16.04.05 that probably resulted in the creation of /run/sshd/ by systemd-tmpfiles-setup.service

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580

An even older bug regarding the same issue.
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/45234

Again it shows up.
https://serverfault.com/questions/941855/why-am-i-missing-var-run-sshd-after-every-boot

[JakFrost (jakfrost273)]

When the /run/sshd/ directory exits and looks good.

```
'''stat /run/sshd'''

  File: /run/sshd
  Size: 40 Blocks: 0 IO Block: 4096 directory
Device: 0,25 Inode: 1786 Links: 2
Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2024-03-03 03:43:40.144212455 -0600
Modify: 2024-03-03 03:12:06.919999347 -0600
Change: 2024-03-03 03:12:06.919999347 -0600
 Birth: 2024-03-03 03:12:06.919999347 -0600
```

[JakFrost (jakfrost273)]

I'm looking at the journalctl logs for systemd-tmpfiles-setup.service and sysinit.target/start and it shows up that one of the mount and automount units that I created might have caused a problem and systemd somehow deleted the start events for systemd-tmpfiles-setup.service/start event.

This line below shows a possible problem.

''sysinit.target: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/start''

```
''journalctl --no-pager --no-hostname -b-2 --grep=systemd-tmpfiles-setup.service''

Mar 02 21:30:54 systemd[1]: sysinit.target: Found dependency on systemd-tmpfiles-setup.service/start
Mar 02 21:30:54 systemd[1]: sysinit.target: Found dependency on systemd-tmpfiles-setup.service/start
Mar 02 21:30:54 systemd[1]: network.target: Found dependency on systemd-tmpfiles-setup.service/start
Mar 02 21:30:54 systemd[1]: sysinit.target: Found ordering cycle on systemd-tmpfiles-setup.service/start
Mar 02 21:30:54 systemd[1]: sysinit.target: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/start
Mar 02 21:30:55 systemd[1]: sysinit.target: Found dependency on systemd-tmpfiles-setup.service/start
Mar 02 21:30:55 systemd[1]: sysinit.target: Found dependency on systemd-tmpfiles-setup.service/start
Mar 02 21:30:55 systemd[1]: network.target: Found dependency on systemd-tmpfiles-setup.service/start
Mar 02 21:30:55 systemd[1]: sysinit.target: Found ordering cycle on systemd-tmpfiles-setup.service/start
Mar 02 21:30:55 systemd[1]: sysinit.target: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/start
```

```
''journalctl --no-pager --no-hostname -b-2 -u '*.target'''

Mar 02 21:30:54 systemd[1]: Reached target local-fs-pre.target - Preparation for Local File Systems.
Mar 02 21:30:54 systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).
Mar 02 21:30:54 systemd[1]: Reached target cryptsetup.target - Local Encrypted Volumes.
Mar 02 21:30:55 systemd[1]: Reached target swap.target - Swaps.
Mar 02 21:30:55 systemd[1]: local-fs.target: Found ordering cycle on mnt-xbmc\x2ddata.automount/start
Mar 02 21:30:55 systemd[1]: local-fs.target: Found dependency on remote-fs-pre.target/start
Mar 02 21:30:55 systemd[1]: local-fs.target: Found dependency on open-iscsi.service/start
Mar 02 21:30:55 systemd[1]: local-fs.target: Found dependency on network-online.target/start
Mar 02 21:30:55 systemd[1]: local-fs.target: Found dependency on network.target/start
Mar 02 21:30:55 systemd[1]: local-fs.target: Found dependency on wpa_supplicant.service/start
Mar 02 21:30:55 systemd[1]: local-fs.target: Found dependency on basic.target/start
Mar 02 21:30:55 systemd[1]: local-fs.target: Found dependency on sysinit.target/start
Mar 02 21:30:55 systemd[1]: local-fs.target: Found dependency on apparmor.service/start
Mar 02 21:30:55 systemd[1]: local-fs.target: Found dependency on local-fs.target/start
Mar 02 21:30:55 systemd[1]: local-fs.target: Job remote-fs-pre.target/start deleted to break ordering cycle starting with local-fs.target/start
Mar 02 21:3...

[JakFrost (jakfrost273)]

I've changed the Unit files for the mount and automount points and will see if this was the cause of the unit ordering issue. I commented out the Requires= files and just left the After= files to create a softer dependency tree.

```
''# cat mnt-xbmc\\x2ddata.mount''

[Unit]
Description=mount cifs \\xbmc\data to /mnt/xbmc-data
#Requires=network-online.target nss-lookup.target systemd-resolved.service
After=remote-fs-pre.target network-online.target nss-lookup.target systemd-resolved.service

[Mount]
Where=/mnt/xbmc-data
What=//xbmc/data
Type=cifs
Options=credentials=/etc/samba/xbmc-smbuser.cred

[Install]
WantedBy=multi-user.target
```

```
''root@htpc:/etc/systemd/system# cat mnt-xbmc\\x2ddata.automount''

[Unit]
Description=automount cifs \\xbmc\data to /mnt/xbmc-data
#Requires=remote-fs-pre.target
After=remote-fs-pre.target network-online.target nss-lookup.target systemd-resolved.service

[Automount]
Where=/mnt/xbmc-data
TimeoutIdleSec=0

[Install]
WantedBy=remote-fs.target
```

[Nick Rosbrook (enr0n)]

I think we originally broke this out into a tmpfile since the openssh-server.postinst was calling sshd -G to parse config. However, with the sshd-socket-generator approach, we don't call sshd directly anymore, so we could probably just go back to setting RuntimeDirectory=/run/sshd in ssh.service.

[Launchpad Janitor (janitor)]

This bug was fixed in the package openssh - 1:9.6p1-3ubuntu11

---------------
openssh (1:9.6p1-3ubuntu11) noble; urgency=medium

  * d/t/ssh-gssapi: make the test a bit more rebust (LP: #2058276):
    - deal with return codes
    - match a more specific success expression from the logs
    - add klist output in the case of failure

 -- Andreas Hasenack <email address hidden> Mon, 18 Mar 2024 10:25:15 -0300