docs/Features/Admin-Panel/Problems/README.md
Status: Implemented · Owner: xet7
Admin Panel → Problems is where a WeKan admin sees what is wrong or in
progress: performance (CPU / RAM / disk), data-safety and recovery, migrations and
repairs, broken data, and the causes that can keep users off the login page. Open
it at Admin Panel → Problems (you must be an admin — currentUser.isAdmin).
The same information is available without the Admin Panel, from the server
command line, via snap run wekan.problems — see Snap.md — so an
admin who only has server (snap) access can read it without being given Admin
Panel access.
The Summary tab shows a Status overview at the top:
Below that is the acknowledge list of the Security / Speed / Tests problem streams.
Settings — the two panes that came from the removed Features tab, which are settings rather than reports but are what an admin reaches for when something is unsafe or noisy:
Reports — Security Report, Impersonation Report, Performance, Speed, Tests, CPU
usage, Broken Cards, Files Report, Rules Report, Boards Report, Cards Report and
Recovery. Every one is the same shared table page:
a search box, the total, page X / N, prev/next, and one page of rows fetched from
the server at a time. Performance sits with the Speed / Tests / CPU usage streams
it configures: card loading is automatic per board size, with
CARDS_LOADING=all|lazy|auto and CARDS_LOADING_LAZY_THRESHOLD for operators.
| Page | What it covers |
|---|---|
| Repairs.md | Automatic board data-repairs (#6484 lists that vanish, orphaned/missing-swimlane cards): what they fix, when they run (board open, server startup, during migration), and the progress dashboard. |
| Migrations.md | The MongoDB ↔ FerretDB v1 (SQLite) text-data migration, the repair phase it runs, and the shared blue, Product-name-branded progress dashboard. |
| Login-Problems.md | Everything that can make the login page show "Must be logged in" or a stuck "Loading, please wait." spinner, and how to fix each. |
| Snap.md | The snap run wekan.problems commands that print this whole overview (and problem-specific detail like CPU) as text. |
| CPU-usage.md | CPU-usage monitor / governor and the CPU report. A pegged ferretdb process is the usual cause of slow pages. |
| RAM-usage.md | RAM-usage report. |
| Disk-usage.md | Disk-usage report. |
| Recovery.md | SQLite corruption/bloat safety and the automatic Recovery history. |
After an upgrade, several sites reported the login page showing "Must be logged
in", or — after login — the logo with "Loading, please wait." and a spinner that
never finished; pages took five or more minutes, the All Boards counts stayed at
0, and some labels showed raw i18n keys (e.g. allboards.starred). In top the
ferretdb process was pegged near 200% CPU for a long time. That is the FerretDB
v1 (SQLite) backend saturated under WeKan's poll load — often a migration/repair
still running, or simply a heavy instance on SQLite.
Problems → Status and snap run wekan.problems make that visible: an admin can now
see at a glance "a migration/repair is in progress; that is why logins are slow",
or "nothing is running; the backend itself is saturated — consider MongoDB", both
from the browser and from the server command line.
Design.md is the design behind the panes below: one summary row per problem rather than a row per event, the per-actor tally inside it, the IPv4 and IPv6 columns, and the API report, per-address login tally and blocking that are still being built. Read it if you are changing how Problems records things rather than what it shows.
Every pane of this tab, in the order the menu shows them. The slug is what
the address uses: /admin/problems/<slug>.
| Menu path | URL slug | Page |
|---|---|---|
| Problems / Summary | summary | — |
| Problems / Security | security | — |
| Problems / Notifications | notifications | — |
| Problems / Security Report | security-report | — |
| Problems / Impersonation Report | impersonation | — |
| Problems / Performance | performance | — |
| Problems / Speed | speed | — |
| Problems / Tests | tests | — |
| Problems / CPU usage | cpu | CPU-usage.md |
| Problems / Broken Cards | broken-cards | — |
| Problems / Files Report | files | — |
| Problems / Rules Report | rules | — |
| Problems / Boards Report | boards | — |
| Problems / Cards Report | cards | — |
| Problems / Recovery | recovery | Recovery.md |
| Problems / Offices | office | — |
| Problems / API | api | API.md |
| Problems / Database problems | database | — |
| Problems / Filesystem integrity | integrity | — |
16 of these 19 panes has no page of its own yet. A dash is a gap to fill, not a pane that does nothing - what the pane shows is described in this README until somebody writes it up.