I have two systems running NVIDIA jetpack 5.0.2, based on Ubuntu 20.04. /etc and /boot are identical on both systems. On the first system, after boot, if I try to run logger I get an error /dev/log: Connection refused. If I run systemctl restart systemd-journald-dev-log.socket then it works fine until the next reboot. On the second system, logger works reliably every time.
I’ve run systemd-analyze plot and there are some differences between the two systems:
on the first system: systemd-journald-dev-log.socket seems to run for only a short time
on the first system: rsyslog.service seems to start much much later, right after systemd-journald-dev-log.socket ends
You said you can make it back to work with restarting “systemd-journald-dev-log.socket”. So, what is the status of this service in the first time after boot up? It is possible that it fails at boot.
You can use journalctl to check the status of the systemd service status and it will tell us whether there is error or not.