These are chat archives for CZ-NIC/knot-resolver

21st
Dec 2016
Ondřej Surý
@oerdnj
Dec 21 2016 12:47
@andir: If you are ready for another round of testing, the updated packages have a fix for the out-of-the-bailiwick glitch
Andreas Rammhold
@andir
Dec 21 2016 12:52
oerdnj: upgrading :-)
Andreas Rammhold
@andir
Dec 21 2016 12:58
well it SIG7's (BUS error) after a few seconds
Ondřej Surý
@oerdnj
Dec 21 2016 12:59
can you get us a coredump?
Andreas Rammhold
@andir
Dec 21 2016 12:59
just installed coredumpctl..
Ondřej Surý
@oerdnj
Dec 21 2016 13:04
@andir Can you remove the cache (rm /run/knot-resolver/cache/*.mdb) and try again? The crash in lmdb suggest something with the cache
Andreas Rammhold
@andir
Dec 21 2016 13:04
I'll do that just now.. was trying to find some liblmdb debug symbols without luck :/
Vladimír Čunát
@vcunat
Dec 21 2016 13:05
You can build with embedded lmdb and thus generate them just by -g
Andreas Rammhold
@andir
Dec 21 2016 13:07
oerdnj: it died again
but no coredump yet :/
ahh well... it did log 50GB of stuff... I'll have to remove the verbose flag or get largers disks for those tests.. I'll run it again with empty caches
Ondřej Surý
@oerdnj
Dec 21 2016 13:09
so it ate all the disk space? and it's crashing because lmdb fails to write to cache?
Andreas Rammhold
@andir
Dec 21 2016 13:10
well it worked before... i'm trying to reprodcue now :-)
Vladimír Čunát
@vcunat
Dec 21 2016 13:13
Out-of-space on cache write should be handled on our side, but it's certainly almost untested condition.
Actually, LMDB creates a holey file and mmaps it into memory. I'm not sure if it's possible to catch the situation when it accesses the part that has no disk space assigned yet - and the disk is full ATM.
Andreas Rammhold
@andir
Dec 21 2016 13:18
I did some tuning of the rsyslog settings.. they are rather VERBOSE on debian per default.. logging stuff >=2x + journald ...
hopefully that false result wont happen again