[Openvas-commits] r10543 - trunk/doc/website
scm-commit@wald.intevation.org
scm-commit at wald.intevation.org
Tue Mar 15 14:27:39 CET 2011
Author: mwiegand
Date: 2011-03-15 14:27:38 +0100 (Tue, 15 Mar 2011)
New Revision: 10543
Modified:
trunk/doc/website/setup-and-start.htm4
Log:
Add documentation for --server parameter and for checking for running services. Update examples. Remove now superfluous "Launching services" section.
Modified: trunk/doc/website/setup-and-start.htm4
===================================================================
--- trunk/doc/website/setup-and-start.htm4 2011-03-15 12:24:58 UTC (rev 10542)
+++ trunk/doc/website/setup-and-start.htm4 2011-03-15 13:27:38 UTC (rev 10543)
@@ -48,7 +48,9 @@
<p>
openvas-check-setup will now analyze the state of your OpenVAS 4 installation
-and propose fixes should it detect any errors or misconfigurations.
+and propose fixes should it detect any errors or misconfigurations. It will also
+check if all required OpenVAS services are running and listening on the correct
+ports.
</p>
<p>
@@ -57,6 +59,17 @@
<a href="http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss">OpenVAS Users Mailing List</a>.
</p>
+<p>
+If you want to install the OpenVAS services on a server and you do not need
+clients like OpenVAS CLI or GSD in your installation you can skip the checks for
+these modules by starting openvas-check-setup with the --server parameter
+instead:
+</p>
+
+<pre>
+./openvas-check-setup --server
+</pre>
+
<h3>Examples of openvas-check-setup results</h3>
<p>
@@ -69,7 +82,7 @@
</h4>
<pre>
-openvas-check-setup 0.3.0
+openvas-check-setup 2.0.1
Test completeness and readiness of OpenVAS 4
Please report us any non-detected problems and
@@ -78,21 +91,24 @@
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.1.
+ 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 20004 NVTs.
+ OK: NVT collection in /var/lib/openvas/plugins contains 20380 NVTs.
Step 2: Checking OpenVAS Manager ...
- OK: OpenVAS Manager is present in version 2.0.0.
+ OK: OpenVAS Manager is present in version 3.0.0.
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: sqlite3 found, extended checks of the OpenVAS Manager installation enabled.
- OK: OpenVAS Manager database is at revision 39.
- OK: OpenVAS Manager expects database at revision 39.
+ OK: OpenVAS Manager database is at revision 42.
+ OK: OpenVAS Manager expects database at revision 42.
OK: Database schema is up to date.
OK: xsltproc found.
Step 3: Checking OpenVAS Administrator ...
- OK: OpenVAS Administrator is present in version 1.1.0.
+ OK: OpenVAS Administrator is present in version 1.1.2.
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'
@@ -113,7 +129,7 @@
</h4>
<pre>
-openvas-check-setup 0.3.0
+openvas-check-setup 2.0.1
Test completeness and readiness of OpenVAS 4
Please report us any non-detected problems and
@@ -122,29 +138,42 @@
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.1.
+ 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 20004 NVTs.
+ OK: NVT collection in /var/lib/openvas/plugins contains 20380 NVTs.
Step 2: Checking OpenVAS Manager ...
- OK: OpenVAS Manager is present in version 2.0.0.
+ OK: OpenVAS Manager is present in version 3.0.0.
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: sqlite3 found, extended checks of the OpenVAS Manager installation enabled.
- OK: OpenVAS Manager database is at revision 39.
- OK: OpenVAS Manager expects database at revision 39.
+ OK: OpenVAS Manager database is at revision 42.
+ OK: OpenVAS Manager expects database at revision 42.
OK: Database schema is up to date.
OK: xsltproc found.
Step 3: Checking OpenVAS Administrator ...
- OK: OpenVAS Administrator is present in version 1.1.0.
+ OK: OpenVAS Administrator is present in version 1.1.2.
OK: At least one user exists.
- OK: At least admin user exists.
+ OK: At least one admin user exists.
Step 4: Checking Greenbone Security Assistant (GSA) ...
- OK: Greenbone Security Assistant is present in version 2.0+rc4.
+ OK: Greenbone Security Assistant is present in version 3.0.0.
Step 5: Checking OpenVAS CLI ...
OK: OpenVAS CLI version 1.1.2.
Step 6: Checking Greenbone Security Desktop (GSD) ...
- OK: Greenbone Security Desktop is present in Version 1.1+beta2.
+ OK: Greenbone Security Desktop is present in Version 1.1.1.
+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.
+ OK: Greenbone Security Assistant is running and listening on all interfaces.
+ OK: Greenbone Security Assistant is listening on port 9392, which is the default port.
It seems like your OpenVAS 4 installation is OK.
@@ -154,105 +183,3 @@
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.
</pre>
-<h3>Launching services</h3>
-
-<p>
-Once you have made sure that your OpenVAS 4 installation is in a working state,
-you may start the individual services which make up OpenVAS 4.
-</p>
-
-<p>
-Keep in mind that this is only one way to start the services. You may choose
-different ports and use further command line parameters for specific behaviour
-of the daemons. Furthermore, your distribution may already provide optimized
-scripts for starting the OpenVAS services.
-</p>
-
-<ol>
-
-<li> <p><b>Launch Scanner daemon:</b></p>
-
- <pre>
-openvassd
- </pre>
-
- <p>
- This may take several minutes when starting for the first time.
- The scanner daemon now runs in the background
- and serves requests at port 9391.
- </p>
-
- <p>
- Check whether it is running properly:
- </p>
-
- <pre>
-netstat -tlp | grep 9391
- </pre>
-</li>
-
-<li> <p><b>Launch Manager daemon:</b></p>
-
- <pre>
-openvasmd
- </pre>
-
- <p>
- The manager daemon now runs in the background
- and serves requests at port 9390.
- </p>
-
- <p>
- Check whether it is running properly:
- </p>
-
- <pre>
-netstat -tlp | grep 9390
- </pre>
-</li>
-
-<li> <p><b>Launch Administrator daemon:</b></p>
-
- <pre>
-openvasad
- </pre>
-
- <p>
- The administrator daemon now runs in the background
- and serves requests at port 9393.
- </p>
-
- <p>
- Check whether it is running properly:
- </p>
-
- <pre>
-netstat -tlp | grep 9393
- </pre>
-</li>
-
-<li> <p><b>Launch GSA daemon:</b></p>
-
- <pre>
-gsad -p 8000
- </pre>
-
- <p>
- The GSA daemon now runs in the background
- and serves requests at port 8000.
- </p>
-
- <p>
- Check whether it is running properly:
- </p>
-
- <pre>
-netstat -tlp | grep 8000
- </pre>
-
- <p>
- Or simply open "https://localhost:8000" in your browser.
- </p>
-</li>
-
-</ol>
More information about the Openvas-commits
mailing list