For debugging help here is the output of check-setup:
[root@scanner yum.repos.d]# openvas-check-setup
openvas-check-setup 2.2.0
Test completeness and readiness of OpenVAS-5
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 3.3.1.
OK: OpenVAS Scanner CA Certificate is present as
/var/lib/openvas/CA/cacert.pem.
OK: NVT collection in /var/lib/openvas/plugins contains 25498 NVTs.
WARNING: Signature checking of NVTs is not enabled in OpenVAS
Scanner.
SUGGEST: Enable signature checking (see
http://www.openvas.org/trusted-nvts.html).
Step 2: Checking OpenVAS Manager ...
OK: OpenVAS Manager is present in version 3.0.1.
OK: OpenVAS Manager client certificate is present as
/var/lib/openvas/CA/clientcert.pem.
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 56.
OK: OpenVAS Manager expects database at revision 56.
OK: Database schema is up to date.
OK: OpenVAS Manager database contains information about 25498 NVTs.
OK: xsltproc found.
Step 3: Checking OpenVAS Administrator ...
OK: OpenVAS Administrator is present in version 1.2.0.
OK: At least one user exists.
OK: At least one admin user exists.
Step 4: Checking Greenbone Security Assistant (GSA) ...
OK: Greenbone Security Assistant is present in version 3.0.1.
Step 5: Checking OpenVAS CLI ...
OK: OpenVAS CLI version 1.1.4.SVN.
Step 6: Checking Greenbone Security Desktop (GSD) ...
ERROR: No Greenbone Security Desktop (gsd) found or too old.
FIX: Please install Greenbone Security Desktop 1.1.0.
On 6/18/2012 1:29 PM, Russell Jones wrote:
I added a schedule that was supposed to repeat every 4 weeks using
GSA. After doing so the manager process bombed and I have been unable
to start it again. Attempting to start it up after adding the schedule
yields:
[root@scanner ~]# service openvas-manager start
Starting openvas-manager:
[ OK ]
[root@scanner ~]# openvasmd:
/builddir/build/BUILD/openvas-manager-3.0.1/src/manage.c:3253:
manage_schedule: Assertion `first <= now' failed.
[root@scanner ~]#
[root@scanner ~]#
[root@scanner ~]# /etc/init.d/openvas-manager start
Starting openvas-manager:
[ OK ]
[root@scanner ~]# openvasmd:
/builddir/build/BUILD/openvas-manager-3.0.1/src/manage.c:3253:
manage_schedule: Assertion `first <= now' failed.
[root@scanner ~]#
This is latest openvas available on CentOS 6.2. Any ideas how I can
get my management process back?
Thanks :-)
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
