Oliver try the following commands, in any order, with sudo or as root :
greenbone-nvt-sync greenbone-scap-sync greenbone-cert-sync Hope this helps On 17 July 2017 at 23:49, oliver demich <[email protected]> wrote: > Hi there, > > after various request and trying i found myself blocked , my scans stops > at 1% and when i open the browser, after connecting to openvas and logging > inside, the panel in Feeds says that my nvt feed are old of 37 days ( 6 for > the others). I tried also to run openvas-nvt-sync but the terminal > responds with unknown command and so i cannot do any update. > > my system is virtual machine with kali linux 2017.1 ver > > the openvas-check-setup gives this report : > > root@kali2017:~# openvas-check-setup > openvas-check-setup 2.3.7 > 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.9. OK: scanner (kb_location setting) is configured properly > using the redis-server socket: /var/run/redis/redis.sock OK: > redis-server is running and listening on socket: > /var/run/redis/redis.sock. OK: redis-server configuration is OK and > redis-server is running. OK: NVT collection in > /var/lib/openvas/plugins contains 53750 NVTs. WARNING: Signature > checking of NVTs is not enabled in OpenVAS Scanner. SUGGEST: Enable > signature checking (see http://www.openvas.org/trusted-nvts.html > <http://www.openvas.org/trusted-nvts.html>). OK: The NVT cache in > /var/cache/openvas contains 53750 files for 53750 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 53748 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. WARNING: OpenVAS Manager is > running and listening only on the local interface. This means that > you will not be able to access the OpenVAS Manager from the outside > using GSD or OpenVAS CLI. SUGGEST: Ensure that OpenVAS Manager > listens on all interfaces unless you want a local service > only. OK: Greenbone Security Assistant is listening on port 80, > which is the default port.Step 8: Checking nmap installation ... OK: > nmap is present in version 5.51.6.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-9 installation is OK.If you think it is not > OK, please report your observationand help us to improve this check > routine:http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > <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.* > > _______________________________________________ > Openvas-discuss mailing list > [email protected] > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss > -- -- GPG key fingerprint: 07DF B95B DB58 57B6 9656 682E 830A D092 288E F017 GPG public key available on pgp(dot)net key server
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
