我使用 Fedora 31 并尝试解决我收到从 Rawhide 升级软件包的建议的错误。我已经安装了存储库，dnf install fedora-repos-rawhide然后尝试升级单个包。由于 GPG 问题，此操作失败：

# env LC_ALL=C dnf --enablerepo=rawhide update texlive-microtype
Last metadata expiration check: 0:02:15 ago on Wed Nov 13 10:11:12 2019.
Modular dependency problems:

 Problem 1: conflicting requests
  - nothing provides module(platform:f31) needed by module afterburn:rolling:3120190921123425:22d7e2a5-0.x86_64
 Problem 2: conflicting requests
  - nothing provides module(platform:f31) needed by module avocado:69lts:3120190813194337:f636be4b-0.x86_64
 Problem 3: conflicting requests
  - nothing provides module(platform:f31) needed by module meson:latest:3120190826183302:dc56099c-0.x86_64
 Problem 4: conflicting requests
  - nothing provides module(platform:f31) needed by module zram-generator:rolling:3120190813200958:22d7e2a5-0.x86_64
 Problem 5: conflicting requests
  - nothing provides module(platform:f31) needed by module afterburn:rolling:3120191015163839:22d7e2a5-0.x86_64
 Problem 6: conflicting requests
  - nothing provides module(platform:f31) needed by module avocado:69lts:3120191004211344:f636be4b-0.x86_64
 Problem 7: conflicting requests
  - nothing provides module(platform:f31) needed by module meson:latest:3120191009081836:dc56099c-0.x86_64
 Problem 8: conflicting requests
  - nothing provides module(platform:f31) needed by module zram-generator:rolling:3120191009082925:22d7e2a5-0.x86_64
 Problem 9: conflicting requests
  - nothing provides module(platform:f31) needed by module zola:rolling:3120190922161148:22d7e2a5-0.x86_64
 Problem 10: conflicting requests
  - nothing provides module(platform:f31) needed by module zincati:rolling:3120190926112556:22d7e2a5-0.x86_64
 Problem 11: conflicting requests
  - nothing provides module(platform:f31) needed by module tokei:rolling:3120190921122652:22d7e2a5-0.x86_64
 Problem 12: conflicting requests
  - nothing provides module(platform:f31) needed by module stratis:1:3120190907214611:22d7e2a5-0.x86_64
 Problem 13: conflicting requests
  - nothing provides module(platform:f31) needed by module skim:rolling:3120190921123929:22d7e2a5-0.x86_64
 Problem 14: conflicting requests
  - nothing provides module(platform:f31) needed by module silver:rolling:3120190912064049:22d7e2a5-0.x86_64
 Problem 15: conflicting requests
  - nothing provides module(platform:f31) needed by module sd:rolling:3120190921120742:22d7e2a5-0.x86_64
 Problem 16: conflicting requests
  - nothing provides module(platform:f31) needed by module rpick:latest:3120190515141045:4004e21e-0.x86_64
 Problem 17: conflicting requests
  - nothing provides module(platform:f31) needed by module ripgrep:latest:3120190803131619:22d7e2a5-0.x86_64
 Problem 18: conflicting requests
  - nothing provides module(platform:f31) needed by module pretty-git-prompt:rolling:3120190714104357:22d7e2a5-0.x86_64
 Problem 19: conflicting requests
  - nothing provides module(platform:f31) needed by module ninja:latest:3120190304180949:f636be4b-0.x86_64
 Problem 20: conflicting requests
  - nothing provides module(platform:f31) needed by module newsboat:latest:3120190728140405:22d7e2a5-0.x86_64
 Problem 21: conflicting requests
  - nothing provides module(platform:f31) needed by module minetest:5:3120190308194723:f636be4b-0.x86_64
 Problem 22: conflicting requests
  - nothing provides module(platform:f31) needed by module lsd:rolling:3120190803124134:22d7e2a5-0.x86_64
 Problem 23: conflicting requests
  - nothing provides module(platform:f31) needed by module jmc:latest:3120190813124555:7188e41a-0.x86_64
 Problem 24: conflicting requests
  - nothing provides module(platform:f31) needed by module hyperfine:latest:3120190721071357:22d7e2a5-0.x86_64
 Problem 25: conflicting requests
  - nothing provides module(platform:f31) needed by module heatseeker:latest:3120190921124230:22d7e2a5-0.x86_64
 Problem 26: conflicting requests
  - nothing provides module(platform:f31) needed by module gimp:2.10:3120190904121229:f636be4b-0.x86_64
 Problem 27: conflicting requests
  - nothing provides module(platform:f31) needed by module fish:3:3120190219150858:6045e57d-0.x86_64
 Problem 28: conflicting requests
  - nothing provides module(platform:f31) needed by module ffsend:latest:3120190812145625:22d7e2a5-0.x86_64
 Problem 29: conflicting requests
  - nothing provides module(platform:f31) needed by module fedora-coreos-pinger:rolling:3120190813195119:22d7e2a5-0.x86_64
 Problem 30: conflicting requests
  - nothing provides module(platform:f31) needed by module fd-find:rolling:3120190813195105:22d7e2a5-0.x86_64
 Problem 31: conflicting requests
  - nothing provides module(platform:f31) needed by module exa:latest:3120190813195051:22d7e2a5-0.x86_64
 Problem 32: conflicting requests
  - nothing provides module(platform:f31) needed by module eclipse:2019-06:3120190902131726:efdece7d-0.x86_64
 Problem 33: conflicting requests
  - nothing provides module(platform:f31) needed by module dwm:6.2:3120190813195003:f636be4b-0.x86_64
 Problem 34: conflicting requests
  - nothing provides module(platform:f31) needed by module dutree:rolling:3120190926112243:22d7e2a5-0.x86_64
 Problem 35: conflicting requests
  - nothing provides module(platform:f31) needed by module cbindgen:rolling:3120190515070043:4004e21e-0.x86_64
 Problem 36: conflicting requests
  - nothing provides module(platform:f31) needed by module bat:latest:3120190813194409:22d7e2a5-0.x86_64
 Problem 37: conflicting requests
  - nothing provides module(platform:f31) needed by module askalono-cli:rolling:3120190813194323:22d7e2a5-0.x86_64
Dependencies resolved.
=======================================================================================================================
 Package                          Architecture          Version                           Repository              Size
=======================================================================================================================
Upgrading:
 texlive-microtype                noarch                9:svn50187-5.fc32                 rawhide                 67 k

Transaction Summary
=======================================================================================================================
Upgrade  1 Package

Total size: 67 k
Is this ok [y/N]: y
Downloading Packages:
[SKIPPED] texlive-microtype-svn50187-5.fc32.noarch.rpm: Already downloaded                                            
warning: /var/cache/dnf/rawhide-2d95c80a1fa0a67d/packages/texlive-microtype-svn50187-5.fc32.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 12c944d0: NOKEY
Fedora - Rawhide - Developmental packages for the next Fedora release                  1.6 MB/s | 1.6 kB     00:00    
GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-31-x86_64 (0x3C3359C4) is already installed
The GPG keys listed for the "Fedora - Rawhide - Developmental packages for the next Fedora release" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.. Failing package is: texlive-microtype-9:svn50187-5.fc32.noarch
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-31-x86_64
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED

这些步骤似乎是正确的，至少它们是在 2014 年。我错过了一步吗？我是否也需要手动导入 Rawhide 密钥？

我最近将工作站从 Debian 9 升级到了 Debian 10。使用旧版本，人们已经能够安装 USB 驱动器并播放和录制声音（用于视频会议）。更新后两者都不起作用。

远程用户帐户

用户帐户存在一些特殊性，因此这可能是问题的根源。我们使用 NIS 和 NFS 在所有机器上提供用户帐户和主目录。升级到 Debian 10 后，我需要添加一个NISto，/etc/nsswitch.conf因为它们compat之前是打开的，现在只有files. 也ypbind没有运行，因为它不再用作 -broadcast默认启动选项。我在以下位置添加了一个新的 systemd 文件 /etc/systemd/system/ypbind.service：

[Unit]
Description=ypbind
Wants=network-online.target nis.service
After=network-online.target nis.service

[Service]
Type=simple
ExecStart=/usr/sbin/ypbind -broadcast -foreground

[Install]
WantedBy=multi-user.target

这样用户帐户就在那里，主目录也在那里。在命令行上我也可以登录。但是 LightDM 显示管理器仍然不允许用户进入。所以在/etc/lightdm/lightdm.conf部分中[LightDM] 我添加了该选项greeter-show-manual-login = True，从那时起远程用户可以登录。有些机器仍然将 GDM 作为默认设置显示管理器，登录显示与 LightDM 在我更改配置之前所做的相同行为。密码检查通过，屏幕可能会短暂变黑，然后再次显示登录屏幕。当用户超出其配额并且.Xauthority无法创建建立会话 (?) 所需的文件时，也会发生同样的情况。

奇怪的是，当我通过 SSH 登录并在实际屏幕上登录时，这些会话正确显示为who：

$ who
ueding   pts/0        2019-08-26 12:42 (131.220.226.20)
ueding   tty7         2019-08-26 12:43 (:0)

但同时会话未列出loginctl：

$ loginctl
No sessions.

当我使用本地用户帐户在我的个人 Fedora 30 笔记本电脑上执行相同操作时，我得到以下输出who：

$ who
mu       tty1         2019-08-25 10:33 (:0)
mu       pts/0        2019-08-25 10:34 (:0)
mu       pts/1        2019-08-26 12:08 (:0)
mu       pts/2        2019-08-26 12:14 (:0)
mu       pts/3        2019-08-26 12:42 (:0)
mu       pts/4        2019-08-26 12:38 (:0)
mu       pts/5        2019-08-26 12:55 (:0)

并且还loginctl显示了一些明智的东西：

$ loginctl
SESSION  UID USER SEAT  TTY
      1 1000 mu   seat0    

1 sessions listed.

我在其中一个 Debian 10 工作站上创建了一个 UID 为 50000 的新本地用户帐户，发现我可以登录，显示会话，loginctl并且下面描述的可移动媒体和声音问题不存在，声音和可移动媒体作品。所以这绝对是来自 NIS 的用户的问题。

到目前为止，让我印象深刻的一件事是，由于历史原因，我们给出的用户 ID 以 500 开头。但我的用户ueding的 uid 为 1085，所以即使这是未列出帐户的问题，这account 应该没问题，因为不被视为系统用户的用户 ID 的默认起始值​​为 1000。

我没有足够的经验，但我只是觉得不知何故用户帐户没有完全在系统中，只是仍然缺少一些东西。

一位 uid 为 536 的用户在登录后必须输入他的 GNOME 钥匙串密码。我不确定他那里是否有不同的密码，但也可能是在启动过程中没有解锁。不过，这可能并不意味着什么。

授权日志

在当前状态下，这是/var/log/auth.log自启动机器以来显示的所有内容，通过 SSH 以 root 身份连接以检索日志并使用我的 NIS 用户登录机器本身。此外，monitoring用户已通过 SSH 登录以检索我的监控系统的一些信息。

Sep  3 12:45:42 helios systemd-logind[497]: New seat seat0.
Sep  3 12:45:42 helios systemd-logind[497]: Watching system buttons on /dev/input/event1 (Power Button)
Sep  3 12:45:42 helios systemd-logind[497]: Watching system buttons on /dev/input/event0 (Power Button)
Sep  3 12:45:42 helios systemd-logind[497]: Watching system buttons on /dev/input/event3 (Cherry USB keyboard)
Sep  3 12:45:42 helios systemd-logind[497]: Watching system buttons on /dev/input/event4 (Cherry USB keyboard System Control)
Sep  3 12:45:46 helios sshd[650]: Server listening on 0.0.0.0 port 22.
Sep  3 12:45:46 helios sshd[650]: Server listening on :: port 22.
Sep  3 12:45:57 helios lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Sep  3 12:45:57 helios systemd-logind[497]: New session c1 of user lightdm.
Sep  3 12:45:57 helios systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Sep  3 12:47:08 helios sshd[1339]: rexec line 16: Deprecated option UsePrivilegeSeparation
Sep  3 12:47:08 helios sshd[1339]: rexec line 19: Deprecated option KeyRegenerationInterval
Sep  3 12:47:08 helios sshd[1339]: rexec line 20: Deprecated option ServerKeyBits
Sep  3 12:47:08 helios sshd[1339]: rexec line 31: Deprecated option RSAAuthentication
Sep  3 12:47:08 helios sshd[1339]: rexec line 38: Deprecated option RhostsRSAAuthentication
Sep  3 12:47:08 helios sshd[1339]: Connection closed by 131.220.226.3 port 39932 [preauth]
Sep  3 12:47:16 helios sshd[1341]: rexec line 16: Deprecated option UsePrivilegeSeparation
Sep  3 12:47:16 helios sshd[1341]: rexec line 19: Deprecated option KeyRegenerationInterval
Sep  3 12:47:16 helios sshd[1341]: rexec line 20: Deprecated option ServerKeyBits
Sep  3 12:47:16 helios sshd[1341]: rexec line 31: Deprecated option RSAAuthentication
Sep  3 12:47:16 helios sshd[1341]: rexec line 38: Deprecated option RhostsRSAAuthentication
Sep  3 12:47:16 helios sshd[1341]: reprocess config line 31: Deprecated option RSAAuthentication
Sep  3 12:47:16 helios sshd[1341]: reprocess config line 38: Deprecated option RhostsRSAAuthentication
Sep  3 12:47:19 helios sshd[1341]: Accepted password for root from 131.220.226.160 port 44060 ssh2
Sep  3 12:47:19 helios sshd[1341]: pam_unix(sshd:session): session opened for user root by (uid=0)
Sep  3 12:47:19 helios systemd-logind[497]: New session 2 of user root.
Sep  3 12:47:19 helios systemd: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Sep  3 12:47:20 helios sshd[1367]: rexec line 16: Deprecated option UsePrivilegeSeparation
Sep  3 12:47:20 helios sshd[1367]: rexec line 19: Deprecated option KeyRegenerationInterval
Sep  3 12:47:20 helios sshd[1367]: rexec line 20: Deprecated option ServerKeyBits
Sep  3 12:47:20 helios sshd[1367]: rexec line 31: Deprecated option RSAAuthentication
Sep  3 12:47:20 helios sshd[1367]: rexec line 38: Deprecated option RhostsRSAAuthentication
Sep  3 12:47:20 helios sshd[1367]: reprocess config line 31: Deprecated option RSAAuthentication
Sep  3 12:47:20 helios sshd[1367]: reprocess config line 38: Deprecated option RhostsRSAAuthentication
Sep  3 12:47:20 helios sshd[1367]: Accepted publickey for monitoring from 131.220.226.3 port 39970 ssh2: RSA SHA256:ulxULyONiGRB8VUFctWd/WSBcRxjGX+5Dq/IXyZS+gI
Sep  3 12:47:20 helios sshd[1367]: pam_unix(sshd:session): session opened for user monitoring by (uid=0)
Sep  3 12:47:20 helios systemd-logind[497]: New session 4 of user monitoring.
Sep  3 12:47:20 helios systemd: pam_unix(systemd-user:session): session opened for user monitoring by (uid=0)
Sep  3 12:47:20 helios sshd[1385]: Received disconnect from 131.220.226.3 port 39970:11: disconnected by user
Sep  3 12:47:20 helios sshd[1385]: Disconnected from user monitoring 131.220.226.3 port 39970
Sep  3 12:47:20 helios sshd[1367]: pam_unix(sshd:session): session closed for user monitoring
Sep  3 12:47:20 helios systemd-logind[497]: Session 4 logged out. Waiting for processes to exit.
Sep  3 12:47:20 helios systemd-logind[497]: Removed session 4.
Sep  3 12:47:30 helios systemd: pam_unix(systemd-user:session): session closed for user monitoring
Sep  3 12:47:32 helios sshd[1398]: rexec line 16: Deprecated option UsePrivilegeSeparation
Sep  3 12:47:32 helios sshd[1398]: rexec line 19: Deprecated option KeyRegenerationInterval
Sep  3 12:47:32 helios sshd[1398]: rexec line 20: Deprecated option ServerKeyBits
Sep  3 12:47:32 helios sshd[1398]: rexec line 31: Deprecated option RSAAuthentication
Sep  3 12:47:32 helios sshd[1398]: rexec line 38: Deprecated option RhostsRSAAuthentication
Sep  3 12:47:32 helios sshd[1398]: reprocess config line 31: Deprecated option RSAAuthentication
Sep  3 12:47:32 helios sshd[1398]: reprocess config line 38: Deprecated option RhostsRSAAuthentication
Sep  3 12:47:32 helios sshd[1398]: Accepted publickey for monitoring from 131.220.226.3 port 39992 ssh2: RSA SHA256:ulxULyONiGRB8VUFctWd/WSBcRxjGX+5Dq/IXyZS+gI
Sep  3 12:47:32 helios sshd[1398]: pam_unix(sshd:session): session opened for user monitoring by (uid=0)
Sep  3 12:47:32 helios systemd-logind[497]: New session 6 of user monitoring.
Sep  3 12:47:32 helios systemd: pam_unix(systemd-user:session): session opened for user monitoring by (uid=0)
Sep  3 12:47:32 helios sshd[1416]: Received disconnect from 131.220.226.3 port 39992:11: disconnected by user
Sep  3 12:47:32 helios sshd[1416]: Disconnected from user monitoring 131.220.226.3 port 39992
Sep  3 12:47:32 helios sshd[1398]: pam_unix(sshd:session): session closed for user monitoring
Sep  3 12:47:32 helios systemd-logind[497]: Session 6 logged out. Waiting for processes to exit.
Sep  3 12:47:32 helios systemd-logind[497]: Removed session 6.
Sep  3 12:47:42 helios systemd: pam_unix(systemd-user:session): session closed for user monitoring
Sep  3 12:48:14 helios lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
Sep  3 12:48:14 helios systemd-logind[497]: Removed session c1.
Sep  3 12:48:14 helios lightdm: pam_unix(lightdm:session): session opened for user ueding by (uid=0)
Sep  3 12:48:14 helios lightdm: pam_systemd(lightdm:session): Failed to create session: No such file or directory
Sep  3 12:48:24 helios systemd: pam_unix(systemd-user:session): session closed for user lightdm

