bosh: director syslogs missing since bumping director to 266.3.0
Since bumping our director to 266.x we are missing syslog (/var/log/syslog) director logs.
We debugged it and the following call to Syslog::Logger is called with the correct parameters but no syslogs are written.
Further investigation: 1.) Calling the following from the console (/var/vcap/jobs/director/bin/console)
logger = Syslog::Logger.new('vcap.bosh.director')
logger.log(:info,'message')
On the bosh host vm it logs correctly to /var/log/syslog. Executed from the director container we don’t find the logs on container or hostvm under /var/log/syslog.
2.) We forward logs using the syslog-release configured in /etc/rsyslog.d/rsyslog.conf.
*.* @@IP:Port;SyslogForwarderTemplate
Again:
- Syslogs from the hostvm do get forwarded to the provided endpoint.
- Syslogs from within the director container do NOT get forwarded though the container has the same configuration.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 18 (17 by maintainers)
Ok, I’m going to close the BPM issue for now. When we’ve decided what we want the BOSH behavior to be then we can open another one.
I just wanted to state the goal without saying how to get there. If we need the logs to show up on the host to forward them, that’s fine with me. If there would be another means for forwarding without the logs showing up in the host VM, also good 😉
It’s the first time I’ve heard it requested but it’s worth exploring if it could be supported. I’ve opened an issue on bpm-release to dig into this: https://github.com/cloudfoundry-incubator/bpm-release/issues/68.