From dc96f2cc717d3f4191ec22956a64bb749e3852f0 Mon Sep 17 00:00:00 2001 From: Paul Philippov Date: Wed, 14 Dec 2022 16:32:28 -0500 Subject: [PATCH] Create trouble-majestic.md --- en/trouble-majestic.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 en/trouble-majestic.md diff --git a/en/trouble-majestic.md b/en/trouble-majestic.md new file mode 100644 index 0000000..e4175f1 --- /dev/null +++ b/en/trouble-majestic.md @@ -0,0 +1,15 @@ +# OpenIPC Wiki +[Table of Content](../index.md) + +## Troubleshooting: Majestic does not work, camera reboots + +To troubleshoot majestic you first need to get access to its logs, right to the moment as it crashes, +that leads to watchdog rebooting the system and deleting the logs from the camera. So you need to copy +log to a safe place as it populates. And you can achieve that using ssh access to the camera and piping +output to a file on your desktop. + +Run this command on your Linux desktop and wait for the camera to reboot once again. The resulting log +file will be in the same directory named and dated similar to _majestic-2022-12-14.log_ +``` +ssh root@192.168.1.10 "killall majestic; sleep 2; majestic" > majestic-$(date +"%F").log +```