6fe4bafc2a
Also discussed previously in #213 (Github Pull Request). shared-secret-auth and rest-auth logging is still at `INFO` intentionally, as user login events seem more important to keep. Those modules typically don't spam as much.
1.4 KiB
1.4 KiB
Maintenance and Troubleshooting
How to see the current status of your services
You can check the status of your services by using systemctl status
. Example:
sudo systemctl status matrix-nginx-proxy
● matrix-nginx-proxy.service - Matrix nginx proxy server
Loaded: loaded (/etc/systemd/system/matrix-nginx-proxy.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2018-11-14 19:38:35 UTC; 49min ago
You can see the logs by using journalctl. Example:
sudo journalctl -fu matrix-synapse
Increasing Synapse logging
Because the Synapse Matrix server is originally very chatty when it comes to logging, we intentionally reduce its logging level from INFO
to WARNING
.
If you'd like to debug an issue or report a Synapse bug to the developers, it'd be better if you temporarily increasing the logging level to INFO
or even DEBUG
.
Example configuration (inventory/host_vars/matrix.DOMAIN/vars.yml
):
matrix_synapse_log_level: "DEBUG"
matrix_synapse_storage_sql_log_level: "DEBUG"
matrix_synapse_root_log_level: "DEBUG"
Re-run the playbook after making these configuration changes.
Postgres
See the dedicated PostgreSQL Maintenance documentation page.