These logs tell us about internal errors or diagnostic information. They are accessed through Terminal or the Superuser panel (red dashboard) .
You may see them through terminal like so. You may need to become root if you dont see any information about Shinobi.
pm2 logs --lines 100
These logs tell us about internal errors or diagnostic information.
You can make these logs more informative by adding the following snippet to line 2 of your conf.json
Additionally if you want the logs to start showing stacktraces you can add
Here is a quick way to restart Shinobi and begin viewing a fresh log stream. This command only works as root. You may need to add sudo if using another user.
pm2 flush && pm2 restart camera && pm2 logs
These logs tell us about the Monitor Processes, like FFmpeg errors and warnings or when the Monitor has started or updated.
via the Global Log Stream
via the Monitor Stream window
via the Monitor Settings window
These logs are not saved by default. You can enable saving them by toggling the Monitor Settings window to Advanced in the bottom right corner then scrolling down to the Logging section and set it to save to Logs. You can leave the Log level as Warning. Once set these Logs will appear along side your User Logs .
This information will show you about who has logged in to your group or information about connected apps associated to the account.
Here you can find information about failures in the client side.
These logs are only available on browsers that offer the Developer Console. Usually this is only available on PC or Mac versions of browsers.