On Thu, Jan 12, 2023 at 03:31:25PM +0000, Lewis Gaul <lewis.gaul@xxxxxxxxx> wrote:
> Could you suggest commands to run to do this?
# systemd-analyze set-log-level debug
# logger MARK-BEGIN
# ...whatever restart commands
# ...wait for the failure
# logger MARK-END
# systemd-analyze set-log-level info
# journalctl -b | sed -n '/MARK-BEGIN/,/MARK-END/p'
> Should we be suspicious of the host systemd version and/or the fact that
> the host is in 'legacy' mode while the container (based on the systemd
> version being higher) is in 'hybrid' mode? Maybe we should try telling the
> container systemd to run in 'legacy' mode somehow?
I'd be wary of the legacy@host and {hybrid,unified}@container combo.
Also the old versions on the host could mean that the cgroup setup may
be buggy.
(I only have capacity to look into the recent code but the debug logs
above may show something obvious.)
Ideally, you should tell both host and container to run in the unified
mode ;-)
Michal
Attachment:
signature.asc
Description: Digital signature
