+++ This bug was initially created as a clone of Bug #993561 +++ Description of problem: Create jenkins server, and touch any blank file under the repo. Git push the change. And check the jenkins.log via rhc tail. We can found in the jenkins.log: WARNING: Failed to broadcast over UDP java.net.BindException: Permission denied at java.net.PlainDatagramSocketImpl.bind0(Native Method) at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:95) at java.net.DatagramSocket.bind(DatagramSocket.java:376) at java.net.MulticastSocket.<init>(MulticastSocket.java:172) at java.net.MulticastSocket.<init>(MulticastSocket.java:137) at hudson.UDPBroadcastThread.<init>(UDPBroadcastThread.java:69) at jenkins.model.Jenkins.<init>(Jenkins.java:822) at hudson.model.Hudson.<init>(Hudson.java:81) at hudson.model.Hudson.<init>(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:214) Version-Release number of selected component (if applicable): devenv_3616 How reproducible: always Steps to Reproduce: 1.Create jenkins server 2.Do some changes in the git repo and push them 3.Check the jenkins.log Actual results: Some warning message appears in the jenkins.log Expected results: No such warning meesages. Additional info: Since AWS is not allowed broadcast/multicast over UDP, we should disable such modules to avoid the warning/error messages. --- Additional comment from Andy Goldstein on 2013-08-07 16:50:26 EDT --- It looks like this commit adds support to disable it by setting a Java system property: https://github.com/jenkinsci/jenkins/commit/19f34b54d6cd69f837552a21d8adb41f3b5fba91 I think this was first introduced in Jenkins 1.514 --- Additional comment from Ben Parees on 2013-12-16 11:03:06 EST --- Waiting on testing of update to latest jenkins. --- Additional comment from openshift-github-bot on 2014-01-03 13:06:50 EST --- Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/48f66cdf01510560bbf4bfda1313813da405987a bug 993561: WARNING: Failed to broadcast over UDP appears in jenkins.log when git push change to a jenkins app --- Additional comment from Ben Parees on 2014-01-10 11:26:46 EST --- The fix for this is prepared but until we move up to jenkins 1.540+ we don't have all the pieces aligned to deliver it. The version of jenkins that supports disabling UDP also requires that the openshift-jenkins-plugin needs to pass "-jar-cache $OPENSHIFT_DATA_DIR/.jenkins/cache/jars" on the slave launch to avoid putting the jar-cache in a non-writeable directory. --- Additional comment from Ben Parees on 2014-06-30 23:35:04 EDT --- https://github.com/openshift/origin-server/pull/5552 --- Additional comment from Meng Bo on 2014-07-02 02:17:46 EDT --- Checked on devenv_4932, with disable_jenkins_udp_broadcast present, the UDP broadcast error will not show anymore. Jul 02, 2014 6:11:53 AM jenkins.InitReactorRunner$1 onAttained INFO: Completed initialization Jul 02, 2014 6:11:54 AM org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@1a3dda2: display name [Root WebApplicationContext]; startup date [Wed Jul 02 06:11:54 EDT 2014]; root of context hierarchy Jul 02, 2014 6:11:54 AM org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@1a3dda2]: org.springframework.beans.factory.support.DefaultListableBeanFactory@1b1786 Jul 02, 2014 6:11:54 AM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1b1786: defining beans [authenticationManager]; root of factory hierarchy Jul 02, 2014 6:11:54 AM org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@f4821d: display name [Root WebApplicationContext]; startup date [Wed Jul 02 06:11:54 EDT 2014]; root of context hierarchy Jul 02, 2014 6:11:54 AM org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@f4821d]: org.springframework.beans.factory.support.DefaultListableBeanFactory@a02f4f Jul 02, 2014 6:11:54 AM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@a02f4f: defining beans [filter,legacy]; root of factory hierarchy Jul 02, 2014 6:11:55 AM hudson.WebAppMain$3 run INFO: Jenkins is fully up and running
We'll need this PR too: https://github.com/openshift/origin-server/pull/5552
With 2.1.4 we will ship the required Jenkins version for this change. Upstream commit: commit 130f246a1940ed5b56e64bff7f3ba2ceee23f78e Author: Ben Parees <bparees> Date: Mon Jun 23 14:08:50 2014 -0400 "WARNING: Failed to broadcast over UDP" appears in jenkins.log https://bugzilla.redhat.com/show_bug.cgi?id=993561
Checked the code on puddle 2.1.z/2014-08-01.1, found not all changes in the patch were merged into latest packages. "disable_jenkins_udp_broadcast" marker file was missing from package openshift-origin-cartridge-jenkins-1.20.3.3-1.el6op.noarch.
My apologies. When diff'ing for changes to build for 2.1.5 I missed the fact that this new marker file was added since it's an empty file.
Checked on puddle 2.1.z/2014-08-04.1, the patch has been merged into openshift-origin-cartridge-jenkins-client-1.19.3.3-1.el6op.noarch and openshift-origin-cartridge-jenkins-1.20.3.4-1.el6op.noarch No UDP broadcast error shown during git push for jenkins app.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1095.html