Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

QuickBuild

Linux Build Agent Not Connecting to Build Server #1024

#1
brichard ·
I have successfully started agents on my Solaris machines and they appear in the grid just fine.

However, I downloaded the proper linux agents and run them on my two linux boxes (same gateway as the Solaris) and they cannot connect. The agent processes starts and keeps alive using the default port 8811 but the build server grid never sees them. In the logs I can see:

$> tail -f console.log
jvm 1 | at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:244)
jvm 1 | at java.lang.Thread.run(libgcj.so.7rh)
jvm 1 | 2010-07-13 09:23:58,617 ERROR - Error connecting server.
jvm 1 | java.lang.NoClassDefFoundError: java.lang.ProcessBuilder
jvm 1 | at com.pmease.quickbuild.bootstrap.Bootstrap.getHostName(Bootstrap.java:278)
jvm 1 | at com.pmease.quickbuild.bootstrap.Bootstrap.init(Bootstrap.java:230)
jvm 1 | at com.pmease.quickbuild.bootstrap.Bootstrap.main(Bootstrap.java:111)
jvm 1 | at java.lang.reflect.Method.invoke(libgcj.so.7rh)
jvm 1 | at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:244)
jvm 1 | at java.lang.Thread.run(libgcj.so.7rh)
jvm 1 | 2010-07-13 09:24:00,323 ERROR - Error connecting server.
jvm 1 | java.lang.NoClassDefFoundError: java.lang.ProcessBuilder
jvm 1 | at com.pmease.quickbuild.bootstrap.Bootstrap.getHostName(Bootstrap.java:278)
jvm 1 | at com.pmease.quickbuild.bootstrap.Bootstrap.init(Bootstrap.java:230)
jvm 1 | at com.pmease.quickbuild.bootstrap.Bootstrap.main(Bootstrap.java:111)
jvm 1 | at java.lang.reflect.Method.invoke(libgcj.so.7rh)
jvm 1 | at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:244)
jvm 1 | at java.lang.Thread.run(libgcj.so.7rh)

AND

2010-07-13 09:05:53,115 [WrapperSimpleAppMain] ERROR com.pmease.quickbuild.bootstrap.Bootstrap - Error connecting server.
java.lang.NoClassDefFoundError: java.lang.ProcessBuilder
at com.pmease.quickbuild.bootstrap.Bootstrap.getHostName(Bootstrap.java:278)
at com.pmease.quickbuild.bootstrap.Bootstrap.init(Bootstrap.java:230)
at com.pmease.quickbuild.bootstrap.Bootstrap.main(Bootstrap.java:111)
at java.lang.reflect.Method.invoke(libgcj.so.7rh)
at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:244)
at java.lang.Thread.run(libgcj.so.7rh)
2010-07-13 09:05:58,126 [WrapperSimpleAppMain] ERROR com.pmease.quickbuild.bootstrap.Bootstrap - Error connecting server.
java.lang.NoClassDefFoundError: java.lang.ProcessBuilder
at com.pmease.quickbuild.bootstrap.Bootstrap.getHostName(Bootstrap.java:278)
at com.pmease.quickbuild.bootstrap.Bootstrap.init(Bootstrap.java:230)
at com.pmease.quickbuild.bootstrap.Bootstrap.main(Bootstrap.java:111)
at java.lang.reflect.Method.invoke(libgcj.so.7rh)
at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:244)
at java.lang.Thread.run(libgcj.so.7rh)
  • replies 7
  • views 4031
  • stars 0
#2
robinshen ADMIN ·
It seems that class "java.lang.ProcessBuilder" can not resolve some of its dependencies. This class is newly added in Java 1.5. Please edit file "<QuickBuild install dir>/conf/wrapper.conf" to make sure that the property "wrapper.java.command" points to JDK 1.5 or higher (the default value "java" means QuickBuild will look for java in the PATH environment variable). If it still does not work, please let me know which JVM you are using.
#3
brichard ·
Hi Robin,

Yes, I am using 1.4.2 on Linux. I installed JDK5, modified the wrapper.conf to hardwire the java path, and I still received those error messages.

wrapper.java.command=/home/pm_cntl/java/j2ee_sdk5/jdk
also tried
wrapper.java.command=/home/pm_cntl/java/j2ee_sdk5/jdk/bin
and
wrapper.java.command=/home/pm_cntl/java/j2ee_sdk5/jdk/bin/java

I do not want to change the $PATH for this account as many apps depend on this for building and it may break them. What I did to get it work was modify the agent.sh script to prepend the new JDK path to $PATH. Is there a way for me to get this to work using the wrapper.conf, however? That would be my desired method of deployment. Please advise.
#4
robinshen ADMIN ·
It is sufficient to modify "wrapper.java.command" in "conf/wrapper.conf". It is very odd that the "ProcessBuilder" class can not find its dependencies even if you've switched to use JDK5. Which Linux platform and JDK are you using?
#5
brichard ·
Correct, I would like to modify the wrapper.conf instead, but like I said it did not work using any of the three modifications in my previous thread.

What am I doing wrong? Here is my Linux version:

Linux 2.6.18-194.3.1.el5 #1 SMP Sun May 2 04:17:42 EDT 2010 x86_64 x86_64 x86_64

The JDK in my $PATH is 1.4.2 but my wrapper.conf is pointing (well, at least I am attempting to) to the JDK 1.5 I just downloaded.
#6
robinshen ADMIN ·
Please edit "conf/wrapper.conf" to uncomment the line "wrapper.debug=TRUE", restart the agent, and post content of "logs/console.log" here.
#7
brichard ·
The jdk is at the proper location:

$> ll /home/pm_cntl/java/j2ee_sdk5/jdk/bin/java
-rwxr-xr-x 1 uid gid 65076 Jul 14 09:35 /home/pm_cntl/java/j2ee_sdk5/jdk/bin/java*

-------------------------------

#********************************************************************
# Wrapper Java Properties
#********************************************************************
# Java Application
#wrapper.java.command=java
wrapper.java.command=/home/pm_cntl/java/j2ee_sdk5/jdk/bin

#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Enables Debug output from the Wrapper.
wrapper.debug=TRUE

$> ./agent.sh start
Starting QuickBuild Build Agent...wrapper | Spawning intermediate process...


wrapper | Advice:
wrapper | Usually when the Wrapper fails to start the JVM process, it is because
wrapper | of a problem with the value of the configured Java command. Currently:
wrapper | wrapper.java.command=/home/pm_cntl/java/j2ee_sdk5/jdk/bin
wrapper | Please make sure that the PATH or any other referenced environment
wrapper | variables are correctly defined for the current environment.
wrapper | ------------------------------------------------------------------------
wrapper |
wrapper | JVM was only running for 0 seconds leading to a failed restart count of 4.
wrapper | Waiting 5 seconds before launching another JVM.
wrapper | Command[0] : /home/pm_cntl/java/j2ee_sdk5/jdk/bin
wrapper | Command[1] : -Djava.awt.headless=true
wrapper | Command[2] : -Xverify:none
wrapper | Command[3] : -Xms64m
wrapper | Command[4] : -Xmx512m
wrapper | Command[5] : -Djava.library.path=.:/appl/toolbox/linux/sybase/IQ-15_1/lib64:/appl/toolbox/linux/sybase/OCS-15_0/lib:/home/wsuser/prod/lbin64:/home/wsuser/vendor/ims/prod/lbin64:/home/wsuser/prod/lbin:/home/wsuser/vendor/ims/prod/lbin:/appl/intexcmo/prod.lx-x86_64:/appl/pm/vendor/omniORB-4.1.4/lx-x86_64/lib
wrapper | Command[6] : -classpath
wrapper | Command[7] : wrapper.jar:../plugins/com.pmease.quickbuild.bootstrap:../plugins/com.pmease.quickbuild.bootstrap/lib/joda-time-1.6.jar:../plugins/com.pmease.quickbuild.bootstrap/lib/slf4j-api-1.5.8.jar:../plugins/com.pmease.quickbuild.bootstrap/lib/commons-logging-1.0.4.jar:../plugins/com.pmease.quickbuild.bootstrap/lib/javax.servlet_2.4.0.v200806031604.jar:../plugins/com.pmease.quickbuild.bootstrap/lib/hessian-3.2.1.jar:../plugins/com.pmease.quickbuild.bootstrap/lib/jul-to-slf4j-1.5.8.jar:../plugins/com.pmease.quickbuild.bootstrap/lib/commons-lang-2.4.jar:../plugins/com.pmease.quickbuild.bootstrap/lib/commons-codec-1.3.jar:../plugins/com.pmease.quickbuild.bootstrap/lib/slf4j-log4j12-1.5.8.jar:../plugins/com.pmease.quickbuild.bootstrap/lib/commons-io-1.4.jar:../plugins/com.pmease.quickbuild.bootstrap/lib/log4j-1.2.15.jar
wrapper | Command[8] : -Dwrapper.key=HzIzFKp-Dbm-WA2cSJTJKIMxAkK3CYCB
wrapper | Command[9] : -Dwrapper.port=32001
wrapper | Command[10] : -Dwrapper.jvm.port.min=31000
wrapper | Command[11] : -Dwrapper.jvm.port.max=31999
wrapper | Command[12] : -Dwrapper.debug=TRUE
wrapper | Command[13] : -Dwrapper.disable_console_input=TRUE
wrapper | Command[14] : -Dwrapper.pid=28834
wrapper | Command[15] : -Dwrapper.version=3.3.9-st
wrapper | Command[16] : -Dwrapper.native_library=wrapper
wrapper | Command[17] : -Dwrapper.service=TRUE
wrapper | Command[18] : -Dwrapper.cpu.timeout=3600
wrapper | Command[19] : -Dwrapper.jvmid=5
wrapper | Command[20] : org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper | Command[21] : com.pmease.quickbuild.bootstrap.Bootstrap
wrapper | Ping settings: wrapper.ping.interval=3600, wrapper.ping.interval.logged=1, wrapper.ping.timeout=0
wrapper | Launching a JVM...
wrapper | Signal trapped. Details:
wrapper | signal number=17 (SIGCHLD), source="unknown"
wrapper | Received SIGCHLD, checking JVM process status.
wrapper | JVM process exited with a code of 1, setting the wrapper exit code to 1.
wrapper | JVM exited while loading the application.
wrapper | Unable to start JVM: Permission denied (13)
wrapper |
wrapper | ------------------------------------------------------------------------
wrapper | Advice:
wrapper | Usually when the Wrapper fails to start the JVM process, it is because
wrapper | of a problem with the value of the configured Java command. Currently:
wrapper | wrapper.java.command=/home/pm_cntl/java/j2ee_sdk5/jdk/bin
wrapper | Please make sure that the PATH or any other referenced environment
wrapper | variables are correctly defined for the current environment.
wrapper | ------------------------------------------------------------------------
wrapper |
wrapper | JVM was only running for 0 seconds leading to a failed restart count of 5.
wrapper | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
wrapper | There may be a configuration problem: please check the logs.
wrapper | <-- Wrapper Stopped

