On an installer setup the server logs to stdout/journald only, so x:Log/query fails with "No log tracers configured on the server" (inbuxa-servercrates/jmap/src/registry/mapping/log.rs). The list shows the error's type and then the generic empty state ("No log entries yet. When one is added, it shows up here."), which reads as if logging were working.
Fix: for that error on the Logs page, say that the server writes its log to the system journal (journalctl -u inbuxa-server -f) and that adding a Log tracer under Telemetry shows it here. More generally, show the error's description rather than its type in DynamicList, and don't show the empty state while there's an error. The installer side is inbuxa/inbuxa-installer#70.
Reported on the forum (https://community.coffeylabs.org/t/232, post 27).
On an installer setup the server logs to stdout/journald only, so `x:Log/query` fails with "No log tracers configured on the server" (`inbuxa-server` `crates/jmap/src/registry/mapping/log.rs`). The list shows the error's `type` and then the generic empty state ("No log entries yet. When one is added, it shows up here."), which reads as if logging were working.
Fix: for that error on the Logs page, say that the server writes its log to the system journal (`journalctl -u inbuxa-server -f`) and that adding a Log tracer under Telemetry shows it here. More generally, show the error's description rather than its type in `DynamicList`, and don't show the empty state while there's an error. The installer side is inbuxa/inbuxa-installer#70.
Fixed in #220. On a server with no Log tracer, the Logs page now says the log is going to the journal, gives the commands to follow it, and links to Tracers. Lists also show the server's error description instead of its type. Thanks to khashmeshab (https://community.coffeylabs.org/t/232). In the next console RC; the installer side is inbuxa/inbuxa-installer#70.
Fixed in #220. On a server with no Log tracer, the Logs page now says the log is going to the journal, gives the commands to follow it, and links to Tracers. Lists also show the server's error description instead of its type. Thanks to khashmeshab (https://community.coffeylabs.org/t/232). In the next console RC; the installer side is inbuxa/inbuxa-installer#70.
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.
Reported on the forum (https://community.coffeylabs.org/t/232, post 27).
On an installer setup the server logs to stdout/journald only, so
x:Log/queryfails with "No log tracers configured on the server" (inbuxa-servercrates/jmap/src/registry/mapping/log.rs). The list shows the error'stypeand then the generic empty state ("No log entries yet. When one is added, it shows up here."), which reads as if logging were working.Fix: for that error on the Logs page, say that the server writes its log to the system journal (
journalctl -u inbuxa-server -f) and that adding a Log tracer under Telemetry shows it here. More generally, show the error's description rather than its type inDynamicList, and don't show the empty state while there's an error. The installer side is inbuxa/inbuxa-installer#70.Fixed in #220. On a server with no Log tracer, the Logs page now says the log is going to the journal, gives the commands to follow it, and links to Tracers. Lists also show the server's error description instead of its type. Thanks to khashmeshab (https://community.coffeylabs.org/t/232). In the next console RC; the installer side is inbuxa/inbuxa-installer#70.