-
Notifications
You must be signed in to change notification settings - Fork 20
Nelson crashes after a few hours/days #51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
In my case it crashes several times a day. It's probably a different crash, prints the following error on console:
OS Linux, Nelson v.0.3.16 |
ECONNRESET is anther bug. @rafaelbrizola have you closed your mac's lid in between? I think, there is a bug reported in websockets/ws#1280 that is related to this issue. I will check if this can be fixed/catched somehow... |
Hi Roman, |
I will try catching it and, at least, cleaning up neighbors before crashing. Will need more investigation, though.. |
Let's work together to get the bug fixed upstream. I have a feeling that something isn't working properly in Node.js core though as per this comment. |
@lpinca , I have upgraded to Node LTS 8.9.4 Let's see if this problem persists. @rafaelbrizola , could you upgrade your node version to 8.9.4 and try the new Nelson version 0.3.21? |
@romansemko Sure. Just did it. Let see how it goes |
Hi, I left it running and around 36 hours later I got the error below. Nelson is still running, but doesn't update anymore. 7:03:19 AM.026 16600::NODE new cycle |
@rafaelbrizola can you try to monkey patch ws and change this to This will help us understand if the timeout expires after an error or after the upgrade. |
Ok, done and restarted nelson. Let's see how it goes. |
nelson gui also errors out for me after about a day of running. In the top left quarter of the screen, I see the following error multiple times: Unhandled Rejection at: Promise Promise Seems Nelson is still running though, ,because the bottom half is still updated with neighbor connects and disconnects. |
@rafaelbrizola any update? |
Hi @lpinca sorry for not getting back to you. After that day, I still run Nelson for a couple of days but didn't notice any other crashes. However, I stopped running the experiment, and for other reason, never got back to that. So, it's inconclusive it that change helped in my case. If nobody else is noticing the crash, you can close this issue. Thanks! |
Ok, thanks. I'm pretty sure the issue is not fixed and still persists on ws@4 and Node.js v8.x. Unfortunately I don't have a way to reproduce it, so it's hard to understand what happens and fix it. This is the tracking issue in ws: websockets/ws#1280 |
I don't run nelson as a service. I run it using the command:
nohup sudo nelson --config /Users/iota/nelson/config.ini &
Just happened for the 3rd time. I go to check my node and found out that nelson is not running. This last time it was running for almost 24 hours before crashing. More details in the log below.
Expected behaviour
Nelson running continuously
Actual behaviour
After a while, can be hours or a few days, Nelson crashes.
Steps to reproduce
Not sure. It crashes randomly
Basic Info
Nelson Info
8:30:23 AM.190 16600::NODE new cycle
8:30:23 AM.195 16600::IRI Neighbors removed (if there were any): udp://31.48.190.3:14600
8:30:23 AM.195 16600::NODE connection closed 31.48.190.3:16600 (remotely dropped)
8:30:23 AM.195 16600::IRI Neighbors removed (if there were any): udp://139.226.182.140:14600
8:30:23 AM.195 16600::NODE connection closed 139.226.182.140:16600 (remotely dropped)
8:30:23 AM.196 16600::IRI Neighbors removed (if there were any): udp://31.48.190.3:14600
8:30:23 AM.196 16600::IRI Neighbors removed (if there were any): udp://139.226.182.140:14600
/usr/local/lib/node_modules/nelson.cli/node_modules/ws/lib/WebSocket.js:638
this._req.abort();
^
TypeError: Cannot read property 'abort' of null
at ClientRequest._req.setTimeout (/usr/local/lib/node_modules/nelson.cli/node_modules/ws/lib/WebSocket.js:638:16)
at Object.onceWrapper (events.js:314:30)
at emitNone (events.js:105:13)
at ClientRequest.emit (events.js:207:7)
at Socket.emitTimeout (_http_client.js:722:34)
at Object.onceWrapper (events.js:314:30)
at emitNone (events.js:105:13)
at Socket.emit (events.js:207:7)
at Socket._onTimeout (net.js:398:8)
at ontimeout (timers.js:469:11)
The text was updated successfully, but these errors were encountered: