Dear all,
this message just appeared again in openvassd.messages, on both
OpenVAS 9 for CentOS and Kali.
At the same time, redis takes CPU to 100%, and tcpdump shows that no more
traffic is exanged with targets.
I put here some lines of hundreds...
[Fri Aug 17 13:41:07 2018][3803] Possible dependency cycle detected
1.3.6.1.4.1.25623.1.0.10330
[Fri Aug 17 13:41:07 2018][3803] Possible dependency cycle detected
1.3.6.1.4.1.25623.1.0.10330
[Fri Aug 17 13:41:07 2018][3803] Possible dependency cycle detected
1.3.6.1.4.1.25623.1.0.17975
[Fri Aug 17 13:41:07 2018][3803] Possible dependency cycle detected
1.3.6.1.4.1.25623.1.0.100062
[Fri Aug 17 13:41:07 2018][3803] Possible dependency cycle detected
1.3.6.1.4.1.25623.1.0.17975
[Fri Aug 17 13:41:07 2018][3803] Possible dependency cycle detected
1.3.6.1.4.1.25623.1.0.10330
[Fri Aug 17 13:41:07 2018][3803] Possible dependency cycle detected
1.3.6.1.4.1.25623.1.0.100152
[Fri Aug 17 13:41:07 2018][3803] Possible dependency cycle detected
1.3.6.1.4.1.25623.1.0.100489
[Fri Aug 17 13:41:07 2018][3803] Possible dependency cycle detected
1.3.6.1.4.1.25623.1.0.100082
[Fri Aug 17 13:41:07 2018][3803] Possible dependency cycle detected
1.3.6.1.4.1.25623.1.0.100151
[Fri Aug 17 13:41:07 2018][3803] Possible dependency cycle detected
1.3.6.1.4.1.25623.1.0.900239
[Fri Aug 17 13:41:07 2018][3803] Possible dependency cycle detected
1.3.6.1.4.1.25623.1.0.10330
[Fri Aug 17 13:41:07 2018][3803] Possible dependency cycle detected
Is really due to an hardcoded "100" in pluginscheduler.c??:
if (calls > 100)
{
log_write ("Possible dependency cycle detected %s",
dependencies_ptr[0]->plugin->oid);
return NULL;
}
Is there some workaround with binaries configuration, to avoid compiling
sources?
Many thanks. and have a nice weekend
Leonardo
_______________________________________________
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
