Unable to query the live Linux source machine during P2V conversion of Linux machines using vCenter Converter Standalone
search cancel

Unable to query the live Linux source machine during P2V conversion of Linux machines using vCenter Converter Standalone

book

Article ID: 382838

calendar_today

Updated On:

Products

Converter

Issue/Introduction

When we try to connect to the Source machine having Linux from vCenter Converter Standalone, it gives the following error: 
Unable to query the live Linux source machine 
or 
Unable to query the live source machine

converter-gui.log

YYYY-MM-DDTHH:MM:SS.188+05:30 warning converter-gui[05424] [Originator@6876 sub=vmomi.soapStub[1]] SOAP request returned HTTP failure; <<io_obj p:0x0aa4a938, h:1884, <pipe '\\.\pipe\vmware-converter-server-soap'>, <pipe '\\.\pipe\vmware-converter-server-soap'>>, /converter/sdk>, method: query; code: 500(Internal Server Error)
YYYY-MM-DDTHH:MM:SS.188+05:30 error converter-gui[05424] [Originator@6876 sub=wizardController] Cannot query source HW info: Fault cause: converter.fault.SysinfoQueryBadThumbprintFault
-->
YYYY-MM-DDTHH:MM:SS.192+05:30 info converter-gui[03680] [Originator@6876 sub=SourceSelect] Failed reading SSL thumbprint for host <Source_Linux_VM_IP> from registry.
YYYY-MM-DDTHH:MM:SS.110+05:30 info converter-gui[00252] [Originator@6876 sub=ThreadPool] Spawning additional worker - allocated: 10, idle: 3
YYYY-MM-DDTHH:MM:SS.110+05:30 info converter-gui[06804] [Originator@6876 sub=ThreadPool] Entering worker thread loop
YYYY-MM-DDTHH:MM:SS.511+05:30 warning converter-gui[05424] [Originator@6876 sub=vmomi.soapStub[1]] SOAP request returned HTTP failure; <<io_obj p:0x0d71d400, h:1988, <pipe '\\.\pipe\vmware-converter-server-soap'>, <pipe '\\.\pipe\vmware-converter-server-soap'>>, /converter/sdk>, method: query; code: 500(Internal Server Error)
YYYY-MM-DDTHH:MM:SS.511+05:30 error converter-gui[05424] [Originator@6876 sub=wizardController] Cannot query source HW info: Fault cause: converter.fault.SysinfoQueryFault


vmware-converter-worker.log:

YYYY-MM-DDTHH:MM:SS.186+05:30 warning vmware-converter-worker[02428] [Originator@6876 sub=Default] Converter::Util::SysCommandWrapper::LogResult: Command return code: 249
YYYY-MM-DDTHH:MM:SS.186+05:30 warning vmware-converter-worker[02428] [Originator@6876 sub=Default] Converter::Util::SysCommandWrapper::LogResult: Command stderr:
--> <host_thumbprint>
-->
YYYY-MM-DDTHH:MM:SS.186+05:30 error vmware-converter-worker[02428] [Originator@6876 sub=Default] [Converter Agent SysinfoQuery] while trying to execute "C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone\plink.exe -noprompt -stdin-pass-and-key <ConverterPrivateKeyEnd> -P 22 -thumbprint <emptyThumbprint> root@<Source_Linux_VM_IP> file -L /sbin/init" received error code (249) with result:<host_thumbprint>
-->
YYYY-MM-DDTHH:MM:SS.186+05:30 error vmware-converter-worker[02428] [Originator@6876 sub=Default] [Converter Agent SysinfoQuery] ssh connection to host <Source_Linux_VM_IP> failed because the host thumbprint was different: client: <emptyThumbprint>, host:<host_thumbprint>
YYYY-MM-DDTHH:MM:SS.186+05:30 error vmware-converter-worker[02428] [Originator@6876 sub=Default] Sysinfo Query failed with error [Converter Agent SysinfoQuery] ssh connection to host <Source_Linux_VM_IP> failed because the host thumbprint was different: client: <emptyThumbprint>, host: <host_thumbprint>
.
.
.
YYYY-MM-DDTHH:MM:SS.510+05:30 error vmware-converter-worker[05396] [Originator@6876 sub=Default] No disks for volume with id '/dev/rhel/<device_name>' and label ''

 

Environment

VMware vCenter Converter Standalone 6.6 
VMware vCenter Converter Standalone 6.4 
VMware vCenter Converter Standalone 6.3

Cause

This thumbprint error is reported when the converter connects to a new source, it does not know anything about its thumbprint. emptyThumbprint in the logs reported due to the unavailability of the thumbprint. Since it does not match the host thumbprint, an error is generated, and the host thumbprint is returned. 

The issue is with below error: 
No disks for volume with id '/dev/rhel/<device_name>' and label 

This is a known issue with the standalone converter, which is also documented in the vCenter Converter Standalone 6.6 release notes.

When the source machine has more than one mount point, you receive the following error message: "Unable to query the live Linux source machine"

Converter expects each source file system to have a unique mount point. Having more than one mount point per file system breaks the analysis of volumes and partitions.

Resolution

To resolve the issue, unmount the additional mountpoints for a disk device, and make sure it only has one mountpoint in the source Linux file system.

  1. Steps to identify multiple mountpoints for a disk device:
    • The error messages " No disks for volume with id '/dev/rhel/<device_name>' and label " in vmware-converter-worker.log indicates it  is the /dev/rhel/<device_name> device has  the multiple mountpoints issue.

      For example, this error message indicates that the disk device is '/dev/rhel/var':
      No disks for volume with id '/dev/rhel/var' and label 

    • The following messages in the same log file contain the mountpoint details for the disk device.

      -->   <volume mountPoint="<mountpoint_1>" blockSizeInBytes="####" capacityInBlocks="####" blocksFree="####" blocksUsed="####" devicePath="/dev/rhel/<device_name>" fileSystemType="xfs" isBootVolume="false" label="">
      -->   <volume mountPoint="<mountpoint_2>" blockSizeInBytes="####" capacityInBlocks="####" blocksFree="####" blocksUsed="####" devicePath="/dev/rhel/<device_name>" fileSystemType="xfs" isBootVolume="false" label="">

      For example, the disk '/dev/rhel/var' has two mountpoints, /var and /opt/abc/rpm_mount:

      -->   <volume mountPoint="/var" blockSizeInBytes="4096" capacityInBlocks="5230080" blocksFree="4493612" blocksUsed="736468" devicePath="/dev/rhel/var" fileSystemType="xfs" isBootVolume="false" label="">
      -->   <volume mountPoint="/opt/abc/rpm_mount" blockSizeInBytes="4096" capacityInBlocks="5230080" blocksFree="4493612" blocksUsed="736468" devicePath="/dev/rhel/var" fileSystemType="xfs" isBootVolume="false" label="">

    • To see all disk space information and help identify disks with 2 mount points

# df -ah

  1. Unmount additional mountpoint.
    # umount <mountpoint>

    In the above sample, unmount the mountpoint /opt/abc/rpm_mount which is used for other services:
    # umount /opt/abc/rpm_mount

  2. Check the /proc/mount to verify the disk device has only one mount point.
    # cat /proc/mount

Note:

  • The disk device name and mountpoint may be different in various system.

  • Warning: Do not unmount the root (/) or boot (/boot) mount points. If any of them are mounted more than once, unmount the other mount point/s 

Powered by Wolken Software