starred/hickory-dns

Fork 0

mirror of https://github.com/hickory-dns/hickory-dns.git synced 2026-04-25 19:25:56 +03:00

[GH-ISSUE #687] "can't get next random port" spamming the logs #271

New issue

Closed

opened 2026-03-07 23:09:59 +03:00 by kerem · 4 comments

kerem commented

2026-03-07 23:09:59 +03:00

Owner

Originally created by @axos88 on GitHub (Feb 12, 2019).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/687

Describe the bug
Spamming the logs with the following message:
WARN 2019-02-08T00:07:05.159159836Z: trust_dns_proto::udp::udp_stream: could not get next random port, delaying, filling up the disk. (one line about every 5ms)

To Reproduce

I think it's caused by os error 24 (too many files open, but not sure, it occurs randomly)

Expected behavior

Exponential backoff maybe?

System:

OS: Raspbian GNU/Linux 9 (stretch)
Architecture: arm, raspberry pi
Version: 9
rustc version: 1.31

Version:
Crate: resolver
Version: 0.4.3

Additional context

Occurs randomly, until disk fills up.

Originally created by @axos88 on GitHub (Feb 12, 2019). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/687 **Describe the bug** Spamming the logs with the following message: `WARN 2019-02-08T00:07:05.159159836Z: trust_dns_proto::udp::udp_stream: could not get next random port, delaying`, filling up the disk. (one line about every 5ms) **To Reproduce** I think it's caused by os error 24 (too many files open, but not sure, it occurs randomly) **Expected behavior** Exponential backoff maybe? **System:** - OS: Raspbian GNU/Linux 9 (stretch) - Architecture: arm, raspberry pi - Version: 9 - rustc version: 1.31 **Version:** Crate: resolver Version: 0.4.3 **Additional context** Occurs randomly, until disk fills up.

kerem

2026-03-07 23:09:59 +03:00

closed this issue
added the
bug

cleanup

easy
labels

kerem commented

2026-03-07 23:10:15 +03:00

Author

Owner

@bluejekyll commented on GitHub (Feb 12, 2019):

This is interesting, can you describe your situation a little more? It sounds like you have a significant number of resolutions ocuring if this is the case.

We can drop that message to a debug log message.

@bluejekyll commented on GitHub (Feb 12, 2019): This is interesting, can you describe your situation a little more? It sounds like you have a significant number of resolutions ocuring if this is the case. We can drop that message to a debug log message.

kerem commented

2026-03-07 23:10:20 +03:00

Author

Owner

@axos88 commented on GitHub (Feb 12, 2019):

I'm not sure what is happening exactly either yet, I shouldn't be having multiple resolutions happening simultaneously, I'm still investigating why the error 24 is occuring. However if it does happen, it will spam the logs, because it will log out the same message for every poll that happens.

@axos88 commented on GitHub (Feb 12, 2019): I'm not sure what is happening exactly either yet, I shouldn't be having multiple resolutions happening simultaneously, I'm still investigating why the error 24 is occuring. However if it does happen, it will spam the logs, because it will log out the same message for every poll that happens.

kerem commented

2026-03-07 23:10:25 +03:00

Author

Owner

@bluejekyll commented on GitHub (Feb 12, 2019):

Is this accurate: resolver Version: 0.4.3? That would be really old. can you confirm that version please? I'd highly recommend upgrading to 0.10 (current supported release), or the 0.11 alpha preview release. There were some issues discovered in previous versions related to socket management, that have since been fixed.

Similarly, the 0.6 or 0.7 release of the proto crate has those fixes.

@bluejekyll commented on GitHub (Feb 12, 2019): Is this accurate: `resolver Version: 0.4.3`? That would be really old. can you confirm that version please? I'd highly recommend upgrading to 0.10 (current supported release), or the 0.11 alpha preview release. There were some issues discovered in previous versions related to socket management, that have since been fixed. Similarly, the 0.6 or 0.7 release of the proto crate has those fixes.

kerem commented

2026-03-07 23:10:30 +03:00

Author

Owner

@axos88 commented on GitHub (Feb 13, 2019):

No, I must've missed something, I'm using 0.10.0

@axos88 commented on GitHub (Feb 13, 2019): No, I must've missed something, I'm using 0.10.0

kerem referenced this issue

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

[PR #271] [MERGED] Simplify CNAME chaining. #1334