If your radar agent is unable to communicate with BlazeMeter/Runscope, here are a couple of steps you can take to solve this issue:
- Make sure that you are running the latest version of the agent. You can check your agent version by running it with the
--versionflag. You can download the latest version here.
- Run a
curlrequest on the same machine that the agent is running on, and check that you receive a valid response.
ping -c 5 api.runscope.com
- Run the agent with the
--verboseflag to get a more detailed output, and check for any error messages.
- Check your server's proxy settings to see if it's not blocking any requests to
api.runscope.com. For more information on using the agent with a proxy, check the HTTP/HTTPS Proxy Setup article.
- If the server is successfully communicating with Runscope, and you have checked your proxy settings, check that your API test's environment is not misconfigured to use a disconnected remote agent with the same name.
Radar agent currently performs a DNS pre-check before sending any actual HTTP/s request. If the hostname of the request is unable to be resolved by the local DNS resolver of the system that the agent is running on, the entire tests will fail with a message such as shown next:
"Error communicating with www.example.com
DNS error resolving host: www.example.com: no such host"
This causes issues for users that want to use a proxy to access hosts that are not directly accessible by the system that Radar is running on.
As of Radar agent version 1.9, you can disable DNS pre-checks by through command line interface or config file.
To disable DNS pre-checks:
- Through CLI: --disable-dns-lookup OR --disable-dns-lookup=true
- Through config file: disable-dns-lookup OR disable-dns-lookup=true
To enable DNS pre-checks:
- Through CLI: --disable-dns-lookup=false
- Through config file: disable-dns-lookup=false
Note that the default is set to false (DNS pre-checks enabled).