Installation guide

Nessus plugins fail to update

 Under “System” and “Configuration” in SecurityCenter, ensure that the Nessus Activation Code is marked as

“Valid”.

 Ensure that the user used to connect to the Nessus server is configured as an ‘admin’ class user.

 Ensure that the SecurityCenter system is allowed outbound HTTP(S) connectivity to the Nessus Plugin Update

Site. If it is not, refer to the Nessus 5.0 Installation and Configuration Guide for information on offline plugin

updates.

 Under “System”, “Configuration”, and “Update” in SecurityCenter, ensure that Active Plugins is not set to “Never”.

Manually test a plugin update under “Plugins” with “Update Plugins”. If successful, the line “Active Plugins Last

Updated” will update to the current date and time.

 For all other Nessus plugin update issues, contact Tenable Support at support@tenable.com.

PVS

PVS server does not appear to be operational

 Verify in the SecurityCenter GUI that the PVS server appears as “Unable to Connect” under “Status”.

 SSH to the remote PVS host to make sure the underlying operating system is operational.

 Confirm that the PVS daemon is running (Linux example below):

# service pvs status

PVS is stopped

PVS Proxy (pid 3142) is running

If the PVS service is not running, start the service:

# service pvs start

Starting PVS Proxy [ OK ]

Starting PVS [ OK ]

Can’t add a PVS server

 Confirm that the PVS proxy is listening on port 1243:

# netstat -pan | grep 1243

tcp 0 0 0.0.0.0:1243 0.0.0.0:* LISTEN 406/pvs-proxy

 Check connectivity by telnetting from the SecurityCenter to the PVS server on port 1243 (the pvs-proxy). If

successful, the response will include: Escape character is '^]'.

No vulnerabilities are being received from the PVS server

 Ensure that the PVS service is running on the PVS host.

 Ensure that the PVS is listed in SecurityCenter under “Resources” and “Passive Scanners” and that the status of

the PVS is listed as “Working”. Click “Edit” to ensure that the IP address or hostname, port, username, password,

and selected repositories for the PVS are all correct. Edit any incorrect entries to their correct state and click

“Submit” to attempt to reinitialize the PVS’ scanning interface.

PVS plugins fail to update

 Manually test a plugin update under “Plugins” with “Update Plugins”. If successful, the line “Passive Plugins Last

Updated” will update to the current date and time.