[GH-ISSUE #774] [ERR] yamux: keepalive failed: i/o deadline reached #604

New issue

Closed

opened 2026-05-05 12:23:31 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 12:23:31 -06:00

Owner

Originally created by @roylez on GitHub (May 16, 2018).
Original GitHub issue: https://github.com/fatedier/frp/issues/774

Suddenly my ssh reverse tunnel is broken and I find the following in logs. Both frps and frpc services are managed by systemd, and they do not attempt to recover the connectivity.

2018/05/17 01:59:07 [ERR] yamux: keepalive failed: i/o deadline reached
2018/05/17 01:59:07 [service.go:247] Accept new mux stream error: keepalive timeout
2018/05/17 01:59:07 [control.go:214] [820a448a024ec6d6] control writer is closing
2018/05/17 01:59:07 [proxy.go:72] [820a448a024ec6d6] [ssh] proxy closing
2018/05/17 01:59:07 [proxy.go:118] [820a448a024ec6d6] [ssh] listener is closed
2018/05/17 01:59:07 [proxy.go:72] [820a448a024ec6d6] [web] proxy closing
2018/05/17 01:59:07 [control.go:284] [820a448a024ec6d6] client exit success

Originally created by @roylez on GitHub (May 16, 2018). Original GitHub issue: https://github.com/fatedier/frp/issues/774 Suddenly my ssh reverse tunnel is broken and I find the following in logs. Both frps and frpc services are managed by systemd, and they do not attempt to recover the connectivity. ``` 2018/05/17 01:59:07 [ERR] yamux: keepalive failed: i/o deadline reached 2018/05/17 01:59:07 [service.go:247] Accept new mux stream error: keepalive timeout 2018/05/17 01:59:07 [control.go:214] [820a448a024ec6d6] control writer is closing 2018/05/17 01:59:07 [proxy.go:72] [820a448a024ec6d6] [ssh] proxy closing 2018/05/17 01:59:07 [proxy.go:118] [820a448a024ec6d6] [ssh] listener is closed 2018/05/17 01:59:07 [proxy.go:72] [820a448a024ec6d6] [web] proxy closing 2018/05/17 01:59:07 [control.go:284] [820a448a024ec6d6] client exit success ```

gitea-mirror closed this issue

2026-05-05 12:23:32 -06:00

gitea-mirror commented

2026-05-05 12:23:34 -06:00

Author

Owner

@roylez commented on GitHub (May 17, 2018):

I was wrong. The connection was later restored, but I have no idea how long it took before it did that.

@roylez commented on GitHub (May 17, 2018): I was wrong. The connection was later restored, but I have no idea how long it took before it did that.

gitea-mirror commented

2026-05-05 12:23:35 -06:00

Author

Owner

@fatedier commented on GitHub (May 17, 2018):

1s, 2s, 4s ... max duration is 20s

@fatedier commented on GitHub (May 17, 2018): 1s, 2s, 4s ... max duration is 20s

gitea-mirror commented

2026-05-05 12:23:36 -06:00

Author

Owner

@roylez commented on GitHub (May 17, 2018):

I am pretty sure the connection was down for more than 20s, but never mind.

@roylez commented on GitHub (May 17, 2018): I am pretty sure the connection was down for more than 20s, but never mind.

gitea-mirror referenced this issue

2026-05-05 14:37:56 -06:00

[PR #604] [MERGED] fix new http no traffic stats, fix #590 #4219