On 2/1/22 12:48, Ranbir wrote:
On Thu, 2022-01-27 at 13:38 -0500, Daniel Walsh wrote:
It could be a bug in that version, but it would be nice if you could try on the latest version. I haven't been able to try on the latest upstream release.
podman 3.4 should be showing up in RHEL8.5 in the next week or two, don't know how quickly it will show up in Rocky. I did try the latest version available on CentOS Stream: 3.4.1-dev. I tried setting journald as the log driver and gave the log path, but no file was created.
When set to k8s-file, the file _does_ get created and written to. In addition, the log file looks exactly (minus the journald time stamps) like it does when flexget writes its own log.
On a hunch, I checked the journal for a different container that's running sabnzbd and noticed its logs were in there. Yet, I hadn't specified anything for it. Is journald the default log driver? It is going forward but not for RHEL8, because of issues on systemd and journal not being available to rootless users. Anyway, the log looked the same, although the text colour was all red, which I've seen in the journal before for errors. Can this be changed?
I switched the flexget container back to not specifying a log driver which sent its logs to the journal. But, this time the logs looked nothing like the k8s-file log file that was being written to before. It's actually missing information. See below for the comparisons.
Here's a raw log file written by flexget itself:
2022-02-01 12:34:03 INFO task tv_shows Rerunning the task in case better resolution can be achieved. 2022-02-01 12:34:03 INFO task premieres Plugin next_series_episodes has requested task to be ran again after execution has completed. Reason: Look for next season 2022-02-01 12:34:04 INFO task premieres Rerunning the task in case better resolution can be achieved.
Here's the contents of the k8s-file (not much activity before I changed it):
2022-01-31T23:35:54.992078575-05:00 stdout F 2022-01-31 23:35:54 INFO scheduler Starting scheduler 2022-01-31T23:39:35.081444166-05:00 stdout F 2022-01-31 23:39:35 INFO manager Got SIGTERM. Shutting down.
Here's the journal for the same container:
$ sudo journalctl CONTAINER_NAME=flexget -n 5 -- Logs begin at Fri 2022-01-28 12:23:01 EST, end at Tue 2022-02-01 12:46:37 EST. -- Feb 01 12:34:02 containment01 conmon[31764]: [172B blob data] Feb 01 12:34:03 containment01 conmon[31764]: [122B blob data] Feb 01 12:34:03 containment01 conmon[31764]: [172B blob data] Feb 01 12:34:03 containment01 conmon[31764]: [183B blob data] Feb 01 12:34:04 containment01 conmon[31764]: [122B blob data]
Where'd the rest of the information go?