heka not able to read mariadb log file

[prameswar]

sudo docker logs heka

2016/11/04 11:26:16 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:17 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:17 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:17 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:17 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:18 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:18 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:18 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:18 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:19 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:19 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:19 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:19 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:20 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:20 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:20 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:20 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:21 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:21 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:21 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:21 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:22 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:22 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:22 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:22 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied
2016/11/04 11:26:23 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/394007

[Eduardo Gonzalez (egonzalez90)]

I faced the same error in centos source from master

[Jeffrey Zhang (jeffrey4l)]

how this error happen. why other service do not have such issue?

[zhubingbing (zhubingbing)]

we can add env:UMSK=0640 in heka continer to solve this problmes;

refer to link:

http://dev.mysql.com/doc/refman/5.7/en/file-permissions.html
https://bugs.mysql.com/bug.php?id=57406

[OpenStack Infra (hudson-openstack)]

Change abandoned by prameswar (<email address hidden>) on branch: master
Review: https://review.openstack.org/394007
Reason: zhubingbing will add PS for it.

[Jeffrey Zhang (jeffrey4l)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA