internal error looping module (unbound 1.7.3)
wouter at nlnetlabs.nl
Tue Sep 11 07:11:01 UTC 2018
On 9/10/18 10:40 PM, nusenu via Unbound-users wrote:
> a log entry says:
> error: internal error: looping module (iterator) stopped
> but the DNS service still works.
The error says that the iterator modules is called too many times.
Could be a flaw in eg. qname minimisation that gets stuck in a loop. Or
it could be some other flaw, eg. a user (script) module that keeps
(re-)starting the iterator module. It would be interesting to see what
query that was for.
This patch should log the query name at verbosity level 1.
--- services/mesh.c (revision 4890)
+++ services/mesh.c (working copy)
@@ -1392,7 +1392,7 @@
/* module is looping. Stop it. */
log_err("internal error: looping module (%s) stopped",
- log_query_info(VERB_QUERY, "pass error for qstate",
+ log_query_info(VERB_OPS, "pass error for qstate",
s = module_error;
Then perhaps we can repeat and find out what the problem is. Eg. some
sort of infinite loop for that query.
The other patch you are using is not involved in this bug, I think.
Best regards, Wouter
> Unfortunately there is nothing else in the logs (running in verbosity 1)
> Is this an error where unbound automatically recovers from?
> Should one restart unbound even though it appears to work fine after such an error?
> version: unbound 1.7.3 + patch running on FreeBSD
> kind regards,
>  https://nlnetlabs.nl/pipermail/unbound-users/2018-July/005349.html
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the Unbound-users