Error downloading the agent while running the diagnose

[fblupi]

Describe the bug

I've installed appsginal on my Ruby on Rails application. When I run the diagnose locally (using a MacOS M1) it works. But when I repeat the process on production Ubuntu with x86_64 arch, it fails with the error attached in the section below.

I tried downloading manually the package from the URL in the logs with curl and it works fine. I've also decompressed the downloaded file and run the diagnose task with the env variables _APPSIGNAL_AGENT_PATH and APPSIGNAL_AGENT_PATH pointing the folder where I decompressed with the same issues. I've also moved the downloaded files to the ext directory of the gem. But the issue persists as it tries to download the agent. The agent I downloaded seems to work as it returns me the version where calling it with the --version argument.

The exception is raised on this block: https://github.com/appsignal/appsignal-ruby/blob/main/ext/base.rb#L135

I also tried with the latest published version of the appsignal gem without success.

I'm running out of ideas. Could you help me out if there's anything I can do from my side?

To Reproduce

Steps to reproduce the behavior:

• Using AppSignal for Ruby gem version 4.4.0, Ruby 3.1.7, and OpenSSL 3.0.2
• Specifying the APPSIGNAL_PUSH_API_KEY env variable with a correct API key
• Running RAILS_ENV=production bundle exec appsignal diagnose raise this error:

Could not download archive from any of our mirrors. Please make sure your network allows access to any of these mirrors.
Attempted to download the archive from the following urls:
- URL: https://d135dj0rjqvssy.cloudfront.net/0.35.29/appsignal-x86_64-linux-all-static.tar.gz
  Error: ArgumentError: wrong number of arguments (given 4, expected 0)
- URL: https://appsignal-agent-releases.global.ssl.fastly.net/0.35.29/appsignal-x86_64-linux-all-static.tar.gz
  Error: ArgumentError: wrong number of arguments (given 4, expected 0)

[unflxw]

Hi @fblupi,

I have tried to reproduce the issue using the latest version of the AppSignal gem (OpenSSL 3.0.15, Ruby 3.1.7, AppSignal for Ruby 4.5.13) but I have not been able to reproduce it. Could you provide a reproduction case, like a GitHub repository with instructions that reliably cause this issue?

[fblupi]

This is the repo: https://github.com/Platoniq/decidim-ub. You can use the deps/appsignal branch. As I mention in the issue, I cannot reproduce it locally with development environment. I can only reproduce in a ubuntu server with production environment.

[unflxw]

@fblupi I have been unable to reproduce the issue so far.

First, I am booting the ruby:3.1.7 Docker image, cloning the Platoniq/decidim-ub repository, switching to the deps/appsignal branch, and running bundle install. This installs AppSignal for Ruby 4.4.0.

Then, I run RAILS_ENV=production bundle exec appsignal diagnose. No error like the one in the issue description appears. The diagnose report works as expected.

Note that the agent is installed at bundle install time, when the dependency is installed, not when you run the appsignal binary.

[fblupi]

In my case it seems the agent is being downloaded while running the appsignal diagnose. I'm going to share the diagnosis report via email to support@appsignal.com

[unflxw]

Thank you! Please mention this GitHub thread in the support conversation.

[unflxw]

Can you confirm whether you're running bundle install before attempting RAILS_ENV=production bundle exec appsignal diagnose? If you could also share your Ubuntu version, that would allow me to attempt to reproduce it with greater accuracy.

[fblupi]

Yes, I run it during the deployment. I use Ubuntu 22.04 and the kernel version is 5.15.0-136

[shairyar]

Support conversation on Intercom (internal link)

[backlog-helper]

• This issue has not had any activity in 14 days. Please provide a status update if it is still relevant. Closed it if it is no longer relevant. Or move it to another column if it's blocked or requires another look at it. - (More info)

---

This is a message from the daily scheduled checks.

New issue guide | Backlog management | Rules | Feedback

[fblupi]

I'm still waiting for a response

[unflxw]

Hi @fblupi, apologies for not providing a more definitive response. We're still unable to reproduce this on our end. It is quite likely that it relates to your server's network connection. Could it be that it's sitting behind a proxy that intercepts or blocks connections?