 |
 |
On Wed, 10 Aug 2005, Ron Trompert wrote: > Hi, > > Currently, I am upgradding the RB to 2.6.0. We are running SL304 (not > SLC304). However, when I try to start the mysql server it crashes > immediately. The error log says something like: > > 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. Run mysqld under gdb and type "where" when the segfault is hit. > Now on the RB MySQL 4.0.25 should run while in SL304 mysql is at version > 3.23.58. > Could it be that dependencies are not complete in the MySQL rpms so that > the rpms install but mysql won't run? > > Is it really necessary to run 4.0.25 or would 3.23.58 do also? AFAIK it is indeed necessary, as MySQL 4 offers significant features that are absent in MySQL 3. But you could always give it a try...