Bug #19216
open
we don't log to journald and that's confusing
Added by Peter Amstutz almost 2 years ago.
Updated about 2 months ago.
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.
- Description updated (diff)
- Subject changed from Controller not logging to journalctl? to we don't log to journalctl and that's confusing
- Description updated (diff)
- Subject changed from we don't log to journalctl and that's confusing to we don't log to journald and that's confusing
- Target version changed from 2022-07-06 to 2022-07-20
- Target version changed from 2022-07-20 to 2022-08-03 Sprint
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"
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.
- Target version changed from 2022-08-03 Sprint to 2022-08-17 sprint
- Target version changed from 2022-08-17 sprint to 2022-08-31 sprint
- Target version deleted (
2022-08-31 sprint)
- Target version set to Future
Also available in: Atom
PDF
Updated by 
Updated by