openvas 9 scanner not found

Support/Development for OpenVAS
segurex
New Forum User
New Forum User
Posts: 1
Joined: Tue May 08, 2018 10:41 am
Location: Baltimore

openvas 9 scanner not found

Unread post by segurex »

I tried to scan a /27 network, it finished but in the results the vulnerability says "Check for enabled / working Port scanner plugin". Here is the logs files and check set up results:

Code: Select all

 sudo ./openvas-check-setup --v9
openvas-check-setup 2.3.6
  Test completeness and readiness of OpenVAS-9

  Please report us any non-detected problems and
  help us to improve this check routine:
  http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

  Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem.

  Use the parameter --server to skip checks for client tools
  like GSD and OpenVAS-CLI.

Step 1: Checking OpenVAS Scanner ...
        OK: OpenVAS Scanner is present in version 5.1.1.
        OK: redis-server is present in version v=3.2.10.
        OK: scanner (kb_location setting) is configured properly using the redis-server socket: /tmp/redis.sock
        OK: redis-server is running and listening on socket: /tmp/redis.sock.
        OK: redis-server configuration is OK and redis-server is running.
        OK: NVT collection in /var/lib/openvas/plugins contains 44769 NVTs.
        WARNING: Signature checking of NVTs is not enabled in OpenVAS Scanner.
        SUGGEST: Enable signature checking (see http://www.openvas.org/trusted-nvts.html).
        OK: The NVT cache in /var/cache/openvas contains 60137 files for 44769 NVTs.
Step 2: Checking OpenVAS Manager ...
        OK: OpenVAS Manager is present in version 7.0.2.
        OK: OpenVAS Manager database found in /var/lib/openvas/mgr/tasks.db.
        OK: Access rights for the OpenVAS Manager database are correct.
        OK: sqlite3 found, extended checks of the OpenVAS Manager installation enabled.
        OK: OpenVAS Manager database is at revision 184.
        OK: OpenVAS Manager expects database at revision 184.
        OK: Database schema is up to date.
        OK: OpenVAS Manager database contains information about 44768 NVTs.
        OK: At least one user exists.
        OK: OpenVAS SCAP database found in /var/lib/openvas/scap-data/scap.db.
        OK: OpenVAS CERT database found in /var/lib/openvas/cert-data/cert.db.
        OK: xsltproc found.
Step 3: Checking user configuration ...
        WARNING: Your password policy is empty.
        SUGGEST: Edit the /etc/openvas/pwpolicy.conf file to set a password policy.
Step 4: Checking Greenbone Security Assistant (GSA) ...
        OK: Greenbone Security Assistant is present in version 7.0.2.
        OK: Your OpenVAS certificate infrastructure passed validation.
Step 5: Checking OpenVAS CLI ...
        OK: OpenVAS CLI version 1.4.5.
Step 6: Checking Greenbone Security Desktop (GSD) ...
        SKIP: Skipping check for Greenbone Security Desktop.
Step 7: Checking if OpenVAS services are up and running ...
        OK: netstat found, extended checks of the OpenVAS services enabled.
        OK: OpenVAS Scanner is running and listening on a Unix domain socket.
        OK: OpenVAS Manager is running and listening on a Unix domain socket.
        OK: Greenbone Security Assistant is listening on port 80, which is the default port.
Step 8: Checking nmap installation ...
        WARNING: Your version of nmap is not fully supported: 6.47
        SUGGEST: You should install nmap 5.51 if you plan to use the nmap NSE NVTs.
Step 10: Checking presence of optional tools ...
        OK: pdflatex found.
        WARNING: PDF generation failed, most likely due to missing LaTeX packages. The PDF report format will not work.
        SUGGEST: Install required LaTeX packages.
        OK: ssh-keygen found, LSC credential generation for GNU/Linux targets is likely to work.
        OK: rpm found, LSC credential package generation for RPM based targets is likely to work.
        OK: alien found, LSC credential package generation for DEB based targets is likely to work.
        OK: nsis found, LSC credential package generation for Microsoft Windows targets is likely to work.
        OK: SELinux is disabled.

It seems like your OpenVAS-9 installation is OK.

Abbreviated and sanitized output from /var/log/openvas/openvassd.log (I added ~~~ to skip redundant or similar lines)

Code: Select all

[Mon May  7 07:49:01 2018][2519] Reloading the scanner.
[Mon May  7 07:49:14 2018][2519] Finished reloading the scanner.
[Mon May  7 07:50:00 2018][94506] Client closed the communication
[Mon May  7 17:21:41 2018][2519] Received the Terminated signal
[Mon May  7 17:23:47 2018][1093] openvassd 5.1.1 started
[Tue May  8 03:00:36 2018][15910] Starts a new scan. Target(s) : x.x.x.x/27, with max_hosts = 30 and max_checks = 10
[Tue May  8 03:00:36 2018][15910] exclude_hosts: Skipped 0 host(s).
[Tue May  8 03:00:36 2018][15910] Testing x-x-x-x.com (x.x.x.9) [15921]
~~~
[Tue May  8 03:00:39 2018][15939] The remote host (x.x.x.9) is dead
~~~
[Tue May  8 03:00:39 2018][15936] Finished testing x.x.x.9. Time : 3.21 secs
~~~
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
~~~
[Tue May  8 05:01:41 2018][1093] Reloading the scanner.
[Tue May  8 05:01:44 2018][15923] Warning: scheduler_rm_running_ports failed ?! (Services/www)
[Tue May  8 05:01:44 2018][15923] Warning: scheduler_rm_running_ports failed ?! (443)
[Tue May  8 05:01:44 2018][15921] Warning: scheduler_rm_running_ports failed ?! (139)
[Tue May  8 05:01:44 2018][15921] Warning: scheduler_rm_running_ports failed ?! (445)
[Tue May  8 05:01:44 2018][15923] Warning: scheduler_rm_running_ports failed ?! (Services/www)
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.108199
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.11153
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.108203
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.10330
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.11153
[Tue May  8 03:01:39 2018][15922] Possible dependency cycle detected 1.3.6.1.4.1.25623.1.0.17975
~~~
[Tue May  8 05:02:57 2018][15910] Test complete
[Tue May  8 05:02:57 2018][15910] Total time to scan all hosts : 7353 seconds
[Tue May  8 05:03:29 2018][26695] Client closed the communication
There are a 200 or so of the Warning: scheduler lines and about 300 of the Possible dependency cycle lines.
Appreciate any ideas?
Post Reply