vim.fault.NotAuthenticated at 26% using VMWare converter 6.1.1

[dke4bs]

Hello,

I am having an issue doing a V2V conversion of a Linux machine. The source is located on local storage of an ESX 4.1.0 build 260247 and the destionation system is an ESXi 6.0.0 build 2494585 (using vCenter) and local SSD storage.

I did the same conversion in a test environment (which is identical) last week, without any problem, but at the live environment it keeps failing at 26% with the same error.

Since it is 2 times on the same source disk, I am assuming it is not a network issue, but rather a problem of the source disk. But I attached the logfiles for you to investigate.

The source machine is shut down before conversion, and the second time I tried I even rebooted the whole source ESX just to be sure... but without success.The source ESX only has 25 GB free, but I have read 200 MB should even be enough?

Could you please assist?

Thanks a million!

Kind regards

Davy

[POCEH]

Hmm... it's not clear what's happens, could be a network drop:

2016-03-08T06:39:21.349+01:00 error vmware-converter-worker[54560] [Originator@6876 sub=task-4] VimConnectionHelper Keepalive to host 192.168.45.40 failed: vim.fault.NotAuthenticated

2016-03-08T06:39:21.350+01:00 error vmware-converter-worker[54560] [Originator@6876 sub=task-4] VimConnectionStore failed on keepalive for one connection

2016-03-08T06:39:21.350+01:00 info vmware-converter-worker[43744] [Originator@6876 sub=task-4] Reusing existing VIM connection to 192.168.45.40

2016-03-08T06:39:21.386+01:00 error vmware-converter-worker[43744] [Originator@6876 sub=task-4] managed to managed disk clone failed: vim.fault.NotAuthenticated

2016-03-08T06:39:21.388+01:00 error vmware-converter-worker[43744] [Originator@6876 sub=task-4] Disk clone failed with error vim.fault.NotAuthenticated

2016-03-08T06:39:21.389+01:00 error vmware-converter-worker[43744] [Originator@6876 sub=task-4] TaskImpl has failed with MethodFault::Exception: converter.fault.CloneFault

Could you try to turn off SSL from converter-worker.xml <nfc><useSsl> to false, then restart the service and try again?

HTH

[dke4bs]

Thanks for the quick answer! I will most certainly try to do that. The only disadvantage is that we only have a few hours of downtime we can afford a week. So I have to wait untill next tuesday to try that.

But one more question. I already tried to do the conversion twice for this machine, and it fails on the exact same virtual disk as the first time and at the exact same percentage. So could it be something with the source disk?

And since you post network issues of the destination, is it a good idea to bypass the vcenter and set the esxi as the destination machine instead of the vcenter server?

Thanks again!

[POCEH]

Never see before such kind of error - can't say what exactly happens...

You can avoid VC because after version 4.x (if I'm right) the ESX should not be contacted directly, the only one possibility is to detach ESX from VC before conversion...

HTH

[dke4bs]

Did a new conversion today. Changed UseSSL to false and also set readTimeoutMs to 1200000.

Also used converter 5.5 instead of 6.

The result was a bit satisfying, because the conversion got a lot further, but didn't complete.

I see that the worker xml also has other settings in the NFC section, but they are commented:

   <acceptTimeoutMs>-1</acceptTimeoutMs>

   <requestTimeoutMs>-1</requestTimeoutMs>

   <readTimeoutMs>-1</readTimeoutMs>

   <writeTimeoutMs>-1</writeTimeoutMs>

   <fssrvrReqTimeoutMs>-1</fssrvrReqTimeoutMs>

   <fssrvrWriteTimeoutMs>-1</fssrvrWriteTimeoutMs>

   <maxRecvRetries>-1</maxRecvRetries>

The new plan is to do a new conversion like this morning, but set the readTimeoutMs to let's say 6000000.

But my question is: is it usefull to make adjustments to the commented values as well?

Attached logs and XML for more information.

[dke4bs · Accepted solution]

I finally made it through the conversion. I dont't know what exactly did the trick, but I changed the followin things to make it through

• I used converter 55 (although I don't think that is the issue)
• I changed the following settings in the converter-worker.xml
  • useSSL: false
  • readTimeoutMs: 999999999
  • writeTimeoutMs: 999999999

Thanks for everything!!!