Hello, I am a bit confused about my process list. I have an OpenVAS_Setup with one master and one slave server. I just started a scan of 4 hosts which uses my slave server. Before the scan there was on process of "openvasmd" running on my slave, right now in the middle of the scan there are 3 instances running. I had the same issue yesterday after which I had 2 instances running till the moment I killed one because i was suspicious. Is this working as designed? I am aware that there will be multiple instances of openvassd running while scanning but I assumed there would alwasy only be one openvasmd. Also I noticed that on my slave 2 instances of gsad are running. Seems not right as well. Someone have a clue or an idea how to troubleshoot this behaviour?
Additional Info: I wrote myself an simple init-skript since I compiled OpenVAS from source, maybe something ist broken here. Does anybody already have an init-script for OpenVAS8 on Debian? Any help is appreciated. Greetings, Niklas Klein Linux-Version: Linux lx-openvas 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u1 (2017-02-22) x86_64 GNU/Linux openvas-check-setup output: Step 1: Checking OpenVAS Scanner ... OK: OpenVAS Scanner is present in version 5.0.8. OK: OpenVAS Scanner CA Certificate is present as /usr/local/var/lib/openvas/CA/cacert.pem. OK: redis-server is present in version v=2.8.17. OK: scanner (kb_location setting) is configured properly using the redis-server socket: /tmp/redis.sock OK: redis-server is running and listening on socket: /tmp/redis.sock. OK: redis-server configuration is OK and redis-server is running. OK: NVT collection in /usr/local/var/lib/openvas/plugins contains 53952 NVTs. OK: Signature checking of NVTs is enabled in OpenVAS Scanner. OK: The NVT cache in /usr/local/var/cache/openvas contains 54519 ( tel:54519) files for 53952 NVTs. Step 2: Checking OpenVAS Manager ... OK: OpenVAS Manager is present in version 6.0.10. OK: OpenVAS Manager client certificate is present as /usr/local/var/lib/openvas/CA/clientcert.pem. OK: OpenVAS Manager database found in /usr/local/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 146. OK: OpenVAS Manager expects database at revision 146. OK: Database schema is up to date. OK: OpenVAS Manager database contains information about 53952 NVTs. OK: At least one user exists. OK: OpenVAS SCAP database found in /usr/local/var/lib/openvas/scap-data/scap.db. OK: OpenVAS CERT database found in /usr/local/var/lib/openvas/cert-data/cert.db. OK: xsltproc found. Step 3: Checking user configuration ... WARNING: Your password policy is empty. SUGGEST: Edit the /usr/local/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 6.0.12. 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 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: Greenbone Security Assistant is running and listening on all interfaces. WARNING: Greenbone Security Assistant is listening on port 8080, which is NOT the default port! (This is fine! NK) SUGGEST: Ensure Greenbone Security Assistant is listening on one of the following ports: 80, 443, 9392. Step 8: Checking nmap installation ... WARNING: Your version of nmap is not fully supported: 6.47 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. 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.
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
