Maintained by: NLnet Labs

internal error: looping module stopped

Ralph Dolmans
Tue Nov 7 13:29:28 CET 2017


Hi Jacob,

Not really, I haven't yet been able to figure out how use-caps-for-id
results in a looping module. I took a look at your log for bug #1749,
but the looping doesn't seem to occur there.

You mentioned that you are able to reproduce the issue. Can you maybe
share a log where the looping happens, while using a verbosity of 4?
Maybe that will give more insight.

Thanks,
-- Ralph

On 06-11-17 22:42, Jacob Hoffman-Andrews wrote:
> Any further thoughts on what could be behind this issue?
> 
> Thanks,
> Jacob
> 
> On 10/06/2017 03:15 PM, Jacob Hoffman-Andrews via Unbound-users wrote:
>> I also got a number of these errors on an upgrade to Unbound 1.6.6, on a
>> server doing about 100-300 qps. Similar config: use-caps-for-id, IPv6,
>> DNSSEC. No non-default modules enabled. I also have a test harness where
>> I can reproduce these. What additional information would be useful?
>>
>> On 09/20/2017 01:05 AM, Ralph Dolmans via Unbound-users wrote:
>>> Hi Ales,
>>>
>>> Thanks for reporting. Do you have any non-default module enabled
>>> (subnetcache, ipsecmod, respip, ..)?
>>>
>>> -- Ralph
>>>
>>> On 20-09-17 08:18, Aleš Rygl via Unbound-users wrote:
>>>> Hello,
>>>>
>>>> While inspecting unbound logs after an upgrade to Unbound 1.6.0-3+deb9u1 I have found some errors like this:
>>>>
>>>> Sep 19 12:40:45 unbound[16337:22] error: internal error: looping module stopped
>>>> Sep 19 12:40:45 unbound[16337:22] error: internal error: looping module stopped
>>>> Sep 19 12:41:00 unbound[16337:21] error: internal error: looping module stopped
>>>> Sep 19 12:41:00 unbound[16337:21] error: internal error: looping module stopped
>>>> Sep 19 12:41:01 unbound[16337:4] error: internal error: looping module stopped
>>>> Sep 19 12:41:01 unbound[16337:4] error: internal error: looping module stopped
>>>> Sep 19 12:41:46 unbound[16337:2e] error: internal error: looping module stopped
>>>> Sep 19 12:41:46 unbound[16337:2e] error: internal error: looping module stopped
>>>> Sep 19 12:42:32 unbound[16337:29] error: internal error: looping module stopped
>>>> Sep 19 12:42:32 unbound[16337:29] error: internal error: looping module stopped
>>>> Sep 19 12:43:11 unbound[16337:2a] error: internal error: looping module stopped
>>>> Sep 19 12:43:11 unbound[16337:2a] error: internal error: looping module stopped
>>>>
>>>> I have six instances of Unbound and I can see it on all of them. The load is up to 500qps, DNSSEC enabled, use-caps-for-id enabled, IPv6. 
>>>>
>>>> Thanks
>>>>
>>>> With regards
>>>> Ales
>>>>
>>