systemd:在更新删除后，用户守护进程无法启动。
systemd:在更新删除后，用户守护进程无法启动。
提问于 2020-11-07 16:42:28
大约在上周末，我的快照停止工作，包括Ubuntu软件。结果发现，snap突然不再安装了。此外，音频完全停止工作，在那一点上，我认为这与snap有关，因为我从安装了"PulseAudio卷控制(gtk)“。
我用snap重新安装了apt install snap，所有的快照都正常运行。即使经过多次重新启动，音频仍然无法工作。手动启动脉冲与pulseaudio --start修复音频，直到下次重新启动。我开始研究为什么在启动后没有启动Pulse，但是请注意，我对systemd一无所知。当然，在这个问题发生之前，我并没有和systemd打交道。所以我想是一些更新引起的？
显然，upowerd和用户服务在启动后无法启动：
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
upower.service loaded failed failed Daemon for power management
user@1000.service loaded failed failed User Manager for UID 1000
user@125.service loaded failed failed User Manager for UID 125 $ id -un 1000生成我的用户名，$ id -un 125生成gdm (Gnome？)。
试图连接到upowerd会产生以下结果：
$ upower
(upower:4492): UPower-WARNING **: 17:02:55.585: Cannot connect to upowerd: Error calling StartServiceByName for org.freedesktop.UPower: Timeout was reached尝试使用systemctl标志调用任何--user命令总是会返回Process org.freedesktop.systemd1 exited with status 1。
我检查了所有三个服务的状态：
$ systemctl status user@1000
user@1000.service - User Manager for UID 1000
Loaded: loaded (/lib/systemd/system/user@.service; static; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/user@.service.d
└─timeout.conf
Active: failed (Result: exit-code) since Sat 2020-11-07 17:52:27 CET; 53min left
Docs: man:user@.service(5)
Process: 1307 ExecStart=/lib/systemd/systemd --user (code=exited, status=224/PAM)
Main PID: 1307 (code=exited, status=224/PAM)
Nov 07 17:52:27 systemd[1]: user@1000.service: Main process exited, code=exited, status=22>
Nov 07 17:52:27 systemd[1307]: PAM adding faulty module: pam_umask.so
Nov 07 17:52:27 systemd[1]: user@1000.service: Failed with result 'exit-code'.
Nov 07 17:52:27 systemd[1307]: PAM unable to dlopen(pam_systemd.so): /lib/security/pam_sys>
Nov 07 17:52:27 systemd[1307]: PAM adding faulty module: pam_systemd.so
Nov 07 17:52:27 systemd[1307]: PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so:>
Nov 07 17:52:27 systemd[1307]: PAM adding faulty module: pam_cap.so
Nov 07 17:52:27 systemd[1307]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/p>
Nov 07 17:52:27 systemd[1307]: PAM adding faulty module: pam_gnome_keyring.so
Nov 07 17:52:27 systemd[1]: Failed to start User Manager for UID 1000.$ systemctl status user@125
user@125.service - User Manager for UID 125
Loaded: loaded (/lib/systemd/system/user@.service; static; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/user@.service.d
└─timeout.conf
Active: failed (Result: exit-code) since Sat 2020-11-07 17:52:16 CET; 52min left
Docs: man:user@.service(5)
Process: 943 ExecStart=/lib/systemd/systemd --user (code=exited, status=224/PAM)
Main PID: 943 (code=exited, status=224/PAM)
Nov 07 17:52:16 systemd[943]: PAM adding faulty module: pam_umask.so
Nov 07 17:52:16 systemd[1]: user@125.service: Main process exited, code=exited, status=224>
Nov 07 17:52:16 systemd[943]: PAM unable to dlopen(pam_systemd.so): /lib/security/pam_syst>
Nov 07 17:52:16 systemd[1]: user@125.service: Failed with result 'exit-code'.
Nov 07 17:52:16 systemd[943]: PAM adding faulty module: pam_systemd.so
Nov 07 17:52:16 systemd[943]: PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so: >
Nov 07 17:52:16 systemd[943]: PAM adding faulty module: pam_cap.so
Nov 07 17:52:16 systemd[943]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pa>
Nov 07 17:52:16 systemd[943]: PAM adding faulty module: pam_gnome_keyring.so
Nov 07 17:52:16 systemd[1]: Failed to start User Manager for UID 125.因此，PAM是某种身份验证，它应该在启动后进行，但却以某种方式失败？如何手动使PAM进行身份验证？
$ systemctl status upower
upower.service - Daemon for power management
Loaded: loaded (/lib/systemd/system/upower.service; disabled; vendor preset: enabled)
Active: failed (Result: signal) since Sat 2020-11-07 16:53:14 CET; 3min 26s ago
Docs: man:upowerd(8)
Process: 3163 ExecStart=/usr/lib/upower/upowerd (code=killed, signal=SYS)
Main PID: 3163 (code=killed, signal=SYS)
Nov 07 16:53:14 systemd[1]: upower.service: Scheduled restart job, restart counter is at 5.
Nov 07 16:53:14 systemd[1]: Stopped Daemon for power management.
Nov 07 16:53:14 systemd[1]: upower.service: Start request repeated too quickly.
Nov 07 16:53:14 systemd[1]: upower.service: Failed with result 'signal'.
Nov 07 16:53:14 systemd[1]: Failed to start Daemon for power management.检查systemd-logs会告诉我，它尝试启动upowerd 5次，在多次失败后放弃(修改后只显示重复5次的1项)：
$ journalctl -xe
Nov 07 17:02:30 systemd[1]: Starting Daemon for power management...
-- Subject: A start job for unit upower.service has begun execution
--
-- A start job for unit upower.service has begun execution.
--
-- The job identifier is 2811.
Nov 07 17:02:30 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>
Nov 07 17:02:30 kernel: kauditd_printk_skb: 16 callbacks suppressed
Nov 07 17:02:30 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>
Nov 07 17:02:30 systemd[1]: upower.service: Main process exited, code=killed, status=31/SYS
-- Subject: Unit process exited
--
-- An ExecStart= process belonging to unit upower.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 31.我在这里束手无策。我试着重新设置失败的服务systemctl reset-failed并重新启动，但是它没有改变什么？
知道我能尝试什么或者我应该检查哪一个日志吗？
回答 1
Ask Ubuntu用户
回答已采纳
发布于 2020-11-08 19:33:54
我也有同样的问题，丢失的管理单元包和相同的错误，失败的服务。原来它是在/lib/security中寻找amd64上不存在的pam模块。删除了快照的相同更新怪癖在我的64位计算机上安装了systemd:i 386。修复是为了sudo apt install systemd:amd64 systemd-timesyncd:amd64
请参阅“发射台：https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1903273”
页面原文内容由Ask Ubuntu提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://askubuntu.com/questions/1290430
复制相关文章
相似问题
腾讯云开发者
