Congegni/sintonia
7
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Merge branch '3.0.x' into main

Browse source
This commit is contained in:
jo 2023-02-26 20:16:38 +01:00
commit 9384df7be2
No known key found for this signature in database
GPG key ID: B2FEC9B22722B984
16 changed files with 200 additions and 61 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/admin-manual/setup/install.md
View file

@ -150,6 +150,12 @@ When upgrading be sure to run the installer using the same arguments you used du
:::
:::warning
To update the LibreTime nginx configuration file, for example to change the `--listen-port`, make sure to add the `--update-nginx` flag to allow overwriting the existing configuration file.
:::
If you need to change some configuration, the install script can be configured using flags or environment variables. Changing the listening port of LibreTime or whether you want to install some dependency by yourself, you could run the following:
```bash

56
docs/admin-manual/troubleshooting.md
View file

@ -5,36 +5,21 @@ sidebar_position: 90
This guide walk you though the steps required to troubleshoot LibreTime.
## Services status
## FAQ
When facing a problem with LibreTime the first reflex is to verify whether the services are running.
### I cannot login the interface "Oops! Something went wrong!"
In the web interface, go to **Settings** > **Status** to see the state of the services.
You might be accessing the interface from an invalid URL. Make sure that the URL in your browser and the one set in your configuration file in `[general.public_url]` are the same.
![](./troubleshooting-status-page.png)
Make sure to check the legacy logs at `/var/log/libretime/legacy.log`.
Or directly from a terminal:
References:
```bash
sudo systemctl --all --plain | egrep 'libretime|nginx|php.*-fpm'
```
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-worker
```
:::note
Be sure to replace the service name with the problematic one.
:::
- https://discourse.libretime.org/t/version-3-0-1-debian-oops-something-went-wrong/1400
## Logs
The next place to search for details on potential errors are the log files.
The first place to search for details on potential errors are the log files.
The `/var/log/syslog` file 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 follow the logs using:
@ -61,6 +46,33 @@ sudo -u libretime libretime-analyzer --config /etc/libretime/config.yml --log-le
The `/var/log/nginx/libretime.error.log` file contains logs from the web server.
## Services status
The next reflex is to verify whether the services are running.
In the web interface, go to **Settings** > **Status** to see the state of the services.
![](./troubleshooting-status-page.png)
Or directly from a terminal:
```bash
sudo systemctl --all --plain | egrep 'libretime|nginx|php.*-fpm'
```
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-worker
```
:::note
Be sure to replace the service name with the problematic one.
:::
## Test the stream inputs
To test or debug your input streams, you can use the [`tools/test-stream-input.py`](https://github.com/libretime/libretime/blob/main/tools/test-stream-input.py) script to send a test sound to your stream inputs.