5-08-18T10:46:54.559+0800 ERROR livekit service/rt...
# ask-ai
a
2025-08-18T104654.559+0800 ERROR livekit service/rtcservice.go:381 error reading from websocket {"room": "EyyXGWvNZfiapuIEeZbRF", "roomID": "RM_YnitrvEhmQZA", "participant": "TV-mRTINntwoolov9Ugu60OXa", "pID": "PA_QfhMDsxtnVoj", "remote": false, "connID": "CO_cjdx9MzG6JF9", "error": "websocket: close 3000: Ping timeout"} github.com/livekit/livekit-server/pkg/service.(*RTCService).ServeHTTP /home/runner/go/pkg/mod/github.com/livekit/livekit-server@v1.5.1/pkg/service/rtcservice.go:381 net/http.(*ServeMux).ServeHTTP /opt/hostedtoolcache/go/1.21.3/x64/src/net/http/server.go:2514 github.com/urfave/negroni/v3.(*Negroni).UseHandler.Wrap.func1 /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:59 github.com/urfave/negroni/v3.HandlerFunc.ServeHTTP /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:33 github.com/urfave/negroni/v3.middleware.ServeHTTP /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:51 net/http.HandlerFunc.ServeHTTP /opt/hostedtoolcache/go/1.21.3/x64/src/net/http/server.go:2136 github.com/livekit/livekit-server/pkg/service.(*APIKeyAuthMiddleware).ServeHTTP /home/runner/go/pkg/mod/github.com/livekit/livekit-server@v1.5.1/pkg/service/auth.go:99 github.com/urfave/negroni/v3.middleware.ServeHTTP /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:51 github.com/rs/cors.(*Cors).ServeHTTP /home/runner/go/pkg/mod/github.com/rs/cors@v1.10.1/cors.go:316 github.com/urfave/negroni/v3.middleware.ServeHTTP /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:51 github.com/urfave/negroni/v3.(*Recovery).ServeHTTP /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/recovery.go:210 github.com/urfave/negroni/v3.middleware.ServeHTTP /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:51 github.com/urfave/negroni/v3.(*Negroni).ServeHTTP /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/negroni.go:111 net/http.serverHandler.ServeHTTP /opt/hostedtoolcache/go/1.21.3/x64/src/net/http/server.go:2938 net/http.(*conn).serve /opt/hostedtoolcache/go/1.21.3/x64/src/net/http/server.go:2009 2025-08-18T104654.559+0800 INFO livekit service/rtcservice.go:266 finishing WS connection {"room": "EyyXGWvNZfiapuIEeZbRF", "roomID": "RM_YnitrvEhmQZA", "participant": "TV-mRTINntwoolov9Ugu60OXa", "pID": "PA_QfhMDsxtnVoj", "remote": false, "connID": "CO_cjdx9MzG6JF9"}2025-08-18T104654.812+0800 INFO livekit service/roommanager.go:293 resuming RTC session {"room": "EyyXGWvNZfiapuIEeZbRF", "nodeID": "ND_SZpuRznmRV2W", "participant": "TV-mRTINntwoolov9Ugu60OXa", "reason": "RR_UNKNOWN"} 2025-08-18T104654.812+0800 INFO livekit rtc/participant_signal.go:292 closing signal connection {"room": "EyyXGWvNZfiapuIEeZbRF", "roomID": "RM_YnitrvEhmQZA", "participant": "TV-mRTINntwoolov9Ugu60OXa", "pID": "PA_QfhMDsxtnVoj", "remote": false, "reason": "RESUME", "connID": "CO_cjdx9MzG6JF9"} 2025-08-18T104654.813+0800 INFO livekit service/rtcservice.go:303 new client WS connected {"room": "EyyXGWvNZfiapuIEeZbRF", "roomID": "RM_YnitrvEhmQZA", "participant": "TV-mRTINntwoolov9Ugu60OXa", "pID": "PA_QfhMDsxtnVoj", "remote": false, "connID": "CO_Yw3JP9Dr4EhW", "reconnect": true, "reconnectReason": "RR_UNKNOWN", "adaptiveStream": false} 2025-08-18T104654.851+0800 INFO livekit rtc/room.go:588 setting sync state {"room": "EyyXGWvNZfiapuIEeZbRF", "roomID": "RM_YnitrvEhmQZA", "participant": "TV-mRTINntwoolov9Ugu60OXa", "pID": "PA_QfhMDsxtnVoj", "remote": false, "state": "answer{type\"answer\" sdp:\"v=0\\r\\no=- 3112048677288607455 3 IN IP4 127.0.0.1\\r\\ns=-\\r\\nt=0 0\\r\\na=group:BUNDLE 0 1\\r\\na=extmap-allow-mixed\\r\\na=msid-semantic: WMS\\r\\nm=application 40890 UDP/DTLS/SCTP webrtc-datachannel\\r\\nc=IN IP4 172.16.15.155\\r\\na=candidate:3401769844 1 udp 2122260223 172.16.15.155 40890 typ host generation 0 network-id 3 network-cost 10\\r\\na=ice-ufragkhHv\\r\\na=ice pwdWfXaGNPWVE4VaAvb6dBD13BO\\r\\na=ice-options:trickle renomination\\r\\na=fingerprint:sha-256 CD10351F21476A75F802E9DD16488CDD8A7674F484123EBF072B138CEB69C061\\r\\na=setupactive\\r\\na=mid0\\r\\na=sctp port5000\\r\\nm=video 9 UDP/TLS/RTP/SAVPF 96 98 100 125 35\\r\\nc=IN IP4 0.0.0.0\\r\\na=rtcp:9 IN IP4 0.0.0.0\\r\\na=ice-ufragkhHv\\r\\na=ice pwdWfXaGNPWVE4VaAvb6dBD13BO\\r\\na=ice-options:trickle renomination\\r\\na=fingerprint:sha-256 CD10351F21476A75F802E9DD16488CDD8A7674F484123EBF072B138CEB69C061\\r\\na=setupactive\\r\\na=mid1\\r\\na=extmap2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time\\r\\na=extmap:1 https://aomediacodec.github.io/av1-rtp-spec/#dependency-descriptor-rtp-header-extension\\r\\na=recvonly\\r\\na=rtcp-mux\\r\\na=rtcp-rsize\\r\\na=rtpmap:96 VP8/90000\\r\\na=rtcp-fb:96 goog-remb\\r\\na=rtcp-fb:96 ccm fir\\r\\na=rtcp-fb:96 nack\\r\\na=rtcp-fb:96 nack pli\\r\\na=rtpmap:98 VP9/90000\\r\\na=rtcp-fb:98 goog-remb\\r\\na=rtcp-fb:98 ccm fir\\r\\na=rtcp-fb:98 nack\\r\\na=rtcp-fb:98 nack pli\\r\\na=fmtp:98 profile-id=0\\r\\na=rtpmap:100 VP9/90000\\r\\na=rtcp-fb:100 goog-remb\\r\\na=rtcp-fb:100 ccm fir\\r\\na=rtcp-fb:100 nack\\r\\na=rtcp-fb:100 nack pli\\r\\na=fmtp:100 profile-id=1\\r\\na=rtpmap:125 H264/90000\\r\\na=rtcp-fb:125 goog-remb\\r\\na=rtcp-fb:125 ccm fir\\r\\na=rtcp-fb:125 nack\\r\\na=rtcp-fb:125 nack pli\\r\\na=fmtp:125 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f\\r\\na=rtpmap:35 AV1/90000\\r\\na=rtcp-fb:35 goog-remb\\r\\na=rtcp-fb:35 ccm fir\\r\\na=rtcp-fb:35 nack\\r\\na=rtcp-fb:35 nack pli\\r\\na=fmtp:35 level-idx=5;profile=0;tier=0\\r\\n\"} subscription:{} data_channels{label\"_reliable\" id:1} data_channels{label\"_lossy\" id:3}"}发生了什么问题
t
Thanks for reaching out, 徐旭. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
The error "websocket: close 3000: Ping timeout" means the WebSocket connection was closed because the client didn’t get a response (pong) from the server in time after sending a ping. This can happen for a few reasons: • Network Issues: Sometimes the network can be a bit unstable or slow. • Server Load: The server might be really busy or facing some delays. • Configuration: The ping interval and timeout settings might be a little too strict for your current network conditions. Here are some steps you can try to fix this: 1. Take a look at your network on both the client and server side to make sure things are stable and running smoothly. 2. Check that the server is doing okay and isn’t overloaded. 3. Think about tweaking the ping interval and timeout settings so they fit your network a bit better. If you want, feel free to share your current ping interval and timeout settings, or any info about your network or server situation—I’m here to help you figure this out! Sources: livekit-android-sdk/src/main/java/io/livekit/android/room/SignalClient.kt