I know others have had problems with this, so I tested on my servers after an upgrade (last week) and I don't notice any problems. One of my PHP portals go hosed and cant connect to it from a web browser, but the other 3 and a webmail app that uses MySQL seem to work fine. I can even connect to it and run queries from a Windows MySQL ODBC driver.
Here are my versions if this helps... MySQL: mysql-devel-3.23.49-3 mysql-server-3.23.49-3 php-mysql-4.1.2-7.3.4 mysql-3.23.49-3 mysqlclient9-3.23.22-6 mod_auth_mysql-1.11-1 Apache: apacheconf-0.8.2-2 apache-devel-1.3.23-14 apache-manual-1.3.23-14 apache-1.3.23-14 PHP: asp2php-0.76.2-1 php-ldap-4.1.2-7.3.4 php-manual-4.1.2-7.3.4 php-4.1.2-7.3.4 php-devel-4.1.2-7.3.4 php-mysql-4.1.2-7.3.4 asp2php-gtk-0.76.2-1 php-imap-4.1.2-7.3.4 GLibc glibc-2.2.5-40 glibc-devel-2.2.5-40 glibc-kernheaders-2.4-7.16 glibc-common-2.2.5-40 If you need any further info for research, let me know. Again, mine works fine and has since I upgraded glibc about a week or so ago... -- Joe Giles [EMAIL PROTECTED] AOL: mcigiles Jon Cooper said: > 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 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
