-
Notifications
You must be signed in to change notification settings - Fork 45
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
App crashing occasionally when try to ping hosts through net-ping. #38
Comments
What version of raw-socket are you using, can you look at the package.json file under its directory (under node_modules or wherever it is installed) and give me the exact version? Steve |
Also, I don't see what relevance the link you gave has, it seems to relate to an issue which is not caused by this module. |
Hello Stephen, the version is: Sorry, I've posted a wrong link. |
Hi, is this still an issue for you? |
Hello @stephenwvickers , Unfortunately yes. Still have no time to debug this, but planing to look deeper into this. My app crashes or stops getting answers from net-ping if network have any performance problem(timeout, cognitions and etc, I'm using it via internet, not only in local network). Will update this issue when have something to add. |
Hi, have you had time to look into this? |
I predict the issue is here
You should not set var before session here. If you set the session is limited to the scope of if condition |
Hi,
I'm getting this errors in logs and then app crashs.
node: ../deps/uv/src/unix/poll.c:88: uv_poll_stop: Assertion
!(handle->flags & (UV_CLOSING | UV_CLOSED))' failed.`This happens on Ubuntu server with running node v6.10.0 and net-ping v. 1.2.0
I've found that recently node-uptime project facing with such proplem:
https://groups.google.com/forum/#!topic/nodejs/obdxquewUcE
This usually happens when network has performance issues, such as packet lost and transmit/receive delays. In my app case this could happen 5-7 times for 24 hours.
My ping code looks like this:\
Thanks, Roman.
The text was updated successfully, but these errors were encountered: