When we try to connect to Source machine having Linux from vCenter Converter Standalone, it gives below error:
Unable to query the live Linux source machine
or
Unable to query the live source machine
converter-gui.log
2024-11-25T12:21:06.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)
2024-11-25T12:21:06.188+05:30 error converter-gui[05424] [Originator@6876 sub=wizardController] Cannot query source HW info: Fault cause: converter.fault.SysinfoQueryBadThumbprintFault
-->
2024-11-25T12:21:06.192+05:30 info converter-gui[03680] [Originator@6876 sub=SourceSelect] Failed reading SSL thumbprint for host <source_linux_VM_IP> from registry.
2024-11-25T12:21:14.110+05:30 info converter-gui[00252] [Originator@6876 sub=ThreadPool] Spawning additional worker - allocated: 10, idle: 3
2024-11-25T12:21:14.110+05:30 info converter-gui[06804] [Originator@6876 sub=ThreadPool] Entering worker thread loop
2024-11-25T12:23:02.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)
2024-11-25T12:23:02.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:
2024-11-25T12:21:06.186+05:30 warning vmware-converter-worker[02428] [Originator@6876 sub=Default] Converter::Util::SysCommandWrapper::LogResult: Command return code: 249
2024-11-25T12:21:06.186+05:30 warning vmware-converter-worker[02428] [Originator@6876 sub=Default] Converter::Util::SysCommandWrapper::LogResult: Command stderr:
--> e3:be:ad:1e:8f:5c:17:c8:81:88:6b:58:56:4c:42:66
-->
2024-11-25T12:21:06.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: e3:be:ad:1e:8f:5c:17:c8:81:88:
6b:58:56:4c:42:66
-->
2024-11-25T12:21:06.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: e3:be:ad:1e:8f:5c:17:c8:81:88:6b:58:56:4c:42:66
2024-11-25T12:21:06.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: e3:be:ad:1e:8f:5c:17:c8:81:88:6b:58:56:4c:42:66
2024-11-25T12:23:02.510+05:30 error vmware-converter-worker[05396] [Originator@6876 sub=Default] No disks for volume with id '/dev/rhel/var' and label ''
VMware vCenter Converter Standalone 6.6
VMware vCenter Converter Standalone 6.4
VMware vCenter Converter Standalone 6.3
This thumbprint error is reported When converter connects to a new source, it does not know anything about its thumbprint, emptyThumbprint in the logs reported due to unavailability of thumbprint. Since it does not match the host thumbprint, an error is generated and the host thumbprint is returned.
Issue is with below error:
No disks for volume with id '/dev/rhel/var' and label ''
This is known issue with standalone converter which is documented in 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.
To identify multiple mountpoints for same device,
No disks for volume with id '/dev/rhel/var' and label ''
Above error will convey that which device we need to consider for multiple mountpoints.
review vmware-converter-worker.log file for multiple mountpoint details.
--> <volume mountPoint="/var" blockSizeInBytes="4096" capacityInBlocks="5230080" blocksFree="4493612" blocksUsed="736468" devicePath="/dev/rhel/var" fileSystemType="xfs" isBootVolume="false" label="">
--> <volume mountPoint="/opt/sentinelone/rpm_mount" blockSizeInBytes="4096" capacityInBlocks="5230080" blocksFree="4493612" blocksUsed="736468" devicePath="/dev/rhel/var" fileSystemType="xfs" isBootVolume="false" label="">
Here, for dev/rhel/var, we had 2 mountpoints /var and /opt/sentinelone/rpm_mount.
As per your configuration, names and devices can be different.
To resolve this issue, unmount the one which is used for other services. e.g. here is /opt/sentinelone/rpm_mount.
Once unmounted view /proc/mount , you can also grep this file with mountpoint which we removed to confirm it is successfully unmounted.
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 or points