How to debug panic

Does anyone have a good idea how to better debug a panic without stack trace?

I am regularly seeing that on a few of my servers (running tip from earlier today) caddy dies with the following message:

panic: close of closed channel

But unfortunately I do not see any any stack backtrace. Any ideas to debug this?

See Panic after "update quic-go to v0.48.0" commit · Issue #6643 · caddyserver/caddy · GitHub

1 Like

Yes. That github issue was raised by myself. I can confirm the patch provided in that thread appears to stop the panics. However more testing is required.

This topic was automatically closed after 60 days. New replies are no longer allowed.