openvas-check-setup 2.3.1
  Test completeness and readiness of OpenVAS-8
  (add '--v6' or '--v7' or '--v9'
   if you want to check for another OpenVAS version)

  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.0.4.
        OK: OpenVAS Scanner CA Certificate is present as 
/usr/local/var/lib/openvas/CA/cacert.pem.
        OK: redis-server is present in version v=2.8.17.
        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 /usr/local/var/lib/openvas/plugins contains 39767 
NVTs.
        WARNING: Signature checking of NVTs is not enabled in OpenVAS Scanner.
        SUGGEST: Enable signature checking (see 
http://www.openvas.org/trusted-nvts.html).
        WARNING: The initial NVT cache has not yet been generated.
        SUGGEST: Start OpenVAS Scanner for the first time to generate the cache.
Step 2: Checking OpenVAS Manager ...
        OK: OpenVAS Manager is present in version 6.0.4.
        OK: OpenVAS Manager client certificate is present as 
/usr/local/var/lib/openvas/CA/clientcert.pem.
        OK: OpenVAS Manager database found in 
/usr/local/var/lib/openvas/mgr/tasks.db.
        OK: Access rights for the OpenVAS Manager database are correct.
        OK: At least one user exists.
        OK: sqlite3 found, extended checks of the OpenVAS Manager installation 
enabled.
        OK: OpenVAS Manager database is at revision 146.
        OK: OpenVAS Manager expects database at revision 146.
        OK: Database schema is up to date.
        OK: OpenVAS Manager database contains information about 39585 NVTs.
        OK: OpenVAS SCAP database found in 
/usr/local/var/lib/openvas/scap-data/scap.db.
        OK: OpenVAS CERT database found in 
/usr/local/var/lib/openvas/cert-data/cert.db.
        OK: xsltproc found.
Step 3: Checking user configuration ...
        WARNING: Your password policy is empty.
        SUGGEST: Edit the /usr/local/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 6.0.4.
Step 5: Checking OpenVAS CLI ...
        OK: OpenVAS CLI version 1.4.2.
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 all interfaces.
        OK: OpenVAS Scanner is listening on port 9391, which is the default 
port.
        OK: OpenVAS Manager is running and listening on all interfaces.
        OK: OpenVAS Manager is listening on port 9390, which is the default 
port.
        WARNING: Greenbone Security Assistant is listening on port 80 443, 
which is NOT the default port!
        SUGGEST: Ensure Greenbone Security Assistant is listening on one of the 
following ports: 80, 443, 9392.
./openvas-check-setup: 789: [: 80: unexpected operator
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.
        OK: PDF generation successful. The PDF report format is likely to work.
        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.

It seems like your OpenVAS-8 installation is OK.

If you think it is not OK, please report your observation
and help us to improve this check routine:
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze 
the problem.


Von: Openvas-discuss [mailto:[email protected]] Im 
Auftrag von Eero Volotinen
Gesendet: Donnerstag, 16. Juli 2015 09:08
An: Gerald Vogt
Cc: [email protected]
Betreff: Re: [Openvas-discuss] No reports listed on reports page

Hi,

please download this script: Setup and start 
OpenVAS<http://openvas.org/setup-and-start.html> and run openvas-check-setup 
-v8 paste output to mailing list..

--
Eero

2015-07-16 8:21 GMT+03:00 Eero Volotinen 
<[email protected]<mailto:[email protected]>>:
Ok. I can test this, if this is reproducable on my system.

--
Eero

2015-07-14 16:41 GMT+03:00 Gerald Vogt 
<[email protected]<mailto:[email protected]>>:
I installed OpenVAS 8 from sources on a Debian Jessie. Everthing
worked fine while installing and the check script says that
everything is OK. But after running a scan the reports page doesn't
show me a report. The heading says  "1-1 of 1 (total: 1)" but there
is no report listed in the table. Any idea how to solve this?

I have the same problem. I have just installed OpenVAS from the atomic 
repositories on a CentOS 7 server. Reports page shows "1 - 3 of 3 (total: 3)" 
but nothing in the list...

-Gerald
_______________________________________________
Openvas-discuss mailing list
[email protected]<mailto:[email protected]>
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss


_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to