devpmweb1:pm_cntl[181] vi console [prodpm U]
console.log console.log.1
devpmweb1:pm_cntl[181] vi console.log [prodpm U]
wrapper | Command[8] : -Dwrapper.key=HzIzFKp-Dbm-WA2cSJTJKIMxAkK3CYCB
wrapper | Command[9] : -Dwrapper.port=32001
wrapper | Command[10] : -Dwrapper.jvm.port.min=31000
wrapper | Command[11] : -Dwrapper.jvm.port.max=31999
wrapper | Command[12] : -Dwrapper.debug=TRUE
wrapper | Command[13] : -Dwrapper.disable_console_input=TRUE
wrapper | Command[14] : -Dwrapper.pid=28834
wrapper | Command[15] : -Dwrapper.version=3.3.9-st
wrapper | Command[16] : -Dwrapper.native_library=wrapper
wrapper | Command[17] : -Dwrapper.service=TRUE
wrapper | Command[18] : -Dwrapper.cpu.timeout=3600
wrapper | Command[19] : -Dwrapper.jvmid=5
wrapper | Command[20] : org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper | Command[21] : com.pmease.quickbuild.bootstrap.Bootstrap
wrapper | Ping settings: wrapper.ping.interval=3600, wrapper.ping.interval.logged=1, wrapper.ping.timeout=0
wrapper | Launching a JVM...
wrapper | Signal trapped. Details:
wrapper | signal number=17 (SIGCHLD), source="unknown"
wrapper | Received SIGCHLD, checking JVM process status.
wrapper | JVM process exited with a code of 1, setting the wrapper exit code to 1.
wrapper | JVM exited while loading the application.
wrapper | Unable to start JVM: Permission denied (13)
wrapper |
wrapper | ------------------------------------------------------------------------
wrapper | Advice:
wrapper | Usually when the Wrapper fails to start the JVM process, it is because
wrapper | of a problem with the value of the configured Java command. Currently:
wrapper | wrapper.java.command=/home/pm_cntl/java/j2ee_sdk5/jdk/bin
wrapper | Please make sure that the PATH or any other referenced environment
wrapper | variables are correctly defined for the current environment.
wrapper | ------------------------------------------------------------------------
wrapper |
wrapper | JVM was only running for 0 seconds leading to a failed restart count of 5.
wrapper | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
wrapper | There may be a configuration problem: please check the logs.
wrapper | <-- Wrapper Stopped
#8
robinshen ADMIN ·
The "wrapper.java.command" is incorrectly specified. It should be:
wrapper.java.command=/home/pm_cntl/java/j2ee_sdk5/jdk/bin/java
Log in to reply