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

Logfile filling up with SIP entries

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Component/s: core
    • Labels:
    • Environment:
      Ubuntu 16.04LTS
      Jenkins 2.107.2
    • Similar Issues:

      Description

      I can't explain the logging of those entries to my server. It filled my disk to 100% again this morning.

      There is some existing report about the DNSQuestion logging part but I couldn't find any report about those SIP Asterisk entries. Nothing of that type is used on my side.

       
      SEVERE: Could not find record type: dns[query,146.0.43.5:56100, length=426, id=0x4f50, flags=0x5449:aa, questions=1
      questions:
              [DNSQuestion@323223758 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: 00@81.169.187.198 SIP/2.0
      Via: SIP/2.0/UDP 146.0.43.5:56100;branch=z9hG4bK-1335804982;rport
      Co.Length: 0
      From: "asterisk"<sip:48413005736@1.7.0.0.1>;tag=3531613962626336313465390135373634323.303436
      Accept: application/sdp
      User-Agent: Asterisk.PBX 1.6.5
      To: "asterisk"<sip:48.13005736@127.0.0.1>
      Contact: sip:100@146.0.43.5:561.0
      CSeq: 1 OPTIONS
      Call-ID: 9716743636176791624.920
      Max-Forwards: 70

      ϿϿϿϿϿϿϿϿϿϿϿϿϿϿϿϿ.]]
              question:      [DNSQuestion@323223758 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: 00@81.169.187.198 SIP/2.0
      Via: SIP/2.0/UDP 146.0.43.5:56100;branch=z9hG4bK-1335804982;rport
      Co.Length: 0
      From: "asterisk"<sip:48413005736@1.7.0.0.1>;tag=3531613962626336313465390135373634323.303436
      Accept: application/sdp
      User-Agent: Asterisk.PBX 1.6.5
      To: "asterisk"<sip:48.13005736@127.0.0.1>
      Contact: sip:100@146.0.43.5:561.0
      CSeq: 1 OPTIONS
      Call-ID: 9716743636176791624.920
      Max-Forwards: 70

        Attachments

          Issue Links

            Activity

            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            AFAICT is comes from https://github.com/jenkinsci/jmdns , which is included into the Jenkins core. Last update in the lib dates to 2011...

            I'd guess it happens due to the "TYPE_IGNORE", which is probably just unsupported in the lib

            Show
            oleg_nenashev Oleg Nenashev added a comment - AFAICT is comes from https://github.com/jenkinsci/jmdns , which is included into the Jenkins core. Last update in the lib dates to 2011... I'd guess it happens due to the "TYPE_IGNORE", which is probably just unsupported in the lib
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            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 - 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
            Hide
            kkretsch Kai Kretschmann added a comment -

            That explains the DNS ignore lines, but what about the SIP headers which are shown?

            Show
            kkretsch Kai Kretschmann added a comment - That explains the DNS ignore lines, but what about the SIP headers which are shown?
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            "but what about the SIP headers which are shown?". I am not sure what you mean. The entire log entry comes from here: https://github.com/jenkinsci/jmdns/blob/64f48ab717e0c8022f60d7dcb7f148f47c7f1227/src/main/java/javax/jmdns/impl/DNSIncoming.java#L249 . It means that all headers are shown as diagnostics info.

            Regarding usage in Jenkins.

            Show
            oleg_nenashev Oleg Nenashev added a comment - "but what about the SIP headers which are shown?". I am not sure what you mean. The entire log entry comes from here: https://github.com/jenkinsci/jmdns/blob/64f48ab717e0c8022f60d7dcb7f148f47c7f1227/src/main/java/javax/jmdns/impl/DNSIncoming.java#L249 . It means that all headers are shown as diagnostics info. Regarding usage in Jenkins. The only usage of jmdns is DNS MultiCast support: https://github.com/jenkinsci/jenkins/blob/08def67a18eee51de9f3f99bc2a792fee1c160e0/core/src/main/java/hudson/DNSMultiCast.java#L23 Whatever happens, you can disable the DNS Multicast logic entirely using the "-Dhudson.DNSMultiCast.disabled=true" system property. I really doubt any modern instance really relies on DNS Multicast
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            As I see it actually duplicates JENKINS-25369. Let's continue the discussion there

            Show
            oleg_nenashev Oleg Nenashev added a comment - As I see it actually duplicates JENKINS-25369 . Let's continue the discussion there

              People

              • Assignee:
                Unassigned
                Reporter:
                kkretsch Kai Kretschmann
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: