Fluent-logging generate an error at start

Bug #1796633 reported by Sungil Im
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-helm
Expired
Undecided
Unassigned

Bug Description

The fluent-bit in the Fluent-logging chart generates an error at the start like below.
It is the FileNotFound error for the journal.

+ [ -d /var/log/journal ]
+ export JOURNAL_PATH=/run/log/journal
+ exec /fluent-bit/bin/fluent-bit -c /fluent-bit/etc/fluent-bit.conf
[2018/10/08 07:39:26] [ info] [engine] started (pid=40530)
[2018/10/08 07:39:26] [error] [plugins/in_systemd/systemd_config.c:63 errno=2] No such file or directory
[2018/10/08 07:39:26] [error] [in_systemd] given path /run/log/journal is invalid
[2018/10/08 07:39:26] [error] [in_systemd] cannot initialize
[2018/10/08 07:39:26] [error] Failed initialize input systemd.0
[2018/10/08 07:39:26] [error] [plugins/in_systemd/systemd_config.c:63 errno=2] No such file or directory
[2018/10/08 07:39:26] [error] [in_systemd] given path /run/log/journal is invalid
[2018/10/08 07:39:26] [error] [in_systemd] cannot initialize
[2018/10/08 07:39:26] [error] Failed initialize input systemd.1
[2018/10/08 07:39:26] [ warn] [filter_kube] merge_json_log is deprecated, enabling 'merge_log' option instead
[2018/10/08 07:39:26] [ info] [filter_kube] https=1 host=kubernetes.default.svc.cluster.local port=443
[2018/10/08 07:39:26] [ info] [filter_kube] local POD info OK
[2018/10/08 07:39:26] [ info] [filter_kube] testing connectivity with API server...
[2018/10/08 07:39:26] [ warn] [filter_kube] could not get meta for POD s48

Sungil Im (sungil)
description: updated
Revision history for this message
Gage Hugo (gagehugo) wrote :

Has there been any updates regarding this?

Changed in openstack-helm:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openstack-helm because there has been no activity for 60 days.]

Changed in openstack-helm:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.