We've been running mysql 4.1.11 on our sparc solaris 8 (it's a 12 proc Sun 4800) for over a year without problems, but we just ran into a known innodb bug, so I decided to upgrade to 5.x.
I tried the regular 5.0.24 SPARC 64-bit Solaris 8 package, the 5.0.24 debug package, the 5.1.11 package, and compiling 5.1.11 from source. In each case, mysqld would run between 30 minutes and a few hours before crashing on a signal 11. No other info was generated. So I downgraded to the package version of 4.1.24 which has been running for over 6 hours without incidence. Sorry I don't have any better stack trace info, but the debug version didn't generate anything. Has anyone else encountered such a problem with Solaris 8 and mysql 5.x? I dug around online and couldn't find any mention of such a problem. -chris -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
