[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Oleg Nenashev updated JENKINS-10160 Jenkins / JENKINS-10160 When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140348.1309401794000.7707.1558451882576%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Oleg Nenashev commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. We believe that JENKINS-25369 fixes it as well. Please reopen if you experience any issues Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140348.1309401794000.7703.1558451822895%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Patrick Rose commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Thanks to Francisco Fernández, this should now be fixed in 2.178! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140348.1309401794000.7632.1558451642380%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Patrick Rose edited a comment on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. bq. Might actually add those java parameters mentioned above to prevent it from happening.We're running with those java args, and it still happens to us (albeit infrequently) *EDIT*: Which makes me wonder if JENKINS-33596 would actually fix the issue? If we're turning off on our end, I'm not sure why we keep getting the issue once every 6 months or so. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Patrick Rose commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Might actually add those java parameters mentioned above to prevent it from happening. We're running with those java args, and it still happens to us (albeit infrequently) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Furai commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. What's the status on the fix to that? Recently it brought my machine down yet again. Maybe I should just containerise jenkins instance. Might actually add those java parameters mentioned above to prevent it from happening. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Lior Goikhburg commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. The reason why the workaround doesn't work for people, is because of the bad ordering of the parameters. The parameters -Dhudson.DNSMultiCast.disabled=true -Dhudson.udp=-1 are parameters to java, not jenkins, and therefore should be specified after java command but before -jar /usr/share/jenkins/jenkins.war All parameters after jenkins.war are parameters to jenkins. So, check the process command with pgrep -a java and you should see something similar to 6916 /usr/bin/java -Djava.awt.headless=true -Dhudson.DNSMultiCast.disabled=true -Dhudson.udp=-1 -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1 --httpListenAddress=192.168.255.1 Hope that helps. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Lucas Grzegorczyk assigned an issue to Unassigned Jenkins / JENKINS-10160 When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Change By: Lucas Grzegorczyk Assignee: Lucas Grzegorczyk Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Lucas Grzegorczyk commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. But if I understood right - people who were running their war directly with -Dhudson.DNSMultiCast.disabled=true and -Dhudson.udp=-1 Were still getting the issue as per this link. Is this somehow related? Or are this options disabling completely different things? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Jesse Glick commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Just do JENKINS-33596 already so that it becomes someone else’s problem: whoever decides to maintain that plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Oleg Nenashev commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. As discussed in https://github.com/jenkinsci/jmdns/pull/2, my proposal is to replace the custom library fork by the official release from https://github.com/jmdns/jmdns . All custom patches were before 2010, and I doubt they are really needed anymore Daniel Beck Jesse Glick would be nice to get your feedback here Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Lucas Grzegorczyk commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. This bug have again brought my machine down. Is there any fix to it or a workaround? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Lucas Grzegorczyk assigned an issue to Lucas Grzegorczyk Jenkins / JENKINS-10160 When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Change By: Lucas Grzegorczyk Assignee: Lucas Grzegorczyk Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Patrick Rose commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Ryan Campbell - this one, there's a compilation error I need to look into but I've not had the chance to yet. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Ryan Campbell commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Patrick Rose, which pull request? I don't see it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Patrick Rose commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. The pull request I submitted is now being looked at so it might be fixed soon. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Lucas Grzegorczyk commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. I'm sorry to just bump the thread but it happened few times since the last time I've posted and I haven't seen any patch addressing the issue. Is it going to be fixed? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Patrick Rose commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. This brought down our Jenkins instance again. We're using both of -Dhudson.DNSMultiCast.disabled=true and -Dhudson.udp=-1 and this still happens. Andrew Bayer - is there anything I can do to get the above PR looked at? I'd understand this issue not being fixed if there's no time to get the fix together but there's a PR that just needs to be merged and tested that's had no feedback for 2 months! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Patrick Rose commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Considering how there's not been a commit to that repo for 7 years, I'm going to assume that the infrastructure for that Jenkins build is out of date. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Terry Lacy commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Thanks for your quick response, Patrick. It looks like there is a problem with your PR? It says "All checks have failed" and "Jenkins — Looks like there's a problem with this pull request". Looks like it broke a build? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Patrick Rose commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Is it certain that jmdns is the cause? It was not clear to me that jmdns was the source of the messages, but my logs were so large that I couldn't trace where they came from. Yes - the first log you get makes it obvious that the is in jmdns, but it's difficult to find that when it's logging multiple times a second. Is there anything more I can do to get my PR looked at? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Terry Lacy edited a comment on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. I'm adding another data point for this. My logs filled up with entries similar to:question: [DNSQuestion@1607462970 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] Is it This is on Jenkins 2.89.4 on a Windows Server 2012 R2 VM.Are y'all certain that jmdns is the cause? It was not clear to me that jmdns was the source of the messages entries , but my logs were so large that I couldn't trace where they came from what originally triggered the flood of DNSQuestion entries .This filled a drive once on my VM. Our SAs, not knowing the source of the problem, enlarged the drive, which promptly filled up again (within less than an hour)! In the end logs were almost 100G before I stopped the server.This killed a couple of critical production processes. I disabled DNS multicast, but as I read the comments here, that does not appear to be a permanent solution. I'm also not clear on the consequences of applying these dubious "fixes". I'm very reluctant to manually patch jmdns since that presumably makes it painful to update Jenkins with security patches, etc. Especially since it's not obvious that it will solve the problem, either. My gut feeling, based on the comments here, is that shutting down the server to apply any of these umm...fixes temporarily resolves the issue, maybe for days or weeks, but none of the fixes permanently resolves the problem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Terry Lacy edited a comment on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. I'm adding another data point for this. My logs filled up with entries similar to:question: [DNSQuestion@1607462970 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ]Is it certain that jmdns is the cause? It was not clear to me that jmdns was the source of the messages, but my logs were so large that I couldn't trace where they came from.This filled a drive once on my VM. Our SAs, not knowing the source of the problem, enlarged the drive, which promptly filled up again (within less than an hour)!In the end logs were almost 100G before I stopped the server.This killed a couple of critical production processes. I disabled DNS multicast, but as I read the comments here, that does not appear to be a permanent solution. I'm also not clear on the consequences of applying these dubious "fixes". I'm very reluctant to manually patch jmdns since that presumably makes it painful to update Jenkins with security patches, etc. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Terry Lacy edited a comment on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. I'm adding another data point for this. My logs filled up with entries similar to:question: [DNSQuestion@1607462970 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ]Is it certain that jmdns is the cause? It was not clear to me that jmdns was the source of the messages, but my logs were so large that I couldn't trace where they came from.This filled a drive once on my VM. My SA Our SAs , not knowing the source of the problem, enlarged the drive, which promptly filled up again (within less than an hour)!In the end logs were almost 100G before I stopped the server.This killed a couple of critical production processes. I disabled DNS multicast, but as I read the comments here, that does not appear to be a permanent solution. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Terry Lacy commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. I'm adding another data point for this. My logs filled up with entries similar to: question: [DNSQuestion@1607462970 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] Is it certain that jmdns is the cause? It was not clear to me that jmdns was the source of the messages, but my logs were so large that I couldn't trace where they came from. This filled a drive once on my VM. My SA, not knowing the source of the problem, enlarged the drive, which promptly filled up again (within less than an hour)! In the end logs were almost 100G before I stopped the server. This killed a couple of critical production processes. I disabled DNS multicast, but as I read the comments here, that does not appear to be a permanent solution. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title
Lucas Grzegorczyk edited a comment on JENKINS-10160
Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
I'm running into similar issue right now. My syslog is getting filled with messages from jmdns Ubuntu 17.10 x64 {{java -version}}{{openjdk version "1.8.0_151"}}{{OpenJDK Runtime Environment (build 1.8.0_151-8u151-b12-0ubuntu0.17.10.2-b12)}}{{OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)}} [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.Changed my logrotate to mitigate the issue but I'd love an actual fix for this.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Lucas Grzegorczyk commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. I'm running into similar issue right now. My syslog is getting filled with messages from jmdns Ubuntu 17.10 x64 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. Changed my logrotate to mitigate the issue but I'd love an actual fix for this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title
Clara Mckenzie commented on JENKINS-10160
Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Happening to me with hudson.DNSMultiCast.disable=true MacOSX 10.12.2 defaults read /Library/Preferences/org.jenkins-ci { heapSize = 512m; httpPort = 8080; "hudson.DNSMultiCast.disabled" = true; minHeapSize = 256m; minPermGen = 256m; permGen = 512m; tmpdir = "/Users/Shared/Jenkins/tmp"; }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Lior Goikhburg edited a comment on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Wow, this is craptacular!This has just filled up 100gig of my rootfs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Lior Goikhburg commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Wow, this is craptacular! This has just filled 100gig of my rootfs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title mirabilos commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Just got bitten from that, too. Unfortunately, the network is now non-broken again (save for an empty resolv.conf, which did not trigger the bug), so I am uncertain as to the precise cause. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Maxime Viargues commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Same problem here with jenkins 2.25, using -Dhudson.DNSMultiCast.disabled=true Oct 11, 2016 1:23:04 PM javax.jmdns.impl.DNSIncoming readQuestion SEVERE: Could not find record type: dns[response,10.200.31.173:5353, length=12, id=0x0, flags=0x84f4:r:aa, questions=17623 questions: [DNSQuestion@422648395 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] [DNSQuestion@1723154136 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] etc. The log fills several GB/min. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Zachary LaCelle edited a comment on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. EDIT: I misspelled the argument (disable vs disabled). Seems to work.PREVIOUS:I attempted the fix mentioned by [~ngrigoriev] (-Dhudson.DNSMultiCast.disabled=true -Dhudson.udp=-1), but it doesn't seem to fix the problem.Here's the arguments given to Jenkins:/usr/bin/java -Dmail.smtp.starttls.enable=true -Dhudson.DNSMultiCast.disable=true -Dhudson.udp=-1 -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --httpsPort=-1 --ajp13Port=-1Here's what my jenkins.log looks like:question: [DNSQuestion@2137451499 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@816664983 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1397021935 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@365274778 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1597387715 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@2142995283 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@94356232 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@118673637 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1585153435 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@943519598 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1812730091 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1440318277 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1220146348 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@134233287 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1038834151 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@802211412 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@904112 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1234766810 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@170379198 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@2106342031 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@998228220 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@163782323 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1134412540 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1672826511 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@339263853 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1631728593 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1129001243 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@575558159 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1850896725 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ]
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Zachary LaCelle commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. I attempted the fix mentioned by Nikolai Grigoriev (-Dhudson.DNSMultiCast.disabled=true -Dhudson.udp=-1), but it doesn't seem to fix the problem. Here's the arguments given to Jenkins: /usr/bin/java -Dmail.smtp.starttls.enable=true -Dhudson.DNSMultiCast.disable=true -Dhudson.udp=-1 -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --httpsPort=-1 --ajp13Port=-1 Here's what my jenkins.log looks like: question: [DNSQuestion@2137451499 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@816664983 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1397021935 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@365274778 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1597387715 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@2142995283 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@94356232 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@118673637 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1585153435 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@943519598 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1812730091 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1440318277 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1220146348 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@134233287 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1038834151 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@802211412 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@904112 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1234766810 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@170379198 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@2106342031 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@998228220 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@163782323 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1134412540 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1672826511 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@339263853 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1631728593 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1129001243 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@575558159 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1850896725 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@618325458 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1896930720 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question:
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Cody Scott commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. It looks like development has moved to https://github.com/jmdns/jmdns with the latest version being 3.5.1 https://github.com/jmdns/jmdns/releases Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
