Eu uso o Fedora 31 e tento solucionar um bug onde recebi a sugestão de atualizar o pacote do Rawhide. Eu instalei o repositório dnf install fedora-repos-rawhidee tentei atualizar o pacote único. Isso falhou devido a problemas de 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

Essas etapas parecem estar corretas , pelo menos estavam em 2014. Estou faltando uma etapa? Preciso importar manualmente a chave Rawhide também?

Recentemente, atualizei as estações de trabalho do Debian 9 para o Debian 10. Com a versão antiga, as pessoas podiam montar drives USB e reproduzir e gravar som (para videoconferências). Após a atualização, nada disso funciona.

Contas de usuários remotos

Houve algumas peculiaridades com as contas de usuário, então talvez essa seja a fonte do problema. Usamos NIS e NFS para fornecer contas de usuário e diretórios pessoais em todas as máquinas. Após a atualização para o Debian 10, precisei adicionar um NISporque /etc/nsswitch.confeles estavam compatantes e agora só tinham files. Também ypbindnão estava em execução porque não era mais usado -broadcastcomo opção de inicialização padrão. Eu adicionei um novo arquivo systemd em /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

Com isso, as contas de usuário estavam lá e os diretórios pessoais também. Na linha de comando eu também podia fazer login. Mas o gerenciador de exibição LightDM ainda não estava deixando os usuários entrarem. Então na /etc/lightdm/lightdm.confseção [LightDM] eu adicionei a opção greeter-show-manual-login = Truee a partir de então os usuários remotos poderiam fazer login. Algumas máquinas ainda tinham GDM como padrão gerenciador de exibição, lá os logins mostraram o mesmo comportamento que o LightDM fazia antes de eu alterar a configuração. A verificação de senha foi aprovada, a tela pode ficar preta por um breve momento e, em seguida, a tela de login é exibida novamente. O mesmo ocorre quando os usuários ultrapassaram sua cota e os arquivos necessários para estabelecer a sessão ( .Xauthority?) não puderam ser criados.

O curioso é que quando estou logado via SSH e também na tela real, essas sessões aparecem corretamente com who:

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

Mas, ao mesmo tempo, a sessão não é listada com loginctl:

$ loginctl
No sessions.

Quando faço o mesmo no meu laptop Fedora 30 pessoal com contas de usuário locais, tenho esta saída de 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)

E também loginctlmostra algo sensato:

$ loginctl
SESSION  UID USER SEAT  TTY
      1 1000 mu   seat0    

1 sessions listed.

Eu criei uma nova conta de usuário local com UID 50000 em uma das estações de trabalho Debian 10 e descobri que posso fazer login, fazer a sessão aparecer loginctle também a mídia removível e os problemas de som descritos abaixo não estão lá, som e mídia removível funciona. Então isso definitivamente é um problema com os usuários vindos do NIS.

A única coisa que me atingiu algumas vezes até agora é que, por razões históricas, os IDs de usuário que fornecemos começam com 500. Mas meu usuário uedingtem o uid 1085, então mesmo que isso tenha sido um problema com as contas não listadas, isso account deve funcionar bem porque os valores iniciais padrão para IDs de usuário que não são considerados usuários do sistema são 1000.

Não tenho experiência suficiente, mas tenho a sensação de que, de alguma forma, as contas dos usuários não estão totalmente no sistema, que ainda falta algo.

Um usuário com uid 536 teve que digitar sua senha do chaveiro do GNOME após o login. Não tenho certeza se ele tem senhas diferentes lá, mas também pode ser que não tenha sido desbloqueado durante a inicialização. Isso pode não significar nada, no entanto.

aut.log

Com o estado atual, isso é tudo o que aparece /var/log/auth.logdesde a inicialização da máquina, conectando-se como root via SSH para recuperar o log e efetuando login na própria máquina com meu usuário NIS. Além disso, o monitoringusuário fez login via SSH para recuperar algumas informações para o meu sistema de monitoramento.

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

Acho que a penúltima linha é a realmente interessante.

Acompanhando syslog

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]: user@116.service: 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]: user-runtime-dir@116.service: 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.

Conclusão atual

Eu sinto que há algo que impede os usuários de se tornarem “totalmente logados”, no sentido de que eles têm uma sessão do Xfce e podem ver seus diretórios pessoais, mas não o suficiente para serem registrados com coisas “chiques” como logindou Pulse Audio . Ou talvez estejam faltando um grupo de usuários especial. Uma conta de usuário local nas máquinas funciona exatamente como esperado, então isso definitivamente é algum problema com as contas de usuário em geral e não com um dos sintomas ( loginctlsaída, som, mídia removível).

Eu realmente não consigo entender isso e não tenho certeza de onde exatamente devo procurar. Ponteiros ou (espero) soluções são muito bem-vindos!

