Mysql Dying at random times - points to a lib issue? - sollved
drumslayer2 at yahoo.com
Mon Oct 10 16:46:11 PDT 2005
Just to follow up to my own post (and adding FreeBSD
Questions)- I wanted to share that oddly enough, going
backwards and installing FreeBSD 4.11 with Mysql 4.11
With LinuxThreads solved the problem of the database
I would love any opinions on why this could be.
It seems to have found a possible SCSI issue, but so
far MYSQL hasn't died in 36 hrs. it usualy was at
least once every 8-12.
Tyan S2882 MB with one Opteron 248 - 4 gigs of ram
Was FreeBSD 5.4-RELEASE-p6 i386
Now FreeBSD 4.11-STABLE i386
Infortrend RAID unit with 4 channels.
3 channels of RAID 1 storage with heavy databases
tables on seperate arrays. (symlinked) and one channel
--- NMH <drumslayer2 at yahoo.com> wrote:
> Currently, our mysql database is crashing at random
> intervals though out the day during heavy load. A
> mysql support engineer traced the problem to
> #0 0x28619dfe in mutex_self_lock (mutex=0x0,
> noblock=0) at
> 615 PANIC("Shouldn't resume here?\n");
> The Database server is running i386 FreeBSD 5.4
> Release-P6, with 4 gigs of ram, on an
> AMD Opteron(tm) Processor 248 (2191.84-MHz 686-class
> CPU). W/ infotrend raiding solution.
> Apparently, there have been some updates (beyond my
> ability to understand) to the libthr package, which
> have not yet been backported to the 5.4
> release...?? (changes in 6.0 that seem pertinant)
> We have attempted to use KSE, and pthreads Binary
> from MYSQL, but we encountered even WORSE problems
> with those packages.
> The mysqld would consistantly crash in those
> packages, usually within a minute or so of
> Usually with a message
> that a junk pointer was being released. (Error came
> from malloc.c).
> We were able to reproduce the memory problem on a
> seperate machine with a different hardware
> configuration, but same OS. And on other machines
> with the same hardware configuration.
> A mysql support engineer is currently checking
> to see if there are any solutions, but meanwhile...
> thought many heads are better than one.
> All of these problems started when we migrated to
> this new server, which hardware wise was very
> to the old one. However the old one was running
> 4.0.18 and FreeBSD 5.1-Release-P11.
> According to /usr/src/UPDATING some lib changes
> occured after this time.
> Currenly, on their suggestion, we are using
> /etc/libmap.conf entry of
> libpthread.so libthr.so
> libpthread.co.1 libthr.so.1
> Which seems backwards to what people on here have
> recommended. But seemed to help but we are still
> crashing at least once a day sometimes more.
> Any pointers, tips etc quite welcomed.
The Large Print Giveth And The Small Print Taketh Away
Yahoo! Music Unlimited
Access over 1 million songs. Try it free.
More information about the freebsd-questions