zsootthey
Contributor
Contributor

Timeout issue during Create file from Resource

Hello!

I hope you can help me to find the solution related my issue.

Details:

     - I have a file (as a Resource) what I would like to copy form the vRO to the guest OS (Windows)

     - filesize is 400kb

     - error message: "java.net.SocketTimeoutException: connect timed out"

The code (I have bolded the mentioned section):

// Copy file to VM

System.log("Copying file to " + vm.name + " as " + targetFile);

var fileManager = guestOperationsManager.fileManager;

var attr = new VcGuestFileAttributes();

file = new File(tempLocalFile);

var uri = fileManager.initiateFileTransferToGuest(vm , guestAuth ,targetFile, attr, file.length, true);

   System.log("putFile URI is " + uri);

if (fileManager.putFile(tempLocalFile, uri)) {

    System.log("File successfully created on VM");

} else {

    System.log("Error creating file on VM");

}

The timeout is 30sec and I couldn't find any relevant information regarding where can I increase this.

My question is that where can I increase this "counter" OR how can I create a script or how can I modify this code for that the OUT will be VC:Task to vim3WaitTaskEnd and not to boolean?

Thanks in advance!

11 Replies
iiliev
VMware Employee
VMware Employee

Hi,

You cannot easily modify putFile(), it is a Java code inside vCenter plug-in.

What you can try is to modify the timeouts of Http client used by putFile() implementation. There are 2 properties

  com.vmware.vmo.plugin.vi4.guest.connect.ms  - connection timeout; default value is 30000 milliseconds

  com.vmware.vmo.plugin.vi4.guest.read.ms - socket timeout; default value is 15000 milliseconds

To modify these properties, you can add the new value to /etc/vco/app-server/vmo.properties, and restart vco-server service for change to take effect.

The format of the value in vmo.properties file should be something like

  property_name=value_in_milliseconds

eg. to set socket timeout to 2 minutes

  com.vmware.vmo.plugin.vi4.guest.read.ms=120000



0 Kudos
zsootthey
Contributor
Contributor

Hello,

     first of all, thanks the fast reply Smiley Happy

I have modified what you wrote. In the vmo.properties the mentioned rows was missing, so I have added with value 60000 (connect.ms) and 120000 (read.ms):

$358E196CD2730D96.jpg

Unfortunately the issue isn't solved:

$1FBB51209F0EA8EF.jpg

Additional informations:

we're using vRO 6, but we have vRO 7 as well. It is possible that version 7 is handling difference this URI section than the version 6?

0 Kudos
iiliev
VMware Employee
VMware Employee

Provided logs show the failure has happened 30 seconds after the call to putFile() so it seems the updated timeouts didn't have effect.

Could you tell me the exact versions/build numbers of vRO and vCenter plug-in? And also the Windows version on the machine you're trying to upload the file to?

0 Kudos
zsootthey
Contributor
Contributor

Environment details:

- vCenter 6.0.0 (bulid 3018524) with external PSC, each are running on W2012R2 Std

- vRO 6.0.3.0 (build 3000579) appliance

- Windows version on the VM where I would like to copy/upload the file is W2012R2 Std

I have found that log (unfortunatelly I couldn't insert it as .txt file):

2016-12-01 13:33:21.094+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WrappedJavaMethod] Invocation exception during 'public java.lang.Boolean com.vmware.vmo.plugin.vi4.model.VimGuestFileManager.putFile(java.lang.String,java.lang.String) throws java.io.IOException,java.net.URISyntaxException' call on object 'GuestFileManager<guestOperationsFileManager>'

