Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

500 error from cloud-config with no further information #629

Closed
bigpresh opened this issue Jun 3, 2021 · 2 comments · Fixed by #630
Closed

500 error from cloud-config with no further information #629

bigpresh opened this issue Jun 3, 2021 · 2 comments · Fixed by #630
Labels
frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed.

Comments

@bigpresh
Copy link

bigpresh commented Jun 3, 2021

I have used the install script to install the Grafana Cloud Agent, but the config file /etc/grafana-agent.yaml is empty.

Looking at the script, I see that it fetches the config by calling grafana-agentctl cloud-config so I'm trying to do the same.

I'm running:

grafana-agentctl cloud-config -u 'xxx' -p 'xxxx'

It exits with only:

could not retrieve agent cloud config: unexpected status code 500

I don't think it's a problem with the credentials being supplied, as if I e.g. change the API key being passed as the -p argument, I then get a 401 error.

The lack of additional detail in the response is somewhat related to #360 - it's possible that there's something in the response which would tell me what was wrong, but the response I get from cloud-config gives me nothing to go on.

@rfratto
Copy link
Member

rfratto commented Jun 3, 2021

Hi there! We try to keep this repository focused on open source issues rather than anything related to Grafana Cloud specifically. Could you create a support ticket so they can assist you further?

@bigpresh
Copy link
Author

bigpresh commented Jun 3, 2021

Well, my point was more that the tool could report the error more helpfully, which does sound like a useful improvement to me; the actual problem causing the 500 error would be something to talk to support about, indeed.

@github-actions github-actions bot added the frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed. label Feb 23, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants