td-agent user does not have permission to create /var/run/fluentd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Expired
|
Medium
|
Unassigned |
Bug Description
When elasticsearch is configured as an output fluentd will continuously crash with the following stack trace:
2019-09-18 13:38:24 -0500 [error]: #0 unexpected error error_class=
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /opt/td-
2019-09-18 13:38:24 -0500 [error]: #0 /usr/sbin/
2019-09-18 13:38:24 -0500 [error]: #0 /usr/sbin/
2019-09-18 13:38:24 -0500 [error]: #0 unexpected error error_class=
2019-09-18 13:38:24 -0500 [error]: #0 suppressed same stacktrace
2019-09-18 13:38:24 -0500 [info]: Worker 0 finished unexpectedly with status 1
creating the directory inside the container and assigning ownership to the td-agent user resolves the issue.
Interesting, I think I saw a fix for this in a patch.