java.lang.reflect.InvocationTargetException

    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:606)

    at ch.dunes.vso.sdk.WrappedJavaMethod.call(WrappedJavaMethod.java:152)

    at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:1473)

    at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:815)

    at org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:109)

    at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)

    at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)

    at org.mozilla.javascript.InterpretedFunction.exec(InterpretedFunction.java:120)

    at ch.dunes.scripting.server.script.MainScriptingObject.executeScript(MainScriptingObject.java:237)

    at ch.dunes.scripting.server.script.MainScriptingObject.executeScript(MainScriptingObject.java:223)

    at ch.dunes.workflow.engine.mbean.WorkflowScriptRunner.execute(WorkflowScriptRunner.java:191)

    at ch.dunes.workflow.engine.mbean.runner.WorkflowItemTaskRunner.execute(WorkflowItemTaskRunner.java:43)

    at ch.dunes.workflow.engine.mbean.runner.WorkflowItemTaskRunner.execute(WorkflowItemTaskRunner.java:24)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.executeItem(WorkflowHandler.java:955)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.requestElementExecution(WorkflowHandler.java:919)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.handleWorkflowTokenNextStep(WorkflowHandler.java:627)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.executeToken(WorkflowHandler.java:517)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.handleTokenExecution(WorkflowHandler.java:453)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.access$100(WorkflowHandler.java:104)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler$1.execute(WorkflowHandler.java:360)

    at ch.dunes.model.ar.AccessRightsTemplate.executeWithAccessRights(AccessRightsTemplate.java:16)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.doExecute(WorkflowHandler.java:356)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.run(WorkflowHandler.java:239)

    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

    at java.util.concurrent.FutureTask.run(FutureTask.java:262)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

    at java.lang.Thread.run(Thread.java:745)

Caused by: java.lang.RuntimeException: java.net.SocketTimeoutException: connect timed out

    at com.vmware.vmo.plugin.vi4.HttpUtil.putFile(HttpUtil.java:189)

    at com.vmware.vmo.plugin.vi4.HttpUtil.putFile(HttpUtil.java:152)

    at com.vmware.vmo.plugin.vi4.model.VimGuestFileManager.putFile(VimGuestFileManager.java:108)

    ... 31 more

Caused by: java.net.SocketTimeoutException: connect timed out

    at java.net.PlainSocketImpl.socketConnect(Native Method)

    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:344)

    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)

    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)

    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

    at java.net.Socket.connect(Socket.java:579)

    at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:637)

    at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524)

    at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)

    at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)

    at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)

    at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)

    at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)

    at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)

    at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)

    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)

    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)

    at com.vmware.vmo.plugin.vi4.HttpUtil.putFile(HttpUtil.java:178)

    ... 33 more

2016-12-01 13:33:21.096+0100 [WorkflowExecutorPool-Thread-11] INFO  {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [SCRIPTING_LOG] java.net.SocketTimeoutException: connect timed out (Workflow:MEF3 extract / Create the temp folder and copy the temp extractor into it (item8)#40)

2016-12-01 13:33:21.096+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowScriptRunner] Execute exception

org.mozilla.javascript.EvaluatorException: java.net.SocketTimeoutException: connect timed out (Workflow:MEF3 extract / Create the temp folder and copy the temp extractor into it (item8)#40)

    at org.mozilla.javascript.DefaultErrorReporter.runtimeError(DefaultErrorReporter.java:77)

    at org.mozilla.javascript.Context.reportRuntimeError(Context.java:913)

    at org.mozilla.javascript.Context.reportRuntimeError(Context.java:969)

    at ch.dunes.vso.sdk.WrappedJavaMethod.call(WrappedJavaMethod.java:177)

    at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:1473)

    at script(Workflow:MEF3 extract / Create the temp folder and copy the temp extractor into it (item8):40)

    at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:815)

    at org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:109)

    at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)

    at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)

    at org.mozilla.javascript.InterpretedFunction.exec(InterpretedFunction.java:120)

    at ch.dunes.scripting.server.script.MainScriptingObject.executeScript(MainScriptingObject.java:237)

    at ch.dunes.scripting.server.script.MainScriptingObject.executeScript(MainScriptingObject.java:223)

    at ch.dunes.workflow.engine.mbean.WorkflowScriptRunner.execute(WorkflowScriptRunner.java:191)

    at ch.dunes.workflow.engine.mbean.runner.WorkflowItemTaskRunner.execute(WorkflowItemTaskRunner.java:43)

    at ch.dunes.workflow.engine.mbean.runner.WorkflowItemTaskRunner.execute(WorkflowItemTaskRunner.java:24)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.executeItem(WorkflowHandler.java:955)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.requestElementExecution(WorkflowHandler.java:919)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.handleWorkflowTokenNextStep(WorkflowHandler.java:627)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.executeToken(WorkflowHandler.java:517)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.handleTokenExecution(WorkflowHandler.java:453)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.access$100(WorkflowHandler.java:104)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler$1.execute(WorkflowHandler.java:360)

    at ch.dunes.model.ar.AccessRightsTemplate.executeWithAccessRights(AccessRightsTemplate.java:16)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.doExecute(WorkflowHandler.java:356)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.run(WorkflowHandler.java:239)

    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

    at java.util.concurrent.FutureTask.run(FutureTask.java:262)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

    at java.lang.Thread.run(Thread.java:745)

