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

Couldn't resolve host collector-203.newrelic.com

linux
rfb

#1

Yesterday and today we started receiving alerts about our servers being down, after checking the nrsysmond.log I found this:
sudo tail -f nrsysmond.log
2016-05-17 14:00:54.515 (62036) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-203.newrelic.com
2016-05-17 14:00:54.515 (62036) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2016-05-17 14:01:54.538 (62036) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-203.newrelic.com
2016-05-17 14:01:54.538 (62036) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2016-05-17 14:02:54.570 (62036) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-203.newrelic.com
2016-05-17 14:02:54.570 (62036) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2016-05-17 14:03:54.606 (62036) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-203.newrelic.com
2016-05-17 14:03:54.606 (62036) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2016-05-17 14:04:54.642 (62036) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-203.newrelic.com
2016-05-17 14:04:54.642 (62036) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2016-05-17 14:05:54.669 (62036) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-203.newrelic.com
2016-05-17 14:05:54.669 (62036) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2016-05-17 14:06:49.702 (62036) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Connection time-out
2016-05-17 14:06:49.702 (62036) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed

I searched this forum and found others have had the same problem, but the general stand from new relic seems to be “this is normal”, in our case however, its triggering false alarms, servers are being reported as being offline when they are actually fully functional.

As far as I know (and I should know) we have not made any changes to the firewall and so I cannot identify an issue within our network, is there anything that we can do to troubleshoot this further or fix it completely?


#2

Hi Miguel,

I’m going to go ahead and create a support ticket where we can help investigate this issue. Watch out for my email :e-mail: :blush:


#3

Hi @belgravian,

I thought I’d share what we discovered in the ticket here as well. The Server Not Reporting alerts you experienced were related to DNS latency issues caused by an attack on an upstream DNS provider, if anyone else is concerned an alert may be incorrect, please check our status page to see if the times expected line up. Otherwise please let us know and we’ll be happy to investigate.


#4

Hi there, since two days 3 of my 9 active servers are no more reporting, but servers are okay.

I checked /var/log/newrelic/nrsysmond.log and I have the same error on all servers logs:

2017-04-20 12:53:11.741 (10753) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2017-04-20 12:54:11.755 (10753) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-157.newrelic.com
2017-04-20 12:54:11.755 (10753) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2017-04-20 12:55:11.768 (10753) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-157.newrelic.com
2017-04-20 12:55:11.768 (10753) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2017-04-20 12:56:11.780 (10753) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-157.newrelic.com
2017-04-20 12:56:11.780 (10753) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2017-04-20 12:57:11.800 (10753) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-157.newrelic.com
2017-04-20 12:57:11.801 (10753) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2017-04-20 12:58:11.814 (10753) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-157.newrelic.com
2017-04-20 12:58:11.814 (10753) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2017-04-20 12:59:11.826 (10753) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-157.newrelic.com
2017-04-20 12:59:11.826 (10753) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2017-04-20 13:00:11.838 (10753) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-157.newrelic.com
2017-04-20 13:00:11.838 (10753) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed
2017-04-20 13:01:11.850 (10753) error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-157.newrelic.com
2017-04-20 13:01:11.850 (10753) warning: RPM call=‘metric_data’ for app=‘Infrastructure’ failed

I checked New Relic status page as suggested by @omccolgan but seems that everything is working fine.

Any idea of what is going wrong?

Many thanks,
Diego.


#5

Any news?

These are the permalinks related to servers where I am experiencing the issue:

  1. https://rpm.newrelic.com/accounts/457000/servers/19741701?tw[end]=1492783500&tw[start]=1492781700
  2. https://rpm.newrelic.com/accounts/457000/servers/19367533?tw[end]=1492783557&tw[start]=1492781757
  3. https://rpm.newrelic.com/accounts/457000/servers/8176623?tw[end]=1492783550&tw[start]=1492781750

I remember that the error is:

error: RPM cmd=‘metric_data’ for ‘Infrastructure’ failed: Couldn’t resolve host ‘collector-157.newrelic.com


#7