[Unbound-users] Unbound from EPEL segfaults at start

Maik Zumstrull maik.zumstrull at rz.uni-karlsruhe.de
Tue Mar 23 18:15:14 UTC 2010

[Accidentally didn't send to the list, resending.]

Paul Wouters wrote:

> On Mon, 22 Mar 2010, Maik Zumstrull wrote:
> > I'm trying to setup an Unbound box, only for testing and evaluation
> > at this point. I've put RHEL 5.4 and unbound from EPEL on it and
> > get this:
> >
> > kernel: unbound[3493]: segfault at 00000016000004ae rip
> > 0000003fd48750ed rsp 0000000041b3dee0 error 4
> > kernel: unbound[3495]: segfault at 00000016000004ae rip
> > 0000003fd48750ed rsp 0000000042f3fee0 error 4
> On what architecture is this?


> Can you get a gdb trace on this?

Should be possible, I'll get back to you.

> > Unbound from EPEL is a bit outdated, of course, so maybe a newer
> > version would be enough to fix it.
> Sorry for being a few versions behind on the EL-5 version. I will try
> and fix it over the next couple of days.

I managed to get 1.4.3 compiled using Fedora CVS, but I don't think the
package is particularly stable. I had zero experience building RPMs
before today, I'm more of a Debian person. It doesn't segfault on
startup though and answers to queries. Upper limit seems to be a little
less than 15000 qps according to resperf, but I haven't fine-tuned the
configuration yet.

More information about the Unbound-users mailing list