[SOLVED] LXC Mantic Minotaur (upgraded from Lunar) - systemctl degraded

[papatikka]

Hello!

I upgraded lxc from lunar template available at proxmox gui, to mantic due to get app versions that I want

cat /etc/os-release
PRETTY_NAME="Ubuntu Mantic Minotaur (development branch)"
NAME="Ubuntu"
VERSION_ID="23.10"
VERSION="23.10 (Mantic Minotaur)"
VERSION_CODENAME=mantic
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=mantic
LOGO=ubuntu-logo

When running systemctl

systemctl status
State: degraded
    Units: 252 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 6 units
    Since: Fri 2023-06-30 08:22:14 UTC; 1min 51s ago
  systemd: 252.5-2ubuntu3

6 units are failing, these units are:

systemctl --failed
  UNIT                               LOAD   ACTIVE SUB    DESCRIPTION                      
* ssh.service                        loaded failed failed OpenBSD Secure Shell server
* systemd-sysctl.service             loaded failed failed Apply Kernel Variables
* systemd-sysusers.service           loaded failed failed Create System Users
* systemd-tmpfiles-setup-dev.service loaded failed failed Create Static Device Nodes in /dev
* systemd-tmpfiles-setup.service     loaded failed failed Create Volatile Files and Directories
* ssh.socket                         loaded failed failed OpenBSD Secure Shell server socket

Journal -b

Jun 30 08:22:15 fooContainer systemd[53]: systemd-sysctl.service: Failed at step CREDENTIALS spawning /lib/systemd/systemd-sysctl: Protocol error
Jun 30 08:22:15 fooContainer systemd[57]: systemd-sysusers.service: Failed at step CREDENTIALS spawning systemd-sysusers: Protocol error
Jun 30 08:22:15 fooContainer keyboard-setup.sh[58]: Couldn't get a file descriptor referring to the console.
Jun 30 08:22:15 fooContainer keyboard-setup.sh[59]: Couldn't get a file descriptor referring to the console.
Jun 30 08:22:15 fooContainer systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Persistent Storage...
Jun 30 08:22:15 fooContainer keyboard-setup.sh[61]: Couldn't get a file descriptor referring to the console
Jun 30 08:22:15 fooContainer systemd[62]: systemd-tmpfiles-setup-dev.service: Failed at step CREDENTIALS spawning systemd-tmpfiles: Protocol error
Jun 30 08:22:15 fooContainer systemd[1]: systemd-tmpfiles-setup-dev.service: Main process exited, code=exited, status=243/CREDENTIALS
Jun 30 08:22:15 fooContainer systemd[1]: systemd-tmpfiles-setup-dev.service: Failed with result 'exit-code'.
Jun 30 08:22:15 fooContainer systemd[1]: Failed to start systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.


Jun 30 08:22:15 fooContainer systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Jun 30 08:22:15 fooContainer systemd[1]: Starting systemd-logind.service - User Login Management...
Jun 30 08:22:15 fooContainer systemd[1]: ua-reboot-cmds.service - Ubuntu Pro reboot cmds was skipped because of an unmet condition check (ConditionPathExists=/var/lib/ubuntu-ad>
Jun 30 08:22:15 fooContainer dbus-daemon[97]: [system] AppArmor D-Bus mediation is enabled
Jun 30 08:22:15 fooContainer systemd[1]: Started dbus.service - D-Bus System Message Bus.
Jun 30 08:22:15 fooContainer sshd[102]: Missing privilege separation directory: /run/sshd
Jun 30 08:22:15 fooContainer systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 30 08:22:15 fooContainer systemd[1]: ssh.service: Failed with result 'exit-code'.
Jun 30 08:22:15 fooContainer systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.

No issues when checking journalctl -xa

How can I solve these problems? Any help appreciated!

 

[papatikka]

Update: There was problem with logrotate that I did not detect at the creation of this thread.

Logrotate had "no files problem"

I solved it by following debugging and redoing rotation files

logrotate -f -d /etc/logrotate.conf

Then I looked at ssh.service, went along something like this

systemctl stop ssh.service
systemctl disable ssh.socket
systemctl startssh.service

And then I enabled nesting too from VE-gui for the lxc!

Then I rebooted LXC and all degrades went away. Running prime with no fails!