Maintained by: NLnet Labs

[Unbound-users] looping module stopped

Gareth Hopkins
Tue Sep 14 09:10:35 CEST 2010


Hi Wouter,

Thanks for the reply.

I'll enable logging on one of my dev boxes and see if I get the same
errors.

Latest from the production box

Sep 13 18:59:05 unbound[96721:0] error: internal error: looping module
stopped
Sep 13 18:59:05 unbound[96721:0] info: pass error for qstate <_sipinternal._
tcp.slb.com. SRV IN>
Sep 13 19:44:01 unbound[96721:0] error: internal error: looping module
stopped
Sep 13 19:44:01 unbound[96721:0] info: pass error for qstate
<_sipinternaltls._tcp.slb.com. SRV IN>
Sep 13 20:31:11 unbound[96721:0] error: internal error: looping module
stopped
Sep 13 20:31:11 unbound[96721:0] info: pass error for qstate <_sipinternal._
tcp.slb.com. SRV IN>
Sep 13 20:48:15 unbound[96721:0] error: internal error: looping module
stopped
Sep 13 20:48:15 unbound[96721:0] info: pass error for qstate
<_sipinternaltls._tcp.slb.com. SRV IN>
Sep 13 22:07:07 unbound[96721:0] error: internal error: looping module
stopped
Sep 13 22:07:07 unbound[96721:0] info: pass error for qstate
<_sipinternaltls._tcp.slb.com. SRV IN>
Sep 14 06:35:03 unbound[96721:0] error: internal error: looping module
stopped
Sep 14 06:35:03 unbound[96721:0] info: pass error for qstate
<_sipinternaltls._tcp.slb.com. SRV IN>
Sep 14 07:04:02 unbound[96721:0] error: internal error: looping module
stopped
Sep 14 07:04:02 unbound[96721:0] info: pass error for qstate
<_sipinternaltls._tcp.slb.com. SRV IN>
Sep 14 07:24:37 unbound[96721:0] error: internal error: looping module
stopped
Sep 14 07:24:37 unbound[96721:0] info: pass error for qstate
<_sipinternaltls._tcp.slb.com. SRV IN>

Cheers,

Gareth

On Fri, Sep 10, 2010 at 11:51 AM, W.C.A. Wijngaards <wouter at nlnetlabs.nl>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Gareth,
>
> This error means that a module was activated 1000 times (or so), which
> is impossible or unusual, and should not happen.  The query got
> SERVFAIL, and it prints this log message.
>
> This should not be happening, usually, lookups fail much earlier.
> My quick try says that the name is an NXDOMAIN.  And works fine for me.
>  So SERVFAIL instead of NXDOMAIN is no great loss (for the users), the
> failsafe activated and nothing bad happened.
>
> So, the question is why is it looping (the state machine is activated
> too often)?
>
> I would like to see a high verbosity trace of a resolution of this name
> when it says it is looping; what is that module doing?
>
> Best regards,
>   Wouter
>
> On 09/10/2010 09:59 AM, Gareth Hopkins wrote:
> > Hi,
> >
> > I'm seeing the following in my unbound logs
> > Sep 09 23:53:20 unbound[96721:0] error: internal error: looping module
> > stopped
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkyJ/6wACgkQkDLqNwOhpPgaeACdGtBW8qL6dUV/QSmEL9WGq3yI
> NloAn3lsFwcrz9OnaP33GuxCJoyOm79z
> =urVd
> -----END PGP SIGNATURE-----
> _______________________________________________
> Unbound-users mailing list
> Unbound-users at unbound.net
> http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unbound.nlnetlabs.nl/pipermail/unbound-users/attachments/20100914/44ceb9be/attachment.htm>