Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

When performing a Linux conversion you receive the error: Unable to query live Linux source machine (1009153)

Symptoms

  • Converter Standalone stops responding for 10 minutes while displaying Retrieving source machine information.
  • Converter Standalone displays this error message when you click Next on the Specify Source page:

    Unable to query the live Linux source machine


  • The Converter GUI log file contains an error similar to:

    error 'wizardController'] Cannot query source HW info: converter.fault.SysinfoQueryLinuxFault

  • The Converter worker log contains an error similar to:

    Sysinfo Query failed with error Error executing ssh client for SysinfoQuery: Command not found or is not executable: C:\Program Files\VMware\VMware vCenter Converter Standalone\plink.exe

  • The Converter agent log files contain an error similar to:

    Sysinfo Query failed with error [Converter Agent SysinfoQuery] execution of vmware-sysinfo failed; return code: 126; result: bash: ./vmware-sysinfo-lin32.sh: /bin/sh: bad interpreter: Permission denied

Purpose

This article describes the process of troubleshooting an issue where you might be unable to perform a P2V conversion of a powered-on Linux source machine. You can follow these steps to eliminate a specific cause for your problem by verifying that your login environment does not include an incompatible command.

Resolution

You must perform both troubleshooting steps listed below. Each step provides instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution.

Note: If you are using VMware vCenter Converter standalone 4.3, ensure that VMware vCenter Converter 4.0.1 is removed completely from the system. If you have both copies installed on the same system, you may experience this issue. Also, make sure that UAC is disabled on the system so plink.exe may be executed correctly.

If you perform a corrective action in any of the following steps, attempt converting the Linux source operating system again.
  1. Verify that the Linux source operating system is accepting ssh traffic and that the user name and password used in Converter are correct and result in a functional shell prompt.

    1. From the Linux source operating system, open a shell prompt, type ssh localhost, and press Enter. Log in using the same user name and password used in the Conversion wizard.
      If this does not result in a successful login, correct the problem.

      Note
      : For more information on opening a shell prompt, see Opening a command or shell prompt (1003892) .

    2. From the computer running Converter, open a command prompt, run telnet xxxx nn, where xxxx is replaced by the host name or IP address of the Linux source operating system and nn is replaced by the port being used for SSH.
      If this does not result in information being displayed, a firewall might be preventing the computer running Converter Standalone from connecting to the Linux source operating system. Correct this problem.

  2. Confirm that the .bashrc file of the user name being used for authentication does not contain an echo command.

    If authenticating as root, use a text editor to edit /root/.bashrc. If authenticating as a different user, use a text editor to edit /home/user name/.bashrc, where user name is replaced by the user name being used for authentication.

    If a line in the file begins with
    echo, either delete it or change it to #echo.

  3. Ensure that the /tmp directory on the source machine is writable. If it is not, then the Converter agent will not be able to write to it and will fail. To check the permissions on the /tmp directory:

    1. Login as root and run this command:

      mount | grep /tmp

      The output appears similar to:
      /dev/hda2 on /tmp type ext3 (rw,noexec,nosuid,nodev)

    2. If you see noexec permissions or nosuid permissions, temporarily reset the permissions with the command:

      mount -t ext3 /dev/hdaX /tmp -o rw,exec,nodev
      OR
      mount -o remount,exec /tmp 

      Note: Replace /dev/hdaX with your device name.

  4. Ensure that user is able to log in to the linux shell, Verify that the user is assigned /bin/bash instead of /sbin/nologin in the /etc/passwd file.
    For example: root:x:0:0:root:/root:/bin/bash

Additional Information

Converter Standalone uses the SFTP protocol to copy files on the source Linux system, and SFTP fails in this attempt if there is an echo statement in the .bashrc file. This behavior can be reproduced using any standard SFTP client.

Tags

loss-of-connectivity cannot-connect-linux-source

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 70 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 70 Ratings
Actions
KB: