Troubleshooting
Common problems, where the logs live, and how to get support.
Start on the Health page — it shows every camera's status and every storage pool's state in one place, and most problems surface there first.
A camera is offline
Work through these in order:
-
Network — can the box reach the camera at all?
ping <camera-ip>If not: check cabling, the camera's power (PoE budget?), and — for cameras on another VLAN — that routing between the box and the camera network is in place.
-
Credentials — if the camera is reachable but won't connect, CoreSight distinguishes the two cases: an unreachable error is network, an authentication error means the username/password on the camera changed. Update the credentials on the camera's entry on the Cameras page.
-
RTSP stream — the camera may answer but serve the stream on a non-default path. Check the RTSP URL in the camera's settings against the vendor's documentation.
The health watchdog detects recovery automatically — once the cause is fixed, the camera returns to online within about 30 seconds.
A camera isn't recording
The red REC dot is missing on the live tile. Check, in order:
- Recording mode — is it set to Off? Set Always/Scheduled/Motion in the camera's recording settings (Recording).
- RTSP URL — a camera without a stream URL can be viewed via discovery-negotiated streams but cannot be recorded. Make sure the camera entry has its RTSP URL set.
- Storage — is there an online storage pool with free space? Check the Storage and Health pages (Storage).
- If scheduled: are you inside the schedule window? If motion: has there been motion?
Then confirm on the Playback page that new footage appears on today's timeline.
AI isn't detecting anything
- AI must be provisioned at install time (
--ai) — a box installed without it records and alarms normally but produces no detections. Re-run the installer with--aito add it (Updating). - Face recognition, ALPR, and fire/smoke each require their additional models to be staged; object detection alone works with the base
--aiinstall. - Detections only occur on cameras with analytics enabled and a working stream — an offline camera detects nothing.
Where the logs live
| Log | Where |
|---|---|
| Installer | /var/log/coresight-install.log |
| Main service | journalctl -u coresightd |
| Web UI service | journalctl -u coresight-web |
| Storage mount helper | journalctl -u coresight-storaged |
| In-app updates | /var/log/vms/update.log and journalctl -u coresight-update@<version> |
Useful starting points:
# Recent warnings and errors from the main service:
journalctl -u coresightd -p warning --since "1 hour ago"
# Follow live:
journalctl -u coresightd -f
# Are all services up?
systemctl status coresight.targetThe UI won't load
- Confirm the services are running:
systemctl status coresight.target. - Confirm you are using https:// — the box serves the UI over HTTPS only.
- A certificate warning on the self-signed default certificate is expected; proceed or install your own certificate.
Getting support
If you're stuck, email support@coresightvms.com. Include:
- The CoreSight version (Settings → About).
- What you were doing and what happened instead.
- Relevant log excerpts (see the table above) — the last lines of
journalctl -u coresightdaround the time of the problem are usually the most valuable.