1. Release Notes

These Release Notes summarize current status, information on supported platforms, and known issues with NVIDIA vGPU software License Server, version 2018.06 and 5.1.0.

Note: Uninstall any previous version of NVIDIA vGPU software License Server before installing this release. Installed NVIDIA vGPU software licenses will be retained across an uninstallation followed by reinstallation. For details, see Upgrade installation does not operate correctly.

All releases of the License Server are compatible with all releases of NVIDIA vGPU software.

1.1. Supported Platforms

1.1.1. Operating Systems Supported

This release of NVIDIA vGPU software License Server has been tested on several releases of the Windows and Linux operating systems.

Note:Since 2018.06: Support for installation in console mode on Windows and Linux is introduced in license server release 2018.06. It is not supported in earlier license server releases. The license server installer for earlier releases must be run in a graphical desktop environment.

1.1.1.1. Windows Operating Systems Supported

  • Windows 10 64-bit
  • Windows Server 2016
  • Windows Server 2012 R2
Note: On Windows, the license server supports only the English locale.

1.1.1.2. Linux Operating Systems Supported

  • Red Hat Enterprise Linux 7.3 64-bit
  • CentOS 7.3 64-bit
  • Since 2018.06: Ubuntu 16.04 64-bit

1.1.2. Java Runtime Environment Requirements

NVIDIA vGPU software License Server requires Java Runtime Environment (JRE) version 1.8 or later. JRE should be installed before running the License Server installer package, as described in the Virtual GPU License Server User Guide.

On Windows 32-bit and 64-bit platforms, NVIDIA vGPU software License Server requires a 32-bit JRE.

1.1.3. .NET Framework Requirements

On Windows platforms, NVIDIA vGPU software License Server requires .NET Framework 4.5 or later.

1.1.4. Apache Tomcat Server Requirements

The License Server’s management interface requires Apache Tomcat version 7x or 8x. An Apache Tomcat package is included with the License Server installer package for Windows. For Linux, Tomcat should be installed before running the License Server installer package, as described in Virtual GPU License Server User Guide.

1.1.5. Web Browser Requirements

The license server’s web browser–based management interface supports the following browsers:

  • Mozilla Firefox versions 17 and later
  • Google Chrome versions 27 and later
  • Microsoft Internet Explorer version 9 and later

1.2. Changes in this Release

Changes in Release 2018.06

  • New release numbering scheme in the form yyyy.mm to provide greater differentiation from NVIDIA vGPU software release numbers
  • Support for Ubuntu 16.04
  • Automated backups of the trusted storage database
  • New layout of the Client Details page, which now shows the client expiry date and time
  • Support for installation in console mode on Windows and Linux

Changes in Release 5.1.0

Miscellaneous bug fixes

1.3. Security Updates

Security Updates in Release 2018.06

Inclusion of an updated Apache Tomcat version (8.5.31) with the License Server installer package for Windows

This version contains security updates for the following CVEs that affect Apache Tomcat version 8.5.24, which was previously included with the License Server installer package for Windows:

  • CVE-2018-1304
  • CVE-2018-1305

Security Updates in Release 5.1.0

  • Inclusion of an updated Apache Tomcat version (8.5.24) with the License Server installer package for Windows

    This version contains security updates for the following CVEs that affect Apache Tomcat version 8.5.15, which was previously included with the License Server installer package for Windows:

    • CVE-2017-7675
    • CVE-2017-7674
    • CVE-2017-12615
    • CVE-2017-12617
  • Update of the Apache Struts library included in the license server to version to 2.3.34

    This version contains security updates for the following CVEs:

    • CVE-2017-9804
    • CVE-2017-7672
    • CVE-2017-9805

2. Known Issues

2.1. Apache Tomcat Servlet/JSP Container Default Files Vulnerability (Nessus ID: 12085)

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

2.2. Since 2018.06: Time stamps in the License Server Management Interface and log files are inconsistent

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.

Version

2018.06

Status

Not an NVIDIA bug

Ref. #

200418046

2.3. Since 2018.06: Deleting a license reservation deletes the entire reservation group

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.

Version

2018.06

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 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. #

200418787

2.4. Sudden shutdown of the license server can cause database corruption

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, the following message is written to the license server log file:

/var/opt/flexnetls/nvidia/flexnetls_licenses.mv.db file failed.

Workaround

This workaround requires system administrator privileges.

  1. Delete the trusted storage files, which are located in the directory /var/opt/flexnetls/nvidia/.

    Note: Deleting the trusted storage clears all information about license assignments and allocations.
  2. Start the flexnetls-nvidia service.

    # sudo systemctl restart flexnetls-nvidia.service
  3. Reinstall your licenses on the license server, as described in Virtual GPU License Server User Guide.

Status

Not an NVIDIA bug

Ref. #

2104881

2.5. The license server management UI shows an unusable option to generate a file for the NVIDIA Software Licensing Center

Description

The License Management section on the license server's management interface shows the option Generate license request file for processing by the NVIDIA Licensing Portal. This option cannot be used because the NVIDIA Software Licensing Center does not provide an option for uploading such a request file.

Status

Resolved in release 2018.06.

Ref. #

200410287

2.6. The license server management UI cannot display more than 20 license reservation groups

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

Open

Ref. #

  • 200397688
  • 200403638

2.7. License server MAC address cannot be changed in the management interface

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.

On Windows:
  1. Open the file license-server-installation-folder\server\flexnetls.settings in a plain text editor such as WordPad.

    license-server-installation-folder
    The folder in which the license server software is installed. The default license server installation folder is %SystemDrive%:\Program Files (x86)\NVIDIA\License Server.
  2. Uncomment the #ACTIVE_HOSTID= line and append the MAC address to the line followed by /Ethernet.

    For example:

    ...
    ACTIVE_HOSTID=4E7DBF3A250A/Ethernet
    ...
  3. Save your changes and exit the editor.

  4. As an Administrator user, open a Command Prompt window and change to the license-server-installation-folder\server folder.

    For example:

    C:\>cd C:\Program Files (x86)\NVIDIA\License Server\server
    C:\Program Files (x86)\NVIDIA\License Server\server>
  5. In the Command Prompt window, run the command to update the license server settings from the edited file.

    C:\Program Files (x86)\NVIDIA\License Server\server>flexnetls.bat -update
    Updating service FNLS-nvidia
    Service FNLS-nvidia successfully stopped
    Uninstalling service FNLS-nvidia
    Installing service FNLS-nvidia
    
    C:\Program Files (x86)\NVIDIA\License Server\server>
  6. In the Command Prompt window, run the command to restart the license server.

    C:\Program Files (x86)\NVIDIA\License Server\server>flexnetls.bat -start
    Service FNLS-nvidia successfully started
    
    C:\Program Files (x86)\NVIDIA\License Server\server>
On Linux:
  1. As root, open the file /opt/flexnetls/nvidia/local-configuration.yaml in a plain text editor.

  2. Uncomment the #ACTIVE_HOSTID= line and append the MAC address to the line followed by /Ethernet.

    For example:

    ...
    ACTIVE_HOSTID=4E7DBF3A250A/Ethernet
    ...
  3. Save your changes and exit the editor.

  4. As root, restart the flexnetls-nvidia service.

    # sudo systemctl restart flexnetls-nvidia.service

Status

Open

Ref. #

200397697

2.8. After restart, the log level reverts to its default level

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

2.9. The logging threshold can only be uppercase

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

2.10. License Server upgrade fails

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 and 5.1.0

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

2.11. Log files can exhaust local disk space

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

2.12. Client in time zone ahead of license server may fail to check out a license close to its expiry time

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

2.13. License server fails to start because of an IP address change

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:



Screen capture of the Licensed Clients page showing a connection error after a change of IP address.

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

2.14. Uninstallation on Windows doesn’t remove Apache Tomcat

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

2.15. Upgrade installation does not operate correctly

Description

Installing the license server on a platform that has a previous license server version installed leads to incorrect execution of the license server installer. The upgrade installation is not indicated to the user, and on Windows the Apache Tomcat installer is erroneously rerun.

Platform

All

Workaround

Uninstall the previous license server installation before installing this release of the license server. Any installed NVIDIA vGPU software licenses will persist across an uninstallation followed by installation of this license server release.

Status

Open

Ref. #

1713544, 1713532

2.16. Rerunning the installer doesn’t launch modify/uninstall

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

2.17. Linux uninstaller allows execution as nonroot user

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

Notices

Notice

ALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, "MATERIALS") ARE BEING PROVIDED "AS IS." NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE.

Information furnished is believed to be accurate and reliable. However, NVIDIA Corporation assumes no responsibility for the consequences of use of such information or for any infringement of patents or other rights of third parties that may result from its use. No license is granted by implication of otherwise under any patent rights of NVIDIA Corporation. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all other information previously supplied. NVIDIA Corporation products are not authorized as critical components in life support devices or systems without express written approval of NVIDIA Corporation.

HDMI

HDMI, the HDMI logo, and High-Definition Multimedia Interface are trademarks or registered trademarks of HDMI Licensing LLC.

OpenCL

OpenCL is a trademark of Apple Inc. used under license to the Khronos Group Inc.

Trademarks

NVIDIA, the NVIDIA logo, NVIDIA GRID, vGPU, Pascal, Quadro, and Tesla are trademarks or registered trademarks of NVIDIA Corporation in the U.S. and other countries. Other company and product names may be trademarks of the respective companies with which they are associated.

Third-Party Software

This NVIDIA product contains third party software that is made available under their respective software licenses.

Apache Tomcat (https://tomcat.apache.org/download-80.cgi) is provided under the following terms: Copyright 2015 NVIDIA Corporation Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.