Tenable Nessus Network Monitor Troubleshooting

Tenable Nessus Network Monitor server does not appear to be operational

  1. Verify that the Tenable Nessus Network Monitor server appears as Unable to Connect under Status.

  2. SSH to the remote Tenable Nessus Network Monitor host to make sure the underlying operating system is operational.

  3. Confirm that the Tenable Nessus Network Monitor is running (Linux example below):

    # service pvs status

    NNM is stopped

    NNM Proxy (pid 3142) is running

    #

  4. If the Tenable Nessus Network Monitor service is not running, start the service:

    # service nnm start

    Starting NNM Proxy                                         [  OK  ]

    Starting NNM                                              [  OK  ]

    #

Cannot add a Tenable Nessus Network Monitor server

  1. Confirm that the Tenable Nessus Network Monitor proxy is listening on the same port as Tenable Security Center (port 8835 by default):

    # ss -pan | grep 8835

    tcp        0      0 0.0.0.0:8835    0.0.0.0:*     LISTEN      406/pvs

  2. Check connectivity by telnetting from the Tenable Security Center console into the Tenable Nessus Network Monitor server on port 8835 (the Tenable Nessus Network Monitor listening port). If successful, the response includes: Escape character is '^]'.

No vulnerabilities are being received from the Tenable Nessus Network Monitor server

  1. Ensure that the Tenable Nessus Network Monitor service is running on the Tenable Nessus Network Monitor host.

  2. Ensure that the Tenable Nessus Network Monitor appears in Tenable Security Center under Resources > Tenable Nessus Network Monitors and that the status of the Tenable Nessus Network Monitor appears as Working.

  3. Click Edit to ensure that the IP address or hostname, port, username, password, and selected repositories for the Tenable Nessus Network Monitor are correct.

  4. Edit any incorrect entries to their correct state.

  5. Click Submit to attempt to reinitialize the Tenable Nessus Network Monitor scanning interface.

Tenable Nessus Network Monitor plugins fail to update

  1. Manually test a plugin update under Plugins with Update Plugins.

    If successful, Passive Plugins Last Updated updates to the current date and time.

  2. Ensure that the Tenable Security Center host allows outbound HTTPS connectivity to the Tenable Nessus Network Monitor Plugin Update Site.

  3. For all other Tenable Nessus Network Monitor plugin update issues, contact Tenable Support.