-
Notifications
You must be signed in to change notification settings - Fork 7.3k
Assertion failure in dgram #5977
Comments
I'm getting this problem too on v0.10.17, have not been able to find the cause yet. It does however seem to be related to my worker processes. Without cluster, this doesn't seem to happen. Apparently my app is doing lots of udp listening, because my workers emit that they're listening on address: {
"address": "0.0.0.0",
"port": 51916,
"addressType": "udp4",
"fd": -1
} The error:
For me, it's caused by the graylog module. |
Can one of you get me a |
|
That looks like a very unhealthy situation. I'm guessing the problem arises from every single log message creating a fresh new udp4 socket (I have no idea why it was designed like that). |
If you need more output, like when you asked for "In particular, I'd like to know what print *handle prints when you execute it in the uv__udp_sendmsg frame", could you give me some pointers as to how I can get there? I don't use gdb a lot (or ever). |
Seeing this on v0.10.15 (w/ the lynx statsd client) |
I believe the fix will be released soon: joyent/libuv@29fdb34 |
Fixed in joyent/libuv@29fdb34, fix will be included in next v0.10 release. |
node 0.10.15, Debian 6
This assertion failure happened once after running half a day with about 2k QPS.
The only place in my app using UDP is statsd, which is a simple module that only does UDP socket.send().
The text was updated successfully, but these errors were encountered: