Description

An issue with NVIDIA vGPU software license server 2019.05 prevents VMs from obtaining or renewing licenses.

When this issue occurs, the log files for the flexnetls service report one or both of the following errors:

• Trust break detected
• Unable to read anchor status

Version

NVIDIA vGPU software license server 2019.05.

Workaround

If you are affected by this issue, delete the trusted storage database, then reinstall your licenses on the license server as explained in Virtual GPU License Server User Guide.

If the issue persists or recurs after you delete the trusted storage database and reinstall your licenses, revert to NVIDIA vGPU software license server release 2018.10 as explained in Virtual GPU License Server User Guide.

If you revert to release 2018.10, new features, bug fixes, and security updates that were introduced in release 2019.05 are no longer available. For details, see:

• Changes in this Release
• Security Updates
• Resolved Issues

Status

Open

Description

During an upgrade of an existing license server installation, the installer might quit unexpectedly, throwing an InvocationTargetException.

The application exception details are as follows:

C:\Users\lsuser\AppData\Local\Temp\I1559058258\Windows_Pure_64_Bit\resource\iawin32.dll not found
at Flexeraaw7.af(Unknown Source)
at Flexeraaw7.aa(Unknown Source)
at com.zerog.ia.installer.LifeCycleManager.init(Unknown Source)
at com.zerog.ia.installer.LifeCycleManager.executeApplication(Unknown Source)
at com.zerog.ia.installer.Main.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.zerog.lax.LAX.launch(Unknown Source)
at com.zerog.lax.LAX.main(Unknown Source)

This error occurs if you attempt to install the 64-bit license server software for Windows on a host where a 32-bit license server with 32-bit JRE is installed. Because the 64-bit license server installer requires a 64-bit JRE, the installer fails if a 32-bit JRE is installed.

Workaround

The workaround depends on whether you want to upgrade from a 32-bit license server to a 64-bit license server:

• If you want to upgrade from a 32-bit license server to a 64-bit license server, you must uninstall and reinstall the license server and associated software as explained in Virtual GPU License Server User Guide.

• Otherwise, download and install the 32-bit license server.

  Note: Installed NVIDIA vGPU software licenses are not retained across an uninstallation followed by reinstallation. You must reinstall your licenses after reinstalling the license server software.

Status

Not a bug

Ref. #

2609471

Description

Sometimes, the Configuration page fails to load and the license server management interface reports the following error:

Error occurred: Please contact the administrator with the detailed steps to reproduce this issue.

The following error messages are written to the license server log file:

14:44:00,964 ERROR Trust startup failure:Unable to read anchor, status:FATAL.
14:44:00,964 ERROR Trust break detected at startup time:Unable to read anchor, status:FATAL.

When this issue occurs, any attempt by a license server client to acquire a license fails.

On Linux clients, error messages similar to the following example are logged in the standard activity log (/var/log/messages for distributions based on Red Hat or /var/log/syslog for distributions based on Debian):

Jun 19 14:04:43 localhost nvidia-gridd: Error: Error processing capability response. Server URL : http://10.31.20.45:7070/request - 
#012[1,7E2,2,0[7000001C,7100002E,250137]]#012Server was not able to process request correctly.#012Server status: (Back office server error.)

On Windows clients, no error messages are logged.

Workaround

On Linux, this workaround requires system administrator privileges.

1. Restart the license server service.

   • On Windows, in the Services application, context-click the FlexNet License Server - nvidia service and choose Restart.

   • On Linux, restart the flexnetls-nvidia.service service from the command line.

     [nvidia@localhost ~]$ systemctl restart flexnetls-nvidia.service

2. Confirm that the Configuration page now loads by accessing the license server management interface and clicking Configuration.

   Note: This error occurs when the license server service is started or restarted. Therefore, the error might persist after the license server service is restarted. If the error persists, restart the license server service again.

Status

Open

Ref. #

200463359

Description

If you are upgrading to the 32-bit license server and your earlier version of the license server was configured to use HTTPS, the HTTPS configuration is removed during the upgrade.

• Files for configuring HTTPS for connections between the management interface are stored in a subfolder of the license server installation folder. The installer deletes the entire contents of any existing license server installation folder, including files that were added after the license server software was installed, such as the SSL certificate that the license server was configured with.
• The HTTPS connector for connections from a web browser to the license server management interface is defined in the Tomcat configuration file server.xml. The installer overwrites the existing server.xml file and any custom configuration specified in the file is lost.

Workaround

1. Before installing the new version of the license server software, copy the files that are necessary to re-instate the configuration after the upgrade.

   • If HTTPS is configured for connections between the management interface and the license server, copy the SSL certificate that the license server was configured with.

     Note:

     Copying an SSL certificate might corrupt it. To determine if the certificate is corrupted, run this command:

     $JAVA_HOME/bin/keytool -list -keystore certificate-file-name.jks -storepass certificate-password

     If the certificate is corrupted, contact the CA that issued your certificate to obtain a new certificate.

   • If HTTPS is specified for connections from a web browser to the license server management interface, copy the Tomcat configuration file server.xml.

2. After installing the new version of the license server software, re-create the HTTPS configuration as explained in Virtual GPU License Server User Guide.

Status

Not a bug

Ref. #

• 200500532
• 200521319

Description

The License Server requires an Apache Tomcat server. On Windows, Apache Tomcat is included with the License Server installer package. On Linux, Apache Tomcat must be installed separately.

By default, files such as documentation, the default index page, example JSP files, and example servlets are installed on the host where the Apache Tomcat software is installed. These files may help an attacker uncover information about the Apache Tomcat installation or the host where the Apache Tomcat software is installed. Furthermore, the files may themselves contain vulnerabilities that might allow attacks such as cross-site scripting attacks.

Mitigations

• Review the files and delete the files that are not needed.
• Provide a custom error page for common HTTP errors such as error 404 or 500.

See Also

• Securing Tomcat from the Open Web Application Security Project (OWASP)
• How do I get a customized error page? FAQ on the Tomcat wiki

Description

The time shown in the Client Expiry field on the Client Details page is inconsistent with the time stamps in the license server log files.

For example, the log files might show these time stamps:

• License acquired time is - Wed May 30 16:18:23 2018
• Borrow interval is 1440 mins

From these time stamps, the expected client expiry time is 2018-05-31 16:18:23. However, on the Client Details page, the Client Expiry field shows 2018-05-31T10:48:59.999Z.

This inconsistency occurs because the time of day in the license management interface is given in Coordinated Universal Time (UTC), not the local time of the license server host.

Status

Not an NVIDIA bug

Ref. #

Description

When the management UI is used to delete a single entry from the Reservation page, all entries on the page are deleted because the management UI supports operations only on reservation groups, not individual reservations, specifically:

• Deleting an existing reservation group. Deleting individual reservations within a reservation group is not supported.
• Adding reservations to a new reservation group. Adding reservations to an existing reservation group is not supported.

Workaround

To add or delete reservations in an existing group:

1. Delete the existing group.

2. Re-create the group with the set of reservations that you want:

   • Include the existing reservations that you want to keep and any new reservations that you want to add.
   • Exclude any reservations that you want to remove.

   You can re-create the group by using the Add Reservation page or by importing reservations from a JSON file. For instructions, see Virtual GPU License Server User Guide.

   Note: If you are importing reservations from a JSON file, ensure that the name attribute of each array of reservations is set to a non-null value. Although the name attribute is optional, any imported reservation groups for which the name attribute is not set cannot be deleted through the management UI.

Status

Not a bug

Ref. #

Description

If the license server is shut down suddenly and cannot be shut down cleanly, the trusted storage database may become corrupted. If the database is corrupted, it cannot be read and the flexnetls-nvidia service cannot start.

When the flexnetls-nvidia service cannot start because the database is corrupted, messages similar to the following examples for each platform are written to the license server log file:

• On Windows:

  org.h2.message.DbException: General error: 
  "java.lang.IllegalStateException: File corrupted in chunk ${chunk_number}, 
  expected page length ${page_length}, got ${actual_page_length}" [50000-193]
   
  org.h2.message.DbException: General error: 
  "java.lang.IllegalStateException: Reading from 
  nio:C:/Windows/ServiceProfiles/NetworkService/flexnetls/nvidia/flexnetls_licenses.mv.db failed; 
  file length ${file_length} read length ${read_length} at ${index}"

• On Linux:

  org.h2.message.DbException: General error: 
  "java.lang.IllegalStateException: Reading from
  nio:/var/opt/flexnetls/nvidia/flexnetls_licenses.mv.db failed;
  file length ${file_length} read length ${read_length} at ${index}"

On Windows, event 6008 may be written to the event viewer log indicating that the license server was shut down abruptly and could not be shut down cleanly.

Workaround

Restore the database from a backup as explained in Virtual GPU License Server User Guide.

If the database remains corrupted after it is restored, the backup that you restored it from may also be corrupt. In this situation, delete the trusted storage files, start the flexnetls-nvidia service, and reinstall your licenses. For instructions for performing these tasks, see Virtual GPU License Server User Guide.

Status

Not an NVIDIA bug

Ref. #

2104881

Description

The management interface of the license server enables the MAC address of the license server to be changed and the change to be saved. However, when the license server host is restarted, the MAC address reverts to its previous setting.

Workaround

Change the MAC address by editing the license server settings file, updating the license server settings from the edited file, and restarting the license server.

Before attempting this workaround, ensure that the JAVA_HOME or JRE_HOME environment variable is set to the directory where the Java runtime environment is installed on the license server host.

This workaround requires system administrator privileges.

Status

Open

Ref. #

200397697

Description

The logging threshold under Logging properties on the Configuration page accepts input only in uppercase. When a valid logging threshold value in lowercase is entered, an error message similar to the following message is displayed:

The value "error" for "Logging Threshold" is not valid. [Logging Threshold, error] 

Workaround

Enter logging threshold values in all uppercase.

Status

Not an NVIDIA bug

Ref. #

200334630

Description

An attempt to upgrade from License Server version 2015.12-0001 to the current version fails with the following error:

One or more newer versions of the product are installed. An update is not available.

Version

2019.05

Workaround

1. When the error dialog box opens, click Abort to abandon the upgrade.
2. Cleanly uninstall License Server version 2015.12-0001.
3. Install the current version of the License Server software.

Status

Open

Ref. #

200301811

Description

A long-running license server may fail because the license server log files flexnetls.log and access.log have exhausted the disk space on the server. Although the license server rotates log files by opening a new log file each day, it does not automatically delete old log files.

Workaround

Delete old log files when they are no longer required. On Linux, you can use a cron job to delete files that are more than a specific number of days old.

Status

Open

Ref. #

1932568

Description

A client located in a time zone that is ahead of the license server’s time zone may fail to check out a license, if the license expiration time has passed in the client’s time zone.

Platform

All

Workaround

Locate the license server in a time zone proximate to the clients it will serve.

Status

Open

Ref. #

1685774

Description

If the license server is installed on a platform on which license server software version 2015.12 or earlier is installed, the license server installer is incorrectly executed. The upgrade installation is not indicated to the user and, on Windows, the Apache Tomcat installer is erroneously rerun.

Platform

All

Version

This issue affects upgrades from version 2015.12 or earlier.

Workaround

Before installing this release of the license server, uninstall the previous license server software and, on Windows, uninstall the Apache Tomcat software.

Status

Open

Ref. #

1713544, 1713532