Mender demo deployment stuck at "rebooting"

General Discussions
,
1

Mender demo deployment stuck at “rebooting”.

I am working through the Mender demo, and the first “OS-level/full system” deployment is stuck at rebooting. I think it’s actually past the reboot phase - what I believe happened is, the update occurred and the reboot happened, but the system didn’t come back up fully from the reboot. And now the deployment is stuck looking for a reboot. I have since brought the system up fully, but it still shows as stuck.

Any thoughts?

Thank you for your time.

2

I have encountered, what I call “successfully failed” behaviour, on several occasions. The update run as expected. Main problem is that the mender client is not reporting properly to the backend and thus the UI is stuck in “Rebooting” animation.

Provide some deployment logs from /etc/mender/deployments.000*.*.log

Another reason could be that the device is stuck in a bootloop or mender client did not start due to failed update somewhere after

    NeedsArtifactReboot)
        # This will trigger a propper reboot
        # https://github.com/mendersoftware/mender/blob/master/Documentation/update-modules-v3-file-api.md#artifactreboot-state
        echo "Automatic"
        ;;

in update module.

In my case, sometimes I see “Rebooting” animation or “Deployment failed” followed by _INCONSISTENT.

2023-11-10 14:43:47 +0000 UTC info: Running Mender client version: 3.4.0
2023-11-10 14:43:47 +0000 UTC info: State transition: update-fetch [Download_Enter] -> update-store [Download_Enter]
2023-11-10 14:43:47 +0000 UTC info: Installer: authenticated digital signature of artifact
2023-11-10 14:43:49 +0000 UTC info: Running Mender client version: 3.4.0
2023-11-10 14:43:49 +0000 UTC error: Mender shut down in state: update-store
2023-11-10 14:43:49 +0000 UTC info: State transition: init [none] -> cleanup [Error]
2023-11-10 14:43:49 +0000 UTC info: State transition: cleanup [Error] -> update-status-report [none]
2023-11-10 14:43:49 +0000 UTC info: Device unauthorized; attempting reauthorization
2023-11-10 14:43:49 +0000 UTC info: Output (stderr) from command "/usr/share/mender/identity/mender-device-identity": no suitable interfaces found
2023-11-10 14:43:49 +0000 UTC error: Failed to authorize with "https://<url>": failed to build authorization request: failed to obtain authorization message data: failed to obtain identity data: wait for helper failed: exit status 1
2023-11-10 14:43:49 +0000 UTC warning: Reauthorization failed with error: transient error: authorization request failed
2023-11-10 14:43:49 +0000 UTC error: Failed to report status: transient error: authorization request failed
2023-11-10 14:43:49 +0000 UTC error: error reporting update status: reporting status failed: transient error: authorization request failed
2023-11-10 14:43:49 +0000 UTC error: Failed to send status to server: transient error: reporting status failed: transient error: authorization request failed
2023-11-10 14:43:49 +0000 UTC info: State transition: update-status-report [none] -> update-retry-report [none]
2023-11-10 14:44:44 +0000 UTC info: State transition: update-retry-report [none] -> update-status-report [none]
2023-11-10 14:44:44 +0000 UTC info: Device unauthorized; attempting reauthorization
2023-11-10 14:44:44 +0000 UTC info: successfully received new authorization data from server https://<url>
2023-11-10 14:44:44 +0000 UTC info: Local proxy started
2023-11-10 14:44:44 +0000 UTC info: Reauthorization successful

The MAC address is part of the identity:

2023-11-10 14:43:49 +0000 UTC info: Output (stderr) from command "/usr/share/mender/identity/mender-device-identity": no suitable interfaces found

The way my SBC is behaving is causing the error in my case. Starting mender as the “last” process, did not resolve the issue. Having hard time to adjust mender-device-identity