I have just built a FreeBSD 5.3 box with SMP enabled on a dual processor machine. I kept having a lot of crashes at some point in the install, and I believe I now have the cuprit: mysql-server-4.1.7 is doing it. Lately, when mysql-server is running under no load, it caused lockups of the system, with no core dumps. Troubleshooting: I have been frantically trying to re-install a lot of things -- I did a cvsup on the stable tree, recompiled the source, and tried a generic kernel with no SMP. I reinstalled a lot of ports that could have been doing this. Meanwhile, a lot of things were dumping core. I tried cooling the CPU and memory just in case it was hardware-related. Finally, I now have a stable computer, running in SMP, but only if mysql-server is disabled. Does anyone know what sort of things I can do to get mysql to run? I am in the middle of another recompile of the same mysql-server with the same options (I believe they are openssl, linuxthreads, and optimize) as before. Has anyone seen this problem before? I will report back tomorrow if a "simple" reinstall of the port has fixed this issue, but I have reinstalled it thrice now. Thanks, Billy
--On 1-1-2005 20:17 -0600 Billy Newsom <smartweb@leadhill.net> wrote:> > I have just built a FreeBSD 5.3 box with SMP enabled on a dual processor > machine. I kept having a lot of crashes at some point in the install, > and I believe I now have the cuprit: mysql-server-4.1.7 is doing it. > Lately, when mysql-server is running under no load, it caused lockups of > the system, with no core dumps.I had a similar issue: within one hour after upgrading mysql from 4.0.20 to 4.0.22 on a 4.10 box, my machine crashed. This happened when I asked for a webpage that querys a mysql database. It had been running stable for two years continuously and now it unexpectedly crashed without any available log entry or core dump. On startup the automatig file system check failed because of some unexpected softupdate errors. This could very well be completely unrelated to your problem as my setup is completely different, and all signs suggest a hardware problem. However as the only thing changed was mysql and the thing triggering it was accessing the database, I have my suspicions. As it is a colocated box and someone had to manually run an fsck I've decided not to try to reproduce it, but to disable mysql (all but one application was using postgresql anyway) and the server has been running stable since then. -- Edwin
Billy Newsom wrote:> I have just built a FreeBSD 5.3 box with SMP enabled on a dual processor > machine. I kept having a lot of crashes at some point in the install, > and I believe I now have the cuprit: mysql-server-4.1.7 is doing it. > Lately, when mysql-server is running under no load, it caused lockups of > the system, with no core dumps. > > Troubleshooting: > I have been frantically trying to re-install a lot of things -- I did a > cvsup on the stable tree, recompiled the source, and tried a generic > kernel with no SMP. I reinstalled a lot of ports that could have been > doing this. Meanwhile, a lot of things were dumping core. I tried > cooling the CPU and memory just in case it was hardware-related. > > Finally, I now have a stable computer, running in SMP, but only if > mysql-server is disabled. Does anyone know what sort of things I can do > to get mysql to run? I am in the middle of another recompile of the > same mysql-server with the same options (I believe they are openssl, > linuxthreads, and optimize) as before. Has anyone seen this problem > before? I will report back tomorrow if a "simple" reinstall of the port > has fixed this issue, but I have reinstalled it thrice now. >Either my problem was with a screensaver, or re-compiling carefully one more time has fixed this problem, I think. No more crashes that I have seen. Billy