Fehlersuche in Weblate

Bugs can behave as application crashes or as various misbehavior. You are welcome to collect info on any such issue and submit it to the issue tracker.

Debugmodus

Wenn Sie den Debugmodus aktivieren, werden die Ausnahmen im Webbrowser angezeigt. Dies ist nützlich, um Probleme in der Weboberfläche zu beheben, eignet sich aber nicht für eine Produktionsumgebung, da es Auswirkungen auf die Leistung hat und möglicherweise private Daten preisgibt.

In a production environment, use ADMINS to receive e-mails containing error reports, or configure error collection using a third-party service.

Weblate logs

Weblate can produce detailed logs of what is going on in the background. In the default configuration it uses syslog and that makes the log appear either in /var/log/messages or /var/log/syslog (depending on your syslog daemon configuration).

The Celery process (see Hintergrundaufgaben mit Celery) usually produces its own logs as well. The example system-wide setups logs to several files under /var/log/celery/.

Docker containers log to their output (as per usual in the Docker world), so you can look at the logs using docker-compose logs.

Siehe auch

Sample configuration enthält die LOGGING Konfiguration.

Not processing background tasks

A lot of things are done in the background by Celery workers. If things like sending out e-mails or component removal does not work, there might a related issue.

Dinge, die in diesem Fall zu überprüfen sind:

Keine E-Mails von Weblate erhalten

You can verify whether outgoing e-mail is working correctly by using the sendtestemail management command (see Invoking management commands for instructions on how to invoke it in different environments) or by using Verwaltungsoberfläche under the Tools tab.

These send e-mails directly, so this verifies that your SMTP configuration is correct (see Konfigurieren ausgehender E-Mail). Most of the e-mails from Weblate are however sent in the background and there might be some issues with Celery involved as well, please see Not processing background tasks for debugging that.

Analyse von Anwendungsabstürzen

In case the application crashes, it is useful to collect as much info about the crash as possible. This can be achieved by using third-party services which can collect such info automatically. You can find info on how to set this up in Sammeln von Fehlerberichten.

Stille Ausfälle

Lots of tasks are offloaded to Celery for background processing. Failures are not shown in the user interface, but appear in the Celery logs. Configuring Sammeln von Fehlerberichten helps you to notice such failures easier.

Leistungsprobleme

In case Weblate performs badly in some scenario, please collect the relevant logs showing the issue, and anything that might help figuring out where the code might be improved.

In case some requests take too long without any indication, you might want to install dogslow along with Sammeln von Fehlerberichten and get pinpointed and detailed tracebacks in the error collection tool.

Falls die langsame Leistung mit der Datenbank zusammenhängt, können Sie auch die Protokollierung aller Datenbankabfragen aktivieren, indem Sie nach der Aktivierung von DEBUG die folgende Konfiguration verwenden:

LOGGING["loggers"]["django.db.backends"] = {"handlers": ["console"], "level": "DEBUG"}