systemd：更新删除快照后用户守护程序无法启动

Question

上周末左右，我的快照停止工作，包括 Ubuntu 软件。结果突然snap就不再安装了。音频也完全停止工作，此时我认为这与 snap 有关，因为我从 Ubuntu 软件商店安装了“PulseAudio Volume Control (gtk)”。

\n

我重新安装了snap，apt install snap所有的快照都再次正常工作。即使多次重新启动后，音频仍然无法工作。手动启动 Pulsepulseaudio --start可修复音频，直至下次重新启动。我开始调查为什么 Pulse 守护进程在启动后没有启动，但请注意，我对systemd. systemd当然，在这个问题之前我并没有乱搞。所以我猜是某些更新造成的？

\n

显然upowerd，用户服务在启动后无法启动：

\n

$ systemctl --failed\nUNIT              LOAD   ACTIVE SUB    DESCRIPTION                \nupower.service    loaded failed failed Daemon for power management\nuser@1000.service loaded failed failed User Manager for UID 1000  \nuser@125.service  loaded failed failed User Manager for UID 125 \n

\n

$ id -un 1000产生我的用户名并$ id -un 125产生gdm（Gnome 显示管理器？）。

\n

尝试连接会upowerd产生以下结果：

\n

$ upower\n(upower:4492): UPower-WARNING **: 17:02:55.585: Cannot connect to upowerd: Error calling StartServiceByName for org.freedesktop.UPower: Timeout was reached\n

\n

尝试使用systemctl该标志调用任何命令--user将始终返回Process org.freedesktop.systemd1 exited with status 1。

\n

我检查了所有 3 个服务的状态：

\n

$ systemctl status user@1000\nuser@1000.service - User Manager for UID 1000\n   Loaded: loaded (/lib/systemd/system/user@.service; static; vendor preset: enabled)\n  Drop-In: /usr/lib/systemd/system/user@.service.d\n           \xe2\x94\x94\xe2\x94\x80timeout.conf\n   Active: failed (Result: exit-code) since Sat 2020-11-07 17:52:27 CET; 53min left\n     Docs: man:user@.service(5)\n  Process: 1307 ExecStart=/lib/systemd/systemd --user (code=exited, status=224/PAM)\n Main PID: 1307 (code=exited, status=224/PAM)\n\nNov 07 17:52:27 <MyUser-MyComputer> systemd[1]: user@1000.service: Main process exited, code=exited, status=22>\nNov 07 17:52:27 <MyUser-MyComputer> systemd[1307]: PAM adding faulty module: pam_umask.so\nNov 07 17:52:27 <MyUser-MyComputer> systemd[1]: user@1000.service: Failed with result 'exit-code'.\nNov 07 17:52:27 <MyUser-MyComputer> systemd[1307]: PAM unable to dlopen(pam_systemd.so): /lib/security/pam_sys>\nNov 07 17:52:27 <MyUser-MyComputer> systemd[1307]: PAM adding faulty module: pam_systemd.so\nNov 07 17:52:27 <MyUser-MyComputer> systemd[1307]: PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so:>\nNov 07 17:52:27 <MyUser-MyComputer> systemd[1307]: PAM adding faulty module: pam_cap.so\nNov 07 17:52:27 <MyUser-MyComputer> systemd[1307]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/p>\nNov 07 17:52:27 <MyUser-MyComputer> systemd[1307]: PAM adding faulty module: pam_gnome_keyring.so\nNov 07 17:52:27 <MyUser-MyComputer> systemd[1]: Failed to start User Manager for UID 1000.\n

\n

