[GH-ISSUE #1664] server panic with message Transport endpoint is not connected #730

New issue

Closed

opened 2026-03-16 00:02:13 +03:00 by kerem · 5 comments

kerem commented

2026-03-16 00:02:13 +03:00

Owner

Originally created by @kontsaki on GitHub (Mar 23, 2022).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1664

Hello, i am not sure if this will help and feel free to close this issue if it seems like a waste of your time.

i'm getting this from time to time since a year ago

thread 'trust-dns-server-runtime' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" }', /home/kon/src/trust-dns/crates/server/src/server/server_future.rs:131:63

running on debian bullseye through systemd

i'm not sure how to reproduce this, should i set RUST_BACKTRACE and wait for this to happen again?

Originally created by @kontsaki on GitHub (Mar 23, 2022). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1664 Hello, i am not sure if this will help and feel free to close this issue if it seems like a waste of your time. i'm getting this from time to time since a year ago ``` thread 'trust-dns-server-runtime' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" }', /home/kon/src/trust-dns/crates/server/src/server/server_future.rs:131:63 ``` running on debian bullseye through systemd i'm not sure how to reproduce this, should i set RUST_BACKTRACE and wait for this to happen again?

kerem

2026-03-16 00:02:13 +03:00

closed this issue
added the
bug

crate:server
labels

kerem commented

2026-03-16 00:02:29 +03:00

Author

Owner

@bluejekyll commented on GitHub (Mar 25, 2022):

This is interesting. We should definitely fix this. Clearly an assumption is not true at some points.

@bluejekyll commented on GitHub (Mar 25, 2022): This is interesting. We should definitely fix this. Clearly an assumption is not true at some points.

kerem commented

2026-03-16 00:02:34 +03:00

Author

Owner

@kontsaki commented on GitHub (Mar 25, 2022):

If there is anything I can do to help or provide more information about the system that I'm running, I would be happy to.

@kontsaki commented on GitHub (Mar 25, 2022): If there is anything I can do to help or provide more information about the system that I'm running, I would be happy to.

kerem commented

2026-03-16 00:02:40 +03:00

Author

Owner

@bluejekyll commented on GitHub (Mar 25, 2022):

Actually, one additional piece would be useful, what version of trust-dns are you using?

@bluejekyll commented on GitHub (Mar 25, 2022): Actually, one additional piece would be useful, what version of trust-dns are you using?

kerem commented

2026-03-16 00:02:45 +03:00

Author

Owner

@kontsaki commented on GitHub (Mar 25, 2022):

I'm pulling and building regularly, at least once a month, from master. Last commit i checked out was 22ffc3fd2a but i have logs of this happening since 2021-01-18

@kontsaki commented on GitHub (Mar 25, 2022): I'm pulling and building regularly, at least once a month, from master. Last commit i checked out was 22ffc3fd2abf88d25a0f70186cb9fdcc2be95702 but i have logs of this happening since 2021-01-18

kerem commented

2026-03-16 00:02:50 +03:00

Author

Owner

@bluejekyll commented on GitHub (Mar 25, 2022):

ah, I just took a look. this is a quick and easy fix.

@bluejekyll commented on GitHub (Mar 25, 2022): ah, I just took a look. this is a quick and easy fix.