Boot Journald restarts - rpi4

Troubleshooting
,
1

Hi,
I am on 9.7.0 → 9.7.1 and I’ve been having long boot times. I’ve widdled away boot speed issue by fixing:

  1. Removing realVNC and installing NoMachine for remote access (fantastic performance, extremely low resources).
  2. Running:
timesyncd apt policy systemd-timesyncd 
apt install systemd-timesyncd
systemctl status systemd-timesyncd
  1. Adding dhcpd.service override After=network-pre.target

But, I am seeing activity with Journald at different points in the boot process where is says “Failed to connect stdout to the journal socket”.

Any ideas?

Here is an excerpt:

Sep 07 14:50:53 DietPi systemd-journald[156]: Received SIGTERM from PID 1 (systemd).
Sep 07 14:50:53 DietPi systemd[1]: Stopping systemd-journald.service - Journal Service...
Sep 07 14:50:53 DietPi systemd[1]: systemd-journald.service: Deactivated successfully.
Sep 07 14:50:53 DietPi systemd[1]: Stopped systemd-journald.service - Journal Service.
Sep 07 14:50:53 DietPi systemd[1]: systemd-journald.socket: Deactivated successfully.
Sep 07 14:50:53 DietPi systemd[1]: Closed systemd-journald.socket - Journal Socket.
Sep 07 14:50:53 DietPi systemd[1]: systemd-journald-audit.socket: Deactivated successfully.
Sep 07 14:50:53 DietPi systemd[1]: Closed systemd-journald-audit.socket - Journal Audit Socket.
Sep 07 14:50:53 DietPi systemd[1]: systemd-journald-dev-log.socket: Deactivated successfully.
Sep 07 14:50:53 DietPi systemd[1]: Closed systemd-journald-dev-log.socket - Journal Socket (/dev/log).
Sep 07 14:50:53 DietPi systemd[1]: Finished dietpi-preboot.service - DietPi-PreBoot.
Sep 07 14:50:53 DietPi systemd[1]: Started dietpi-postboot.service - DietPi-PostBoot.
Sep 07 14:50:53 DietPi systemd[1]: Finished ifupdown-pre.service - Helper to synchronize boot up for ifupdown.
Sep 07 14:50:53 DietPi systemd[1]: Reached target network-pre.target - Preparation for Network.
Sep 07 14:50:53 DietPi systemd[1]: Starting dhcpcd.service - DHCP Client Daemon on all interfaces...
Sep 07 14:50:53 DietPi (ifup)[474]: ifup@eth0.service: Failed to connect stdout to the journal socket, ignoring: Connection refused
Sep 07 14:50:53 DietPi systemd[1]: Starting ifup@eth0.service - ifup for eth0...
Sep 07 14:50:53 DietPi (ifup)[476]: ifup@wlan0.service: Failed to connect stdout to the journal socket, ignoring: Connection refused
Sep 07 14:50:53 DietPi systemd[1]: Starting ifup@wlan0.service - ifup for wlan0...
Sep 07 14:50:53 DietPi systemd[1]: Starting networking.service - Raise network interfaces...
Sep 07 14:50:53 DietPi (ifup)[478]: networking.service: Failed to connect stdout to the journal socket, ignoring: Connection refused
Sep 07 14:50:53 DietPi systemd[1]: Starting systemd-networkd.service - Network Configuration...
Sep 07 14:50:53 DietPi (networkd)[484]: systemd-networkd.service: Failed to connect stdout to the journal socket, ignoring: Connection refused
Sep 07 14:50:53 DietPi systemd[1]: Started wpa_supplicant.service - WPA supplicant.
Sep 07 14:50:53 DietPi systemd[1]: Starting polkit.service - Authorization Manager...
Sep 07 14:50:53 DietPi (polkitd)[493]: polkit.service: Failed to connect stdout to the journal socket, ignoring: Connection refused
Sep 07 14:50:53 DietPi systemd[1]: Started polkit.service - Authorization Manager.
Sep 07 14:50:53 DietPi kernel: zram: Added device: zram2
Sep 07 14:50:53 DietPi kernel: zram2: detected capacity change from 0 to 307200
Sep 07 14:50:53 DietPi kernel: brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
Sep 07 14:50:53 DietPi systemd[1]: Listening on systemd-journald.socket - Journal Socket.
Sep 07 14:50:53 DietPi systemd[1]: Listening on systemd-journald-audit.socket - Journal Audit Socket.
Sep 07 14:50:53 DietPi systemd[1]: Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log).
Sep 07 14:50:53 DietPi kernel: 8021q: 802.1Q VLAN Support v1.8
Sep 07 14:50:53 DietPi systemd[1]: Started dhcpcd.service - DHCP Client Daemon on all interfaces.
Sep 07 14:50:53 DietPi kernel: bcmgenet fd580000.ethernet: configuring instance for external RGMII (RX delay)
Sep 07 14:50:53 DietPi kernel: bcmgenet fd580000.ethernet eth0: Link is Down
Sep 07 14:50:53 DietPi systemd[1]: Starting systemd-journald.service - Journal Service...
Sep 07 14:50:53 DietPi systemd[1]: Started systemd-networkd.service - Network Configuration.
Sep 07 14:50:53 DietPi systemd[1]: Started udisks2.service - Disk Manager.
Sep 07 14:50:53 DietPi systemd-journald[579]: Journal started
2

Actually, I find I am still having time-sync issues. I have dietpi-config set to “Boot + Hourly” mode; I’m assuming it has something due to the schedutil adjust the CPU mhz down to 300Mhz.

Was there a fix for this or is it normal?

3

You would need to set CPU to 600. Settings it to 300 will cause time issues as your CPU is to slow now to keep time in sync.

4

Just changed dietpi-config to “daemon + drift” and time is sufficient now.