Hello Everyone, I have OPENVAS9 on Kali. I can't run a scheduled task, manual tasks works ok but not scheduled. Any solution or advice on how to fix ?
thank you, Josemar Brazil see below more details: root@machine# tail -f /var/log/openvas/openvasmd.log md manage:WARNING:2017-07-25 17h07.36 utc:28225: manage_schedule: child failed md manage:WARNING:2017-07-25 17h07.36 utc:28225: reschedule_task: rescheduling task '4d5b8fa2-358e-469c-8901-6ef621d676bd' md manage:WARNING:2017-07-25 17h07.51 utc:28228: manage_schedule: child failed md manage:WARNING:2017-07-25 17h07.51 utc:28228: reschedule_task: rescheduling task '4d5b8fa2-358e-469c-8901-6ef621d676bd' md manage:WARNING:2017-07-25 17h08.06 utc:28235: manage_schedule: child failed md manage:WARNING:2017-07-25 17h08.06 utc:28235: reschedule_task: rescheduling task '4d5b8fa2-358e-469c-8901-6ef621d676bd' md manage:WARNING:2017-07-25 17h08.22 utc:28238: manage_schedule: child failed md manage:WARNING:2017-07-25 17h08.22 utc:28238: reschedule_task: rescheduling task '4d5b8fa2-358e-469c-8901-6ef621d676bd' md manage:WARNING:2017-07-25 17h08.28 utc:28243: manage_schedule: child failed md manage:WARNING:2017-07-25 17h08.28 utc:28243: reschedule_task: rescheduling task '4d5b8fa2-358e-469c-8901-6ef621d676bd' ----- root@machine:~# 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 54230 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 54232 files for 54230 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 54224 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 443, which is the default port. Step 8: Checking nmap installation ... WARNING: Your version of nmap is not fully supported: 7.50 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. WARNING: Could not find rpm binary, LSC credential package generation for RPM and DEB based targets will not work. SUGGEST: Install rpm. WARNING: Could not find makensis binary, LSC credential package generation for Microsoft Windows targets will not work. SUGGEST: Install nsis. It seems like your OpenVAS-9 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. root@machine:~# ---------------------- root@machine:~# uname -a Linux machine 4.9.0-kali4-amd64 #1 SMP Debian 4.9.30-2kali1 (2017-06-22) x86_64 GNU/Linux root@machine:~#
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
