Your data. Anywhere you go.

New Relic for iOS or Android

Download on the App Store    Android App on Google play

New Relic Insights App for iOS

Download on the App Store

Learn more

Close icon

CentOS 7.1 failing to resolve



New implementation of a ‘virtual device’ based upon CentOS 7.1. nrsysmond installs fine and runs. As per below the log shows it’s failing to resolve the URL but an NSLookup does without problem. And I can ping it. The service appears to be running. Any help is appreciated

2016-12-20 14:22:14.179 (15847) warning: error connecting app=‘Infrastructure’ rv=7. Retry after delay.
2016-12-20 14:23:14.180 (15847) error: RPM cmd=‘get_redirect_host’ for ‘eb…8f’ failed: Couldn’t resolve host ‘
2016-12-20 14:23:14.180 (15847) warning: error connecting app=‘Infrastructure’ rv=7. Retry after delay.
[root@MAX01EGNYTE02 egnyteservice]# nslookup

Non-authoritative answer: canonical name =

[root@MAX01EGNYTE02 egnyteservice]# ping
PING ( 56(84) bytes of data.
64 bytes from ( icmp_seq=1 ttl=248 time=182 ms
64 bytes from ( icmp_seq=2 ttl=248 time=183 ms
64 bytes from ( icmp_seq=3 ttl=248 time=182 ms

[root@MAX01EGNYTE02 egnyteservice]# service --status-all | grep new
newrelic-sysmond is running…


And a test curl works

[root@MAX01EGNYTE02 egnyteservice]# curl -v

  • About to connect() to port 443 (#0)
  • Trying…
  • Connected to ( port 443 (#0)
  • Initializing NSS with certpath: sql:/etc/pki/nssdb
  • CAfile: /etc/pki/tls/certs/ca-bundle.crt
    CApath: none
  • SSL connection using TLS_RSA_WITH_RC4_128_SHA
  • Server certificate:
  •   subject: CN=*,O="New Relic, Inc.",L=San Francisco,ST=California,C=US
  •   start date: Mar 13 00:00:00 2015 GMT
  •   expire date: Apr 15 23:59:59 2018 GMT
  •   common name: *
  •   issuer: CN=GeoTrust SSL CA - G3,O=GeoTrust Inc.,C=US

GET /status/mongrel HTTP/1.1
User-Agent: curl/7.29.0
Accept: /

< HTTP/1.1 200 OK
< Content-Type: text/plain
< Content-Length: 22
mongrel ==> up (true)


Hi @nathan_mcclintock

That doesn’t seem right, you shouldn’t be able to ping and curl it if the agent can’t. Can I ask, it’s a few days on since this post.

Has this issue resolved itself or does it persist?

Have you manually kicked the nrsysmond process and restarted it?


What was the solution to this, I’m facing the exact same issue? Curl and ping works


@hussain - Can you confirm which agent you are seeing these errors in?? The original post here references the Linux Server Agent - which at this point is deprecated.