goodeggs / heroku-log-normalizer

Normalize log lines from Heroku Logplex to JSON.
1 stars 0 forks source link

Crashing #10

Closed adborden closed 9 years ago

adborden commented 9 years ago
Error: socket hang up
    at SecurePair.error (tls.js:1013:23)
    at EncryptedStream.CryptoStream._done (tls.js:705:22)
    at CleartextStream.read [as _read] (tls.js:496:24)
    at CleartextStream.Readable.read (_stream_readable.js:320:10)
    at EncryptedStream.onCryptoStreamFinish (tls.js:301:47)
    at EncryptedStream.g (events.js:180:16)
    at EncryptedStream.EventEmitter.emit (events.js:117:20)
    at finishMaybe (_stream_writable.js:360:12)
    at endWritable (_stream_writable.js:367:3)
    at EncryptedStream.Writable.end (_stream_writable.js:345:5)
    at EncryptedStream.CryptoStream.end (tls.js:643:31)
*** /usr/local/bin/heroku_log_normalizer exited with status 8.
May 10 16:24:52 a04f544662e0 syslog-ng[19]: syslog-ng shutting down; version='3.5.3'
*** Shutting down runit daemon (PID 13)...
*** Killing all processes...

Looks to be coming from the sumo transport

{"name":"heroku_log_normalizer","hostname":"a04f544662e0","pid":18,"module":"sumo_logic_transport","level":50,"err":{"message":"socket hang up","name":"Error","stack":"Error: socket hang up\n    at SecurePair.error (tls.js:1013:23)\n    at EncryptedStream.CryptoStream._done (tls.js:705:22)\n    at CleartextStream.read [as _read] (tls.js:496:24)\n    at CleartextStream.Readable.read (_stream_readable.js:320:10)\n    at EncryptedStream.onCryptoStreamFinish (tls.js:301:47)\n    at EncryptedStream.g (events.js:180:16)\n    at EncryptedStream.EventEmitter.emit (events.js:117:20)\n    at finishMaybe (_stream_writable.js:360:12)\n    at endWritable (_stream_writable.js:367:3)\n    at EncryptedStream.Writable.end (_stream_writable.js:345:5)\n    at EncryptedStream.CryptoStream.end (tls.js:643:31)","code":"ECONNRESET"},"msg":"socket hang up","time":"2015-05-10T16:20:14.411Z","v":0}

The process restarts after a minute.

adborden commented 9 years ago

Seems to coincide with our recent deploy.

bobzoller commented 9 years ago

fixed in 431cdc2e0d2f887f3e0949217e6a9e07e606388c