-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Platform: All, OS: Linux
Hi
I have a build server that sometime abort the scheduled build with just error
aborted - else no error messages, see example build log below.
I have configured a logger for the fine level (logger: hudson, log level: fine)
see catelina log below - no useful errors
I have just start calling maven with -X for debug output - if maven was the
course - but have not yet capture the error (if maven is to blame - don't think so)
Any suggestions - please see logs are version data below
Best regards
Peter Andersen
------------
Versions:
Hudson: 1.289
Tomcat: 6.0.18
java version "1.6.0_0"
OpenJDK Runtime Environment (build 1.6.0_0-b11)
OpenJDK 64-Bit Server VM (build 1.6.0_0-b11, mixed mode)
Maven: 2.0.9
OS Debian 5, uname -a:
Linux hudson 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64 GNU/Linux
Example aborted build:
started
Updating svn://svn.lenio.dk/xxxx/trunk
U ...
A build.xml
At revision 11963
Parsing POMs
[trunk] $ /usr/lib/jvm/java-6-openjdk/bin/java -Xmx768m -XX:MaxPermSize=256m -cp
/home/sysadm/apache-tomcat-6.0.18/webapps/hudson/WEB-INF/lib/maven-agent-1.289.jar:/usr/share/maven2/boot/classworlds.jar
hudson.maven.agent.Main /usr/share/maven2
/home/sysadm/apache-tomcat-6.0.18/webapps/hudson/WEB-INF/lib/remoting-1.289.jar
/home/sysadm/apache-tomcat-6.0.18/webapps/hudson/WEB-INF/lib/maven-interceptor-1.289.jar
38194
ERROR: Aborted
No emails were triggered.
finished: ABORTED
Catalina log snippet
Mar 11, 2009 1:33:35 AM hudson.model.Queue maintain
FINE: Queue maintenance started hudson.model.Queue@338f7701
Mar 11, 2009 1:33:40 AM hudson.model.Queue maintain
FINE: Queue maintenance started hudson.model.Queue@338f7701
Mar 11, 2009 1:33:45 AM hudson.model.Queue maintain
FINE: Queue maintenance started hudson.model.Queue@338f7701
Mar 11, 2009 1:33:48 AM hudson.model.Run setResult
FINE: diop-site-build #12 : result is set to ABORTED by
hudson.model.Run.run(Run.java:896)
Mar 11, 2009 1:33:48 AM hudson.model.Run run
INFO: diop-site-build #12 main build action completed: ABORTED
- depends on
-
JENKINS-4345 maven build failure doesn't provide enough informations
-
- Closed
-
- is duplicated by
-
JENKINS-5053 SocketTimeoutException after build start
-
- Resolved
-
gonzalad: What system are you running Hudson on? How much RAM does it have? Is it possible that you could stop some other service and see if it works more reliably?
As you probably read above, I was getting timeouts almost every time, and now after stopping the Artifactory service, I haven't tested it a whole lot but it worked every time I tested. Artifactory was using hundreds of MBs of RAM and swap space and some CPU time, but now that I cut it out, Maven is able to start fast enough to connect to Hudson.