`Failed to retrieve config` in Arm64 Architecture

  • What Grafana version and what operating system are you using?

Grafana Cloud 9.2.4 (2022-11-07) and I am trying to monitor Alamalinux 9 Arm64 server.

  • What are you trying to achieve?

To monitor Linux Server.

  • How are you trying to achieve it?

By following the instruction mentioned in the dashboard.

  • What happened?
--- Using package system rpm. Downloading and installing package for arm64
warning: /var/tmp/rpm-tmp.V1BHxn: Header V4 RSA/SHA512 Signature, key ID 24098cb6: NOKEY
--- Retrieving config and placing in /etc/grafana-agent.yaml
Failed to retrieve config

  • What did you expect to happen?

To install config successfully.

  • Can you copy/paste the configuration(s) that you are having problems with?
sudo ARCH=arm64 GCLOUD_STACK_ID="REDACTED" GCLOUD_API_KEY="REDACTED" GCLOUD_API_URL="https://integrations-api-eu-west.grafana.net" /bin/sh -c "$(curl -fsSL https://raw.githubusercontent.com/grafana/agent/release/production/grafanacloud-install.sh)"
  • Did you receive any errors in the Grafana UI or in related logs? If so, please tell us exactly what they were.

Oops! Something went wrong. Make sure the install instructions were copied correctly and check for any optional configurations. If you’re still running into issues, read the troubleshooting instructions.

  • Did you follow any online instructions? If so, what is the URL?

I even tried to add config in /etc/grafana-agent.yaml manually but it didn’t work.

Logs from journalctl -b -u grafana-agent.service are like this:

Stopping Monitoring system and forwarder...
grafana-agent[96201]: ts=2022-11-15T14:47:48.192934156Z caller=gokit.go:72 level=info msg="=== received SIGINT/SIGTERM ===\n*** exiting"
grafana-agent[96201]: ts=2022-11-15T14:47:48.206520903Z caller=node.go:319 level=info agent=prometheus component=cluster msg="shutting down node"
grafana-agent[96201]: ts=2022-11-15T14:47:48.206576863Z caller=node.go:345 level=info agent=prometheus component=cluster msg="node shut down"
grafana-agent[96201]: ts=2022-11-15T14:47:48.206609143Z caller=node.go:169 level=info agent=prometheus component=cluster msg="node run loop exiting"
grafana-agent[96201]: ts=2022-11-15T14:47:48.206664464Z caller=config_watcher.go:104 level=info agent=prometheus component=cluster msg="config watcher run loop exiting"
grafana-agent[96201]: ts=2022-11-15T14:47:48.210548443Z caller=main.go:74 level=info msg="agent exiting"
systemd[1]: grafana-agent.service: Deactivated successfully.
systemd[1]: Stopped Monitoring system and forwarder.
systemd[1]: Started Monitoring system and forwarder.
grafana-agent[96278]: ts=2022-11-15T14:47:48.823597121Z caller=server.go:191 level=info msg="server listening on addresses" http= grpc= http_tls_enabled=false grpc_tls_enabled=f>
grafana-agent[96278]: ts=2022-11-15T14:47:48.828172623Z caller=node.go:85 level=info agent=prometheus component=cluster msg="applying config"
grafana-agent[96278]: ts=2022-11-15T14:47:48.828738906Z caller=remote.go:180 level=info agent=prometheus component=cluster msg="not watching the KV, none set"
grafana-agent[96278]: ts=2022-11-15T14:47:48.833841612Z caller=zapadapter.go:78 level=info component=traces msg="Traces Logger Initialized"
grafana-agent[96278]: ts=2022-11-15T14:47:48.846206393Z caller=reporter.go:103 level=info msg="running usage stats reporter"
systemd[1]: Stopping Monitoring system and forwarder...
grafana-agent[96278]: ts=2022-11-15T14:51:07.310641168Z caller=gokit.go:72 level=info msg="=== received SIGINT/SIGTERM ===\n*** exiting"

Sorry, if I missed something!
Thank You!

Hi @sahil,

Welcome to the :grafana: community support forums !!

This seems an error about the gpg key. There was a similar issue reported earlier for RPM-based distributions where I wrote a detailed answer. Please have a look into it and hopefully, it can also solve your problem.

Hello and thanks for the reply!
The grafana-agent is installing fine but it’s unable to fetch the config at the time of installation. I am using hosted Grafana Cloud.
Should I post it in Grafana Cloud category?
Thank You!

This seems more fit for the Grafana Cloud category.

I have already moved it there, so someone from the cloud community will update here further.

1 Like

Fix the problem myself!
If you were on free trial and set up a custom domain, remove it to fix this issue as you need paid plan for it. And it was causing request was not successful: unauthorized and will fail to retrieve the config!


How should I remove the custom domain?

I mean if I uninstall integration I lose all Linux servers that I previously installed Grafana on them?

Is there a way to work around this with out having to reinstall Grafana on all Linux servers again?