This is a common faban problem that many new users face (actually even old users when setting up a new test rig also face). It usually happens because : a) The master cannot 'rsh/ssh' to the agent system without password b) The user has specified 'localhost' as the name of the system (not true in your case) c) There is a mismatch between the hostname seen by Java and what you think it is d) There is a genuine network issue between the two systems
Since you say it is sporadic, I suggest you ignore it. All of us run into this sporadic issue. Just start another run. Shanti 2010/6/5 Bruno Guimarães Sousa <[email protected]> > Hi ! > Benchmarks are running very unstable. Sometimes it runs without errors. And > sometimes (most of it) it runs with this problem: > 10:56:06 WARNING Retry connecting to [email protected], count 1. > 10:56:16 WARNING Retry connecting to [email protected], count 2. > 10:56:26 WARNING Retry connecting to [email protected], count 3. > 10:56:36 WARNING Retry connecting to [email protected], count 4. > 10:56:46 WARNING Retry connecting to [email protected], count 5. > 10:56:56 WARNING Retry connecting to [email protected], count 6. > 10:57:06 WARNING Retry connecting to [email protected], count 7. > 10:57:16 WARNING Retry connecting to [email protected], count 8. > 10:57:26 WARNING Retry connecting to [email protected], count 9. > 10:57:36 WARNING Retry connecting to [email protected], count 10. > 10:57:36 SEVERE Could not connect to [email protected] 10:57:36 > SEVERE CmdService setup failed. Exiting > Faban master tries to start the agent in a SUT computer. The agent log from > the computer 192.168.1.12 prints: > java.net.ConnectException: Connection refused > at java.net.PlainSocketImpl.socketConnect(Native Method) > at > java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:310) > at > java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:176) > at > java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:163) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384) > at java.net.Socket.connect(Socket.java:546) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:140) > at > org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:125) > at > org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) > at > org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) > at > org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) > at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) > at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) > at > com.sun.faban.harness.agent.Download.downloadDir(Download.java:122) > at com.sun.faban.harness.agent.Download.download(Download.java:109) > at > com.sun.faban.harness.agent.Download.loadBenchmark(Download.java:60) > at > com.sun.faban.harness.agent.AgentBootstrap.startAgents(AgentBootstrap.java:331) > at > com.sun.faban.harness.agent.AgentBootstrap.main(AgentBootstrap.java:97) > > Couldn't get rid of this prob yet :( > Tried restarting tomcat and faban master but nothing changed. > > -- > Bruno Guimarães Sousa > www.ifba.edu.br > PONTONET - DGTI - IFBA > Ciência da Computação UFBA > Registered Linux user #465914 >
