On Montag, 4. August 2014, red0queen wrote: > 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.
I have no idea why this happens for you. It must be something unrelated to the actual starting of the slave scan. It is even possible to have no running openvassd at all on the master node when starting a scan on a slave node. -- Dr. Jan-Oliver Wagner | +49-541-335084-0 | http://www.greenbone.net/ Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 202460 Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
