systemd stops working until VM is rebooted

Sellis Markos 1 Reputation point

The symptom is that systemctl will timeout - until the VM is rebooted. Everything else works normally in the VM.

In Boot Diagnostics I cannot see Serial Log (it timeouts), however the screenshot option shows the same error message multiple times :

"systemd - journald: Failed to send WATCHDOG-1 notification message: Transport endpoint is not connected"

Note that the VM (ALMA Linux 9) runs perfectly well, all services are ok, except systemctl.

Has anyone seen this before?

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,381 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. vipullag-MSFT 25,441 Reputation points

    Hello Sellis Markos

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    Based on the error message you provided, it seems like there might be an issue with the systemd-journald service. One possible solution is to try restarting the service by running the following command:

    sudo systemctl restart systemd-journald

    If that doesn't work, you can try resetting the journal files by running the following commands:

    sudo systemctl stop systemd-journald

    sudo rm /var/log/journal/*

    sudo systemctl start systemd-journald

    If the issue persists even after trying these solutions, Support team will be able to check and help on this. I would recommend you to open a azure support case.

    Hope this helps.