% mysqladmin shutdown<br><br>... is how I shut down mysql. I did this before the Unix shutdown. I guess I could try killing the process instead. That would seem wierd. I can also try a new rebuild using the latest source code, but I may save that for a...
mysql 3.22.27<br>NetBSD 1.4.1<br><br>Since mysql server was not available in as an executable for<br>my platform (mac68k), it had to be compiled from source code.<br><br>The mysql client was available as a binary, but I chose to<br>compile it from source code anyway.<br>
It turns out that even a safe shutdown corrupts the base files. I did a normal mysql shutdown, then a normal Unix shutdown. Mysqld refused to come back up. Kept core dumping. I had to restore the base files from the distribution again. A...
Sorry about the sarcasm, but prevention and problem-solution are different animals.<br>Indeed there was data corruption despite no apparent activity. I restored the base tables from the mysql distribution and mysqld came back to life. UPS is on the wish...
Yes, of course, a UPS! Very helpful tip. I'll remember that. No process was writing to mysql at power-down. The daemon was running, but that was all.
It was running perfectly well until the power went out. Now the safe_mysqld script, which has never failed before, is core-dumping. Any ideas ?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.