• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • 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

      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.

          [JENKINS-25369] DNS multicast error messages

          For those with size based log rotation strategies, this is more than an annoyance; it greatly diminishes the amount of meaningful log data that gets retained. Sampling my current logs, this message looks to comprise 70 - 80% of Jenkins log output. I consider that to be significant.

          Kenneth Baltrinic added a comment - For those with size based log rotation strategies, this is more than an annoyance; it greatly diminishes the amount of meaningful log data that gets retained. Sampling my current logs, this message looks to comprise 70 - 80% of Jenkins log output. I consider that to be significant.

          Daniel Beck added a comment -

          kbaltrinic The feature causing the log messages can easily be disabled from the next time you start Jenkins again, see my comment from 30/Oct/14 1:31 AM. There's a good chance you're not even using it.

          Daniel Beck added a comment - kbaltrinic The feature causing the log messages can easily be disabled from the next time you start Jenkins again, see my comment from 30/Oct/14 1:31 AM. There's a good chance you're not even using it.

          This error message flooded our log this weekend, till there was no disc space left. The log file was more than 430 GB big. The messages mostly like this one: https://gist.github.com/dzschille/ed739c040b0a5ba4d23c

          David Zschille added a comment - This error message flooded our log this weekend, till there was no disc space left. The log file was more than 430 GB big. The messages mostly like this one: https://gist.github.com/dzschille/ed739c040b0a5ba4d23c

          Daniel Beck added a comment -

          Related to JENKINS-10160, possibly a duplicate.

          Daniel Beck added a comment - Related to JENKINS-10160 , possibly a duplicate.

          Oleg Nenashev added a comment -

          It may happen even without network issues, e.g. when there is an unsupported DNS Message type coming from DNS. We use an old library version, and not all DNS Message types are supported (discovered in JENKINS-50812)

          Record type enumeration in the lib: https://github.com/jenkinsci/jmdns/blob/64f48ab717e0c8022f60d7dcb7f148f47c7f1227/src/main/java/javax/jmdns/impl/constants/DNSRecordType.java

          List of all DNS record types: https://en.wikipedia.org/wiki/List_of_DNS_record_types . Likely some types have been added in new DNS versions via RFCs. E.g. URI identifier has been added in 2015 by https://tools.ietf.org/html/rfc7553 , so no wonder it's not supported by the lib.

          There is https://github.com/jenkinsci/jmdns/pull/2 , which may resolve the issue by bumping to the new version

          Oleg Nenashev added a comment - It may happen even without network issues, e.g. when there is an unsupported DNS Message type coming from DNS. We use an old library version, and not all DNS Message types are supported (discovered in JENKINS-50812 ) Record type enumeration in the lib: https://github.com/jenkinsci/jmdns/blob/64f48ab717e0c8022f60d7dcb7f148f47c7f1227/src/main/java/javax/jmdns/impl/constants/DNSRecordType.java List of all DNS record types: https://en.wikipedia.org/wiki/List_of_DNS_record_types . Likely some types have been added in new DNS versions via RFCs. E.g. URI identifier has been added in 2015 by https://tools.ietf.org/html/rfc7553 , so no wonder it's not supported by the lib. There is https://github.com/jenkinsci/jmdns/pull/2 , which may resolve the issue by bumping to the new version

          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.

          Francisco Fernández added a comment - 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.

          Oleg Nenashev added a comment -

          It was released in Jenkins 2.178, but we do not think backporting is justified for now

          Oleg Nenashev added a comment - It was released in Jenkins 2.178, but we do not think backporting is justified for now

          Oleg Nenashev added a comment -

          LTS backporting comment: let's do more testing before considering backporting

          Oleg Nenashev added a comment - LTS backporting comment: let's do more testing before considering backporting

          Oliver Gondža added a comment - - edited

          Oliver Gondža added a comment - - edited oleg_nenashev , fcojfernandez , have you gain enough confidence in backporting https://github.com/jenkinsci/jenkins/pull/4021 and https://github.com/jenkinsci/jenkins/pull/4037  into .2?

          I am rejecting the backport to be added to 2.176 LTS line. Will appear in the next one naturally.

          Oliver Gondža added a comment - I am rejecting the backport to be added to 2.176 LTS line. Will appear in the next one naturally.

            fcojfernandez Francisco Fernández
            uday Udaypal Aarkoti
            Votes:
            12 Vote for this issue
            Watchers:
            24 Start watching this issue

              Created:
              Updated:
              Resolved: