Closed kinjelom closed 4 years ago
After CF UAA restart, ingestor doesn't start with the old UAA client.
cf-deployment
logsearch
logsearch-for-cloudfoundry
firehose-to-syslog
/var/vcap/jobs/ingestor_cloudfoundry-firehose/bin/pre-start
monit restart uaa
monit restart ingestor_cloudfoundry-firehose
Exception occurred! Message: Error pre-filling cache: Details: Get https://api.cf/v2/apps?results-per-page=100: oauth2: cannot fetch token: 401 Unauthorized Response: {"error":"unauthorized","error_description":"Bad credentials"}
If I call /var/vcap/jobs/ingestor_cloudfoundry-firehose/bin/pre-start every time ingestor_cloudfoundry-firehose starts everything seems to work fine.
ingestor_cloudfoundry-firehose
In my deployment CF/UAA and Logsearch/Ingestor was changing independently firehose-to-syslog client secret. This PR fix this case: https://github.com/cloudfoundry-community/logsearch-boshrelease/pull/153
After CF UAA restart, ingestor doesn't start with the old UAA client.
cf-deployment
: v12.1.0 (UAA: 74.2.0)logsearch
/logsearch-for-cloudfoundry
: v210.3.1,firehose-to-syslog
v0.0.0 ;)Steps to reproduce
/var/vcap/jobs/ingestor_cloudfoundry-firehose/bin/pre-start
monit restart uaa
monit restart ingestor_cloudfoundry-firehose
Workaround
If I call
/var/vcap/jobs/ingestor_cloudfoundry-firehose/bin/pre-start
every timeingestor_cloudfoundry-firehose
starts everything seems to work fine.