2016-12-01 13:33:21.103+0100 [WorkflowExecutorPool-Thread-11] WARN  {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowItemTaskRunner] Script execution error on workflow : AUTOFast Configuration / 'Create the temp folder and copy the temp extractor into it'(item8) : java.net.SocketTimeoutException: connect timed out (Workflow:MEF3 extract / Create the temp folder and copy the temp extractor into it (item8)#40)

2016-12-01 13:33:21.103+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowItemTaskRunner] Script execution error stack

ch.dunes.workflow.engine.mbean.ScriptExecutionException: java.net.SocketTimeoutException: connect timed out (Workflow:MEF3 extract / Create the temp folder and copy the temp extractor into it (item8)#40)

    at ch.dunes.workflow.engine.mbean.WorkflowScriptRunner.execute(WorkflowScriptRunner.java:203)

    at ch.dunes.workflow.engine.mbean.runner.WorkflowItemTaskRunner.execute(WorkflowItemTaskRunner.java:43)

    at ch.dunes.workflow.engine.mbean.runner.WorkflowItemTaskRunner.execute(WorkflowItemTaskRunner.java:24)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.executeItem(WorkflowHandler.java:955)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.requestElementExecution(WorkflowHandler.java:919)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.handleWorkflowTokenNextStep(WorkflowHandler.java:627)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.executeToken(WorkflowHandler.java:517)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.handleTokenExecution(WorkflowHandler.java:453)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.access$100(WorkflowHandler.java:104)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler$1.execute(WorkflowHandler.java:360)

    at ch.dunes.model.ar.AccessRightsTemplate.executeWithAccessRights(AccessRightsTemplate.java:16)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.doExecute(WorkflowHandler.java:356)

    at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.run(WorkflowHandler.java:239)

    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

    at java.util.concurrent.FutureTask.run(FutureTask.java:262)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

    at java.lang.Thread.run(Thread.java:745)

2016-12-01 13:33:21.110+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] popCache

2016-12-01 13:33:21.112+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] popCache

2016-12-01 13:33:21.119+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] popCache

2016-12-01 13:33:21.121+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] popCache

2016-12-01 13:33:21.127+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] popCache

2016-12-01 13:33:21.130+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] popCache

2016-12-01 13:33:21.136+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] popCache

2016-12-01 13:33:21.138+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] popCache

2016-12-01 13:33:21.145+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] popCache

2016-12-01 13:33:21.145+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] popCache

2016-12-01 13:33:21.146+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] popCache

2016-12-01 13:33:21.154+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] Ending WorkflowHandler (1ee2cd5358b4dca70158ba5f75160080), with status[failed]

2016-12-01 13:33:21.154+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] Disconnect factory for WorkflowHandler (1ee2cd5358b4dca70158ba5f75160080), with clean session[true]

2016-12-01 13:33:21.154+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [VSOFactoryClient] Disconnect from server

2016-12-01 13:33:21.157+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] MainScriptingObject exited

2016-12-01 13:33:21.157+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [DynamicFunctionCaching] --contextReleased

