permission failure on loggregator_trafficcontroller_security due missing bpm config

[renelehmann]

Hi

Since loggregator release v104.0 and the use of BPM the loggregator_trafficcontroller cannot startup anymore due access violation on the security event log.
There are wrong file permission settings now.

Error:

2018/10/22 20:58:38.656639 Unable to open access log: open /var/vcap/sys/log/loggregator_trafficcontroller/loggregator_trafficcontroller_security_events.log: permission denied
panic: Unable to open access log: open /var/vcap/sys/log/loggregator_trafficcontroller/loggregator_trafficcontroller_security_events.log: permission denied

file permission:

log-api/0caa00a6-80c0-426a-9ea1-af7d19a0647e:~# ls -al /var/vcap/sys/log/loggregator_trafficcontroller/loggregator_trafficcontroller_security_events.log
---------- 1 vcap vcap 23711400 Oct 22 20:31 /var/vcap/sys/log/loggregator_trafficcontroller/loggregator_trafficcontroller_security_events.log

Related sources:
https://github.com/cloudfoundry/loggregator/blob/d4c6cfea2e83497ed922a08ad7ebedba947e82b3/trafficcontroller/app/traffic_controller.go#L172-L176

BPM commit:
f72613d

Thanks for looking into it and fixing ;-)
Rene

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/161446392

The labels on this github issue will be updated when the story is started.

[Johannes Tuchscherer]

@renelehmann Thanks for troubleshooting this. We will take a look and fix it ASAP.

[Andrew Poydence]

@renelehmann Good catch! Fixed: cloudfoundry/loggregator@5555777

[Johannes Tuchscherer]

This has been done and fixed. Thanks for reporting this.