Unable to query the live Linux source machine.

[itoffice1]

Unable to query the live Linux source machine.

Trying to convert a physical fedora box to a virtual machine

These are my logs

2023-08-15T08:58:11.729Z info vmware-converter-agent[15760] [Originator@6876 sub=Default] Module: C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone\ssleay32.dll The file is signed and the signature was verified. (1 out of 1) dynamic base;nx compat
2023-08-15T08:58:11.733Z info vmware-converter-agent[15760] [Originator@6876 sub=Default] [serviceWin32,1348] Panic message will be logged now...
2023-08-15T08:58:12.575Z info vmware-converter-agent[08868] [Originator@6876 sub=ThreadPool] Spawning additional worker - allocated: 6, idle: 1
2023-08-15T08:58:12.575Z info vmware-converter-agent[08420] [Originator@6876 sub=ThreadPool] Entering worker thread loop
2023-08-15T08:58:13.580Z info vmware-converter-agent[09048] [Originator@6876 sub=ThreadPool] Spawning additional worker - allocated: 7, idle: 2
2023-08-15T08:58:13.580Z info vmware-converter-agent[02336] [Originator@6876 sub=ThreadPool] Entering worker thread loop
2023-08-15T08:58:14.584Z info vmware-converter-agent[15736] [Originator@6876 sub=ThreadPool] Spawning additional worker - allocated: 8, idle: 3
2023-08-15T08:58:14.584Z info vmware-converter-agent[17260] [Originator@6876 sub=ThreadPool] Entering worker thread loop

2023-08-15T09:26:15.684Z error vmware-converter-worker[20068] [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 2e:2b:f1:7e:20:0b:1b:f4:09:56:4a:46:6f:cb:09:d8 root@172.16.255.20 uname -m" received error code (1) with result: FATAL ERROR: Network error: Software caused connection abort
-->
2023-08-15T09:26:15.684Z error vmware-converter-worker[20068] [Originator@6876 sub=Default] [Converter Agent SysinfoQuery] received an error code (1) from the ssh client that will be handled later
2023-08-15T09:26:15.684Z error vmware-converter-worker[20068] [Originator@6876 sub=Default] [Converter Agent SysinfoQuery] could not determine if the source system was 32 or 64 bit; return code: 1; result: FATAL ERROR: Network error: Software caused connection abort
-->
2023-08-15T09:26:15.684Z error vmware-converter-worker[20068] [Originator@6876 sub=Default] Sysinfo Query failed with error [Converter Agent SysinfoQuery] could not determine if the source system was 32 or 64 bit; return code: 1; result: FATAL ERROR: Network error: Software caused connection abort
-->

[ptarnawski]

Hi @itoffice1 

The error message "FATAL ERROR: Network error: Software caused connection abort" indicates that the SSH connection to the source machine was interrupted. This can happen for a number of reasons, such as:

• The source machine is not powered on.
• The source machine is not configured to allow SSH connections.
• The SSH service on the source machine is not running.
• The firewall on the source machine is blocking SSH traffic.
• The network connection between the source machine and the converter is not working properly.

1. Check Network Connectivity:

   • Ensure that the physical Fedora machine and the VMware vCenter Converter Standalone server have proper network connectivity. You should be able to ping the source machine from the converter server and vice versa.

2. Firewall Configuration:

   • Check the firewall settings on both the source machine (Fedora) and the converter server. Make sure that the necessary ports (e.g., SSH port 22) are open for communication between the two machines.

3. SSH Configuration:

   • Verify that SSH is enabled and properly configured on the Fedora machine. Ensure that the SSH service is running and that you can SSH into the Fedora machine from another machine to confirm that SSH is functioning correctly.

4. SSH Key Authentication:

   • It appears that SSH key authentication is being used in your conversion process. Ensure that the SSH key pair used for authentication is correct and that the private key is available and accessible to the converter server.

5. Check for IP Address Changes:

   • Ensure that the IP address of the source Fedora machine (172.16.255.20 in this case) has not changed during the conversion process. The converter server relies on this IP address to connect to the source machine.

6. Converter Software Version:

   • Make sure that you are using a compatible version of VMware vCenter Converter Standalone for both the source and target systems. It's possible that an outdated or incompatible version could lead to connectivity issues.

7. Logs on the Source Machine:

   • Check the logs on the Fedora machine (if accessible) to see if there are any additional error messages or clues about why the SSH connection is failing.

8. Check for Resource Constraints:

   • Ensure that the source Fedora machine has enough resources (CPU, memory, disk space) available to handle the conversion process. Resource constraints could lead to connection failures.

9. Firewall on the Converter Server:

   • Check the firewall settings on the VMware vCenter Converter Standalone server itself. Make sure that it allows outgoing SSH connections to the source machine.

10. Try SSH Manually:

    • Attempt to SSH manually from the converter server to the Fedora machine using the same command that is failing in the logs. This will help you diagnose any SSH-specific issues.

11. Update Converter and Dependencies:

    • Ensure that VMware vCenter Converter Standalone and its dependencies are up to date. Sometimes, updating the software can resolve compatibility issues.