Hi Rob Here is your answer. There is a serious conflict between Red Hat's glibc update, RHSA-2002:197-06, and MySql, in Red Hat 7.1, 7.2, and 7.3 and perhaps other versions. See this bugzilla report for more details. Thanks to Mike Bird http://lwn.net/
Cheers Steven -----Original Message----- From: Walls Rob W Contr 75 CS/SCBS [mailto:[EMAIL PROTECTED]] Sent: 08 October 2002 12:34 To: Enigma-List@Redhat. Com (E-mail); Seawolf-List@Redhat. Com (E-mail) Subject: MySQL Broken After Up2date I ran up2date on 6 Oct on a 7.1 and several 7.2 systems. MySQL is flakey on all systems now. They are dropping connections and all have quit accepting MyODBC connections from a Windows machine with DSN's that previously worked fine. MyODBC gives the following error: "Lost connection to server during query (#2013)". I get a segmentation fault when a MyODBC connection is being attempted when running /usr/libexec/mysqld directly. The safe_mysql start mechnism seems to make troubleshooting MySQL very hard... The log reports "mysqld process hanging, pid xxxx - killed" and restarts every few seconds. I freshened mysql and mysql-server rpms on the 7.1 system from the CD with rpm -F --allfiles. No change. I ran an index check on all the dbs. No change. up2date was last run on 1 Oct. Help! The 7.1 macine is a production db box and my hair is on fire! [EMAIL PROTECTED] Rob Walls 75 CS/SCBS Hill AFB, Utah 84056 DSN 777-2230 COM (801) 777-2230 [EMAIL PROTECTED] _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
