Le 03/08/2014 19:07, Jan-Oliver Wagner a écrit : > Am Montag, 28. Juli 2014, 12:59:07 schrieb red0queen: >> I was trying the master slave mode and I have a strange behavior : when >> the scan end, a scan process (openvassd) stay alive on the master node, >> and use 100% cpu. If I lauch another scan, a second will stay alive with >> full cpu usage (the master node is a dual core). I must to kill this >> process by hand to avoid the load. > are you sure the openvassd process with 100% is on the master node? Yes. When I start a delegated analysis, the master open a new openvassd "listen 127.0.0.1" (in addition of the first openvassd lauched at startup) . At the end of the scan, all the openvassd lauched on the slave ends normally, but the openvassd running on the master rise at 100% of cpu usage. All seems fine on the web gui, I just need to kill the new openvassd on the master node manually.
> Running a scan on a slave node means that openvasmd of master node will talk > to > the openvasmd on the slave node which then talks to the openvassd on that > node. For my first try, the slave openvasmd listen the external address, the master listen localhost. I've try to configure the master openvasmd by the same way, but I have the same problem. > In other words: for a slave scan, the openvassd on the master node > is not issued at all. >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
