Debian unstable, rodando em um container nspawn no Debian Jessie, travou.
No host:
$ sudo systemctl status systemd-nspawn@unstable-srv
● [email protected] - Container unstable-srv
Loaded: loaded (/lib/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since Wed 2017-05-31 15:02:51 BST; 6h ago
Docs: man:systemd-nspawn(1)
Main PID: 15693 (code=exited, status=1/FAILURE)
May 31 15:02:51 brick systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
May 31 15:02:51 brick systemd[1]: Unit [email protected] entered failed state.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Faça o registro dentro do contêiner. As últimas mensagens de log são de upgrades não assistidos (com needrestart no modo automático):
May 31 14:02:44 unstable-srv apt.systemd.daily[4911]: Restarting services...
May 31 14:02:44 unstable-srv apt.systemd.daily[4911]: systemctl restart apt-cacher-ng.service console-getty.service cron.service
May 31 14:02:44 unstable-srv systemd[1]: Stopping Regular background program processing daemon...
May 31 14:02:44 unstable-srv systemd[1]: Stopping Console Getty...
May 31 14:02:44 unstable-srv systemd[1]: Stopping Apt-Cacher NG software download proxy...
May 31 14:02:45 unstable-srv cron[7230]: (CRON) INFO (pidfile fd = 3)
May 31 14:02:44 unstable-srv systemd[1]: Stopped Regular background program processing daemon.
May 31 14:02:45 unstable-srv cron[7230]: (CRON) INFO (Skipping @reboot jobs -- not system startup)
May 31 14:02:44 unstable-srv systemd[1]: Stopped Console Getty.
May 31 14:02:44 unstable-srv systemd[1]: Started Console Getty.
May 31 14:02:45 unstable-srv systemd[1]: Started Regular background program processing daemon.
May 31 14:02:45 unstable-srv systemd[1]: Stopped Apt-Cacher NG software download proxy.
May 31 14:02:45 unstable-srv systemd[1]: Starting Apt-Cacher NG software download proxy...
May 31 14:02:45 unstable-srv apt-cacher-ng[7231]: WARNING: No configuration was read from file:sfnet_mirrors
May 31 14:02:45 unstable-srv systemd[1]: Started Apt-Cacher NG software download proxy.
May 31 14:02:45 unstable-srv apt.systemd.daily[4911]: Unable to get Terminal Size. The TIOCGWINSZ ioctl didn't work. The COLUMNS and LINES environment
May 31 14:02:45 unstable-srv apt.systemd.daily[4911]: Services being skipped:
May 31 14:02:45 unstable-srv apt.systemd.daily[4911]: systemctl restart apt-daily.service
May 31 14:02:45 unstable-srv apt.systemd.daily[4911]: /etc/needrestart/restart.d/dbus.service
May 31 14:02:45 unstable-srv apt.systemd.daily[4911]: systemctl restart systemd-journald.service
May 31 14:02:45 unstable-srv apt.systemd.daily[4911]: systemctl restart systemd-logind.service
May 31 14:02:45 unstable-srv apt.systemd.daily[4911]: Unable to get Terminal Size. The TIOCGWINSZ ioctl didn't work. The COLUMNS and LINES environment
May 31 14:02:45 unstable-srv apt.systemd.daily[4911]: No containers need to be restarted.
May 31 14:02:45 unstable-srv apt.systemd.daily[4911]: Unable to get Terminal Size. The TIOCGWINSZ ioctl didn't work. The COLUMNS and LINES environment
May 31 14:02:45 unstable-srv apt.systemd.daily[4911]: No user sessions are running outdated binaries.
May 31 14:02:46 unstable-srv apt.systemd.daily[4911]: All upgrades installed
-- Reboot --
May 31 20:41:49 unstable-srv systemd-journald[13]: Journal started
Os timestamps se alinham como você esperaria - eu não defini o fuso horário dentro do contêiner, então os timestamps estão fora por uma hora exatamente.
EDIT1:
atualizações não assistidas-0.93.1 + nmu1
needrestart-2.11-3
systemd-232-24, upgrade mostrado neste log leva o systemd de 232-23 para 232-24 (de acordo com o dpkg.log)
EDIT2:
Tentativa de reproduzir, desclassificando os componentes do systemd para 232-23 (usando o teste Debian) e, em seguida, disparando novamente manualmente o apt-daily.service . Ele foi atualizado com sucesso, mas não travou o contêiner novamente.
Eu também instalei apt-listchanges agora, para registrar algumas informações sobre upgrades quando eles estão instalados.