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

Unexpected collector HTTP status code: 503


#1

New Relic 9.2.0.247 (“iceberg” - “51143810a9c6”)
PHP 7.2.16 (fpm) / nginx/1.12.2
Amazon Linux 2

New relic is enabled in phpinfo, daemon running OK, however: tail -f /var/log/newrelic/newrelic-daemon.log

Warning: app ‘xxx’ connect attempt returned unexpected collector HTTP status code: 503

No data is getting to new rellic admin panel


#2

503 is definitely unexpected! Could you share the full log line from that error?

In particular I’m curious if this is happening on the preconnect or connect phase. Preconnect connects to collector.newrelic.com and gets a redirect to the actual collector which the connect uses, something like collector-003.newrelic.com

I notice you are on Amazon but does this system have direct access to the internet?


#3

2019/11/01 02:12:20.504727 (11226) Warning: app ‘xxx’ connect attempt returned unexpected collector HTTP status code: 503
2019/11/01 02:12:50.498123 (11226) Warning: app ‘xxx’ connect attempt returned unexpected collector HTTP status code: 503
2019/11/01 02:13:20.761757 (11226) Warning: app ‘xxx’ connect attempt returned unexpected collector HTTP status code: 503
2019/11/01 02:13:52.761006 (11226) Warning: app ‘xxx’ connect attempt returned unexpected collector HTTP status code: 503

Yes it has access to the internet:

[ec2-user@ip-10-0-8-205 ~]$ ping collector-003.newrelic.com
PING collector-pool.newrelic.com (162.247.242.27) 56(84) bytes of data.
64 bytes from collector-7.newrelic.com (162.247.242.27): icmp_seq=1 ttl=238 time=88.8 ms
64 bytes from collector-7.newrelic.com (162.247.242.27): icmp_seq=2 ttl=238 time=89.0 ms
64 bytes from collector-7.newrelic.com (162.247.242.27): icmp_seq=3 ttl=238 time=88.9 ms
^C

[ec2-user@ip-10-0-8-205 ~]$ wget collector-003.newrelic.com
–2019-11-01 16:16:33-- http://collector-003.newrelic.com/
Resolving collector-003.newrelic.com (collector-003.newrelic.com)… 162.247.242.14, 162.247.242.27, 162.247.242.28, …
Connecting to collector-003.newrelic.com (collector-003.newrelic.com)|162.247.242.14|:80… connected.
HTTP request sent, awaiting response… 403 Forbidden
2019-11-01 16:16:33 ERROR 403: Forbidden.


#4

I just installed the PHP agent, having the exact same error.

Enabling the audit log in the config files prints this in the audit log:

2019/11/01 22:41:30.062551 command='preconnect' url='https://collector.eu01.nr-data.net/agent_listener/invoke_raw_method?license_key=<mykey>&marshal_format=json&method=preconnect&protocol_version=16', response={}

Indeed, connecting to that HTTP Url seems to be problematic:

curl -I "https://collector.eu01.nr-data.net/agent_listener/invoke_raw_method?license_key=<mykey>&marshal_format=json&method=preconnect&protocol_version=16"
HTTP/1.1 503 Service Unavailable
Content-Length: 50
Content-Type: text/plain
Date: Fri, 01 Nov 2019 21:43:45 GMT

#5

When I hit that URL with my key I get:

“System currently unavailable due to maintenance.”


#6

Hello Dears,

I faced the same issue and gave me “System currently unavailable due to maintenance.”
When I can push app config or when system begin up again


#7

We have had enough of waiting - no responses, no emails back from Simon Williams (Commercial UK & Ireland Manager) who has not even bothered to reply.

We’ve decided to get a trial on https://appdynamics.com/free-trial/


#8

Sorry you’ve yet to receive a reply…

I looked at your account and see that it is configured for our EU Datacenter, but your Ping results appear to be going to the US Collector URLs. Can you confirm that by trying to ping the EU collector?

ping collector.eu01.nr-data.net

#9

A 503 Service Unavailable Error is an HTTP response status code indicating that a server is temporarily unable to handle the request!


#10

Thanks for all of your patience here! After some digging into this with our backend engineering teams, it looks like there was a small interruption over the weekend to our collectors for a small subset of customer accounts in our EU Region that would have resulted in the error messages you are seeing. I have confirmed that this issue has since been resolved and all EU Region apps should be connecting without issue. Please let us know if you’re still experiencing this and we can open a ticket for further investigation with our engineering team for your specific account.