Systemd::JournalError: No such file or directory

[dev-on2air]

Im continually getting this warning when running this container in kubernetes.

I've searched and found the:
env:
- name: FLUENTD_SYSTEMD_CONF
value: "disable"

which I've added under the containers section but its not making a difference.

Any idea how to remove those warnings?

[dev-on2air]

thoughts?

[cmrust]

I don't work on this project anymore, but can try to help. I'll assume you're using the associated fluentd-deployment project to deploy this to Kubernetes and that you do not have a need for sourcing logs from systemd and want to disable this.

If so, remove this line from your ConfigMap in Kubernetes: https://github.com/solarwinds/fluentd-deployment/blob/master/kubernetes/fluentd-daemonset-papertrail.yaml#L80

...which will skip loading the following file that manages the systemd sources and filters: https://github.com/solarwinds/fluentd-deployment/blob/master/docker/conf/systemd.conf

Good luck.

[dev-on2air]

awesome, thanks @cmrust . that works to remove the warning. i don't know if I want to remove logging of systemd logs, do I? I just wanted to suppress that warning that happens 2x per second.

[cmrust]

With that error, it would appear that you are missing at least some of the logs that you're trying to pull. You need to ssh to one of the worker nodes itself and use a tool like journalctl to review the kubelet and docker paths specified in the systemd.conf linked above, if you do indeed have systemd logging on the host machines you've chosen. That last part can vary wildly by OS.

In order to ensure you're collecting everything you want, you may need to customize that systemd.conf (or some other logging rules to capture wherever your daemon logs are going), and then get that new conf loaded into the pod either with a volume mount or by repackaging your own fluentd docker image.