2016-12-01 13:33:21.157+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [DynamicFunctionCaching] Cleaning compilation cache

2016-12-01 13:33:21.157+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [DynamicFunctionCaching]   : com.comp.com.autofast/getVMByName

2016-12-01 13:33:21.157+0100 [WorkflowExecutorPool-Thread-11] DEBUG {admin@admin.local:AUTOFast Configuration:1ee2cd5358b4dca70158ba5f75160080:16e95400-af00-4b28-b876-a8ec4ebab5c5:[16e95400-af00-4b28-b876-a8ec4ebab5c5]} [WorkflowHandler] Context exited

0 Kudos
iiliev
VMware Employee
VMware Employee

I just checked the source code and it appears that vCenter plug-in that ships with vRO 6.0.3 still has hard-coded timeouts.

The timeouts configurable via those 2 properties are supported in a later build of vCenter plug-in - the one that ships with vRO 6.0.5.

Not sure if it applicable to your case, but one option would be to deploy a new vRO 6.0.5 appliance, get the plug-in DAR file from there, and upload it to you existing 6.0.3 vRO. In theory, these vCenter plug-in versions should be compatible.

0 Kudos
zsootthey
Contributor
Contributor

!

Hello, again! Smiley Happy

Sorry for the late reply, but we didn't have enough time to pay attention about the issue.

But finally, we have...

So, I have downloaded the latest vRO 6.0.5 release, because it has a newer vCenter plugin (maybe 6.5, but I don't remember). I have deployed, changed the previously wrote settings and now the timeout is extendable. !But the issue did not solved.

The vRO and the mentioned VM is "sitting" in different Datacenter, but the same vCenter environment. Maybe the different Datacenter the main problem?

0 Kudos
qc4vmware
Virtuoso
Virtuoso

I have just found we seem to be having the same issue here.  6.0.5 orchestrator is failing but our 7.2 orchestrators seem to work.  I tried tweaking the timeouts but I am still not successful at connecting.  Any additional help would be appreciated if anyone got further with this.

0 Kudos
dvatov
VMware Employee
VMware Employee

The guest ops timeouts are part of the VC plugin released with vRO 6.0.5. Can you attach the server.log file with the failure and vmo.properties.

0 Kudos
qc4vmware
Virtuoso
Virtuoso

I'm pretty sure I am dealing with a port issue.  I just got this to fail on 7.2 host on a different network.  Maybe you can help me zero on on the ports that need to be open and if the communication is from vRO to ESX or vRO to vCenter?  I can't seem to totally decipher exactly how it all works.  It seems like it is over port 902 that the file transfer occurs but I'm not sure if that happens via the vCenter or the ESX host.  All the other guest operations work aside from those that are trying to transfer a file so I am wondering if for those maybe the connection is handed off to the ESX host whereas executing a command is handed off from vCenter to guest os.

The error on the 7.2 host is different than on the 6.0.5 host error is:

org.apache.http.conn.HttpHostConnectException: Connect to xx.xx.xx.xxx:443 [/xx.xx.xx.xxx] failed: Connection timed out (Connection timed out) (Workflow:Copy file from vCO to guest / Scriptable task (item1)#12)

Actually upon pasting this error in I noticed the ip address is actually an esx host.  I think I just answered my own question (at least partially).  So it looks like port 443 connectivity to the ESX host is required to connect.  Is this also where the file transfer occurs or is that on a different port?  Like 902?

bulatkaz
Contributor
Contributor

Hi qc4vmware,

We faced with the same issue, your post helped us to solve it, thank you!

So, I performed tests using iptables, 902 is not required, only 443.

carl1
Expert
Expert

Port 902 is used for console access (which you are not doing).  Port 443 is used to communicate with the host API (which you are doing).  The file is transferred to the host and the host gives it to the Guest OS via VMTools (aka: via the virtual mother board).

FYI, commands, being a small piece of data, actually go via vCenter but file transfers (which could be large) go directly to the host.

Carl L.