$ systemctl status user@125\nuser@125.service - User Manager for UID 125\n   Loaded: loaded (/lib/systemd/system/user@.service; static; vendor preset: enabled)\n  Drop-In: /usr/lib/systemd/system/user@.service.d\n           \xe2\x94\x94\xe2\x94\x80timeout.conf\n   Active: failed (Result: exit-code) since Sat 2020-11-07 17:52:16 CET; 52min left\n     Docs: man:user@.service(5)\n  Process: 943 ExecStart=/lib/systemd/systemd --user (code=exited, status=224/PAM)\n Main PID: 943 (code=exited, status=224/PAM)\n\nNov 07 17:52:16 <MyUser-MyComputer> systemd[943]: PAM adding faulty module: pam_umask.so\nNov 07 17:52:16 <MyUser-MyComputer> systemd[1]: user@125.service: Main process exited, code=exited, status=224>\nNov 07 17:52:16 <MyUser-MyComputer> systemd[943]: PAM unable to dlopen(pam_systemd.so): /lib/security/pam_syst>\nNov 07 17:52:16 <MyUser-MyComputer> systemd[1]: user@125.service: Failed with result 'exit-code'.\nNov 07 17:52:16 <MyUser-MyComputer> systemd[943]: PAM adding faulty module: pam_systemd.so\nNov 07 17:52:16 <MyUser-MyComputer> systemd[943]: PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so: >\nNov 07 17:52:16 <MyUser-MyComputer> systemd[943]: PAM adding faulty module: pam_cap.so\nNov 07 17:52:16 <MyUser-MyComputer> systemd[943]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pa>\nNov 07 17:52:16 <MyUser-MyComputer> systemd[943]: PAM adding faulty module: pam_gnome_keyring.so\nNov 07 17:52:16 <MyUser-MyComputer> systemd[1]: Failed to start User Manager for UID 125.\n

\n

那么PAM，是否应该在启动后进行某种身份验证，但不知何故失败了？如何手动让 PAM 进行身份验证？

\n

$ systemctl status upower\nupower.service - Daemon for power management\n   Loaded: loaded (/lib/systemd/system/upower.service; disabled; vendor preset: enabled)\n   Active: failed (Result: signal) since Sat 2020-11-07 16:53:14 CET; 3min 26s ago\n     Docs: man:upowerd(8)\n  Process: 3163 ExecStart=/usr/lib/upower/upowerd (code=killed, signal=SYS)\n Main PID: 3163 (code=killed, signal=SYS)\n\nNov 07 16:53:14 <MyUser-MyComputer>  systemd[1]: upower.service: Scheduled restart job, restart counter is at 5.\nNov 07 16:53:14 <MyUser-MyComputer>  systemd[1]: Stopped Daemon for power management.\nNov 07 16:53:14 <MyUser-MyComputer>  systemd[1]: upower.service: Start request repeated too quickly.\nNov 07 16:53:14 <MyUser-MyComputer>  systemd[1]: upower.service: Failed with result 'signal'.\nNov 07 16:53:14 <MyUser-MyComputer>  systemd[1]: Failed to start Daemon for power management.\n

\n

检查systemd-logs 显示，它尝试启动upowerd5 次，并在重复失败后放弃（已编辑为仅显示重复 5 次的 1 个条目）：

\n

$ journalctl -xe\nNov 07 17:02:30 <MyUser-MyComputer> systemd[1]: Starting Daemon for power management...\n-- Subject: A start job for unit upower.service has begun execution\n-- \n-- A start job for unit upower.service has begun execution.\n-- \n-- The job identifier is 2811.\nNov 07 17:02:30 <MyUser-MyComputer> audit[4495]: SECCOMP auid=4294967295 uid=0 gid=0 ses=4294967295 pid=4495 comm="upowerd" exe="/usr/lib/upower/upowerd" sig=31 arch=c000003e syscall=12 compat=0 ip=0x>\nNov 07 17:02:30 <MyUser-MyComputer> kernel: kauditd_printk_skb: 16 callbacks suppressed\nNov 07 17:02:30 <MyUser-MyComputer> kernel: audit: type=1326 audit(1604764950.576:8019): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=4495 comm="upowerd" exe="/usr/lib/upower/upowerd" sig=31 arch=c0>\nNov 07 17:02:30 <MyUser-MyComputer> systemd[1]: upower.service: Main process exited, code=killed, status=31/SYS\n-- Subject: Unit process exited\n-- \n-- An ExecStart= process belonging to unit upower.service has exited.\n-- \n-- The process' exit code is 'killed' and its exit status is 31.\n

\n

我已经无计可施了。我尝试重置失败的服务systemctl reset-failed并重新启动，但没有任何改变？

\n

知道我可以尝试什么或者我应该检查哪个日志吗？

\n

Answer 1

我遇到了同样的问题，缺少 snapd 软件包，以及有关失败服务的相同错误。结果它在 /lib/security 中寻找 pam 模块，而 amd64 上不存在该模块。删除 snapd 的相同更新怪癖已在我的 64 位计算机上安装了 systemd:i386。解决办法是sudo apt install systemd:amd64 systemd-timesyncd:amd64

另请参阅启动板：https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1903273