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

DNS multicast error messages

    XMLWordPrintable

Details

    • 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

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-10160 When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.

          • Major - Major loss of function.
          • Fixed but Unreleased

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-29490 Jenkins flood HDD with DNS Errors

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-50812 Logfile filling up with SIP entries

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-10160 When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.

          • Major - Major loss of function.
          • Fixed but Unreleased

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-33596 Disable DNSMultiCast & UDPBroadcastThread by default

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link PR#4021

          Web Link PR#4037

          Activity

            Ascending order - Click to sort in descending order
            View 10 older comments
            fcojfernandez 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.

            fcojfernandez 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 Oleg Nenashev added a comment -

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

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

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

            oleg_nenashev Oleg Nenashev added a comment - LTS backporting comment: let's do more testing before considering backporting
            olivergondza 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?

            olivergondza 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?
            olivergondza 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.

            olivergondza 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.

            People

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

              Dates

                Created:
                Updated:
                Resolved: