Re: mt.shmpool PANIC
Posted in 1996
rasto,
it helps to post a little background info, to even say that you don't
know what specifically was going on when this happened if this was the case.
this could be caused by any number of a million things, so with no background
info, all one can say is that there was a possible memory block trailer
corruption!
> --------------------------------------------------------------------------
> 17:40:40 Pool = 0x18fe020, Pool name = 1070, Blkhdr = 0x19c9d40
> 17:40:40 Block magic is 10790, expecting 10790
> 17:40:40 Possible memory block trailer corruption
> 17:40:40 mtshpool.c, line 2535, thread 1422, proc id 484,
> Condition Failed (CHECK_ALLOC_BLOCK), In (mt_shm_free)
> Thread(1422, sqlexec, 0, 1).
> 17:40:40 PANIC: Attempting to bring system down
> --------------------------------------------------------------------------
i saw this same thing yesterday. i accidentally did an onmode -M 40,
instead of an onmode -D 40, which attempted to modify my memory available
for pdq. this put all the queries that came after the currently executing
query into the wait queue, waiting on gate 5. (do an onstat -g mgm). the
system ran fine, except that queries that were attempting to use pdq hung,
waiting for the present query to finish, so the system could attempt to
do a memory reinit. (at this point, it is really a bug. i got an error
message in my log file that 40 was less than the allowable minimun. so
what is there to do after this? there shouldn't have been a reinit waiting
to happen).
anyway, the server was running fine, and queries could execute fine
as long as they had "set pdqpriority 0;" as the first statement. then, about
2 hours after this, the system went down with the same sort of message. now
whether the two are related, i and support don't know. i would suspect they
are, simply because the attempt to do a reinit should have been completely
aborted once it knew that the memory value was illegal.
i can either forget it for now, or try to reproduce it.
this is off the main subject, but thought i would post it anyway.
mickm