Eu tenho usado duplicidade em um cron job há um ano, funcionou muito bem. A partir da semana passada, recebi a seguinte mensagem:

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'

A última atualização do duplicitypacote no meu sistema Fedora 30 foi 2019-05-09, estou executando a versão 0.7.19. O backup vai para o Backblaze B2.

Existe alguma maneira de eu conseguir fixar isso?

Eu gostaria de usar o perfutilitário para coletar medidas para o meu programa. Ele é executado em uma máquina de cluster compartilhada com o Debian 9, onde por padrão /proc/sys/kernel/perf_event_paranoidé definido como 3, portanto, não me permite coletar medições. Antes de mudar, gostaria de saber quais são as implicações disso.

É apenas a segurança que permite que outros usuários criem perfis de coisas executadas por outros usos e, portanto, obtenham insights? Nós não nos importamos com isso, pois é um círculo interno de usuários de qualquer maneira. Ou talvez seja o desempenho, que afetará todos os outros também?

Eu postei isso no ask.fedora.org , pois ainda não tenho certeza se este ou o outro lado tem a maior base de usuários do Fedora.

Há alguns dias não consigo instalar atualizações devido a este erro:

# 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

Descobri que se deve fazer esses comandos para corrigi-lo e tentei, mas não resolveu o problema.

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

No Ask Fedora, alguém sugeriu que o dnf não é capaz de se recuperar disso e que é preciso reparar o banco de dados SQLite manualmente.

Eu tentei executar o comando dado,

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

Fazer isso /var/lib/dnf/history/history-2015-10-25.sqlitenão surtiu efeito. Fazer isso /var/lib/dnf/history.sqliteresultou em um novo erro:

# 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)

Olhando mais para a sqlite3 .dumpcoisa, vejo isso:

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

No entanto, quando copio isso history.sqlitee /tmpexecuto isso .dump, recebo um banco de dados de aparência sensata. Também abri-lo com a GUI sqlitemanfunciona bem. Parece que o banco de dados em si está bem.

Despejar o banco de dados em um novo arquivo em outro lugar e copiá-lo de volta me dá isso:

/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

Também restaurei os rótulos do SELinux, mas isso não mudou nada, é

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

Root também pode ler o arquivo:

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

Como é isso no Fedora 29, posso me recuperar disso?

Eu configurei as estações de trabalho Debian em nosso departamento para usar o Exim 4 para entrega de e-mail. Também criei um alias para receber todos os e- rootmails. A configuração Exim 4 (via Ansible e debconf) tem essas configurações:

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'

Em cada uma das máquinas, posso mailxenviar um e-mail para roote ele aparecerá na minha caixa de entrada perfeitamente. Além disso , algumas execuções dos trabalhos cron são enviadas corretamente para mim.

No entanto, a maioria dos trabalhos cron falha ao entregar seus e-mails e, em vez disso, recebo o seguinte e-mail:

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 git@github.com:…/….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

Eu realmente não entendo porque isso está acontecendo. Todas as entregas de e-mail falham ou quase todas são bem-sucedidas. Como o e-mail do cron pode falhar na maioria das estações de trabalho, mas ter sucesso em outras, enquanto os e-mails de falha na entrega sempre chegam?

O log do sistema referente ao exim na máquina, echo, é realmente esparso:

# 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.

Olhar para dentro /var/log/exim4/mainlogserve a explicação em uma bandeja de prata:

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

O erro provavelmente é “a mensagem é muito grande (limite de transporte = 1)”. Mas isso ainda não faz muito sentido, pois tenho 30 estações de trabalho configuradas de forma idêntica e, para algumas delas, as mensagens passam vários dias seguidos. O comprimento da mensagem deve ser o mesmo para cada máquina (exceto o comprimento do nome do host), e as duas máquinas que atualmente recebem seus e-mails têm nomes mais longos.

Agora estou encarregado de administrar cerca de 40 computadores com Debian 8. O computador onde os arquivos de configuração (com Debian FAI) foram armazenados tinha um defeito no HDD, não havia backup. Portanto, não sabemos realmente o que realmente está configurado lá fora.

Meu plano é extrair a configuração de uma estação de trabalho e construir tudo novamente com o Ansible. Se eu puder criar uma nova VM a partir disso, saberei o que está configurado. Eu descobri algumas coisas (interfaces de rede, impressão, DNS, ...), mas o mecanismo de conta do usuário não. Os diretórios iniciais são montados via NFS4.

Eles têm algum mecanismo de login central, pode-se fazer login com as mesmas contas em todos os computadores. Para alterar sua senha, você deve usar yppasswd. Então eu presumo que seja alguma coisa YP/NIS. Mas os /etc/yp*arquivos são todos os padrão. E não encontrei nada com NIS.

Qual sistema de gerenciamento de usuários é usado lá? Onde encontro os arquivos de configuração que precisam ser configurados?