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 license server may fail to start because the database connection is closed. When this error occurs, the following error messages are written to the license server log file:

org.h2.message.DbException: General error: "java.util.ConcurrentModificationException" [50000-196]

org.h2.jdbc.JdbcSQLException: The database has been closed [90098-196]
 
Internal Exception: org.h2.jdbc.JdbcSQLException: General error: 
"java.lang.IllegalStateException: Transaction is closed [1.4.196/4]"  [50000-196]

A side effect of this error is that these error messages are frequently written to the log file, which may cause the log files to exhaust the disk space on the server.

Status

Resolved in release 2018.10

Ref. #

200400065

Description

When more than 20 license reservation groups are added to the license server, the management UI displays only the first 20 groups. Groups that are not displayed cannot be found through search because the UI provides no option to search for license reservations. If an existing group is deleted, one of the previously hidden groups is listed in the UI. Groups that are not listed in the UI function normally.

This issue occurs regardless of whether the groups are added through the UI or imported from a JSON file. When groups are imported from a JSON file, only one record in the file is displayed.

Workaround

For reservations entered through the management UI, use fewer than 20 reservation groups.

For reservations exported to and imported from a JSON file, use only one reservation group.

Status

Resolved in release 2018.10

Ref. #

• 200397688
• 200403638

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

After the license server is restarted, the log level reverts to its default level of INFO, even if a different level has been set.

Workaround

Set the license server log level to the level that you require as explained in Virtual GPU License Server User Guide.

Status

Open

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

2018.06

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 IP address of the license server changes, the license server fails to start. The license server management interface reports a connection error to the FNE server:

The license server logs report this error:

2015-09-06 14:47:41,726 FATAL Database may be already in use: 
"Locked by another computer: 10.31.223.39".
Possible solutions: close all other connection(s); use the server mode [90020-184]
2015-09-06 14:47:41,726 INFO  Sending stop request to FlexNet License Server.

Platform

All

Workaround

None. Ensure that the license server host is configured with a constant IP address.

Ref. #

1685681

Description

Running the Windows License Server uninstaller fails to remove Apache Tomcat.

Platform

All Windows variants

Workaround

Remove Apache Tomcat manually.

1. Open Windows Control Panel.
2. Select Programs and Features.
3. In the list of programs, select Apache Tomcat and click Uninstall/Change.

Status

Open

Ref. #

1684980

Description

Upgrading the license server software on Windows does not upgrade Apache Tomcat.

Platform

All Windows variants

Workaround

Uninstall Apache Tomcat and the license server software manually before upgrading the license server software on Windows.

Status

Duplicate of 1684980

Ref. #

200475014

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

Description

After the license server is upgraded or installed on Windows, the license server may fail with the error Connection refused: connect.

This error occurs if the Windows service Server is not running when the license server installer is run. The license server installation script depends on this service. When this error occurs, the license server service FlexNet License Server – nvidia does not exist.

Platform

Windows

Workaround

1. Uninstall the license server software and the Apache Tomcat software.

2. Start the Windows service Server.

   1. Start the Services desktop app.

   2. In the list of Services, context click Server and choose Start.

3. Install the license server software.

   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

Open

Ref. #

200488813

Description

Rerunning the license server installer doesn’t provide options to modify or uninstall the license server. Instead, an error is reported that an upgrade is not applicable.

Platform

All

Workaround

To uninstall the license server, follow the uninstallation instructions in the Virtual GPU License Server User Guide.

Status

Open

Ref. #

1713546

Description

The Linux uninstaller allows execution as a nonroot user. The uninstallation fails, and leaves the license server operational.

Platform

Linux

Workaround

1. Change to the license server installation directory.

   [~]$ cd /opt/flexnetls/nvidia

2. Run the uninstaller as root.

   [~]$ sudo ./Change\ License\ Server\ Installation

Status

Open

Ref. #

200162338