我想倒数第二行是非常有趣的。

附带系统日志

Sep 04 14:10:10 helios systemd[1]: session-c3.scope: Killing process 28814 (lightdm) with signal SIGTERM.
Sep 04 14:10:10 helios systemd[1]: session-c3.scope: Killing process 28829 (lightdm-gtk-gre) with signal SIGTERM.
Sep 04 14:10:10 helios systemd[1]: Stopping Session c3 of user lightdm.
Sep 04 14:10:10 helios lightdm[28814]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Sep 04 14:10:10 helios systemd[1]: session-c3.scope: Succeeded.
Sep 04 14:10:10 helios systemd[1]: Stopped Session c3 of user lightdm.
Sep 04 14:10:10 helios systemd-logind[497]: Removed session c3.
Sep 04 14:10:10 helios lightdm[28869]: pam_unix(lightdm:session): session opened for user ueding by (uid=0)
Sep 04 14:10:10 helios lightdm[28869]: pam_systemd(lightdm:session): Failed to create session: No such file or directory
Sep 04 14:10:10 helios lightdm[28869]: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
Sep 04 14:10:10 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.a11y.Bus' requested by ':1.3' (uid=1085 pid=28933 comm="xfce4-session ")
Sep 04 14:10:10 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.a11y.Bus'
Sep 04 14:10:10 helios org.a11y.Bus[28914]: dbus-daemon[28940]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1085 pid=28933 comm="xfce4-session ")
Sep 04 14:10:10 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.xfce.Xfconf' requested by ':1.3' (uid=1085 pid=28933 comm="xfce4-session ")
Sep 04 14:10:10 helios org.a11y.Bus[28914]: dbus-daemon[28940]: Successfully activated service 'org.a11y.atspi.Registry'
Sep 04 14:10:10 helios org.a11y.Bus[28914]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Sep 04 14:10:10 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.xfce.Xfconf'
Sep 04 14:10:11 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.gtk.vfs.Daemon' requested by ':1.9' (uid=1085 pid=28954 comm="Thunar --sm-client-id 2e9ea3a26-363a-4e06-b723-b6d")
Sep 04 14:10:11 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.gtk.vfs.Daemon'
Sep 04 14:10:11 helios org.gtk.vfs.Daemon[28914]: fusermount: failed to open mountpoint for reading: Permission denied
Sep 04 14:10:11 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.16' (uid=1085 pid=28972 comm="xfdesktop --display :0.0 --sm-client-id 24fe00ba0-")
Sep 04 14:10:11 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.freedesktop.Notifications' requested by ':1.20' (uid=1085 pid=28988 comm="xfce4-power-manager --restart --sm-client-id 270b9")
Sep 04 14:10:11 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.freedesktop.Notifications'
Sep 04 14:10:12 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.freedesktop.Tracker1' requested by ':1.28' (uid=1085 pid=29060 comm="gdbus call -e -d org.freedesktop.DBus -o /org/free")
Sep 04 14:10:12 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='ca.desrt.dconf' requested by ':1.29' (uid=1085 pid=29045 comm="light-locker ")
Sep 04 14:10:12 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'ca.desrt.dconf'
Sep 04 14:10:12 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.freedesktop.Tracker1'
Sep 04 14:10:12 helios org.freedesktop.thumbnails.Thumbnailer1[28914]: Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Sep 04 14:10:12 helios org.freedesktop.thumbnails.Thumbnailer1[28914]: Registered thumbailer evince-thumbnailer -s %s %u %o
Sep 04 14:10:12 helios org.freedesktop.thumbnails.Thumbnailer1[28914]: Registered thumbailer gnome-thumbnail-font --size %s %u %o
Sep 04 14:10:12 helios org.freedesktop.thumbnails.Thumbnailer1[28914]: Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Sep 04 14:10:12 helios org.freedesktop.thumbnails.Thumbnailer1[28914]: Registered thumbailer atril-thumbnailer -s %s %u %o
Sep 04 14:10:12 helios org.freedesktop.thumbnails.Thumbnailer1[28914]: Registered thumbailer /usr/share/blender/scripts/blender-thumbnailer.py %i %o
Sep 04 14:10:12 helios org.freedesktop.thumbnails.Thumbnailer1[28914]: Registered thumbailer /usr/bin/totem-video-thumbnailer -s %s %u %o
Sep 04 14:10:12 helios kernel: traps: light-locker[29045] trap int3 ip:7f6a78690c75 sp:7ffec8e2fea0 error:0 in libglib-2.0.so.0.5800.3[7f6a78658000+7e000]
Sep 04 14:10:12 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.gnome.evolution.dataserver.Sources5' requested by ':1.38' (uid=1085 pid=29044 comm="/usr/lib/evolution/evolution-data-server/evolution")
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.gnome.OnlineAccounts' requested by ':1.40' (uid=1085 pid=29094 comm="/usr/lib/evolution/evolution-source-registry ")
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.gnome.evolution.dataserver.Sources5'
Sep 04 14:10:13 helios goa-daemon[29107]: goa-daemon version 3.30.1 starting
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.gnome.Identity' requested by ':1.41' (uid=1085 pid=29107 comm="/usr/lib/gnome-online-accounts/goa-daemon ")
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.gnome.OnlineAccounts'
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.gnome.Identity'
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.gnome.evolution.dataserver.Calendar7' requested by ':1.38' (uid=1085 pid=29044 comm="/usr/lib/evolution/evolution-data-server/evolution")
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.23' (uid=1085 pid=28986 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd ")
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.gtk.vfs.AfcVolumeMonitor' requested by ':1.23' (uid=1085 pid=28986 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd ")
Sep 04 14:10:13 helios org.gtk.vfs.AfcVolumeMonitor[28914]: Volume monitor alive
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.gnome.evolution.dataserver.Calendar7'
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.gnome.evolution.dataserver.AddressBook9' requested by ':1.43' (uid=1085 pid=29125 comm="/usr/lib/evolution/evolution-calendar-factory ")
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.gtk.vfs.GoaVolumeMonitor' requested by ':1.23' (uid=1085 pid=28986 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd ")
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook9'
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Sep 04 14:10:13 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.gtk.vfs.MTPVolumeMonitor' requested by ':1.23' (uid=1085 pid=28986 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd ")
Sep 04 14:10:14 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Sep 04 14:10:14 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.gtk.vfs.GPhoto2VolumeMonitor' requested by ':1.23' (uid=1085 pid=28986 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd ")
Sep 04 14:10:14 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Sep 04 14:10:14 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Sep 04 14:10:14 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Activating service name='org.gtk.vfs.Metadata' requested by ':1.14' (uid=1085 pid=28972 comm="xfdesktop --display :0.0 --sm-client-id 24fe00ba0-")
Sep 04 14:10:14 helios dbus-daemon[28914]: [session uid=1085 pid=28912] Successfully activated service 'org.gtk.vfs.Metadata'
Sep 04 14:10:20 helios systemd[1]: Stopping User Manager for UID 116...
Sep 04 14:10:20 helios systemd[28818]: Stopping D-Bus User Message Bus...
Sep 04 14:10:20 helios gvfsd[28842]: A connection to the bus can't be made
Sep 04 14:10:20 helios systemd[28818]: Stopping Accessibility services bus...
Sep 04 14:10:20 helios systemd[28818]: Stopping Virtual filesystem service...
Sep 04 14:10:20 helios systemd[28818]: Stopped target Default.
Sep 04 14:10:20 helios systemd[28818]: gvfs-daemon.service: Main process exited, code=killed, status=15/TERM
Sep 04 14:10:20 helios systemd[28818]: at-spi-dbus-bus.service: Succeeded.
Sep 04 14:10:20 helios systemd[28818]: Stopped Accessibility services bus.
Sep 04 14:10:20 helios systemd[28818]: dbus.service: Succeeded.
Sep 04 14:10:20 helios systemd[28818]: Stopped D-Bus User Message Bus.
Sep 04 14:10:20 helios systemd[1]: run-user-116-gvfs.mount: Succeeded.
Sep 04 14:10:20 helios systemd[28818]: run-user-116-gvfs.mount: Succeeded.
Sep 04 14:10:20 helios systemd[25779]: run-user-116-gvfs.mount: Succeeded.
Sep 04 14:10:20 helios systemd[28818]: gvfs-daemon.service: Succeeded.
Sep 04 14:10:20 helios systemd[28818]: Stopped Virtual filesystem service.
Sep 04 14:10:20 helios systemd[28818]: Stopped target Basic System.
Sep 04 14:10:20 helios systemd[28818]: Stopped target Sockets.
Sep 04 14:10:20 helios systemd[28818]: gpg-agent-browser.socket: Succeeded.
Sep 04 14:10:20 helios systemd[28818]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 04 14:10:20 helios systemd[28818]: gpg-agent.socket: Succeeded.
Sep 04 14:10:20 helios systemd[28818]: Closed GnuPG cryptographic agent and passphrase cache.
Sep 04 14:10:20 helios systemd[28818]: gpg-agent-ssh.socket: Succeeded.
Sep 04 14:10:20 helios systemd[28818]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Sep 04 14:10:20 helios systemd[28818]: dirmngr.socket: Succeeded.
Sep 04 14:10:20 helios systemd[28818]: Closed GnuPG network certificate management daemon.
Sep 04 14:10:20 helios systemd[28818]: gpg-agent-extra.socket: Succeeded.
Sep 04 14:10:20 helios systemd[28818]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Sep 04 14:10:20 helios systemd[28818]: pulseaudio.socket: Succeeded.
Sep 04 14:10:20 helios systemd[28818]: Closed Sound System.
Sep 04 14:10:20 helios systemd[28818]: Stopped target Timers.
Sep 04 14:10:20 helios systemd[28818]: Stopped target Paths.
Sep 04 14:10:20 helios systemd[28818]: dbus.socket: Succeeded.
Sep 04 14:10:20 helios systemd[28818]: Closed D-Bus User Message Bus Socket.
Sep 04 14:10:20 helios systemd[28818]: Reached target Shutdown.
Sep 04 14:10:20 helios systemd[28818]: systemd-exit.service: Succeeded.
Sep 04 14:10:20 helios systemd[28818]: Started Exit the Session.
Sep 04 14:10:20 helios systemd[28818]: Reached target Exit the Session.
Sep 04 14:10:20 helios systemd[28819]: pam_unix(systemd-user:session): session closed for user lightdm
Sep 04 14:10:20 helios systemd[1]: [email protected]: Succeeded.
Sep 04 14:10:20 helios systemd[1]: Stopped User Manager for UID 116.
Sep 04 14:10:20 helios systemd[1]: Stopping User Runtime Directory /run/user/116...
Sep 04 14:10:20 helios systemd[25779]: run-user-116.mount: Succeeded.
Sep 04 14:10:20 helios systemd[1]: run-user-116.mount: Succeeded.
Sep 04 14:10:20 helios systemd[1]: [email protected]: Succeeded.
Sep 04 14:10:20 helios systemd[1]: Stopped User Runtime Directory /run/user/116.
Sep 04 14:10:20 helios systemd[1]: Removed slice User Slice of UID 116.

目前的结论

我觉得有些东西会阻止用户“完全登录”，从某种意义上说，他们确实有 Xfce 会话并且可以看到他们的主目录，但不足以注册“花哨”的东西，比如 logindPulse Audio . 或者他们可能缺少一个特殊的用户组。机器上的本地用户帐户按预期工作，因此这肯定是一般用户帐户的一些问题，而不是症状之一（loginctl输出、声音、可移动媒体）。

我无法真正掌握这一点，我不确定我应该在哪里看。非常欢迎指针或（希望）解决方案！

我已经在 cron 工作中使用 duplicity 一年了，效果很好。从上周开始，我收到以下消息：

Ausdruckbasierte Dateiliste wird gelesen /home/mu/.config/exclude-b2.txt
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1637, in <module>
    if "Forced assertion for testing" in util.uexc(e):
  File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 82, in uexc
    return ufn(m)
  File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 63, in ufn
    return filename.decode(globals.fsencoding, 'replace')
AttributeError: 'tuple' object has no attribute 'decode'

我的 Fedora 30 系统上对软件包的最后一次升级duplicity是 2019-05-09，我运行的是 0.7.19 版本。备份转到 Backblaze B2。

有什么办法可以把它固定下来吗？

我想使用该perf实用程序为我的程序收集测量值。它在 Debian 9 的共享集群机器上运行，默认情况下 /proc/sys/kernel/perf_event_paranoid设置为 3，因此不允许我收集测量值。在更改它之前，我想知道这意味着什么。

是否只是安全性允许其他用户分析其他用途运行的内容并因此获得洞察力？我们不关心这一点，因为它无论如何都是用户的核心圈子。还是可能是性能，这也会影响其他所有人？

我已经在ask.fedora.org上交叉发布了这个，因为我仍然不确定这方或另一方是否拥有更大的 Fedora 用户群。

几天以来，由于此错误，我无法安装更新：

# env LC_ALL=C dnf update
Last metadata expiration check: 0:18:57 ago on Wed Jan 23 16:16:14 2019.
Traceback (most recent call last):
  File "/usr/bin/dnf", line 58, in <module>
    main.user_main(sys.argv[1:], exit_code=True)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 179, in user_main
    errcode = main(args)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 64, in main
    return _main(base, args, cli_class, option_parser_class)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 99, in _main
    return cli_run(cli, base)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 123, in cli_run
    ret = resolving(cli, base)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 146, in resolving
    base.resolve(cli.demands.allow_erasing)
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 760, in resolve
    self._transaction = self._goal2transaction(goal)
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 681, in _goal2transaction
    ts.add_upgrade(pkg, upgraded, obs)
  File "/usr/lib/python3.7/site-packages/dnf/db/group.py", line 269, in add_upgrade
    ti_new = self.new(new, libdnf.transaction.TransactionItemAction_UPGRADE)
  File "/usr/lib/python3.7/site-packages/dnf/db/group.py", line 222, in new
    reason = self.get_reason(pkg)
  File "/usr/lib/python3.7/site-packages/dnf/db/group.py", line 237, in get_reason
    return self.history.swdb.resolveRPMTransactionItemReason(pkg.name, pkg.arch, -1)
  File "/usr/lib64/python3.7/site-packages/libdnf/transaction.py", line 788, in resolveRPMTransactionItemReason
    return _transaction.Swdb_resolveRPMTransactionItemReason(self, name, arch, maxTransactionId)
RuntimeError: Step: database disk image is malformed in

        SELECT
            ti.action as action,
            ti.reason as reason
        FROM
            trans_item ti
        JOIN
            trans t ON ti.trans_id = t.id
        JOIN
            rpm i USING (item_id)
        WHERE
            t.state = 1
            /* see comment in TransactionItem.hpp - TransactionItemAction */
            AND ti.action not in (3, 5, 7, 10)
            AND i.name = 'python2-rpkg'
            AND i.arch = 'noarch'
        ORDER BY
            ti.trans_id DESC
        LIMIT 1

我发现应该执行这些命令来修复它，我尝试了，但它没有解决问题。

• dnf clean all
• dnf makecache
• rpm --buildddb

在Ask Fedora 上，有人建议dnf 无法从中恢复，必须手动修复 SQLite 数据库。

我试图运行给定的命令，

sqlite3 history-<date>.sqlite ".dump" | sqlite3 history-<new date>.db && rm history-<date>.sqlite

这样做/var/lib/dnf/history/history-2015-10-25.sqlite没有效果。这样做会/var/lib/dnf/history.sqlite导致一个新的错误：

# dnf update
Letzte Prüfung auf abgelaufene Metadaten: vor 1:22:29 am Mi 23 Jan 2019 16:39:44 CET.
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 64, in main
    return _main(base, args, cli_class, option_parser_class)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 99, in _main
    return cli_run(cli, base)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 123, in cli_run
    ret = resolving(cli, base)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 146, in resolving
    base.resolve(cli.demands.allow_erasing)
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 760, in resolve
    self._transaction = self._goal2transaction(goal)
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 657, in _goal2transaction
    ts.add_install(pkg, obs, reason)
  File "/usr/lib/python3.7/site-packages/dnf/db/group.py", line 256, in add_install
    ti_new = self.new(new, libdnf.transaction.TransactionItemAction_INSTALL, reason)
  File "/usr/lib/python3.7/site-packages/dnf/db/group.py", line 219, in new
    rpm_item = self._pkg_to_swdb_rpm_item(pkg)
  File "/usr/lib/python3.7/site-packages/dnf/db/group.py", line 210, in _pkg_to_swdb_rpm_item
    rpm_item = self.history.swdb.createRPMItem()
  File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 291, in swdb
    self._swdb = libdnf.transaction.Swdb(self.dbpath)
  File "/usr/lib64/python3.7/site-packages/libdnf/transaction.py", line 729, in __init__
    this = _transaction.new_Swdb(*args)
RuntimeError: Exec failed: malformed database schema (1467577792)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/dnf", line 58, in <module>
    main.user_main(sys.argv[1:], exit_code=True)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 179, in user_main
    errcode = main(args)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 64, in main
    return _main(base, args, cli_class, option_parser_class)
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 121, in __exit__
    self.close()
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 472, in close
    self._finalize_base()
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 455, in _finalize_base
    self.history.close()
  File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 305, in close
    self.swdb.closeTransaction()
  File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 291, in swdb
    self._swdb = libdnf.transaction.Swdb(self.dbpath)
  File "/usr/lib64/python3.7/site-packages/libdnf/transaction.py", line 729, in __init__
    this = _transaction.new_Swdb(*args)
RuntimeError: Exec failed: malformed database schema (1467577792)

进一步研究这sqlite3 .dump件事，我看到了这一点：

/var/lib/dnf# sqlite3 history.sqlite .dump 
PRAGMA foreign_keys=OFF;
BEGIN TRANSACTION;
/**** ERROR: (10) disk I/O error *****/
ROLLBACK; -- due to errors

但是，当我将它复制history.sqlite到那里/tmp并在那里执行.dump时，我得到了一个看起来很合理的数据库。使用 GUI 打开它也sqliteman可以正常工作。看来数据库本身没问题。

将数据库转储到其他地方的新文件中并将其复制回来然后给我这个：

/v/l/dnf# dnf update
Letzte Prüfung auf abgelaufene Metadaten: vor 0:30:51 am Sa 26 Jan 2019 13:21:13 CET.
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 64, in main
    return _main(base, args, cli_class, option_parser_class)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 99, in _main
    return cli_run(cli, base)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 123, in cli_run
    ret = resolving(cli, base)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 146, in resolving
    base.resolve(cli.demands.allow_erasing)
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 760, in resolve
    self._transaction = self._goal2transaction(goal)
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 650, in _goal2transaction
    reason_obsolete = ts.get_reason(obsolete)
  File "/usr/lib/python3.7/site-packages/dnf/db/group.py", line 237, in get_reason
    return self.history.swdb.resolveRPMTransactionItemReason(pkg.name, pkg.arch, -1)
  File "/usr/lib64/python3.7/site-packages/libdnf/transaction.py", line 788, in resolveRPMTransactionItemReason
    return _transaction.Swdb_resolveRPMTransactionItemReason(self, name, arch, maxTransactionId)
RuntimeError: Step: disk I/O error in

        SELECT
            ti.action as action,
            ti.reason as reason
        FROM
            trans_item ti
        JOIN
            trans t ON ti.trans_id = t.id
        JOIN
            rpm i USING (item_id)
        WHERE
            t.state = 1
            /* see comment in TransactionItem.hpp - TransactionItemAction */
            AND ti.action not in (3, 5, 7, 10)
            AND i.name = 'libmodulemd'
            AND i.arch = 'x86_64'
        ORDER BY
            ti.trans_id DESC
        LIMIT 1


During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/dnf", line 58, in <module>
    main.user_main(sys.argv[1:], exit_code=True)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 179, in user_main
    errcode = main(args)
  File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 64, in main
    return _main(base, args, cli_class, option_parser_class)
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 121, in __exit__
    self.close()
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 473, in close
    self.reset(sack=True, repos=True, goal=True)
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 504, in reset
    self.history.close()
  File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 305, in close
    self.swdb.closeTransaction()
  File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 291, in swdb
    self._swdb = libdnf.transaction.Swdb(self.dbpath)
  File "/usr/lib64/python3.7/site-packages/libdnf/transaction.py", line 729, in __init__
    this = _transaction.new_Swdb(*args)
