Actions
Bug #19216
open
we don't log to journald and that's confusing
Story points:
-
Release:
Release relationship:
Auto
Description
I have arvados-controller installed but failing to start.
If you check journalctl, there is no logs.
It turns out it logs to /var/log/syslog
But that's not very obvious. We should either log to both (although, I think one of the reasons it logs to syslog is that journalctl was getting overwhelmed by logging volume) or at least see if we can log a message to journalctl that tells you where to look.
Updated by Tom Clegg almost 3 years ago
afaik packaged services do log to journald (except rails and nginx). 9tee4 has a /etc/systemd/system/arvados-controller.service.d/override.conf to bypass journald:
[Service] Type=simple ExecStart= ExecStart=/bin/bash -ce "exec /usr/bin/arvados-controller 2>&1 | /usr/bin/rotatelogs -f /var/log/arvados/%%Y%%m%%d-arvados-controller 86400"
Updated by Peter Amstutz almost 3 years ago
Except that in practice they don't, at least on the nodes I was testing on, the only logs I could find were in syslog, not journald, unless I'm doing it wrong.
Actions