Hi, We are having a serious problem with a simple replication setup using MySQL. One small database with 12 tables is being replicated one way - one master, one slave. Write transaction load is small, about 1 record per second, usually on only one of the tables. Read load is also light. The replication starts out fine. However, after a few hours the mysql daemon on either the master or the slave just quits. No error is logged. No core dump. It just quits. As far as we can tell, nothing special is going on with the system at the time the mysql daemon quits. For example, yesterday, we did a fresh install at about 3:30 pm. At about 7:05 pm the master mysql daemon quit. We restarted it and about 9:30 am this morning the slave mysql daemon quit. ??? Systems using the same versions, but without replication, have never experienced a loss of the mysql daemon.
Ideas? Suggestions? Environment is NetBSD 1.5Y with MySQL 3.23.47 (the latest supported by NetBSD). Al __________________________________ Al Johnson Network Storage Solutions voice 865.675-4070 ext 2 cell 865.604.5869 [EMAIL PROTECTED] --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
