Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
Mac OS X 10.10
Jenkins ver. 1.565.3.1 (Jenkins Enterprise by CloudBees 14.05)
JDK - java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)
-
-
Jenkins 2.178
Description
I've seen these error messages in my console output, which comes from jmdns.
The level of the logging messages should be toned down significantly given that these are from a relatively minor feature in Jenkins.
Attachments
Issue Links
- is duplicated by
-
JENKINS-10160 When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
-
- Fixed but Unreleased
-
-
JENKINS-29490 Jenkins flood HDD with DNS Errors
-
- Resolved
-
-
JENKINS-50812 Logfile filling up with SIP entries
-
- Resolved
-
- is related to
-
JENKINS-10160 When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
-
- Fixed but Unreleased
-
-
JENKINS-33596 Disable DNSMultiCast & UDPBroadcastThread by default
-
- Resolved
-
- links to
I've been doing some research here and updating the library seems to fix the problem. At least is a starting point.
As I can see, the library was forked just because we want to use an abort method instead of the close method provided by jmdns. Moving the logic of this abort method to the core, probably we can put aside the fork and use the library instead, so any update would be easier. Opening a PR soon.