Summary: | net-dns/bind-9.9.0[geoip,threads] fails to start wird an internal error: task.c:1637: REQUIRE(task->state == task_state_running) failed, back trace | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mark Nowiasz <mark+gentoobugs> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bind+disabled |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
named.conf
Patch to fix broken geoip-9.8.0-P1 application to 9.9.0 |
Description
Mark Nowiasz
2012-03-01 09:03:34 UTC
Please show me "emerge --info bind". Can you also show me your config(s) + /etc/conf.d/named? taks.c sounds related to the recent threading changes... (In reply to comment #1) > Please show me "emerge --info bind". OK: net-dns/bind-9.8.1_p1 was built with the following: USE="caps geoip idn ipv6 (multilib) ssl threads xml -berkdb -dlz -doc -gost -gssapi -ldap -mysql -odbc -pkcs11 -postgres -rpz -sdb-ldap (-selinux) -static-libs -urandom" > Can you also show me your config(s) + /etc/conf.d/named? I'll attach named.conf. Created attachment 303847 [details]
named.conf
named.conf
Ok, this is related to the geoip patch. I'd suggest to disable it since you don't seem to use it at all. Created attachment 303893 [details, diff]
Patch to fix broken geoip-9.8.0-P1 application to 9.9.0
This is a side-effect of this patch being applied with -F != 0. The patch was applied incorrectly, causing a geoip function to be called from the wrong bind function. Whatever mechanism applies these patches should set "patch -F0", since fuzz is almost guaranteed to cause failure. Attached is a patch which should apply to a badly-patched 9.8.x, and the official 9.9.0 patch is now up on http://code.google.com/p/bind-geoip/. Thanks for the update, Ken! Fixed in CVS, if you want to use bind with geoip support then please re-sync in about 2-3 hours and try again. Thanks for your bug report! @base-system: Could you guys please check if the named "-F" parameter would useful for us? See bug 411183 re epatch/-F. Closing now. |