-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ipfs : panic: expected chan in accept muxer #9693
Comments
I'm getting this too, on a daemon running in a windows shell. Similar error, except for the start. Note that this started after updating to the latest version. Performing a clean installs with fresh repo (rather than upgraded) is still presenting the below error. I also have ipfs-desktop runing on another machine with inbuilt daemon, which has also started to fail multiple times a day. panic: expected chan in accept muxer goroutine 358 [running]: |
From the above stack trace, tried to dig into the code. So, adding into the map is coming from Listen() which listens to new QUIC connections on the passed multiaddr. |
me too |
俺也一样 |
I got the same error on windows.: panic: expected chan in accept muxer goroutine 467 [running]: goroutine 468 [running]: |
Same for me, Kubo version: 0.19.0 "Could not connect to the IPFS API" message appears after some time of IPFS work in Status window of IPFS Desktop. This time is quite random, and can be from 10 min to several hours. If to restart then with the right-click button on tray icon, or with the "ipfs daemon" command in Windows PowerShell, everything works again. But the after a while again stops. The log in Powershell gives the following before I get the "panic" line (each 1 minute these 7 warnings coming up, I don't know if this important): goroutine 395 [running]: |
Same problem on 0.19.1 panic: expected chan in accept muxer
|
Installation of Windows Subsystem for Linux (WSL) solved this issue ipfs/ipfs-desktop#2463 (working several hours for now and not quitting). Also, no |
I have intall WSL and get error after several hours: |
The issue for this in go-libp2p is libp2p/go-libp2p#2259, once there's a fix + release there it'll get updated in kubo. |
We'll try to cut a patch release with this fix today |
Actually, I also have similar message each 3-9 hours. But it seem not to influence the IPFS work. |
Checklist
Installation method
ipfs-desktop
Version
Config
Description
Various times per day, the ipfs daemon quits with the following error message, on both of my Windows Servers (one 2019, the other 2022):
ipfs : panic: expected chan in accept muxer
At line:1 char:1
goroutine 326 [running]:
github.com/libp2p/go-libp2p/p2p/transport/quic.(*acceptLoopRunner).RmAcceptForVersion(0xc002d49a58, 0x7691e50?)
github.com/libp2p/go-libp2p@v0.24.2/p2p/transport/quic/virtuallistener.go:72 +0x14a
github.com/libp2p/go-libp2p/p2p/transport/quic.(*virtualListener).Close(0xc000598440)
github.com/libp2p/go-libp2p@v0.24.2/p2p/transport/quic/virtuallistener.go:32 +0x28
github.com/libp2p/go-libp2p/p2p/net/swarm.(*Swarm).AddListenAddr.func2.1()
github.com/libp2p/go-libp2p@v0.24.2/p2p/net/swarm/swarm_listen.go:117 +0x14e
github.com/libp2p/go-libp2p/p2p/net/swarm.(*Swarm).AddListenAddr.func2()
github.com/libp2p/go-libp2p@v0.24.2/p2p/net/swarm/swarm_listen.go:130 +0x3a4
created by github.com/libp2p/go-libp2p/p2p/net/swarm.(*Swarm).AddListenAddr
github.com/libp2p/go-libp2p@v0.24.2/p2p/net/swarm/swarm_listen.go:106 +0x271
The text was updated successfully, but these errors were encountered: