Log files
The platform consists of several components, and not all of them write to the in-database system log. This page maps each component to where its log output lives.
| Component | Log location |
|---|---|
| Recording service (MiaRec recorder) | Log messages in the database — Administration › Maintenance › System Log. With trace enabled, trace files are written to /var/log/miarec/trace/ (Linux) or Data\log\trace (Windows). |
| Web portal | Log messages in the database (System Log). The Apache web server additionally logs to /var/log/httpd/ (Linux) or Data\log\apache (Windows). |
| Celery (background task scheduler/workers) | /var/log/miarecweb/celery/ or /var/log/celery/ (Linux); Data\log\celery (Windows). |
| Redis (cache and task broker) | /var/log/redis_*/ (Linux); Data\log\redis (Windows). |
| Operating system | /var/log/messages (Linux); Event Viewer (Windows). |
Tip
Start with the System Log in the web UI — most recorder and web-portal errors surface there with stack traces. Fall back to the file logs when a component cannot reach the database at all (for example Celery failing to start, or Apache errors before the application loads).
Related pages
- System log — the in-database log and its retention settings.
- Troubleshooting — enabling recorder trace logging.
- System status — live health of the same components.