Workaround for InfoScale LMS 8.0.2 Configuration failure on Linux Servers

Description

This article provides a step-by-step workaround for resolving a configuration failure in Arctera License Management Service (LMS) 8.0.2 when installed on top of Veritas InfoScale Operations Manager (VIOM) 8.0.2.550 on Red Hat Enterprise Linux (RHEL) servers. The issue manifests as a Database configuration failed error during the LMS configuration process, even after verifying prerequisites such as patch levels, permissions, and firewall settings. The failure is due to the LMS configuration script (cli_lms_config.pl) failing to update the LMS UUID in the VIOM/CMS database and configuration file, causing the configuration to abort.

This workaround involves manually updating the database and configuration file, modifying the configuration script to bypass the failing step, and re-running the configuration. The steps have been tested and confirmed to resolve the issue, allowing the LMS web interface to become accessible and license registration to be completed successfully.

Symptoms

• LMS 8.0.2 configuration fails with the error: Database configuration failed
• Log files indicate issues with database schema updates or missing/empty configuration files.
• Multiple attempts to re-run the configuration or reinstall LMS do not resolve the issue.
• The issue occurs consistently across multiple RHEL servers with VIOM 8.0.2.550 installed.

Environment

• Product: InfoScale LMS 8.0.2 (Arctera License Management Service)
• Platform: Red Hat Enterprise Linux (RHEL)
• Prerequisite: Veritas InfoScale Operations Manager (VIOM) 8.0.2.550 installed
• Configuration Script: /opt/VRTSlms/bin/cli_lms_config.pl

Root Cause

The LMS configuration script (cli_lms_config.pl) attempts to update the LMS UUID in the VIOM/CMS database during setup. For reasons possibly related to permissions, environment settings, or script logic, the script fails to execute the database update when run as root. This results in the LMS UUID not being written to the database or the configuration file (e.g., /etc/vx/VRTSlms/.lmsuuid), causing the configuration to fail with a database error. Manual execution of the same SQL command succeeds, indicating a problem specific to the script's automated process.

How To

Follow these steps to resolve the LMS 8.0.2 configuration failure and successfully complete the setup:

1. Uninstall and Reinstall LMS
   
   Ensure a clean state by removing and reinstalling the LMS package.

   • Run the following commands as root: rpm -e VRTSlmsrpm ; rpm -ivh VRTSlms-8.0.2.550
   • Verify the installation completed successfully before proceeding.

2. Manually Update the Database with LMS UUID
   
   Identify and execute the SQL command to insert the LMS UUID into the VIOM/CMS database.

   • Access the VIOM/CMS database using the appropriate credentials (consult your database administrator for connection details).
      
   • Run the SQL command that the configuration script attempts to execute. For example:

     /opt/VRTSsfmcs/pgsql/bin/psql -p 5636 SFMdb3 habguest -c "INSERT INTO p_db_default (name, value, note) VALUES ('server_identifier_value', gen_random_uuid(), 'unique LMS identifier for UIS json report');"
     
     /opt/VRTSsfmcs/pgsql/bin/psql -p 5636 SFMdb3 habguest -c "\COPY (SELECT value FROM p_db_default WHERE name = 'server_identifier_value') TO '/etc/vx/VRTSlms/licenses/.lmsuuid' WITH (FORMAT text)"   
     
     >> (if we do above step then we do not need 3rd step to be performed)

   • Replace <generated_uuid> with a valid UUID (use a UUID generator if needed or retrieve the intended UUID from logs).
      
   • Verify the UUID was inserted correctly by querying the database:
     
     /opt/VRTSsfmcs/pgsql/bin/psql -p 5636 SFMdb3 habguest -c "SELECT * FROM p_db_default WHERE name = 'server_identifier_value';"
     
      

3. Manually Update the Configuration File
   Update the LMS configuration file with the UUID value.

   • Locate the configuration file, typically at cat /etc/vx/VRTSlms/licenses/.lmsuuid
   • Open the file in a text editor (e.g., vi or nano):

     vi /etc/vx/VRTSlms/licenses/.lmsuuid       

   • Add or update the UUID entry to match the value inserted into the database. For example:

     LMS_UUID=<generated_uuid>

   • Save and close the file.

4. Modify the LMS Configuration Script
   Bypass the failing step in the configuration script by commenting out the problematic function call.

   • Open the script in a text editor:

     vi /opt/VRTSlms/bin/cli_lms_config.pl

   • Locate line 231, which contains the update_lms_uuid() function call.
   • Comment out the line by adding a # at the beginning:

     # update_lms_uuid(); # Line 231

   • Save and close the file.

5. Re-run the LMS Configuration
   Execute the configuration script again to complete the setup.

   • Run the following command as root:

     /opt/VRTSsfmh/bin/perl /opt/VRTSlms/bin/cli_lms_config.pl

   • Verify that the configuration is completed without errors.
   • Check that the LMS web interface is accessible (e.g., via the configured URL).

6. Register the LMS License
   Generate and apply the LMS license key.

   • Access the Veritas Entitlement Portal to generate the license key.
   • Log in to the LMS web interface.
   • Navigate to the license registration section and apply the license key.
   • Verify that the license is successfully registered.

Verification

• Confirm that the LMS web interface is accessible and functional.
• Verify that the license key is applied correctly in the LMS web UI.
• Check the configuration file (/etc/vx/VRTSlms/licenses/.lmsuuid) to ensure the UUID is present and matches the database entry.
• Monitor logs for any residual errors and address them as needed.

Internal Notes

Root Cause Analysis

The issue stems from the cli_lms_config.pl script failing to execute the update_lms_uuid() function, which is responsible for writing the LMS UUID to the VIOM/CMS database and the configuration file (/etc/vx/VRTSlms/license/.lmsuuid). The failure occurs despite the script running with root privileges and all prerequisites (patch levels, permissions, firewall settings) being met. Manual execution of the SQL command to insert the UUID succeeds, suggesting a script-specific issue, possibly related to:

• Permissions: The script may not correctly handle database permissions in certain RHEL environments.
• Environment Variables: Missing or misconfigured environment variables may prevent the script from connecting to the database.
• Script Logic: A bug in the update_lms_uuid() function may cause it to fail silently or mishandle errors.

Engineering is investigating the root cause to determine if a patch or updated script is needed. A future release may address this issue to prevent the need for manual intervention.

Additional Considerations

• Environment-Specific Issues: This issue was observed on RHEL servers with VIOM 8.0.2.550. Other Linux distributions or VIOM versions may not exhibit the same behavior.

• Log Analysis: Check the LMS and VIOM logs (e.g., /var/log/vx/*) for specific error messages related to database connectivity or schema updates.

• UUID Generation: If the UUID is not available in logs, generate a new one using a standard UUID generator (e.g., uuidgen on Linux) and ensure consistency between the database and configuration file.

• Script Modification Risks: Commenting out the update_lms_uuid() function bypasses a critical step. Ensure the manual UUID updates are accurate to avoid downstream issues with LMS functionality.

Reference

• Script to Modify: /opt/VRTSlms/bin/cli_lms_config.pl & comment out below line:
  
  # update_lms_uuid(); # Line 231

• Configuration File: /etc/vx/VRTSlms/licenses/.lmsuuid

• Logs to Check: /var/opt/VRTSsfmh/logs/lms_config.log;/var/opt/VRTSlms/logs/*