Just for our own sanity we tested this out on a clean 7.3 box. We started with a clean RH7.3 install, installed mysql via up2date. In mysql we reset the admin password and set the user table to allow connections from everywhere. At this point we can make a connection to the box on 3306 and everything works as expected.
We ran an up2date which included the new glibc update (2.2.5-40) and then restarted the mysql daemon. At this point we are unable to make a remote connection to the server on 3306 and the mysql process is very unstable. The mysql process will seg fault under even low load. If a large query is thrown at it, it will die almost instantly. These are the entries that show up in the mysql log: Number of processes running now: 3 mysqld process hanging, pid 7626 - killed mysqld process hanging, pid 7626 - killed mysqld process hanging, pid 7626 - killed 021005 09:58:41 mysqld restarted 021005 9:58:41 Can't start server: Bind on TCP/IP port: Address already in use 021005 9:58:41 Do you already have another mysqld server running on port: 3306 ? 021005 9:58:41 Aborting 021005 9:58:41 /usr/libexec/mysqld: Shutdown Complete 021005 09:58:41 mysqld ended If we roll back to the previous version of glibc (2.2.5-39) everything starts working properly again. We have also seen this same behavior on a fresh 8.0 install, which must include the same changes to glibc. Has anyone else seen these same problems and come up with a different workaround or solution. We tried this with a fresh system just to make sure that this had nothing to do with our data. Jon -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
