|Anonymous | Login||2023-12-05 10:08 EST|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001467||PacketFence||upstream||public||2012-06-14 10:58||2012-10-19 13:59|
|Target Version||Fixed in Version|
|Summary||0001467: OpenVAS tasks starts after 10 minutes|
i use OpenVAS in combination with Packetfence. If Packetfence insert a new scan task into OpenVAS the task only starts after 10 minutes. First the task is "requested" for 10min, then the task "run" for 15sec. If i start an task manuell, it waits 10 min.
|Tags||No tags attached.|
|fixed in git revision|
|fixed in mtn revision|
|This situation has been encountered several times during development of the OpenVAS integration.|
Post from Matthew Mundell on the OpenVAS mailing-list:
"When the Manager connects to the Scanner to start the task, the Scanner always sends all the details of the NVTs to the Manager. Processing of this might be what is taking the 10 minutes. This happens every time a client connects to the Manager."
|Asked Matthew / OpenVAS mailing about the correct way to triggers a scan using OMP.|
Reply from Matthew:
What you're doing is "correct". You could also use the same OMP connection
multiple times. That way the Manager would only connect to the Scanner the
first time. A new connection each time is more resistant to bugs and leaks
in the Manager though.
Discussion about Matthew's reply:
>>> What I'm looking for is the "correct" way to triggers scan on OpenVAS
>>> without having to wait that 10minute delay each time.
>> What you're doing is "correct".
> By correct you mean we can work something better?
What you are doing is the standard way. The GSA does it this way, for
>> You could also use the same OMP connection
>> multiple times. That way the Manager would only connect to the Scanner the
>> first time.
> That way we only face the 10 minutes delay the first time?
>> A new connection each time is more resistant to bugs and leaks
>> in the Manager though.
> But we'll face the 10 minutes delay at each connection?
This should speed up considerably in the future, if that's any consolation.
> So your recommandation would be to stay that way and wait for Openvas to
> speed up ?
Depends how bad 10 minutes is for you, and how much time you have to try
the alternative. The Scanner speedup could be a year or more away.
End of story:
It is an OpenVAS issue. We may try to keep the connection active from the first time but this may cause some memory leaks on the OpenVAS side.
It seems to be in the roadmap to fix this issue from the OpenVAS side.
|2012-06-14 10:58||dwuelfrath||New Issue|
|2012-06-14 10:58||dwuelfrath||Note Added: 0002769|
|2012-06-14 10:59||dwuelfrath||Note Added: 0002770|
|2012-06-14 11:00||dwuelfrath||Note Added: 0002771|
|2012-06-14 11:00||dwuelfrath||Status||new => assigned|
|2012-06-14 11:00||dwuelfrath||Assigned To||=> dwuelfrath|
|2012-06-14 14:32||dwuelfrath||Note Added: 0002785|
|2012-06-14 14:33||dwuelfrath||Note Added: 0002786|
|2012-06-14 14:33||dwuelfrath||Note Added: 0002787|
|2012-06-14 14:34||dwuelfrath||Note Added: 0002788|
|2012-06-15 09:48||obilodeau||Resolution||open => suspended|
|2012-06-15 09:48||obilodeau||Category||scanning => upstream|
|2012-06-15 09:48||obilodeau||Product Version||=> 3.2.0|
|2012-10-19 13:59||fgaudreault||Target Version||=> long-term|
|Copyright © 2000 - 2012 MantisBT Group|