You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, my app crash with an "Unexpected token u" error.
I'm using the 1.6.0 version.
throw er; // Unhandled 'error' event
^
SyntaxError: Unexpected token u
at Object.parse (native)
at /app/node_modules/coffee-resque/lib/index.js:105:37
at try_callback (/app/node_modules/redis/index.js:573:9)
at RedisClient.return_reply (/app/node_modules/redis/index.js:661:13)
at ReplyParser.<anonymous> (/app/node_modules/redis/index.js:309:14)
at ReplyParser.EventEmitter.emit (events.js:95:17)
at ReplyParser.send_reply (/app/node_modules/redis/lib/parser/javascript.js:300:10)
at ReplyParser.execute (/app/node_modules/redis/lib/parser/javascript.js:203:22)
at RedisClient.on_data (/app/node_modules/redis/index.js:534:27)
at Socket.<anonymous> (/app/node_modules/redis/index.js:91:14)
at Socket.EventEmitter.emit (events.js:95:17)
at Socket.<anonymous> (_stream_readable.js:745:14)
at Socket.EventEmitter.emit (events.js:92:17)
at emitReadable_ (_stream_readable.js:407:10)
at emitReadable (_stream_readable.js:403:5)
at readableAddChunk (_stream_readable.js:165:9)
at Socket.Readable.push (_stream_readable.js:127:10)
at TCP.onread (net.js:528:21)
at TCP.onread (/app/node_modules/newrelic/node_modules/continuation-local-storage/node_modules/async-listener/glue.js:177:31)
events.js:72
State changed from up to crashed
State changed from crashed to starting
This bug seems to happen only when the newrelic agent is loaded
The text was updated successfully, but these errors were encountered:
I'm going to close this issue since we haven't heard anything in a while. We're also closing down the public GitHub issues, so if you do still hit this issue please follow up with us at http://support.newrelic.com. We can better support you through our dedicated portal there.
Hi, my app crash with an "Unexpected token u" error.
I'm using the 1.6.0 version.
This bug seems to happen only when the newrelic agent is loaded
The text was updated successfully, but these errors were encountered: