Error: socket hang up and Error with latest version

[morwalz]

i still see this error even if we are using latest npm version.
13:06:07.976 2014-05-21 07:36:07.671884+00:00 app web.3 - -

{
    "name": "newrelic",
    "hostname": "93451f12-6534-4344-b68d-b98319f21e28",
    "pid": 2,
    "component": "collector_api",
    "level": 10,
    "err": {
        "message": "socket hang up",
        "name": "Error",
        "stack": "Error: socket hang up\n at createHangUpError (http.js:1412:15)\n at CleartextStream.socketCloseListener (http.js:1462:23)\n at CleartextStream.EventEmitter.emit (events.js:117:20)\n at tls.js:616:10\n at /app/node_modules/newrelic/node_modules/continuation-local-storage/node_modules/async-listener/glue.js:177:31\n at process._tickDomainCallback as _tickCallback",
        "code": "ECONNRESET"
    },
    "msg": "Error 1 during metric_data:",
    "time": "2014-05-21T07:36:07.671Z",
    "v": 0
} {
    "name": "newrelic",
    "hostname": "93451f12-6534-4344-b68d-b98319f21e28",
    "pid": 2,
    "component": "collector_api",
    "level": 50,
    "err": {
        "message": "socket hang up",
        "name": "Error",
        "stack": "Error: socket hang up\n at createHangUpError (http.js:1412:15)\n at CleartextStream.socketCloseListener (http.js:1462:23)\n at CleartextStream.EventEmitter.emit (events.js:117:20)\n at tls.js:616:10\n at /app/node_modules/newrelic/node_modules/continuation-local-storage/node_modules/async-listener/glue.js:177:31\n at process._tickDomainCallback as _tickCallback",
        "code": "ECONNRESET"
    },
    "msg": "Calling metric_data on New Relic failed unexpectedly. Data will be held until it can be submitted:",
    "time": "2014-05-21T07:36:07.671Z",
    "v": 0
} {
    "name": "newrelic",
    "hostname": "93451f12-6534-4344-b68d-b98319f21e28",
    "pid": 2,
    "level": 30,
    "err": {
        "message": "socket hang up",
        "name": "Error",
        "stack": "Error: socket hang up\n at createHangUpError (http.js:1412:15)\n at CleartextStream.socketCloseListener (http.js:1462:23)\n at CleartextStream.EventEmitter.emit (events.js:117:20)\n at tls.js:616:10\n at /app/node_modules/newrelic/node_modules/continuation-local-storage/node_modules/async-listener/glue.js:177:31\n at process._tickDomainCallback as _tickCallback",
        "code": "ECONNRESET"
    },
    "msg": "Error on submission to New Relic (data held for redelivery):",
    "time": "2014-05-21T07:36:07.672Z",
    "v": 0
}

[kcq]

Seeing the same socket hang up errors with the latest version as of June 5. It crashes the apps. Had to disable newrelic because of that.

[brandoncarl]

I'm also running into this: even with an older version of New Relic: 1.3.2. I haven't upgraded due to some of the memory leak concerns.

[wraithan]

@kcq if you are seeing crashing of your app. Please contact our support https://support.newrelic.com/ so we can gather more data from you and better address this.

Occasional socket hangups when talking to the collector are not unexpected. Between things like the collectors being updated, the internet being fickle at times, etc. If you are seeing them constantly or they are causing serious disruption, contacting our support is going to let us ask for much more detailed information from you that we will need to fix this.

[brandoncarl]

@wraithan Hey Chris - I am a New Relic user through Heroku but also ran into this problem. The ECONNRESET seemed to induce some panic which stopped the Heroku process from automatically restarting.

I had to disable New Relic to ensure stability. Unfortunately, I now have no way to contact you guys, since the support page isn't available. Could you please advise? I am at @brandonjcarl on Twitter, and would like to work with you guys to get this resolved.

Cheers,

Brandon

[groundwater]

@brandoncarl there should be multiple support channels available.

• https://support.newrelic.com/
• https://discuss.newrelic.com/

If you are experiencing a failure in either of those, please let us know. General support issues should be directed to one of those places. Thanks.

[brandoncarl]

@groundwater Jacob, both of those services require login to access support so far as I can tell. Given that I host on Heroku, and that I had to disable my account due to the problems, I do not have a login. Can you advise another way to get in touch?

Brandon Carl
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

On Monday, June 9, 2014 at 11:00 PM, Jacob Groundwater wrote:

@brandoncarl (https://github.com/brandoncarl) there should be multiple support channels available.
https://support.newrelic.com/
https://discuss.newrelic.com/

If you are experiencing a failure in either of those, please let us know. General support issues should be directed to one of those places. Thanks.

—
Reply to this email directly or view it on GitHub (#145 (comment)).

[groundwater]

@brandoncarl great question, let me check with the team and see how Heroku logins are handled.

Sorry to hijack the thread, forking to #150

[ajslater]

Title should be edited to reference exact version numbers. Seeing this in newrelic node package v1.6.0

[txase]

Hi folks,

We are transitioning away from GitHub issues to our own dedicated support portal: http://support.newrelic.com. We are better able to help customers individually through our own system. If you continue to see this issue, please follow up there and we will help you.

A few people here have mentioned difficulties accessing http://support.newrelic.com as a Heroku user. In order to access our support channel, please log into Heroku first, then navigate to http://support.newrelic.com. We use Heroku authentication to log you in.

We appreciate your understanding as we undergo this transition.