Skip to main content

Hud 2.2.1 - Intermittent failure to start Maven 3 build - Process failed to connect

  1 post   Feedicon  
Replies: 0 - Last Post: June 30, 2012 02:19
by: louis.burton
showing 1 - 1 of 1
Posted: June 30, 2012 02:19 by louis.burton
I have no problems for a while, then, no matter how much I retry, this debug port for hudson eventspy is never connected to in time. I don't know how to configure the timeout. Using a 2 cpu VM which is dedicated to Hudson, memory and cpu availability seems decent. netstat output seems sensible.

I find little documentation on hudson.eventspy.port, and this issue is actually causing our hudson CI to be unusable.

About 13 builds run from this hudson, nothing else runs from the machine. There's only one executor.

Any help is much appreciated! Thanks.

Started by user anonymous
Updating svn://mysvn revision: 30-Jun-2012 02:58:29 depth:infinity ignoreExternals: false
At revision 74045
no change for svn://mysvn since the previous build
[INFO] Using Maven 3 installation: Maven 3.0.3
[INFO] Checking Maven 3 installation environment
[workspace] $ /usr/local/apache-maven-3.0.3/bin/mvn --help
[INFO] Checking Maven 3 installation version
[INFO] Detected Maven 3 installation version: 3.0.3
[workspace] $ /usr/local/apache-maven-3.0.3/bin/mvn clean deploy -V -B -Dlog4j.configuration=fileHmmmvar/lib/hudson/jobs/test/workspace/src/test/resources/log4j.xml -Dslf4j=false -Dmaven.ext.class.path=/var/lib/hudson/maven/slavebundle/resourcesHmmmvar/lib/hudson/maven/slavebundle/lib/maven3-eventspy-3.0.jarHmmmvar/lib/hudson/war/WEB-INF/lib/hudson-remoting-2.2.1.jar -Dhudson.eventspy.port=41403 -f pom.xml -P coverage -U
[DEBUG] Waiting for connection on port: 41403
Apache Maven 3.0.3 (r1075438; 2011-02-28 17:31:09+0000)
Maven home: /usr/local/apache-maven-3.0.3
Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
Java home: /usr/java/jdk1.6.0_29/jre
Default locale: en_GB, platform encoding: ISO-8859-1
OS name: "linux", version: "2.6.18-194.el5", arch: "amd64", family: "unix"
[ERROR] Process did not initiate connection and is still alive; killing it
[ERROR] Failure: hudson.AbortException: Process failed to connect; exit code: 143
ERROR: Process failed to connect; exit code: 143
[CHECKSTYLE] Skipping publisher since build result is FAILURE
Publishing Javadoc
Recording test results
Emma: looking for coverage reports in the provided path: target/emma/coverage.xml
[htmlpublisher] Archiving HTML reports...
[htmlpublisher] Archiving at BUILD level /var/lib/hudson/jobs/test/workspace/target/deployed-site to /var/lib/hudson/jobs/test/builds/2012-06-30_02-58-29/htmlreports/Maven_Site
ERROR: Specified HTML directory '/var/lib/hudson/jobs/test/workspace/target/deployed-site' does not exist.
Sending e-mails to:
Build was marked for publishing on http://build2:8080/
[DEBUG] Skipping watched dependency update for build: test #75 due to result: FAILURE
Finished: FAILURE

Replies: 0 - Last Post: June 30, 2012 02:19
by: louis.burton
Please Confirm