Debian Jessie의 nspawn 컨테이너에서 실행할 때 Debian이 불안정하고 충돌합니다.
호스트 머신에서:
$ 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.
컨테이너 내부의 일기장. 마지막 로그 메시지는 무인 업그레이드에서 나온 것입니다(자동 모드에서 다시 시작해야 함).
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
여기에 있는 타임스탬프는 예상한 대로 정렬됩니다. 컨테이너 내부에 시간대를 설정하지 않았기 때문에 타임스탬프는 정확히 1시간 차이가 납니다.
- 제가 찾아야 할 다른 것이 있나요?
- 이는 이와 같은 문제를 디버그하는 데 도움이 되는 추가 로깅/모니터링이 필요하다는 것을 의미합니까?
- 이 교통사고가 익숙하다고 생각하는 사람이 있나요?
편집 1:
무인 업그레이드-0.93.1+nmu1은
다시 시작해야 함-2.11-3
시스템 D-232-24,이 로그에 표시된 업그레이드는 systemd를 232-23에서 232-24로 업그레이드합니다.(dpkg.log에 따르면)
편집 2:
systemd 구성 요소를 232-23(Debian으로 테스트)으로 다운그레이드한 다음 수동으로 다시 트리거하여 재현을 시도했습니다 apt-daily.service. 업그레이드는 성공했지만 컨테이너는 다시 충돌하지 않았습니다.
지금 설치 했으며 apt-listchanges설치 중에 업그레이드에 대한 일부 정보를 기록하겠습니다.