3ec85d7821
* docs: rework files structure * rewrite documentation entrypoint * update category files and use yml * add manuals entry page * update admin-manual titles and page order * create releases sections * move ssl configuration to reverse proxy * docs: update website vars and links * update release note codeblock syntax key * resurect troubleshooting guide * Update freeipa custom auth documentation * add notice about the state of the documentation * update the backup documentation * tmp: allow to deploy the website for preview * Don't use require.resolve for plugins * Update the main page link dest * update development environment title * rewrite the install/upgrade/migrate as guides * update website docs sections links * Fix urls * move release note to documentation * move home links to vars files * tmp: update deploy url * add react to tsconfig to handle jsx linting * fix: replace absolute url to relative path to files * tmp: allow CI Website dpeloy on working branch * Update release note title * use default syntax highlighting theme * update the troubleshooting guide * Wording * use CodeBlock components * Better prose * remove api_client config section * fix prose errors * update import prefix for vars file * reroder docs manuals links * use sentence capitalization for page titles * Wording * missing word * Update note about syslog log file * wording
52 lines
1.7 KiB
Markdown
52 lines
1.7 KiB
Markdown
---
|
|
title: Troubleshooting
|
|
sidebar_position: 90
|
|
---
|
|
|
|
This guide walk you though the steps required to troubleshoot LibreTime.
|
|
|
|
## Services status
|
|
|
|
When facing a problem with LibreTime the first reflex is to verify whether the services are running.
|
|
|
|
In the web interface, go to **Settings** > **Status** to see the state of the services.
|
|
|
|
|
|
|
|
If a service isn't running, you should search for details using the tool running those services.
|
|
On a common setup, you should use the systemd service status:
|
|
|
|
```bash
|
|
sudo systemctl status libretime-celery
|
|
```
|
|
|
|
:::note
|
|
|
|
Be sure to replace the service name with the problematic one.
|
|
|
|
:::
|
|
|
|
## Logs
|
|
|
|
The next place to search for details on potential errors are the log files.
|
|
On a common setup, you should search for the following files:
|
|
|
|
- `/var/log/libretime/analyzer.log` contains logs from the analyzer,
|
|
- `/var/log/libretime/api.log` contains logs from the api,
|
|
- `/var/log/libretime/legacy.log` contains logs from the legacy app,
|
|
- `/var/log/libretime/liquidsoap.log` contains logs from liquidsoap,
|
|
- `/var/log/libretime/playout.log` contains logs from playout.
|
|
|
|
For some LibreTime services, you can set a higher log level using the `LIBRETIME_LOG_LEVEL` environment variable, or by running the service by hand and using a command line flag:
|
|
|
|
```bash
|
|
sudo -u www-data libretime-analyzer --config /etc/airtime/airtime.conf --log-level debug
|
|
```
|
|
|
|
- `/var/log/syslog` contains most of the system logs combined. This log file may contain information that the application logger wasn't able to log, such as early startup errors. You can get the LibreTime logs using:
|
|
|
|
```bash
|
|
sudo tail -f "/var/log/syslog" | grep "libretime-"
|
|
```
|
|
|
|
- `/var/log/apache2/error.log` contains logs from the web server.
|