VMware Cloud Community
SkumarAB
Contributor
Contributor

'SSL Exception:BIO Error'

I testing PTV of windows 2003 physical (Dell PE) Server using VMware vCenter Converter Standalone to ESXi 4.1.

please find the below complete error message.

FAILED: Unable to establish a secure communication channel between the vCenter Converter server and the remote machine at 172.16.4.10 on port 9089. Verify that the remote machine is running, the firewall is turned off, and the vCenter Converter agent service is running and listening on port 9089. Error details: 'SSL Exception:BIO Error'

Regards

Reply
0 Kudos
5 Replies
admin
Immortal
Immortal

Can you please attach the Convert log bundle to this thread so that we can see exactly what is happening?

Regards,

Graham Daly

Knowledge Champion

VMware Inc.

Reply
0 Kudos
SkumarAB
Contributor
Contributor

Hi Graham,

i have tryed to convert the same one more time it got failed again at the 47% and find the bleow logs for the same.

Regards,

Skumar

Reply
0 Kudos
admin
Immortal
Immortal

Thanks for supplying the logs.

Here are what I think the relevant excerpts from the logs are:

From vmware-converter-worker-2.log

GetManagedDiskName: Get virtual disk filebacking Test-CRM/Test-CRM.vmdk[#6] GetManagedDiskName: ticket has empty hostname, using hostname 172.16.3.47 from connection[#6] GetManagedDiskName: updating nfc port as 902[#6] GetManagedDiskName: get protocol as ha-nfc[#6] GetManagedDiskName: Get disklib file name as ha-nfc://[datastore1] Test-CRM/Test-CRM.vmdk@172.16.3.47:902!52 19 34 6c fd 1d b7 71-78 5b 62 63 8c b8 e3 08

SSLStreamImpl::BIORead (030b4858) failed: The specified network name is no longer available. SSLStreamImpl::DoClientHandshake (030b4858) SSL_connect failed with BIO Error[2010-09-22 15:56:13.829 01064 error 'App'] ConverterConnection: Keepalive thread failed with exception SSL Exception: BIO Error

SSLStreamImpl::BIORead (0311fd20) failed: The specified network name is no longer available. SSLStreamImpl::DoClientHandshake (0311fd20) SSL_connect failed with BIO Error[#6] TaskImpl has failed with Vmacore::Exception: SSL Exception: BIO Error

From vmware-converter-server-2.log

Found dangling SSL error: error:00000001:lib(0):func(0):reason(1)

Unexpected Exception: vmodl.fault.SystemError[2010-09-22 17:55:23.479 01472 info 'App'] -- ERROR -- Convert: vmodl.fault.SystemError(vmodl.fault.SystemError) { dynamicType = <unset>, faultCause = (vmodl.MethodFault) null, reason = "SSL Exception: BIO Error", msg = "", }

From vmware-converter-agent-2.log

stream is NULL - no read scheduled[2010-09-22 14:28:38.179 07032 error 'App'] SSLStreamImpl::DoServerHandshake (02fbe2a8) SSL_accept failed. Dumping SSL error queue:[2010-09-22 14:28:38.179 07032 error 'App'] error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate[2010-09-22 14:28:38.179 07032 error 'Ufa.HTTPService'] accept failure class Vmacore::Ssl::SSLException(SSL Exception: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate) on stream (null)

-


The errors are certainly pointing towards an issue along the SSL connection, but where exactly I am not a 100% sure.

I have been working with Converter for a few years now, but I have seen these messages before, at least not in this exact layout. Probably due to the newer messaging in Converter Standalone 4.3.

Can you provide more information in relation to this conversion attempt?

  1. What exactly is the source? From the logs I can see it is a virtual machine, but where is this virtual machine running? On an ESX 3.x server? On a ESX 4.x server?

  2. Where is converter being run from? Is it located inside the same LAN as the ESX server hosting the source virtual machine, or is it located somewhere else, like a in a WAN?

  3. If you turn on the specific VM, point converter at it as if it were a powered-on physical machine and try to convert it.....does it complete?

Regards,

Graham Daly

Knowledge Champion

VMware Inc.

Reply
0 Kudos
SkumarAB
Contributor
Contributor

Hi Graham,

The first point, source system is not Virtual machine it is in physical machine (Dell PE R410) & it is in diffrent subnet.

The second point, the ESX 4.1 server & the vSpere client & vCenter converter (Installaed in same system) are in the same LAN.

The third point, i have selected the powered-on physical machine for coverting.

Regards,

Skumar

Reply
0 Kudos
admin
Immortal
Immortal

Thanks for the clarification. After looking at the logs in closer detail, I can see that the source was in fact a physical machine. I must not have had enough coffee when I looked at them initially, and hence the mistake in thinking it was a virtual machine Smiley Happy

Can you make sure that all of the needed ports are opened between the converter server, the source machine and the destination ESX server? Especially port 902 between the source machine and the destination ESX server, as this is the port which is used for transferring the data from the source into the destination ESX.

You can view the relevant Converter documentation for a list of all of the ports that need to be open in order for a conversion to work.

Also, just to rule out any possible DNS issues, use IP addresses when specifying the source and destination machines.

Regards,

Graham Daly

Knowledge Champion

VMware Inc.

Reply
0 Kudos