Marc Harter
Marc Harter
I've since discovered this error is happening when the process runs out of open files (sockets): - The response from `fetch` is being used as the response for the HTTP...
Thx for the update @Jarred-Sumner , I will give the latest version a try and report back my findings. May be a few days to get some data.
@Jarred-Sumner So far I'm seeing roughly the same FD increases for TCP against `0.7.1`. As of writing this, the process is at `779` TCP sockets open. I am using the...
Just another update on this. Running 0.8.1. I still have the same issue. However, if I set `keepalive: false`, the issue goes away. Sockets don't seem to top off at...
GELF requires `host` to be set in the message, but I suppose that could be set improperly by the client, and likely wouldn't include the port. You can sniff those...
Thanks for the heads, care to submit a PR correcting this?
This lib just uses Node.js `dgram.bind` under the hood, which should support ipv6: https://nodejs.org/api/dgram.html#dgram_socket_bind_port_address_callback
Ahh, missed that. Yes, that would need to be `udp6` in your case. Care to make a PR?
I don't know enough about `hrtime` to say either way but it would appear this comment still is relevant: https://github.com/wadey/node-microtime/pull/16#issuecomment-29836878 I also run Node 8 and I cannot duplicate your...
Ran into same issue. In my case, user logs out, clear cache (per documentation), and logs in before the dedup interval, gets no data.