Alan DeKok <aland@deployingradius.com> wrote:
Then shortly after restarting it: ---- Program received signal SIGABRT, Aborted. [Switching to Thread 0x4f492950 (LWP 23808)] 0x00007f0060554ed5 in raise () from /lib/libc.so.6 (gdb) wher #0 0x00007f0060554ed5 in raise () from /lib/libc.so.6 #1 0x00007f00605563f3 in abort () from /lib/libc.so.6 #2 0x00000000004281f2 in rad_assert_fail (file=0x4455ef "threads.c", line=406, expr=0x445628 "(*request)->magic == REQUEST_MAGIC") at util.c:363 #3 0x0000000000426adf in request_dequeue (request=0x7f004c006f30, fun=0x4f491d30) at threads.c:406
That shouldn't happen... ever!
In fact, I've never seen it happen. It can occur only when memory is free'd, and still used.
[snipped]
As for the latter one, that's new to me. Alas it is going to be difficult to repeat this 'experiment' as I would have to turn power off to one of our server rooms...tends to annoy the yokels.
It should either happen a lot, or not at all.
Well as I said it is the first time I have seen it and I have been running this code straight since that commit came out on the 5th. So we cannot say 'not at all'. Want to put it down to a neutrino burst? :) Cheers -- Alexander Clouter .sigmonster says: Shut off engine before fueling.