{% extends "base/base.html" %} {% load static %} {% block title %} Server status {% endblock title %} {% block page_heading %} Server status {% endblock page_heading %} {% block main_content %}
Django v{{ django_version }}
Huey v{{ huey_version }}
PyMuPDF v{{ pymupdf_version }}
ZXing-C++ v{{ zxingcpp_version }}
Plom's background processes (“chores”) are managed by Huey.
{% for queue in queues %}
Enqueued: {{ queue.length }}
Results: {{ queue.result_count }}
Other info: {{ queue.other_info }}
Pending chores: {{ queue.pending3 }}
(at most three)
As of early 2025, the management of these chores has proven to be a frequent source of bugs in Plom, for example, because the error messages if one fails are not always displayed to users and because they are occasionally killed by the OS during low-memory situations.
The database must be working or you couldn't be here.
Almost all data and settings are stored in the database.
Plom's documentation is available at https://plom.readthedocs.io.
(1/3 of the time, this button fail with a 404 error, 1/3 of the time with a 500 error (div by zero), and 1/3 it will succeed and change the button text to "button pushed")