Troubleshoot the load generator Linux installation

This section describes troubleshooting tasks relating to the setup of the Linux load generator.

Environment variables were not set correctly in the system-wide startup scripts

To enable the load generator to run, the system-wide startup scripts must be modified to set specific environment variables. The required modifications to the startup scripts are made by the Load Generator Setup wizard. If the startup scripts were not correctly modified during the setup of the load generator, you can manually make the required changes to the startup scripts as described below. The required changes differ slightly between C shell users, and Bourne and Korn shell users.

  • Manually modifying the startup scripts for C shell users

    During the load generator installation process, the Setup wizard creates the env.csh script. This script includes the commands to set the required environment variables for C shell users. A sample env.csh script is shown below.

    setenv PRODUCT_DIR <Load Generator installation directory>
    setenv M_LROOT ${PRODUCT_DIR}
       if ( ! $?PATH ) then
          setenv PATH ""
       endif
    setenv PATH ${M_LROOT}/bin:${PATH}"

    Add the following line to the /etc/csh.cshrc or ~/.cshrc startup script to execute the env.csh script during the shell startup:

    source <Load Generator installation directory>/env.csh

    For example:

    source /opt/OT/OT_LoadGenerator/env.csh

    The effect of making the above modification to the startup script is similar to the modifications that are made by the Setup wizard. A sample of the modifications that the Setup wizard makes to the /etc/csh.cshrc startup script is shown below:

    # New environment setting added by OT_LoadGenerator on Wed Jan 30 16:20:10 IST 2020 2.
    # The unmodified version of this file is saved in /etc/.login1557000131.
    # Do NOT modify these lines; they are used to uninstall.
    setenv PRODUCT_DIR "/opt/OT/OT_LoadGenerator"
    # End comments by InstallAnywhere on Wed Jan 30 16:20:10 IST 2020 2.
    # New environment setting added by OT_LoadGenerator on Wed Jan 30 16:20:10 IST 2020 5.
    # The unmodified version of this file is saved in /etc/.login1557000131.
    # Do NOT modify these lines; they are used to uninstall.
    setenv M_LROOT "/opt/OT/OT_LoadGenerator"
    # End comments by InstallAnywhere on Wed Jan 30 16:20:10 IST 2020 5.
    # New environment setting added by OT_LoadGenerator on Wed Jan 30 16:20:10 IST 2020 8.
    # The unmodified version of this file is saved in /etc/.login1557000131.
    # Do NOT modify these lines; they are used to uninstall.
    if ( ! $?PATH ) then
    setenv PATH ""
    endif
    setenv PATH "/opt/OT/OT_LoadGenerator/bin:${PATH}"
    # End comments by InstallAnywhere on Wed Jan 30 16:20:10 IST 2020 8.

  • Manually modifying the startup scripts for Bourne and Korn shell users

    During the load generator installation, the Setup wizard creates the env.sh script. This script includes commands to set the required environment variables for Bourne shell and Korn shell users.

    Add the following line to the /etc/profile or ~/.profile startup script to execute the env.sh script during the shell startup:

    source <Load Generator installation directory>/env.sh

    For example:

    source /opt/OT/OT_LoadGenerator/env.sh

    The effect of making the above modification to the startup script is similar to the modifications that are made by the Setup wizard. A sample of the modifications that the Setup wizard makes to the /etc/profile startup script is shown below:

    # New environment setting added by OT_LoadGenerator on Fri Jan 16 11:14:24 IST 2020 1.
    # The unmodified version of this file is saved in /etc/profile1806316421.
    # Do NOT modify these lines; they are used to uninstall.
    PRODUCT_DIR=/opt/OT/OT_LoadGenerator
    export PRODUCT_DIR
    # End comments by InstallAnywhere on Fri Jan 16 11:14:24 IST 2020 1.
    # New environment setting added by OT_LoadGenerator on Fri Jan 16 11:14:24 IST 2020 4.
    # The unmodified version of this file is saved in /etc/profile1806316421.
    # Do NOT modify these lines; they are used to uninstall.
    M_LROOT=/opt/OT/OT_LoadGenerator
    export M_LROOT
    # End comments by InstallAnywhere on Fri Jan 16 11:14:24 IST 2020 4.
    # New environment setting added by OT_LoadGenerator on Fri Jan 16 11:14:24 IST 2020 7.
    # The unmodified version of this file is saved in /etc/profile1806316421.
    # Do NOT modify these lines; they are used to uninstall.
    PATH="/opt/OT/OT_LoadGenerator/bin:${PATH}"
    export PATH
    # End comments by InstallAnywhere on Fri Jan 16 11:14:24 IST 2020 7. Settings #PATH=${M_LROOT}/bin:$PATH; export PATH

Back to top

Error when installing the load generator on a Linux platform

When you use the source installer.sh command to install the latest load generator version on a Linux machine on which a load generator was previously installed, you may receive the following error message:

"An error occurred while trying to manage the selected instance."

Solution:

  1. Open the registry file /var/.com.zerog.registry.xml and locate the element "product" with attribute "name"="OT_LoadGenerator".

    For example:

    <product name="OT_LoadGenerator" id="77f695c1-1f0c-11b2-883d-c486a85f6555" version="20.00.0.0" copyright="2019" info_url="http://www.anyco.com" support_url="http://www.anyco.com" location="/opt/OT/OT_LoadGenerator" last_modified="2019-11-21 13:12:14">

  2. Record the value of the "location" attribute.
  3. Remove the entire directory that is referred to by the "location" attribute.
  4. Delete the registry file /var/.com.zerog.registry.xml.
  5. Rerun the source installer.sh command.

Back to top

Environment variables are not unset after uninstalling the load generator

When you uninstalled the Linux load generator, the Setup wizard might not have unset the load generator environment variables (M_LROOT, PRODUCT_DIR, and PATH) for the current shell. To unset the environment variables, close the current shell session and invoke a new one, or manually unset the variables as described below:

  • To unset the M_LROOT and PRODUCT_DIR variables:

    • [bash shells] Use the unset command.
    • [csh shells] Use the unsetenv command.

  • To update the PATH variable to exclude the load generator binary directory, type:

    • [bash shells] PATH=<required list of paths>; export PATH
    • [csh shells] setenv PATH <required list of paths>

Back to top

Unable to run Vusers on the load generator

If you are unable to run Vusers on the load generator, no specific error is reported, and the Vuser protocol requires a third-party application or client to be present on load generator side, check the dynamic libraries used by the application. This enables you to establish if any shared objects cannot be found. A shared object that cannot be found may indicate either a missing prerequisite package or an environment variable issue.

To check the dynamic libraries used by an application, type:

ldd application_name

For example, type ldd mdrv to determine if all the dependencies of the mdrv executable can be found. If any dependencies are not found, run verify_generator as described in Configure the Linux environment.

Note: If you are running Vusers for a protocol that requires a client installation (for example, Oracle), make sure that the path for the client libraries is included in the dynamic library path environment variable (LD_LIBRARY_PATH or SHLIB_PATH).

Back to top

See also: