Re: logsearch-for-cloudfoundry instance failing


Josh Ghiloni
 

This should probably be in cf-dev, but I will say that the first error looks like your user/client does not have the `doppler.firehose` scope in its credentials. As for the second error, looks like the logsearch vm could not verify the whole cert chain of your SSL cert. (Clearing up the second may clear up the first)

--
Josh Ghiloni | ECS Team, now part of CGI | Senior Cloud Architect
5575 DTC Parkway Suite 135, Greenwood Village, CO 80111
T: (303) 590-5427
jghiloni(a)ecsteam.com | www.cgi.com <http://www.cgi.com> | www.ecsteam.com <http://www.ecsteam.com>

On 5/31/17, 8:53 AM, "Kieran Robinson" <kieran.robinson7(a)gmail.com> wrote:

Hey Guys,

We have been having an issue when trying to deploy logsearch, all VM’s are running within CF and all instances running for log search except `logsearch-for-cloudfoundry` which is failing. We have been unable to figure out this issue after troubleshooting for a few days. I was wondering if anyone else ran into similar issues or would have any guidance on possible solutions.

I have included two logs below, one from the instance which is failing `logsearch-for-cloudfoundry` and the second from the log-api instance running in CF

From logsearch-for-cloudfoundry

```
Exception occurred! Message: Closing connection with traffic controller due to error Details: Error dialing trafficcontroller server: Unauthorized error: You are not authorized. Error: Invalid authorization.
```

From traffic controller

```
Error getting auth data: Post https://uaa.cf.prod-infra.gl1.allstate.com/check_token: remote error: tls: handshake failure
```

Join cf-bosh@lists.cloudfoundry.org to automatically receive all group messages.