Bootstrap gives the server a single stdout tracer, and the server only adds its own Log tracer when it has none, so installed servers never wrote log files and the console's Logs page was always empty. Setup now adds a Log tracer next to the stdout one using the setup API key. It matches the server's default: inbuxa.log, rotated daily, and deleted after keepForDays, which is 30 on a new install. On the host the files go to /var/log/inbuxa. The unit creates that directory with LogsDirectory=, and the installer creates it too. In a container they go to /var/lib/inbuxa/logs on the data volume. /var/log/inbuxa isn't a volume there, and a volume mounted at that path would be owned by root, so the image's user couldn't write to it.
Existing installs get the tracer from inbuxa upgrade --key - (which now takes --key and works even when no upgrade is due) or from re-running install with --key. Until then, both commands say what to run. The installer doesn't touch a Log tracer that an admin set up. When a server moves between a container and the host, the installer's tracer follows it. Moving to the host leaves the container's log files behind in its volume, and uninstall --purge removes /var/log/inbuxa.
The server's data inventory already reports log files from the live tracer and keepForDays, so it needs no change. The installer ships no privacy text. The docs need one fix: docs/run/monitoring.md on inbuxa.org says a new install writes to /var/log/inbuxa, but on container installs made by the installer the files are in /var/lib/inbuxa/logs.
Bootstrap gives the server a single stdout tracer, and the server only adds its own Log tracer when it has none, so installed servers never wrote log files and the console's Logs page was always empty. Setup now adds a Log tracer next to the stdout one using the setup API key. It matches the server's default: inbuxa.log, rotated daily, and deleted after keepForDays, which is 30 on a new install. On the host the files go to /var/log/inbuxa. The unit creates that directory with LogsDirectory=, and the installer creates it too. In a container they go to /var/lib/inbuxa/logs on the data volume. /var/log/inbuxa isn't a volume there, and a volume mounted at that path would be owned by root, so the image's user couldn't write to it.
Existing installs get the tracer from `inbuxa upgrade --key -` (which now takes --key and works even when no upgrade is due) or from re-running install with --key. Until then, both commands say what to run. The installer doesn't touch a Log tracer that an admin set up. When a server moves between a container and the host, the installer's tracer follows it. Moving to the host leaves the container's log files behind in its volume, and uninstall --purge removes /var/log/inbuxa.
The server's data inventory already reports log files from the live tracer and keepForDays, so it needs no change. The installer ships no privacy text. The docs need one fix: docs/run/monitoring.md on inbuxa.org says a new install writes to /var/log/inbuxa, but on container installs made by the installer the files are in /var/lib/inbuxa/logs.
Fixes #70
Bootstrap takes one tracer and was given stdout, and the server adds its
own file tracer only when it has none, so no installed server ever wrote
a log file and Observability › Logs, which reads them, was always empty.
A Log tracer is now added beside the stdout one with the setup's API key:
the server's own default (inbuxa.log, rotated daily, plain text), deleted
after inbuxa:LogSettings.keepForDays, which a new install sets to 30. On
the host the files go to /var/log/inbuxa, which the unit makes with
LogsDirectory= and the installer makes too; in a container, where that
path is not a volume and the image's user could not write to one mounted
there, to /var/lib/inbuxa/logs on the data volume.
An install from before this is given its tracer by `inbuxa upgrade --key`
or a run of install with --key, and is told so until then. A tracer an
administrator set up is left alone, and a server moved between a
container and the host takes the installer's tracer with it. A move to
the host leaves the container's log files in its volume, and purge
removes /var/log/inbuxa.
Rebased on main (rc.24 pins) and tested on the debian13 lab: install-local 28, install-host 48 and the new upgrade-log-files 15 (OLD_REF=v27.1-rc.11), all passed. A container install writes /var/lib/inbuxa/logs/inbuxa.log. in the data volume; a host install writes /var/log/inbuxa, owned by inbuxa and kept by LogsDirectory; an install from before this gets them with inbuxa upgrade --key -, says so without a key, and a second run adds no second tracer.
Rebased on main (rc.24 pins) and tested on the debian13 lab: install-local 28, install-host 48 and the new upgrade-log-files 15 (OLD_REF=v27.1-rc.11), all passed. A container install writes /var/lib/inbuxa/logs/inbuxa.log.<date> in the data volume; a host install writes /var/log/inbuxa, owned by inbuxa and kept by LogsDirectory; an install from before this gets them with `inbuxa upgrade --key -`, says so without a key, and a second run adds no second tracer.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Bootstrap gives the server a single stdout tracer, and the server only adds its own Log tracer when it has none, so installed servers never wrote log files and the console's Logs page was always empty. Setup now adds a Log tracer next to the stdout one using the setup API key. It matches the server's default: inbuxa.log, rotated daily, and deleted after keepForDays, which is 30 on a new install. On the host the files go to /var/log/inbuxa. The unit creates that directory with LogsDirectory=, and the installer creates it too. In a container they go to /var/lib/inbuxa/logs on the data volume. /var/log/inbuxa isn't a volume there, and a volume mounted at that path would be owned by root, so the image's user couldn't write to it.
Existing installs get the tracer from
inbuxa upgrade --key -(which now takes --key and works even when no upgrade is due) or from re-running install with --key. Until then, both commands say what to run. The installer doesn't touch a Log tracer that an admin set up. When a server moves between a container and the host, the installer's tracer follows it. Moving to the host leaves the container's log files behind in its volume, and uninstall --purge removes /var/log/inbuxa.The server's data inventory already reports log files from the live tracer and keepForDays, so it needs no change. The installer ships no privacy text. The docs need one fix: docs/run/monitoring.md on inbuxa.org says a new install writes to /var/log/inbuxa, but on container installs made by the installer the files are in /var/lib/inbuxa/logs.
Fixes #70
a3565bb05dtofe7e08e189Rebased on main (rc.24 pins) and tested on the debian13 lab: install-local 28, install-host 48 and the new upgrade-log-files 15 (OLD_REF=v27.1-rc.11), all passed. A container install writes /var/lib/inbuxa/logs/inbuxa.log. in the data volume; a host install writes /var/log/inbuxa, owned by inbuxa and kept by LogsDirectory; an install from before this gets them with
inbuxa upgrade --key -, says so without a key, and a second run adds no second tracer.