Hiya, tried LD_ASSUME_KERNEL=2.2.5?
See here: http://sources.redhat.com/ml/libc-hacker/2003-06/msg00032.html May work, then again your machine may blow up! So use at your own risk as I am guessing! Greg > -----Original Message----- > From: Owen Scott Medd [mailto:[EMAIL PROTECTED] > Sent: 03 November 2003 15:08 > To: [EMAIL PROTECTED] > Subject: Re: MySQL 4.0.16 on RHEL3 AS AMD64 > > > I should sleep before posting, I suppose. > > I suppose this is the issue with the NPTL threads library? > If so, has > anyone dealt with that issue with MySQL? I remember hearing that > perhaps using a dynamically linked mysqld would work around > the problem. > > Owen > > Owen Scott Medd wrote: > > > I have Red Hat Enterprise Linux 3 AS installed on a dual Opteron > > server with 16GB of memory (hoping to solve innodb_buffer_pool size > > issues under x86). I upgraded the MySQL included with > RHEL3 (3.23.58) > > to the 4.0.16 rpms from the MySQL website. > > > > I had thought this would be a piece of cake, as we're > running 4.0.16 > > in production with very few issues. However, when starting the > > upgraded MySQL on the Opteron server, I get a segmentation fault. > > Anyone have any actual experience with this configuration? > I had to > > physically remove the 3.23.58 packages (and the packages > dependent on > > them), doing an upgrade did not fly with the rpm dependencies. I > > don't really have an option of going back to 3.23.58, as I have > > post-4.0.14 innodb data. > > > > 031102 22:07:17 mysqld started > > mysqld got signal 11; > > This could be because you hit a bug. It is also possible > that this binary > > or one of the libraries it was linked against is corrupt, > improperly > > built, > > or misconfigured. This error can also be caused by malfunctioning > > hardware. > > We will try our best to scrape up some info that will > hopefully help > > diagnose > > the problem, but since we have already crashed, something is > > definitely wrong > > and this may fail. > > > > key_buffer_size=8388600 > > read_buffer_size=131072 > > max_used_connections=0 > > max_connections=100 > > threads_connected=0 > > It is possible that mysqld could use up to > > key_buffer_size + (read_buffer_size + > > sort_buffer_size)*max_connections = 225791 K > > bytes of memory > > Hope that's ok; if not, decrease some variables in the equation. > > > > 031102 22:07:17 mysqld ended > > > > > > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
