I seem to have the same issue like the second one described below, running 
OpenVAS 7.

>From time to time settings like Target and Port Lists remain on the salve 
after a scan, and a new scan of the same target via the slave does not 
start.


28.05.2015----15:05:47"Openvas-discuss" 
<[email protected]> wrote on 28.05.2015 
15:05:47:

> From: Rene Behring <beh
[email protected]>> To: Openvas Mailingliste Englisch 
<openvas-discuss
@wald.intevation.org>, >
 Date: 28.05.2015 15:05> Subject: [Openvas-discuss] 
Master - Slave Problems> Sent by: "Openvas-discuss" <openvas-discuss-bounc
[email protected]
evation.org>> 
> Hello,> 
> i have some Problems with OpenVAS in Master/Slave mode. I got the 
> responsibility for OpenVAS a few days ago, so i dont know much about
> the Server Config or 
the initial conditions.> 
> After the Master has send all the scan settings to the Slave, the 
> Manger of the Slave has a CPU workload of 100% for 15 minutes. 
> During that time you can 
not access the Manager.> The second problem is, that not all settings will 
be deleted on the 
> Slave. So the portlist and the scan confi
gs remain on the Slave.> 
> Another problem is, that when the Scan Target config is still on the
> Slave i cant start another Scan for that Target. So i requested the 
> Scan on the Master, the Master sends all the scan configs but the 
> Slave does not start the scan. After i deleted the old target config

> the new scan starts.> 
> Is it normal, that the Manager has such a high and long cpu workload
> after receiving the scan config? Or is the problem, that there are 
> so many sca
n configs an portlists?> Why does these things remain on the Server after 
the scan? I thought
> that the master deletes all the settings on th
e Slave after the scan.> 
> Both Servers are 
RHEL and use OpenVAS 7.> 
> Rene Behring_______________________________________________
> Openvas-discuss mailing list
> [email protected]
> 
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to