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
did you experience also some stability issues?
after a random time but usually a few hours, the script dies with the message Killed.
I enabled debug and I see the ws died and has issues to reconnect after the first failure (it seems to be the box creating this situation as I tried with 2 ws from 2 PCs and they failed at the same time.
do you experience the same behaviour ?
note: I tried node v 0.10.29 4.5.0 and currently running some tests with 6.5.0
logs:
...
[11/09/2016 16:02:45] WS on port 7682: sending ping
[11/09/2016 16:02:45] WS on port 7684: sending ping
[11/09/2016 16:02:51] WS on port 7682 closed, restarting
[11/09/2016 16:02:51] WS on port 7684 closed, restarting
[11/09/2016 16:02:51] WS on port 7682 got an error: "Error: connect ECONNREFUSED 192.168.0.3:7682", restarting
[11/09/2016 16:02:51] WS on port 7682 closed, restarting
[11/09/2016 16:02:51] WS on port 7684 got an error: "Error: connect ECONNREFUSED 192.168.0.3:7684", restarting
...
[11/09/2016 16:04:07] WS on port 7684 got an error: "Error: connect ECONNREFUSED 192.168.0.3:7684", restarting
[11/09/2016 16:04:07] WS on port 7684 closed, restarting
[11/09/2016 16:04:07] WS opened on port 7682
[11/09/2016 16:04:07] WS opened on port 7682
[11/09/2016 16:04:07] WS opened on port 7682
[11/09/2016 16:04:07] WS on port 7684 got an error: "Error: connect ECONNREFUSED 192.168.0.3:7684", restarting
[11/09/2016 16:04:07] WS on port 7684 closed, restarting
...
[11/09/2016 16:05:34] WS on port 7682 got an error: "Error: socket hang up", restarting
[11/09/2016 16:05:34] WS on port 7682 closed, restarting
[11/09/2016 16:05:34] WS on port 7682 got an error: "Error: socket hang up", restarting
[11/09/2016 16:05:34] WS on port 7682 closed, restarting
[11/09/2016 16:05:34] WS on port 7682 got an error: "Error: socket hang up", restarting
[11/09/2016 16:05:34] WS on port 7682 closed, restarting
[11/09/2016 16:05:34] WS on port 7682 got an error: "Error: socket hang up", restartin
[11/09/2016 16:05:34] WS on port 7682 closed, restarting
Killed
The text was updated successfully, but these errors were encountered:
I experienced some random disconnections after a random time, like you, that's why the client tries to restart the connection every time it happens.
But I never saw the "killed" message when I was developing the plugin or after.
Maybe Numéricable updated their ws security parameters since the plugin was written. One solution could be to "decompile" the latest apk from their android mobile app, and analyse the code to check for it.
Unfortunately, I moved to Canada some months ago, so I don't use Numéricable anymore as internet access provider.
I would like to help more but I don't know how...
Don't hesitate to comment if you have some ideas.
Hi,
did you experience also some stability issues?
after a random time but usually a few hours, the script dies with the message Killed.
I enabled debug and I see the ws died and has issues to reconnect after the first failure (it seems to be the box creating this situation as I tried with 2 ws from 2 PCs and they failed at the same time.
do you experience the same behaviour ?
note: I tried node v 0.10.29 4.5.0 and currently running some tests with 6.5.0
logs:
...
[11/09/2016 16:02:45] WS on port 7682: sending ping
[11/09/2016 16:02:45] WS on port 7684: sending ping
[11/09/2016 16:02:51] WS on port 7682 closed, restarting
[11/09/2016 16:02:51] WS on port 7684 closed, restarting
[11/09/2016 16:02:51] WS on port 7682 got an error: "Error: connect ECONNREFUSED 192.168.0.3:7682", restarting
[11/09/2016 16:02:51] WS on port 7682 closed, restarting
[11/09/2016 16:02:51] WS on port 7684 got an error: "Error: connect ECONNREFUSED 192.168.0.3:7684", restarting
...
[11/09/2016 16:04:07] WS on port 7684 got an error: "Error: connect ECONNREFUSED 192.168.0.3:7684", restarting
[11/09/2016 16:04:07] WS on port 7684 closed, restarting
[11/09/2016 16:04:07] WS opened on port 7682
[11/09/2016 16:04:07] WS opened on port 7682
[11/09/2016 16:04:07] WS opened on port 7682
[11/09/2016 16:04:07] WS on port 7684 got an error: "Error: connect ECONNREFUSED 192.168.0.3:7684", restarting
[11/09/2016 16:04:07] WS on port 7684 closed, restarting
...
[11/09/2016 16:05:34] WS on port 7682 got an error: "Error: socket hang up", restarting
[11/09/2016 16:05:34] WS on port 7682 closed, restarting
[11/09/2016 16:05:34] WS on port 7682 got an error: "Error: socket hang up", restarting
[11/09/2016 16:05:34] WS on port 7682 closed, restarting
[11/09/2016 16:05:34] WS on port 7682 got an error: "Error: socket hang up", restarting
[11/09/2016 16:05:34] WS on port 7682 closed, restarting
[11/09/2016 16:05:34] WS on port 7682 got an error: "Error: socket hang up", restartin
[11/09/2016 16:05:34] WS on port 7682 closed, restarting
Killed
The text was updated successfully, but these errors were encountered: