Is this page helpful?

Networking and System Configuration Issues#

NTP Configuration Issue in DLS#

After configuring NTP details in DLS, time is not synced because both the Chrony and systemd-timesyncd services being active. With both services running, systemd-timesyncd takes precedence over Chrony.

Next Steps

  • Option 1: Disable the systemd-timesyncd service.

  • Option 2: Configure the systemd-timesyncd service.

For more detailed instructions and additional information, visit the full article here.

How to Quickly Test a Connection to an SQL Database in Windows#

If you’re experiencing difficulties connecting to an SQL Server, a simple test can help verify SQL connectivity. This approach works on any version of Windows later than Windows 2000 and can rule out environmental issues.

Next Steps

  1. Create a .udl file:

    1. Right-click on the desktop or folder, select New > Text Document, and name it with a .udl extension.

    2. Double-click the file to open the Data Link Properties dialog box.

  2. In the Provider tab, ensure Microsoft OLE DB Provider for SQL Server is selected.

  3. Switch to the Connection tab, enter your SQL Server credentials, and test the connection.

Additional Troubleshooting

  • Verify that TCP/IP protocol is enabled in the SQL Server Configuration Manager.

  • Ensure ports 1433 and 1434 are open.

  • Test basic network connectivity with a ping test.

  • Confirm that the ‘sa’ login is enabled on the SQL Server.

For more detailed instructions and additional information, visit the full article here.

Security Challenge on Every Login#

Users face a security challenge during every login due to:

  • Logging in from new environments (e.g., virtual machines).

  • Unchecking the “Stay logged in” option.

  • Blocking third-party cookies in browser settings.

  • Multi-factor security set to “Every time I sign in.”

Next Steps

  1. Change Multi-Factor Security Settings by setting it to “Only when needed to protect my account.”

  2. Enable third-party cookies if blocked.

For more detailed instructions and information, visit the full article here.

Steps to Configure LDAP with the DLS Appliance#

The DLS GUI displays the error “Connection not successful, please check LDAP Properties” when LDAP fields are not populated correctly. Starting with DLS version 3.1, LDAP can be configured on the DLS appliance to allow LDAP users to log in to the appliance from the CLI and the GUI.

Next Steps

  1. Log in to the DLS appliance GUI and navigate to Settings → LDAP configuration.

  2. Follow the steps in Configuring LDAP via DLS Web UI.

After LDAP is successfully configured, all users in the LDAP directory can log in to the DLS appliance.

Unable to Access DLS Web UI Following Deployment of Containers When IPv6 Is Disabled#

Following deployment of DLS using containers on a customer-managed operating system, the DLS Web UI may be inaccessible if IPv6 is disabled on the host. The DLS appliance container uses gunicorn — a Python web server — to serve the DLS Web UI. Gunicorn binds to an IPv6 address by default at startup. When IPv6 is disabled on the host, this bind fails and the web service does not start, making the DLS Web UI unreachable.

Note

This issue applies to DLS deployments using containers only. DLS appliances deployed as hypervisor images are not affected.

Next Steps

  1. Confirm that both DLS containers (the postgres and the appliance container) are running:

    podman container ls

    Replace podman with docker if you are using Docker. Both containers should show an Up status.

  2. Check the DLS appliance va.log for errors related to the gunicorn service failing to bind to port 8085:

    • Log location: /var/lib/containers/storage/volumes/logs/_data

    • Look for entries such as: [ERROR] Can't connect to ('::',  8085)

  3. Check whether IPv6 is disabled on the host:

    • Option 1: Check /etc/default/grub for ipv6.disable=1 in the GRUB_CMDLINE_LINUX parameter.

    • Option 2: Run sysctl -a | grep disable_ipv6 and check for a value of 1.

  4. If IPv6 is confirmed to be disabled and is the cause of the issue, enable IPv6 on the operating system that the DLS containers are running on. Contact NVIDIA Enterprise Support for further assistance.

For more detailed instructions and additional information, visit the full article here.

Steps to Remove the NGINX Version from DLS Request and Response Headers#

When accessing the DLS appliance through a browser, the request and response headers visible in the browser’s Developer Tools also reveal the NGINX server version. This information is shared by default during client-server communication and may be flagged in security audits as an information exposure finding.

Next Steps

  1. Log in to the DLS appliance CLI as the rsu_admin user.

  2. Edit the following NGINX configuration template file using the nano editor:

    sudo nano /var/lib/docker/volumes/configurations/_data/ui/dls-web-ui.conf.template

  3. Under all server tags in the file, add the following line:

    server_tokens off;

  4. Save the file.

  5. Restart the DLS appliance:

    sudo systemctl restart applicationStartup

  6. Wait for the service to come back up, then verify in the browser’s Developer Tools that the NGINX version is no longer visible in the response headers.