Re: MySQL 4 Kernel Panic-ing
John May wrote: I've got an xserve running 10.3.9 and MySQL 4.0.27-max that is restarting itself every 2-3 days. It appears that it is due to a kernel panic, though I don't have direct access to the machine (colocated) to verify when it occurs. There are no crash.logs from MySQL, and watchdog and system.logs show nothing. I have culled the following panic.log - can anyone tell if MySQL is the cause of such? Has anyone seen MySQL 4 crash on an Xserve (G4 specifically)? I have tried two totally different servers, and the problems continue. - John * Mon Jun 12 06:53:02 2006 Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0xFF864A5C PC=0x00056218 Latest crash info for cpu 0: Exception state (sv=0x3E6ABC80) PC=0x00056218; MSR=0x9030; DAR=0xFF864A5C; DSISR=0x4000; LR=0x00053AB4; R1=0x1C17BC70; XCP=0x000C (0x300 - Data access) Backtrace: 0x 0x00055DC8 0x0002F750 0x00033710 0x00032028 0x00031FE4 Proceeding back via exception chain: Exception state (sv=0x3E6ABC80) previously dumped as Latest state. skipping... Exception state (sv=0x0091F280) PC=0x; MSR=0xD030; DAR=0x; DSISR=0x; LR=0x; R1=0x; XCP=0x (Unknown) Kernel version: Darwin Kernel Version 7.9.0: Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC panic(cpu 0): copyin/out has no recovery point Latest stack backtrace for cpu 0: Backtrace: 0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C Proceeding back via exception chain: Exception state (sv=0x3E6ABC80) PC=0x00056218; MSR=0x9030; DAR=0xFF864A5C; DSISR=0x4000; LR=0x00053AB4; R1=0x1C17BC70; XCP=0x000C (0x300 - Data access) Backtrace: 0x 0x00055DC8 0x0002F750 0x00033710 0x00032028 0x00031FE4 Exception state (sv=0x0091F280) PC=0x; MSR=0xD030; DAR=0x; DSISR=0x; LR=0x; R1=0x; XCP=0x (Unknown) Kernel version: Darwin Kernel Version 7.9.0: Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC How could a user space program like mysqld possibly cause a kernel panic? Sounds like bad kernel or bad hardware. -- Gerald L. Clark Supplier Systems Corporation -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 4 Kernel Panic-ing
Hi John - Yes, at my former workplace, we had a couple of different instances where we experienced severe crashing problems on G4-based machines. Prior to using a G4 Xserve, we were using a dual-G4 tower as our MySQL and Intranet server, and as we ramped up MySQL usage, the hard crashing got to where it was nearly every morning. Finally traced it to our backup process, Retrospect, accessing files while MySQL was trying to access them. Specifically excluding MySQL's data directory from your backup process is a must. Excluding temp and log dirs is also probably a good idea. We were already dumping out data out to another directory daily, but didn't realize that the simultaneous access would be such a problem. This was with MySQL 3.23 and later 4.0, and OS 10.1 through 10.2 I think. When we moved to a G4 Xserve (serving MySQL and our Intranet), we again had horrible crashing problems. Weird, like none I'd ever seen, where the OS basically just entered a slow spiral of death that led to it either rebooting on its own or us noticing the problem first and hard-resetting it. Apps would stop opening, cli processes would no longer run, running apps would slowly stop responding. Traced it to a pair of Kingston RAM modules. Once those were out, the machine righted itself and I believe continues to serve data (though no longer MySQL) to this day. Weird I know but I swear that was it. This was with MySQL 4.0 and (I think) OS 10.2 through 10.3. HTH, Dan John May wrote: I've got an xserve running 10.3.9 and MySQL 4.0.27-max that is restarting itself every 2-3 days. It appears that it is due to a kernel panic, though I don't have direct access to the machine (colocated) to verify when it occurs. There are no crash.logs from MySQL, and watchdog and system.logs show nothing. I have culled the following panic.log - can anyone tell if MySQL is the cause of such? Has anyone seen MySQL 4 crash on an Xserve (G4 specifically)? I have tried two totally different servers, and the problems continue. - John -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 4 Kernel Panic-ing
Nope, no backups happening at the time. Anyone other ideas? - John At 11:42 AM -0500 6/12/06, Dan Buettner wrote: Hi John - Yes, at my former workplace, we had a couple of different instances where we experienced severe crashing problems on G4-based machines. Prior to using a G4 Xserve, we were using a dual-G4 tower as our MySQL and Intranet server, and as we ramped up MySQL usage, the hard crashing got to where it was nearly every morning. Finally traced it to our backup process, Retrospect, accessing files while MySQL was trying to access them. Specifically excluding MySQL's data directory from your backup process is a must. Excluding temp and log dirs is also probably a good idea. We were already dumping out data out to another directory daily, but didn't realize that the simultaneous access would be such a problem. This was with MySQL 3.23 and later 4.0, and OS 10.1 through 10.2 I think. When we moved to a G4 Xserve (serving MySQL and our Intranet), we again had horrible crashing problems. Weird, like none I'd ever seen, where the OS basically just entered a slow spiral of death that led to it either rebooting on its own or us noticing the problem first and hard-resetting it. Apps would stop opening, cli processes would no longer run, running apps would slowly stop responding. Traced it to a pair of Kingston RAM modules. Once those were out, the machine righted itself and I believe continues to serve data (though no longer MySQL) to this day. Weird I know but I swear that was it. This was with MySQL 4.0 and (I think) OS 10.2 through 10.3. HTH, Dan John May wrote: I've got an xserve running 10.3.9 and MySQL 4.0.27-max that is restarting itself every 2-3 days. It appears that it is due to a kernel panic, though I don't have direct access to the machine (colocated) to verify when it occurs. There are no crash.logs from MySQL, and watchdog and system.logs show nothing. I have culled the following panic.log - can anyone tell if MySQL is the cause of such? Has anyone seen MySQL 4 crash on an Xserve (G4 specifically)? I have tried two totally different servers, and the problems continue. - John -- --- John May : President http://www.pointinspace.com Point In Space Internet Solutions [EMAIL PROTECTED] Professional Lasso / PHP / MySQL / FileMaker Pro Hosting -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
