Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Geckos 2.0 http server hangs after a while

See original GitHub issue

Hey, there! I recently upgraded to geckos 2.0. Everything has been working swimmingly, except for one mysterious problem. After about two days of runtime, my geckos server starts timing out all requests. It sits behind an NGINX proxy, so the first error I see is:

2021/11/09 15:44:56 [error] 15785#15785: *5965624 upstream timed out (110: Connection timed out) while reading response header from upstream, request: "POST /geckos/.wrtc/v2/connections HTTP/1.1", upstream: "http://127.0.0.1:3030/.wrtc/v2/connections"

eventually followed by the similar:

2021/11/09 16:06:34 [error] 15785#15785: *5969357 upstream timed out (110: Connection timed out) while connecting to upstream, request: "POST /geckos/.wrtc/v2/connections HTTP/1.1", upstream: "http://127.0.0.1:3030/.wrtc/v2/connections"

I haven’t found any correlated errors coming from the geckos server itself. It just suddenly starts hanging and won’t reply anymore 😦 CPU and MEM usage seem normal.

Any idea how best to dig into this?

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:45 (31 by maintainers)

Top GitHub Comments

3reactions

paullouisageneaucommented, Dec 1, 2021

@marcwehbi Thank you for the gdb output, it looks like a regression introduced in libdatachannel v0.15.4. I refactored the transports teardown and it looks like it might make the PeerConnection deadlock on close. The timings triggering the deadlock must happen on one machine and not on the other for some reason.

2reactions

bennlichcommented, Dec 7, 2021

Haven’t seen any deadlocks in the last 4 days! Looks fixed!