为什么我不能用正确的密码登录？

Question

Apr  6 01:05:11 ASUS-tek systemd-logind[1108]: Failed to create inotify watch on /var/run/utmp, ignoring: No space left on device
Apr  6 01:05:11 ASUS-tek systemd-logind[1108]: New session c2 of user prosec.
Apr  6 01:05:11 ASUS-tek systemd: pam_limits(systemd-user:session): wrong limit value 'hard' for limit type 'hard'
Apr  6 01:05:11 ASUS-tek systemd: pam_unix(systemd-user:session): session opened for user prosec by (uid=0)
Apr  6 01:05:11 ASUS-tek lightdm: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Apr  6 01:05:11 ASUS-tek systemd-logind[1108]: Session c2 logged out. Waiting for processes to exit.
Apr  6 01:05:12 ASUS-tek lightdm: pam_limits(lightdm-greeter:session): wrong limit value 'hard' for limit type 'hard'
Apr  6 01:05:12 ASUS-tek lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Apr  6 01:05:12 ASUS-tek systemd-logind[1108]: Failed to create inotify watch on /var/run/utmp, ignoring: No space left on device
Apr  6 01:05:12 ASUS-tek systemd-logind[1108]: New session c3 of user lightdm.
Apr  6 01:05:12 ASUS-tek lightdm: gkr-pam: gnome-keyring-daemon started properly
Apr  6 01:05:13 ASUS-tek lightdm: pam_succeed_if(lightdm:auth): incomplete condition detected
Apr  6 01:05:21 ASUS-tek systemd-logind[1108]: Removed session c1.
Apr  6 01:05:24 ASUS-tek dbus-daemon[1050]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Apr  6 01:05:25 ASUS-tek systemd-logind[1108]: Power key pressed.
Apr  6 01:05:25 ASUS-tek systemd-logind[1108]: Powering Off...
Apr  6 01:05:25 ASUS-tek systemd-logind[1108]: System is powering down.
Apr  6 01:05:25 ASUS-tek lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
Apr  6 01:07:39 ASUS-tek systemd-logind[1100]: Failed to create inotify watch on /var/run/utmp, ignoring: No space left on device
Apr  6 01:07:39 ASUS-tek systemd-logind[1100]: New seat seat0.
Apr  6 01:07:39 ASUS-tek systemd-logind[1100]: Watching system buttons on /dev/input/event0 (Lid Switch)
Apr  6 01:07:39 ASUS-tek systemd-logind[1100]: Watching system buttons on /dev/input/event1 (Power Button)
Apr  6 01:07:39 ASUS-tek systemd-logind[1100]: Watching system buttons on /dev/input/event5 (Logitech USB Receiver Consumer Control)
Apr  6 01:07:39 ASUS-tek systemd-logind[1100]: Watching system buttons on /dev/input/event2 (AT Translated Set 2 keyboard)
Apr  6 01:07:49 ASUS-tek lightdm: pam_limits(lightdm-greeter:session): wrong limit value 'hard' for limit type 'hard'
Apr  6 01:07:49 ASUS-tek lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Apr  6 01:07:49 ASUS-tek systemd-logind[1100]: Failed to create inotify watch on /var/run/utmp, ignoring: No space left on device
Apr  6 01:07:49 ASUS-tek systemd-logind[1100]: New session c1 of user lightdm.
Apr  6 01:07:49 ASUS-tek systemd: pam_limits(systemd-user:session): wrong limit value 'hard' for limit type 'hard'
Apr  6 01:07:49 ASUS-tek systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Apr  6 01:07:50 ASUS-tek lightdm: gkr-pam: gnome-keyring-daemon started properly
Apr  6 01:07:51 ASUS-tek lightdm: pam_succeed_if(lightdm:auth): incomplete condition detected
Apr  6 01:07:53 ASUS-tek systemd-logind[1100]: System is rebooting.
Apr  6 01:07:53 ASUS-tek lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm

我有足够的自由空间。

恢复模式：

root@ASUS-tek:~# df
df: /root/.cache/doc: Operation not permitted
Filesystem     1K-blocks      Used Available Use% Mounted on
udev             7809992         0   7809992   0% /dev
tmpfs            1576896      1596   1575300   1% /run
/dev/nvme1n1p5 134229752  25579448 101758940  21% /
tmpfs            7884460         0   7884460   0% /dev/shm
tmpfs               5120         4      5116   1% /run/lock
tmpfs            7884460         0   7884460   0% /sys/fs/cgroup
/dev/nvme1n1p4  57819156  10605124  44244536  20% /var
/dev/nvme1n1p3  19509484    918652  17574464   5% /boot
/dev/nvme1n1p2   9740796        96   9224300   1% /tmp
/dev/nvme1n1p6 255619604 129112864 113449204  54% /home
/dev/loop0           384       384         0 100% /snap/bpytop/256
/dev/nvme1n1p1    997456      6196    991260   1% /boot/efi
/dev/loop1           128       128         0 100% /snap/bare/5
/dev/loop2         93952     93952         0 100% /snap/gtk-common-themes/1535
/dev/loop3         88064     88064         0 100% /snap/session-desktop/275
/dev/loop4           384       384         0 100% /snap/bpytop/261
/dev/loop5        224256    224256         0 100% /snap/gnome-3-34-1804/77

我将fs.inotify.max_user_watches=1048576添加到sysctl.conf中，结果不变。这是在系统更新之后发生的。是不是有什么东西覆盖了配置文件？

Answer 1

lightdm: pam_limits(systemd-user:session): wrong limit value 'hard' for limit type 'hard'

在/etc/security/limits.conf文件或任何/etc/security/limits.d/*.conf文件中，似乎都存在错误。

在资源限制配置文件中，每个非空的非注释行应该有四个字段：

• 应用限制的域：username、@groupname或通配符* (特例：%和%groupname表示maxlogin限制)
• 极限类型：soft或hard
• 限制项:您计划分配的限制的名称
• 限值:通常是一个数字

错误消息表明，第四个字段中有一个单词hard (限值)，这将是不正确的。

可能是格式错误的行导致将相应的限制设置为0或其他一些极具限制性的值，这将导致会话失败？

如果是这样的话，那么错误消息Failed to create inotify watch on /var/run/utmp, ignoring: No space left on device实际上可能是由于遇到了错误设置的资源限制而导致的。

lightdm: pam_succeed_if(lightdm:auth): incomplete condition detected

这表明/etc/pam.d/lightdm文件中可能存在错误、截断或其他形式的损坏，或者使用@include语句引用的文件之一。错误似乎出现在一条auth行上。

有关正确语法的说明，请参见man pam_succeed_if 或者在这里。简单地说，一个条件应该是一个由三个单词组成的组:字段名、测试和要测试的值。

Answer 2

这是由于达到inotify服务的调用限制而导致的错误，systemd正在使用inotify服务。可以使用以下命令增加inotify服务的调用限制：

sysctl fs.inotify.max_user_watches=1048576

https://github.com/google/cadvisor/issues/1581#issuecomment-367616070

但是，您无法输入shell，您可以从包含OS映像的USB内存启动，挂载您一直使用的磁盘，然后将chroot发送到它以执行上述命令。

Answer 3

关键错误是

设备上没有剩余空间

磁盘空间已经用完，这使您无法登录。

您需要在恢复模式下启动并释放一些磁盘空间。