[Pkg-dns-devel] Bug#819049: Bug#819049: unbound stopped suddenly.

[Shogo Mori]

Hi, Robert Edmonds

> Does unbound regularly crash for you with this error message, or is this
> the first occurrence?

this is first occurrence.

> My suggestion would be to upgrade the version of unbound that you are
> running. Based on the version number, you are probably running wheezy
> (oldstable). You can install unbound 1.4.22 from wheezy-backports, or by
> upgrading to jessie (stable). If you upgrade to jessie, you can also try
> the very latest upstream version (1.5.8) from jessie-backports.

I use wheezy. If possible, backports doesn't want to use.
It is because of stability concerns. 

You cannot modify the 1.4.17 ?



On Wed, 23 Mar 2016 14:00:08 -0400
Robert Edmonds <edmonds at debian.org> wrote:

> Shogo Mori wrote:
> > Hello. Unbound stopped suddenly. condition of occur is unknown.
> > can you fix this problem ?
> > 
> > *log messages
> > Mar  5 07:09:50 dns-cache6 unbound: [3881:b] error: validator: bad event module_event_reply
> > Mar  5 07:09:50 dns-cache6 unbound: [3881:b] fatal error: services/outside_network.c:1508: serviced_callbacks: pointer whitelist fptr_whitelist_serviced_query(p->cb) failed
> 
> Hi, Shogo Mori:
> 
> Does unbound regularly crash for you with this error message, or is this
> the first occurrence?
> 
> This log message is almost identical to the one reported on the
> unbound-users mailing list here:
> 
>     https://unbound.net/pipermail/unbound-users/2012-July/002501.html
> 
> The upstream author suggests upgrading to a newer version in that
> thread.
> 
> My suggestion would be to upgrade the version of unbound that you are
> running. Based on the version number, you are probably running wheezy
> (oldstable). You can install unbound 1.4.22 from wheezy-backports, or by
> upgrading to jessie (stable). If you upgrade to jessie, you can also try
> the very latest upstream version (1.5.8) from jessie-backports.
> 
> -- 
> Robert Edmonds
> edmonds at debian.org