[JIRA] [core] (JENKINS-25369) DNS multicast error messages

23 views
Skip to first unread message

dev@baltrinic.com (JIRA)

unread,
Jul 7, 2015, 8:07:05 AM7/7/15
to jenkinsc...@googlegroups.com
Kenneth Baltrinic commented on Bug JENKINS-25369
 
Re: 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.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

dbeck@cloudbees.com (JIRA)

unread,
Jul 7, 2015, 9:18:02 AM7/7/15
to jenkinsc...@googlegroups.com

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.

zschille@kombinat-berlin.de (JIRA)

unread,
Jul 27, 2015, 6:54:03 AM7/27/15
to jenkinsc...@googlegroups.com

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

dbeck@cloudbees.com (JIRA)

unread,
Jul 27, 2015, 4:53:01 PM7/27/15
to jenkinsc...@googlegroups.com

Related to JENKINS-10160, possibly a duplicate.

furai@thd.vg (JIRA)

unread,
Feb 15, 2018, 3:25:02 AM2/15/18
to jenkinsc...@googlegroups.com

I'm running into similar issue right now. My syslog is getting filled with messages from jmdns

https://file.furai.pl/2018-02-15-09-18-46.txt
And from this point onward it just keeps looping over and over again.
Increasing that question (queue?) by 1 entry.
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

furai@thd.vg (JIRA)

unread,
Feb 15, 2018, 3:26:02 AM2/15/18
to jenkinsc...@googlegroups.com
I'm running into similar issue right now. My syslog is getting filled with messages from jmdns

https://file.furai.pl/2018-02-15-09-18-46.txt
And from this point onward it just keeps looping over and over again.
Increasing that question (queue?) by 1 entry.

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 16, 2018, 4:42:02 AM4/16/18
to jenkinsc...@googlegroups.com
Oleg Nenashev assigned an issue to Oleg Nenashev
Change By: Oleg Nenashev
Assignee: Oleg Nenashev

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 16, 2018, 4:46:08 AM4/16/18
to jenkinsc...@googlegroups.com

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

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 16, 2018, 4:46:09 AM4/16/18
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
Labels: dns dnsquestion sip

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 16, 2018, 4:47:04 AM4/16/18
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
Labels: dns dnsquestion logging sip

o.v.nenashev@gmail.com (JIRA)

unread,
Dec 25, 2018, 5:00:04 AM12/25/18
to jenkinsc...@googlegroups.com
Oleg Nenashev assigned an issue to Unassigned
Change By: Oleg Nenashev
Assignee: Oleg Nenashev
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

fjfernandez@cloudbees.com (JIRA)

unread,
May 14, 2019, 3:55:10 AM5/14/19
to jenkinsc...@googlegroups.com
Francisco Fernández started work on Bug JENKINS-25369
 
Change By: Francisco Fernández
Status: Open In Progress

fjfernandez@cloudbees.com (JIRA)

unread,
May 14, 2019, 3:55:11 AM5/14/19
to jenkinsc...@googlegroups.com
Change By: Francisco Fernández
Assignee: Francisco Fernández

fjfernandez@cloudbees.com (JIRA)

unread,
May 14, 2019, 3:59:03 AM5/14/19
to jenkinsc...@googlegroups.com

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.

fjfernandez@cloudbees.com (JIRA)

unread,
May 14, 2019, 6:00:03 AM5/14/19
to jenkinsc...@googlegroups.com
Change By: Francisco Fernández
Status: In Progress Review

fjfernandez@cloudbees.com (JIRA)

unread,
May 21, 2019, 11:10:04 AM5/21/19
to jenkinsc...@googlegroups.com
Change By: Francisco Fernández
Status: In Review Resolved
Resolution: Fixed

o.v.nenashev@gmail.com (JIRA)

unread,
May 21, 2019, 11:12:05 AM5/21/19
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue

It was released in Jenkins 2.178, but we do not think backporting is justified for now
Change By: Oleg Nenashev
Released As: Jenkins 2.178

o.v.nenashev@gmail.com (JIRA)

unread,
May 21, 2019, 11:13:04 AM5/21/19
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
Labels: 2.176.1-rejected dns dnsquestion logging lts-candidate sip

o.v.nenashev@gmail.com (JIRA)

unread,
May 21, 2019, 11:14:07 AM5/21/19
to jenkinsc...@googlegroups.com

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

ogondza@gmail.com (JIRA)

unread,
Jul 1, 2019, 2:41:03 AM7/1/19
to jenkinsc...@googlegroups.com

ogondza@gmail.com (JIRA)

unread,
Jul 1, 2019, 2:41:04 AM7/1/19
to jenkinsc...@googlegroups.com
Oliver Gondža edited a comment on Bug JENKINS-25369
[~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?

ogondza@gmail.com (JIRA)

unread,
Aug 1, 2019, 7:09:04 AM8/1/19
to jenkinsc...@googlegroups.com
Oliver Gondža updated an issue
Change By: Oliver Gondža
Labels: 2.176.1-rejected 2.176.2-rejected 2.176.3-rejected dns dnsquestion logging lts-candidate sip

ogondza@gmail.com (JIRA)

unread,
Aug 1, 2019, 7:09:14 AM8/1/19
to jenkinsc...@googlegroups.com

I am rejecting the backport to be added to 2.176 LTS line. Will appear in the next one naturally.
Reply all
Reply to author
Forward
0 new messages