Troubleshooting: Difference between revisions
| Line 1: | Line 1: | ||
=== Systems work but no logs recorded === | === Systems work but no logs recorded === | ||
==== Symptom ==== | |||
The system operates normally—IPIO outputs respond to events—but no event logs appear in Visor. Expected email alerts may also be missing. | |||
==== Diagnostics: ==== | ==== Diagnostics: ==== | ||
# | # '''Logs but no videos:''' [[Troubleshooting#Possible cause 3: Encoder exception|encoder exception]] | ||
# | # '''No logs at all:''' [[Troubleshooting#Possible cause 2: Broken or full SSD|broken SSD]] '''- do not restart!''' | ||
# | # '''Only older logs:''' [[Troubleshooting#Possible cause 2: Broken or full SSD|full SSD]] '''- do not restart!''' | ||
# | # '''System logs but no event logs and system's new:''' [[Troubleshooting#Possible cause 4: Interpreter exception|Interpreter issue]] | ||
# | # '''System logs and old event logs but no new event logs:''' [[Troubleshooting#Possible cause 1: Vislet exception|Vislet issue]] | ||
==== Possible cause 1: Vislet exception ==== | ==== Possible cause 1: Vislet exception ==== | ||
| Line 18: | Line 20: | ||
===== Diagnostics: ===== | ===== Diagnostics: ===== | ||
# Full disk: Check logs | # '''Full disk:''' | ||
# 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 Visor logs; older logs and videos should remain accessible. | ||
# SSD may need to be | ## Check free space. SSH access yields an exception telling there's no disk space. Restart may solve the issue or may open some space to allow SSH to remove manually, else free space manually. | ||
# '''Overheating:''' 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. | |||
# '''Failed SSD:''' SSD may need to be replaced with a new one. Do not restart until you are ready to attend. | |||
==== Possible cause 3: Encoder exception ==== | ==== 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. | 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: | '''Resolution:''' Restart. If issue continues, open a ticket or escalate. | ||
==== Possible cause 4: Interpreter exception ==== | ==== 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. | 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: | '''Resolution:''' Restart. If issue continues, open a ticket or escalate. | ||
Revision as of 17:57, 18 September 2025
Systems work but no logs recorded
Symptom
The system operates normally—IPIO outputs respond to events—but no event logs appear in Visor. Expected email alerts may also be missing.
Diagnostics:
- Logs but no videos: encoder exception
- No logs at all: broken SSD - do not restart!
- Only older logs: full SSD - do not restart!
- System logs but no event logs and system's new: Interpreter issue
- 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 Visor logs; older logs and videos should remain accessible.
- Check free space. SSH access yields an exception telling there's no disk space. Restart may solve the issue or may open some space to allow SSH to remove manually, else free space manually.
- Overheating: 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.
- Failed SSD: SSD may need to be replaced 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 issue 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 issue continues, open a ticket or escalate.