Troubleshooting: Difference between revisions
| Line 4: | Line 4: | ||
==== Diagnostics: ==== | ==== Diagnostics: ==== | ||
# There are logs but no videos: encoder exception | # There are logs but no videos: [[Troubleshooting#Possible cause 3: Encoder exception|encoder exception]] | ||
# There are no logs at all: broken SSD '''- do not restart!''' | # There are no logs at all: [[Troubleshooting#Possible cause 2: Broken or full SSD|broken SSD]] '''- do not restart!''' | ||
# There are only older logs: full SSD '''- do not restart!''' | # There are only older logs: full SSD '''- do not restart!''' | ||
# There are system logs but no event logs and system's new: interpreter | # There are system logs but no event logs and system's new: interpreter | ||
| Line 15: | Line 15: | ||
==== Possible cause 2: Broken or full SSD ==== | ==== Possible cause 2: Broken or full SSD ==== | ||
A permanent or temporary problem with the '''SSD''' such as high working temperature may break it, permanently or temporarily. In case of an SSD failure system keeps working until it is restarted so do not restart unless you are ready to attend. | A permanent or temporary problem with the '''SSD''' such as high working temperature may break it, permanently or temporarily. In case of an SSD failure system keeps working until it is restarted so do not restart unless you are ready to attend. | ||
===== Diagnostics: ===== | ===== Diagnostics: ===== | ||
# Check free space | # Full disk: Check logs, both older system and event logs including videos should be accessible via Visor. Check free space. SSH access yields an exception telling there's no disk space. If there's no free space, housekeeping may not have worked correctly. Restart may solve the issue or open some space to allow SSH to remove manually. | ||
# Check SSD temperature. Consider changing SSD or improve cooling. A broken SSD may prevent from remote access to the device. If it is warm, cooling the system system may fix the SSD so that a remote access is possible. | # Check SSD temperature. Consider changing SSD or improve cooling. A broken SSD may prevent from remote access to the device. If it is warm, cooling the system system may fix the SSD so that a remote access is possible. | ||
# SSD may need to be changed with a new one. | # SSD may need to be changed with a new one. Do not restart until you are ready to attend. | ||
==== Possible cause 3: Encoder exception ==== | ==== Possible cause 3: Encoder exception ==== | ||
Revision as of 17:48, 18 September 2025
Systems work but no logs recorded
System works as expected which (most probably) means output on IPIO are changing based on events as expected but there's no log of event in records section of Visor, no emails arrive if this was expected.
Diagnostics:
- There are logs but no videos: encoder exception
- There are no logs at all: broken SSD - do not restart!
- There are only older logs: full SSD - do not restart!
- There are system logs but no event logs and system's new: interpreter
- There are system logs and old event logs but no new event logs: Vislet issue
Possible cause 1: Vislet exception
An unhandled exception in the pipeline may break recording. Visor must show previous recordings. H/B may not stop.
Possible cause 2: Broken or full SSD
A permanent or temporary problem with the SSD such as high working temperature may break it, permanently or temporarily. In case of an SSD failure system keeps working until it is restarted so do not restart unless you are ready to attend.
Diagnostics:
- Full disk: Check logs, both older system and event logs including videos should be accessible via Visor. Check free space. SSH access yields an exception telling there's no disk space. If there's no free space, housekeeping may not have worked correctly. Restart may solve the issue or open some space to allow SSH to remove manually.
- Check SSD temperature. Consider changing SSD or improve cooling. A broken SSD may prevent from remote access to the device. If it is warm, cooling the system system may fix the SSD so that a remote access is possible.
- SSD may need to be changed with a new one. Do not restart until you are ready to attend.
Possible cause 3: Encoder exception
This applies only to systems with Jetson modules. Visor and outputs works fine. Emails may fail. Logs are recorded but no video play. System logs show GStreamer/NVidia libraries exceptions. Videos in Visor log page seem to exist but when you try to watch it doesn't load but a indicator keeps turning.
Resolution: restart, if continues open a ticket or escalate.
Possible cause 4: Interpreter exception
An interpreter issue may prevent logs from being recorded. This most probably occurs in systems during deployment and should be found out during initial testing. System must be new, or recently altered and had no prior records of logs and/or video. This applies to event logs only. System logs must be there.
Resolution: restart, if continues open a ticket or escalate.