If i do it manually it takes for ever loading all the plugins
[edit]
I came back this morning and it had started, but I still do see this never working
Code:
# ./openvas-check-setup
openvas-check-setup 2.0.6
Test completeness and readiness of OpenVAS-4
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.2.3.
OK: OpenVAS Scanner CA Certificate is present as /var/lib/openvas/CA/cacert.pem.
OK: NVT collection in /var/lib/openvas/plugins contains 21019 NVTs.
Step 2: Checking OpenVAS Manager ...
OK: OpenVAS Manager is present in version 2.0.3.
OK: OpenVAS Manager client certificate is present as /var/lib/openvas/CA/clientcert.pem.
ERROR: No OpenVAS Manager database found. (Tried: /var/lib/openvas/mgr/tasks.db)
FIX: Run 'openvasmd --rebuild' while OpenVAS Scanner is running.
ERROR: Your OpenVAS-4 installation is not yet complete!
Please follow the instructions marked with FIX above and run this
script again.
If you think this result is wrong, 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.
# openvasmd --rebuild
Aborted
# service openvas-scanner status
openvassd (pid 813200) is running...
# service openvas-manager status
-l is stopped
# service openvas-manager start
Starting openvas-manager:
[ OK ]
# service openvas-manager status
-l is stopped
So apparently it didnt like that it didnt create the db file, so I created an empty one and now that all is ok
Code:
# touch /var/lib/openvas/mgr/tasks.db
# openvasmd --backup
# openvasmd --rebuild
# service openvas-manager status
-l is stopped
# service openvas-manager start
Starting openvas-manager:
[ OK ]
# service openvas-manager status
-l (pid 463527) is running...
Now the setup verification script is complaining about something else
Code:
# ./openvas-check-setup --server
openvas-check-setup 2.0.6
Test completeness and readiness of OpenVAS-4
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.
Step 1: Checking OpenVAS Scanner ...
OK: OpenVAS Scanner is present in version 3.2.3.
OK: OpenVAS Scanner CA Certificate is present as /var/lib/openvas/CA/cacert.pem.
OK: NVT collection in /var/lib/openvas/plugins contains 21019 NVTs.
Step 2: Checking OpenVAS Manager ...
OK: OpenVAS Manager is present in version 2.0.3.
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 41.
OK: OpenVAS Manager expects database at revision 41.
OK: Database schema is up to date.
OK: OpenVAS Manager database contains information about 21019 NVTs.
OK: xsltproc found.
[b]Step 3: Checking OpenVAS Administrator ...
ERROR: No OpenVAS Administrator (openvasad) found.
FIX: Please install OpenVAS Administrator.[/b]
ERROR: Your OpenVAS-4 installation is not yet complete!
Please follow the instructions marked with FIX above and run this
script again.
If you think this result is wrong, 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.
So it wanted me to install openvas-administrator which didnt auto install with the yum install openvas command previously.
and even though I did this from the start, it now wants me to create a user
Code:
Step 3: Checking OpenVAS Administrator ...
OK: OpenVAS Administrator is present in version 1.1.1.
OK: At least one user exists.
ERROR: No admin user found. You need to create at least one admin user to log in.
FIX: Create a user using 'openvasad -c 'add_user' -n <name> -r Admin'
# openvasad -c 'add_user' -n ovAdmin -r Admin
Enter password:
ad main:MESSAGE:465416:2011-04-26 09h22.41 PDT: No rules file provided, the new user will have no restrictions.
ad main:MESSAGE:465416:2011-04-26 09h22.41 PDT: User ovAdmin has been successfully created.
it also didnt start the openvas administrator, so I had to start that manually as well.
Now it seems to be "ok" except that it always complains that the GSA is not bound to anything other than the local interface, and says it fixes it, but it says this every time - how can I make that permanent?
Code:
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.
OK: OpenVAS Administrator is running and listening on all interfaces.
OK: OpenVAS Administrator is listening on port 9393, which is the default port.
[b]WARNING: Greenbone Security Assistant is running and listening only on the local interface. This means that you will not be able to access the Greenbone Security Assistant from the outside using a web browser.
SUGGEST: Ensure that Greenbone Security Assistant listens on all interfaces.
OK: Greenbone Security Assistant is listening on port 9392, which is the default port.[/b]
It seems like your OpenVAS-4 installation is OK.
Code:
# netstat -an | grep 939
tcp 0 0 0.0.0.0:9390 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:9391 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:9392 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:9393 0.0.0.0:* LISTEN