RuntimeError: Exec failed: disk I/O error
Exception ignored in: <function SwdbInterface.__del__ at 0x7f28b02e4510>
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 262, in __del__
  File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 305, in close
  File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 291, in swdb
  File "/usr/lib64/python3.7/site-packages/libdnf/transaction.py", line 729, in __init__
RuntimeError: Exec failed: disk I/O error

我还恢复了 SELinux 标签，但这并没有改变任何东西，它是

-rw-r--r--. 1 root root unconfined_u:object_r:rpm_var_lib_t:s0 29M 26. Jan 13:52 history.sqlite

root 也可以读取文件：

/v/l/dnf# head -c 1000 history.sqlite 
SQLite format 3@  ,�,.,P��⏎

Fedora 29 上的情况如何，我可以从中恢复吗？

我已将我们部门的 Debian 工作站配置为使用 Exim 4 进行邮件传递。我还创建了一个别名，以便我收到所有root电子邮件。Exim 4 配置（通过 Ansible 和 debconf）具有以下设置：

exim4_dc_eximconfig_configtype: internet
exim4_dc_readhost: …
exim4_dc_smarthost: …
exim4_dc_use_split_config: 'true'
exim4_dc_hide_mailname: 'true'
exim4_dc_mailname_in_oh: 'true'

在每台机器上，我都可以mailx用来发送电子邮件root，它会很好地显示在我的收件箱中。一些cron 作业的执行也被正确地发送给我。

但是，大多数 cron 作业都无法发送电子邮件，而是收到以下电子邮件：

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  ueding@…
    (generated from root@echo)



Reporting-MTA: dns; echo

Action: failed
Final-Recipient: rfc822;ueding@…
Status: 5.0.0



Return-path: <root@echo>
Received: from root by echo with local (Exim 4.89)
    (envelope-from <root@echo>)
    id 1f7Jqz-0007jU-7y
    for root@echo; Sat, 14 Apr 2018 14:00:25 +0200
From: root@echo (Cron Daemon)
To: root@echo
Subject: Cron <root@echo> ansible-pull -U [email protected]:…/….git --private-key /root/.ssh/ansible_pull localhost.yml
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
Message-Id: <E1f7Jqz-0007jU-7y@echo>
Date: Sat, 14 Apr 2018 14:00:25 +0200
X-Exim-DSN-Information: Due to administrative limits only headers are returned

我真的不明白为什么会这样。要么所有电子邮件传递都失败，要么几乎全部成功。来自 cron 的电子邮件如何在大多数工作站上失败但在其他工作站上成功，而交付失败的电子邮件总是通过？

机器上有关 exim 的系统日志 echo 非常稀疏：

# journalctl -u exim4.service 
-- Logs begin at Tue 2018-03-06 18:35:11 CET, end at Sat 2018-04-14 17:13:08 CEST. --
Apr 02 18:00:30 echo systemd[1]: Starting LSB: exim Mail Transport Agent...
Apr 02 18:01:23 echo exim4[27433]: Starting MTA: exim4.
Apr 02 18:01:23 echo systemd[1]: Started LSB: exim Mail Transport Agent.

调查在一个银盘/var/log/exim4/mainlog上提供解释：

2018-04-14 14:00:25 1f7Jqz-0007jU-7y <= root@echo U=root P=local S=7948
2018-04-14 14:00:25 1f7Jqz-0007jU-7y ** ueding@… <root@echo> R=dnslookup T=remote_smtp: message is too big (transport limit = 1)
2018-04-14 14:00:25 1f7Jqz-0007jW-BM <= <> R=1f7Jqz-0007jU-7y U=Debian-exim P=local S=1856
2018-04-14 14:00:25 1f7Jqz-0007jU-7y Completed
2018-04-14 14:00:26 1f7Jqz-0007jW-BM => ueding@… <root@echo> R=dnslookup T=remote_smtp H=… […] X=TLS1.0:RSA_AES_256_CBC_SHA1:256 CV=yes DN="C=DE,ST=…,L=…,O=…,OU=…,CN=…" C="250 2.0.0 Ok: queued as 6FCA1155FC32"
2018-04-14 14:00:26 1f7Jqz-0007jW-BM Completed

错误可能是“消息太大（传输限制 = 1）”。但这仍然没有多大意义，因为我有 30 个相同配置的工作站，其中一些工作站的消息连续几天通过。每台机器的消息长度应该相同（主机名的长度除外），并且当前接收电子邮件的两台机器具有更长的名称。

我现在受托管理大约 40 台装有 Debian 8 的计算机。存储配置文件（装有 Debian FAI）的计算机有硬盘缺陷，没有备份。因此，我们并不真正知道那里实际配置了什么。

我的计划是从一个工作站刮取配置，然后使用 Ansible 重新构建所有内容。如果我可以从中构建一个新的虚拟机，那么我就知道配置了什么。我已经弄清楚了一些事情（网络接口，打印，DNS，...），但我还没有弄清楚用户帐户机制。主目录通过 NFS4 挂载。

他们有一些中央登录机制，可以在所有计算机上使用相同的帐户登录。要更改密码，您必须使用yppasswd. 所以我认为这是一些 YP/NIS 的事情。但是这些/etc/yp*文件都是默认文件。而且我没有发现任何与 NIS 相关的东西。

那里使用什么用户管理系统？我在哪里可以找到需要设置的配置文件？