Keepalived logs needs to be writed on correct directory

[Carlos Cesario]

Currently keepalived write the logs on /var/log/kolla/haproxy instead /var/log/kolla/keepalived.

Last login: Sun Apr 3 15:33:08 2016 from operator
root@kolla-network:~# docker exec -it keepalived /bin/bash
root@kolla-network:/# ls -la /var/log/kolla/
total 16
drwxrwsr-x 4 102 kolla 4096 Apr 3 14:53 .
drwxrwxr-x 8 root syslog 4096 Apr 3 14:34 ..
drwxr-sr-x 2 102 kolla 4096 Apr 3 14:32 haproxy
drwxr-sr-x 2 1000 kolla 4096 Apr 3 14:54 neutron

root@kolla-network:/# ls -la /var/log/kolla/haproxy/
total 56
drwxr-sr-x 2 102 kolla 4096 Apr 3 14:32 .
drwxrwsr-x 4 102 kolla 4096 Apr 3 14:53 ..
-rw-r--r-- 1 102 kolla 35105 Apr 3 14:55 haproxy.log
-rw-r--r-- 1 102 kolla 6617 Apr 3 14:54 keepalived.log

root@kolla-network:/# tail -f /var/log/kolla/haproxy/keepalived.log
<6>2016-04-03T14:54:01Z kolla-network Keepalived_healthcheckers[14]: Netlink: filter function error
<6>2016-04-03T14:54:02Z kolla-network Keepalived_vrrp[15]: Netlink: filter function error
<6>2016-04-03T14:54:02Z kolla-network Keepalived_vrrp[15]: Netlink: filter function error
<6>2016-04-03T14:54:02Z kolla-network Keepalived_vrrp[15]: Netlink: filter function error
<6>2016-04-03T14:54:19Z kolla-network Keepalived_healthcheckers[14]: Netlink: filter function error
<6>2016-04-03T14:54:19Z kolla-network Keepalived_healthcheckers[14]: Netlink: filter function error
<6>2016-04-03T14:54:19Z kolla-network Keepalived_healthcheckers[14]: Netlink: filter function error
<6>2016-04-03T14:54:19Z kolla-network Keepalived_vrrp[15]: Netlink: filter function error
<6>2016-04-03T14:54:19Z kolla-network Keepalived_vrrp[15]: Netlink: filter function error
<6>2016-04-03T14:54:19Z kolla-network Keepalived_vrrp[15]: Netlink: filter function error

[Éric Lemoine (elemoine)]

If you want the keepalived logs to be placed in /var/log/kolla/keepalived/keepalived.log then you need to change the path in the FileOutput configuration. See [*]. I'd also recommend creating a keepalived-specific heka configuration file, heka-keepalived.toml.j2, and move the keepalived heka configuration from heka-haproxy.toml.j2 to that file.

[*] <https://github.com/openstack/kolla/blob/master/ansible/roles/common/templates/heka-haproxy.toml.j2#L14>

[Carlos Cesario (ccesario)]

Eric, thank you a lot by your tips and comments. This help me a lot.

The proposed patch is in https://review.openstack.org/#/c/300896/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/300896
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=1e8abe35926a96bd6d8fab8c299b6ee21adddacd
Submitter: Jenkins
Branch: master

commit 1e8abe35926a96bd6d8fab8c299b6ee21adddacd
Author: Carlos Cesario <email address hidden>
Date: Sun Apr 3 15:30:45 2016 -0300

    Make Heka write Keepalived logs to dedicated directory

    Currently Heka writes the keepalived logs in
    /var/log/kolla/haproxy/keepalived.log.
    This commit changes this to /var/log/kolla/keepalived/keepalived.log.

    Closes-Bug: #1565499
    Change-Id: I3033097bd77ddbf72948697b34a6a499ea903083

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/301452
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=0d81a59d091c14ff1b10b171bde820c5fe7db37d
Submitter: Jenkins
Branch: stable/mitaka

commit 0d81a59d091c14ff1b10b171bde820c5fe7db37d
Author: Carlos Cesario <email address hidden>
Date: Sun Apr 3 15:30:45 2016 -0300

    Make Heka write Keepalived logs to dedicated directory

    Currently Heka writes the keepalived logs in
    /var/log/kolla/haproxy/keepalived.log.
    This commit changes this to /var/log/kolla/keepalived/keepalived.log.

    Closes-Bug: #1565499
    Change-Id: I3033097bd77ddbf72948697b34a6a499ea903083
    (cherry picked from commit 1e8abe35926a96bd6d8fab8c299b6ee21adddacd)

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/kolla 2.0.0.0rc4 release candidate.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/kolla 2.0.0 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/kolla 1.1.0 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/kolla 3.0.0.0b1 development milestone.