Installs have no log files, so the console's Logs page is always empty #70

Closed
opened 2026-11-16 15:15:52 +00:00 by jcoffey-dev · 1 comment
Owner

Reported on the forum (https://community.coffeylabs.org/t/232, post 27): Observability › Logs says "No log entries yet" on a no-containers install.

Bootstrap sets a single Stdout tracer (internal/jmap/setup.go), so the server never adds its default Log tracer (it does that only when there are no tracers), and the console's Logs page, which reads log files, has nothing to show. Logs go to the journal (journalctl -u inbuxa-server.service) or docker compose logs server.

Fix: add a Log tracer next to the Stdout one (prefix inbuxa.log, daily rotation; the server's retention job already deletes old files). For host installs add LogsDirectory=inbuxa to the unit so /var/log/inbuxa exists and belongs to inbuxa; for containers use a path on the data volume. Add it to existing installs on the next installer run (x:Tracer/set). File logs hold IP and email addresses, so the privacy text should mention them. The console side is tracked in inbuxa-admin.

Reported on the forum (https://community.coffeylabs.org/t/232, post 27): Observability › Logs says "No log entries yet" on a no-containers install. Bootstrap sets a single Stdout tracer (`internal/jmap/setup.go`), so the server never adds its default Log tracer (it does that only when there are no tracers), and the console's Logs page, which reads log files, has nothing to show. Logs go to the journal (`journalctl -u inbuxa-server.service`) or `docker compose logs server`. Fix: add a Log tracer next to the Stdout one (prefix `inbuxa.log`, daily rotation; the server's retention job already deletes old files). For host installs add `LogsDirectory=inbuxa` to the unit so `/var/log/inbuxa` exists and belongs to `inbuxa`; for containers use a path on the data volume. Add it to existing installs on the next installer run (`x:Tracer/set`). File logs hold IP and email addresses, so the privacy text should mention them. The console side is tracked in inbuxa-admin.
jcoffey-dev added the
priority
p2
bug
labels 2026-11-16 15:15:52 +00:00
jcoffey-dev self-assigned this 2026-11-16 15:15:52 +00:00
jcoffey-dev added this to the 27.1 milestone 2026-11-16 15:23:26 +00:00
Author
Owner

Fixed in #71. A new install now gives the server daily log files, so the console's Logs page has something to show: /var/lib/inbuxa/logs in the server's data volume for a container install, /var/log/inbuxa for a host install. An install from before this gets them with inbuxa upgrade --key -, using an API key made in the console; without a key, upgrade says so. Thanks to khashmeshab (https://community.coffeylabs.org/t/232). In the next installer RC.

Fixed in #71. A new install now gives the server daily log files, so the console's Logs page has something to show: /var/lib/inbuxa/logs in the server's data volume for a container install, /var/log/inbuxa for a host install. An install from before this gets them with `inbuxa upgrade --key -`, using an API key made in the console; without a key, upgrade says so. Thanks to khashmeshab (https://community.coffeylabs.org/t/232). In the next installer RC.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-installer#70