systemd 저널 서비스를 시작하는 데 2시간이 걸립니다.

systemd 저널 서비스를 시작하는 데 2시간이 걸립니다.

/etc/hostname에서 호스트 이름을 변경한 비교적 새로운 데비안 설치가 있습니다. 부팅하는 동안 다음 메시지가 나타납니다.

[ 7406.882872] systemd[1]: Starting Journal Service...
[ 7406.920156] systemd-journald[2733]: File /run/log/journal/bfd65934be53484d980ccc7304e5fb23/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 7497.066194] systemd[1]: systemd-journald.service: Start operation timed out. Terminating.
[ 7587.320229] systemd[1]: systemd-journald.service: State 'stop-final-sigterm' timed out. Killing.
[ 7677.573560] systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode.
[ 7677.586742] systemd[1]: Failed to start Journal Service.
[ 7677.593748] systemd[1]: systemd-journald.service: Unit entered failed state.
[ 7677.601384] systemd[1]: systemd-journald.service: Failed with result 'timeout'.
[ 7677.625405] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
[ 7677.635948] systemd[1]: Stopped Journal Service.

최종적으로 결정하기 전에 약 2시간 동안 이 작업을 반복해서 수행합니다.

[ 7948.405911] systemd[1]: Starting Journal Service...
[ 7948.443473] systemd-journald[2746]: File /run/log/journal/bfd65934be53484d980ccc7304e5fb23/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 7948.516285] systemd[1]: Started Journal Service.

SSH를 실행하고 실행하면 sudo systemctl enable systemd-journald.service다음과 같은 결과가 나타납니다.

sudo: unable to resolve host [hostname redacted]
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.

나는 에 대한 경험이 거의 없습니다 systemd. 이 문제의 원인은 무엇이며 정상적으로 부팅되도록 수정하려면 어떻게 해야 합니까?

관련 정보