Open geissonator opened 5 years ago
Our automation does this to hard reset the journal at the end of a run:
systemctl stop systemd-journald.service && rm -rf /var/log/journal && systemctl start systemd-journald.service
When this is run, phosphor-gevent stops responding to REST queries. My guess is some race condition with the new code that logs REST calls to the journal.
A workaround is to just run "systemctl restart phosphor-gevent"
Our automation does this to hard reset the journal at the end of a run:
When this is run, phosphor-gevent stops responding to REST queries. My guess is some race condition with the new code that logs REST calls to the journal.
A workaround is to just run "systemctl restart phosphor-gevent"