[PEBKAC] Breaking changes in Graylog v2.4.5?


(Henk) #1

Just installed / updated to Graylog v2.4.5 on a multi-node setup. Now this API-checks is empty:

  • curl -u user:SECRET -H 'Accept: application/json' -X GET 'http://10.11.12.13:9000/api/cluster?pretty=true'

This check used to work on v2.4.4 and used for monitoring.
Has anything changed in the API and if so is there anyone here to enlighten me? TIA!


(Jochen) #2

No, there’s haven’t been any changes in this area, see http://docs.graylog.org/en/2.4/pages/changelog.html#graylog-2-4-5 for the complete change log and https://github.com/Graylog2/graylog2-server/compare/2.4.4...2.4.5 for a diff on GitHub.

Check the logs of your Graylog nodes.
:arrow_right: http://docs.graylog.org/en/2.4/pages/configuration/file_location.html


(Henk) #3

Thanks Jochen. Using a token for authentication does work, so this is probably a PEBKAC on my side. The token was setup more recently than our checks were updated.

So once a auth-token has been setup, user:password will not work in my opinion.


(Jochen) #4

As a general hint, adding -i (informational) or -v (verbose) to a cURL command will often help identifying the cause of a failed request. :wink:

Nope, authentication with username and password should still work, even if access tokens exist for the user.


(system) #5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.