Re: [Cerowrt-devel] Problems with DNSsec on Comcast, with Cero 3.10.38-1/DNSmasq 4-26-2014

[Simon Kelley <simon@thekelleys.org.uk>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

A backtrace is the most important starting point. A query log _if_
it's query dependent, but that seems unlikely since it doesn't break
when forwarding to IPv4. An easy way to reproduce would be great :-)

I can do the same tests here, but it's a bit risky, since my IPv6 is
via a sixXS tunnel. If the tunnel goes down, it needs to do DNS
queries to bring it back up.

Cheers,

Simon.


On 09/01/15 08:52, Dave Taht wrote:
> I was able to lock up this version of dnsmasq twice: 100% cpu
> usage. No syscalls were visible from strace during the lockup.
> Lockups occurred once on nearly at boot, and the second time, after
> a few hours of casual usage, with only ipv6 upstreams, on
> cero-3.10.50-1.
> 
> furthermore, the only thing that kills it is a kill -9. I will
> build a non-stripped version in the morning... (and I do note that
> I was testing two things - one ipv6 upstreams only, and two,
> dnssec. Prior to this version I was using both ipv4 and ipv6
> upstreams, no issues, had dnssec on also, usually no issues)
> 
> Other suggestions for debugging the causes of a lockup requested
> (log all queries?)
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJUr/VzAAoJEBXN2mrhkTWizvcP/3eCyJEY6kwGSWvh+4QiDulK
CMsz1DJYbhYqu1w+oME287Hazd3LcneSZkn/CH05Qo9gLHNIjnQK48OvxaUPLtw5
rereV59vcgSgIVRyeuTJmVeF6Z4uL4kiNsWsNYWT32RNWfZpLQMrww9svrMuNQlN
2LZknand/1XJXVxDdAFOIyx6DIR5NFtRQPtntSr8GFwWMuvyM3PLEfF7Qu4RbrIt
pFAirlM+uiuUrGmCf1T5h8h9C7z++T7WXdFyCU6fmH7k6ZnXqYdl5OY0YkHeRhNF
UHbcd/Eqr5Onm6F0TZpQKKkKotfyyGoj3HkxBpCn1NrPafexRjUK4Rf4aQkys1ie
eLdiSvQafkLDssdPCuNV9+AGKUkZ6zolsf88gG6vxdksrQbVwFw9h25mdbizEw2M
KfvFbsJLYZ67U/FJGyW0trBc+t5j8Qv1KZCq4vhdiJfIn2dwOjtTn8IEHSZrbOIt
f7zvOKr25rR+fuFsw1PnSOXZwJDlBgKdRB7/1NYg2xrLnzL/luBgpfoOVoJNH1Cf
rzpsxZ3ZwzGfFZljokFbbXNWSTDiEgIDEzjLf9ie6+PJtUclhKbcqy35iGRaVRxL
tuWVgv24bQv5+FiSmPRCtytIJXhehCCqBeC9wXFOWvzFxILQ3n8THvvOwiRx6n4p
lWriAqwv+al2mC9CkthE
=9IWM
-----END PGP SIGNATURE-----