Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-25369

DNS multicast error messages

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: core
    • Environment:
    • Similar Issues:

      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

            Activity

            Hide
            danielbeck Daniel Beck added a comment -

            Since they're in a third party component, I don't think effort/gain works out in favor of reducing log level.

            Workaround: java -Dhudson.DNSMultiCast.disabled=true

            Show
            danielbeck Daniel Beck added a comment - Since they're in a third party component, I don't think effort/gain works out in favor of reducing log level. Workaround: java -Dhudson.DNSMultiCast.disabled=true
            Hide
            derfunk Andreas Katzig added a comment -

            unintentional self assign, sorry.

            Show
            derfunk Andreas Katzig added a comment - unintentional self assign, sorry.
            Hide
            ayursha Alex Yursha added a comment - - edited

            So is it going to be fixed as this logging spam is pretty annoying? jmnds original package has not been updated for a while, so we could either fix the fork or drop this dependency completely if we don't need that functionality.

            Show
            ayursha Alex Yursha added a comment - - edited So is it going to be fixed as this logging spam is pretty annoying? jmnds original package has not been updated for a while, so we could either fix the fork or drop this dependency completely if we don't need that functionality.
            Hide
            danielbeck Daniel Beck added a comment -

            It doesn't look to me like it's that annoying if you're not even going to disable the feature and restart Jenkins once in 6+ weeks.

            Show
            danielbeck Daniel Beck added a comment - It doesn't look to me like it's that annoying if you're not even going to disable the feature and restart Jenkins once in 6+ weeks.
            Hide
            neerajlad Neeraj Lad added a comment -

            Does this could harm any execution? since i ma also getting same this when i run sonar-plugin into jenkins.

            Show
            neerajlad Neeraj Lad added a comment - Does this could harm any execution? since i ma also getting same this when i run sonar-plugin into jenkins.
            Hide
            kbaltrinic 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.

            Show
            kbaltrinic 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.
            Hide
            danielbeck Daniel Beck added a comment -

            Kenneth Baltrinic 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.

            Show
            danielbeck Daniel Beck added a comment - Kenneth Baltrinic 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.
            Hide
            dzschille 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

            Show
            dzschille 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
            Hide
            danielbeck Daniel Beck added a comment -

            Related to JENKINS-10160, possibly a duplicate.

            Show
            danielbeck Daniel Beck added a comment - Related to JENKINS-10160 , possibly a duplicate.
            Hide
            oleg_nenashev 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

            Show
            oleg_nenashev 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

              People

              • Assignee:
                oleg_nenashev Oleg Nenashev
                Reporter:
                uday Udaypal Aarkoti
              • Votes:
                12 Vote for this issue
                Watchers:
                23 Start watching this issue

                Dates

                • Created:
                  Updated: