stdout logs files such as contrail-api-0-stdout.log is missing in latest 4.0

[Vedamurthy Joshi]

R4.0 Build 4 Ubuntu 16.04 container setup

Earlier /var/log/contrail/contrail-api-0-stdout.log was created due to supervisord_config_files/contrail-api.ini entries.

Probably, in the absense of such config, we just see contrail-api.log , but no stdout/stderr files

root@testbed-1-vm1(controller):/var# find /var/log -name contrail-api*
/var/log/contrail/contrail-api.log
root@testbed-1-vm1(controller):/var#

root@testbed-1-vm1(controller):/var# exit
exit
[root@testbed-1-vm1 controller]# find /var/log -name contrail-api*
/var/log/contrail/controller/contrail-api.log
[root@testbed-1-vm1 controller]#

root@nodei31(controller):/# ps aux |grep contrail-api
root 14139 1.1 0.0 465156 144420 ? Sl May09 104:07 /usr/bin/python /usr/bin/contrail-api --conf_file /etc/contrail/contrail-api.conf --conf_file /etc/contrail/contrail-keystone-auth.conf --conf_file /etc/contrail/contrail-database.conf --worker_id 0
root 17339 0.0 0.0 8872 808 ? S+ 18:52 0:00 grep --color=auto contrail-api
root@nodei31(controller):/# lsof -p 14139 |grep log
contrail- 14139 root 5w REG 0,43 4410550 5607 /var/log/contrail/contrail-api.log
contrail- 14139 root 6w REG 0,43 1420519 5603 /var/log/contrail/api-0-zk.log
contrail- 14139 root 56w REG 0,43 12200 5602 /var/log/contrail/vnc_openstack.err
root@nodei31(controller):/#

[Ignatious Johnson Christopher (ijohnson-x)]

By default stdout and stderr of a systemd unit are sent to syslog.

They are accessible via journalctl command.

[Vedamurthy Joshi (vedujoshi)]

1) Looks like journalctl logs are not persistent.
2) On a contrail-container setup, as we are now having /var/log/contrail on the host mounted on all the containers, these process logs would not be found there.

Per discussion, moving the target to 4.0.1

[Nagendra Prasath (npchandran)]

Planning to use https://docs.docker.com/engine/admin/logging/journald/. Will try it out and update.

[Nagendra Prasath (npchandran)]

https://bugs.launchpad.net/juniperopenstack/+bug/1690893/comments/3 didnt work in our context.

Issues related to creating log files per service with systemd:
https://github.com/systemd/systemd/issues/3991
https://lists.freedesktop.org/archives/systemd-devel/2012-March/004703.html

I suppose we could just send our logs to system's syslog along with journal, which should resolve our current ask.