Last (re)boot info

[MichaelPhilizot]

Hi

Is there a way inside an Axis camera to know the reason why a camera has rebooted?

In standard Linux system, commands like "last" or "journalctl -b -1 -n" can give some clues, but is there something like this in Axis cameras?

Many thanks

[github-actions[bot]]

This automatically generated reply acts as a friendly reminder.

Answers to your questions will most often come from the community, from developers like yourself. You will, from time to time, find that Axis employees answers some of the questions, but this is not a guarantee. Think of the discussion forum as a complement to other support channels, not a replacement to any of them.

If your question remains unanswered for a period of time, please revisit it to see whether it can be improved by following the guidelines listed in Axis support guidelines.

[vivekatoffice]

Hi @MichaelPhilizot ,
Please check the following update here

VAPIX Systemready API

Wait for the new Axis OS release Or you can also try the Beta Axis OS
AXIS OS beta releases

My test output:

Using AXIS Q1615 Mk III Network Camera
AXIS OS version 11.7.52

SSH to the camera does support "journalctl" 😉

[MichaelPhilizot]

Thanks for those information... But in fact, this gives nothing about the reboot reason:

• crash of the system
• power disruption
• reboot command
• ...

Is it possible to make the system journal persistent?

[vivekatoffice]

Hi @MichaelPhilizot ,
Sorry to disappoint you. May be good feedback to include in the new Axis OS or APIs 😉 .

Generally, I use this tool to know the root cause of the crash from the device server report : AXIS Server Report Viewer

Try using this support ACAP to collect logs if it helps:
Support_ACAP

[MichaelPhilizot]

Hi all / @vivekatoffice

I had 2 more reboots of the camera. Here are some logs found in the system log:

2023-12-03T14:00:48.022+01:00 axis-b8a44fxxxxxx [ ERR ] crashdump-detect[1712]: Kernel crashed Sun Dec 3 14:00:18 CET 2023
2023-12-03T14:00:48.042+01:00 axis-b8a44fxxxxxx [ ERR ] crashdump-detect[1713]: [165917.116438][T1384794] [galcore]: GPU[1] hang, automatic recovery.
2023-12-03T14:00:48.042+01:00 axis-b8a44fxxxxxx [ ERR ] crashdump-detect[1713]: [165917.120746][T1384794] [galcore]: recovery done
2023-12-03T14:00:48.613+01:00 axis-b8a44fxxxxxx [ CRIT ] crashdump-detect[1713]: [165946.878873][ C3] SMP: stopping secondary CPUs
2023-12-03T14:00:48.613+01:00 axis-b8a44fxxxxxx [ EMERG ] crashdump-detect[1713]: [165946.872163][ C3] Kernel panic - not syncing: watchdog pretimeout event

2023-12-04T21:02:25.871+01:00 axis-b8a44fxxxxxx [ ERR ] crashdump-detect[1704]: Kernel crashed Mon Dec 4 21:01:56 CET 2023
2023-12-04T21:02:26.635+01:00 axis-b8a44fxxxxxx [ CRIT ] crashdump-detect[1707]: [111696.470419][ C0] SMP: stopping secondary CPUs
2023-12-04T21:02:26.635+01:00 axis-b8a44fxxxxxx [ EMERG ] crashdump-detect[1707]: [111696.463537][ C0] Kernel panic - not syncing: watchdog pretimeout event

Do you know what can explain such crash/reboots?

Best regards