[JIRA] [core] (JENKINS-23186) Got conflicting probe from ourselves warning message on Jenkins startup
Laurent TOURREAU commented on JENKINS-23186 Got conflicting probe from ourselves warning message on Jenkins startup What is the appropriate setup according to you? Is it mandatory to have 1 instance by VM max? We have constraint about our architecture. For me, we should not get such reported message if everything is ok. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23186) Got conflicting probe from ourselves warning message on Jenkins startup
Daniel Beck commented on JENKINS-23186 Got conflicting probe from ourselves warning message on Jenkins startup Given the fact that all platform installers only support one instance of Jenkins I'd call that the default assumption. While it's not "mandatory to have at most 1 instance", it's just likely to be not as well supported. In this case, it seems to be more of a diagnostic message rather than a real problem (as you can see in the source code linked above) for the unusual situation that one service (Jenkins) is advertised multiple times from the same host. Start Jenkins with java -Dhudson.DNSMultiCast.disabled=true ... -jar jenkins.war --httpPort=... as documented in the wiki to disable advertising the service this way. Or are you using DNS Service Discovery in some way? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23186) Got conflicting probe from ourselves warning message on Jenkins startup
Daniel Beck commented on JENKINS-23186 Got conflicting probe from ourselves warning message on Jenkins startup This is a very unusual setup in the age of virtual machines. The warning seems appropriate for most setups, and you could just ignore it. Tempted to close as Won't Fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23186) Got conflicting probe from ourselves warning message on Jenkins startup
Laurent TOURREAU reopened JENKINS-23186 Got conflicting probe from ourselves warning message on Jenkins startup When i type ifconfig loopback interface seem ok: user@host:/home/user #ifconfig lo loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:47004528 errors:0 dropped:0 overruns:0 frame:0 TX packets:47004528 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:138746413501 (129.2 GiB) TX bytes:138746413501 (129.2 GiB) ping also work: PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.049 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.124 ms What really should be fixed? Change By: Laurent TOURREAU (27/May/14 7:31 AM) Resolution: NotADefect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23186) Got conflicting probe from ourselves warning message on Jenkins startup
Laurent TOURREAU created JENKINS-23186 Got conflicting probe from ourselves warning message on Jenkins startup Issue Type: Bug Assignee: Unassigned Components: core Created: 26/May/14 8:50 AM Description: WARNING: Got conflicting probe from ourselves incoming: Service@562665732 type: TYPE_SRV index 33, class: CLASS_IN index 1, name: Jenkins (9)._http._tcp.local. ttl: 3598/3599 server: server.local.:8050 local : Service@1352459983 type: TYPE_SRV index 33, class: CLASS_IN index 1-unique, name: Jenkins (9)._http._tcp.local. ttl: 3599/3600 server: server.local.:8080 Project: Jenkins Priority: Major Reporter: Laurent TOURREAU This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23186) Got conflicting probe from ourselves warning message on Jenkins startup
Oleg Nenashev resolved JENKINS-23186 as Not A Defect Got conflicting probe from ourselves warning message on Jenkins startup Seems you have misconfigured the network loopback. Useful links: http://www.spigotmc.org/threads/got-conflicting-probe-from-ourselves.5390/ http://stackoverflow.com/questions/2095/which-ipv6-address-should-i-use-for-bonjour Code: http://jmdns.sourceforge.net/clover/javax/jmdns/impl/DNSRecord.html Change By: Oleg Nenashev (26/May/14 4:37 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
