invalid_token","error_description":"Invalid refresh token (expired) about firehose-to-syslog HOT 19 CLOSED

Please which version of firehose to syslog are you using ?

from firehose-to-syslog.

This is what we have deployed
schwab branch: https://github.com/malston/firehose-to-syslog/tree/schwab

from firehose-to-syslog.

not sure what version was that

from firehose-to-syslog.

We are also seeing the same error today. We had to restart the firehose app to fix the authentication issue.

version = "1.2.0 - 1cdb840"

Logs we saw in Firehose:

2016-01-25T23:10:50.000+00:00 [App/0] ERR 2016/01/25 23:10:50 Error requesting apps Get https://api.*.*.*.io/v2/apps?inline-relations-depth=2: oauth2: cannot fetch token: 401 Unauthorized
2016-01-25T23:11:50.000+00:00 [App/0] ERR Response: {"error":"invalid_token","error_description":"Invalid refresh token (password changed): *************************************************************"}
2016-01-25T23:11:50.000+00:00 [App/0] ERR [2016-01-25 23:11:50.790796839 +0000 UTC] Exception occurred! Message: Recovered in caching.GetAllApp() Details: runtime error: invalid memory address or nil pointer dereference

Please assist as we need to know how we can avoid this in future, as we will miss those logs if not catched due to this error.

from firehose-to-syslog.

@deepwright "error":"invalid_token","error_description":"Invalid refresh token (password changed)
Seems the password of the user use by the nozzle have been change. Did you change it ?

from firehose-to-syslog.

@madhuchiluka
1- Can you provide the uaa / login server logs ? Need to understand what is going on.
2- Does something happen to this user "svc.scpfirehose_prod" ???
3- The fork you are using put the firehose logic into a goroutine I am not sure your version is thread-safe..
So please try to use the master branch and told me if you get the same error.

from firehose-to-syslog.

Is there any secure FTP server I can upload logs into? plus log file is larger than 10MB
I don't see any issues with the user.
I'll check with my teammate to see if we can deploy master one. we wouldn't able to get the error right away, it usually taking few weeks to reoccur.

from firehose-to-syslog.

Just put somewhere like google drive or something like that.

from firehose-to-syslog.

I have sent logs to [email protected] through Schwab secure messaging system. Please let me know if you not get it. I can try send it to your email directly if you can provide that

from firehose-to-syslog.

You can send here [email protected]

from firehose-to-syslog.

How did you create the user "svc.scpfirehose_prod" ??
authorized-grant-types ??

from firehose-to-syslog.

I have sent out logs to your gmail account. you might have to register or something to view the logs.

We integrated pcf with LDAP. we had to login to pcf instance with svc.scpfirehose_prod to register that account in uaa database then we provided following scopes to that account
scim.read
cloud_controller.admin
doppler.firehose
and other default ones.

from firehose-to-syslog.

That the scope, I want the grants_type like

$uaac clients
 admin
    scope: uaa.none
    resource_ids: none
    authorized_grant_types: client_credentials
    autoapprove:
    action: none
    authorities: clients.read password.write clients.secret clients.write uaa.admin scim.write scim.read
    lastmodified: 1452911318522
  cc_routing
    scope: uaa.none
    resource_ids: none
    authorized_grant_types: authorization_code refresh_token
    autoapprove:
    action: none
    authorities: uaa.none
    lastmodified: 1452911318087
  cf
    scope: cloud_controller.admin cloud_controller.read cloud_controller.write doppler.firehose openid password.write
        routing.router_groups.read scim.read scim.write uaa.user
    resource_ids: none
    authorized_grant_types: implicit password refresh_token
    autoapprove: true
    access_token_validity: 600
    refresh_token_validity: 2592000
    action: none
    authorities: uaa.none
    lastmodified: 1452911318869

from firehose-to-syslog.

I have sent full list to your email address.

from firehose-to-syslog.

@madhuchiluka Can you try the branch https://github.com/cloudfoundry-community/firehose-to-syslog/tree/feature/uuid_support ??

Please use godep go build to build it.

Thanks

from firehose-to-syslog.

@madhuchiluka any updates ?

from firehose-to-syslog.

No more update, closing that should be fix.

from firehose-to-syslog.

what was the fix for this? has this been merged into any of the releases?

from firehose-to-syslog.

I will comment on #81

from firehose-to-syslog.