Description of Problem: Please read Bug 75128 for a full description. This problem was not fixed in RedHat 8.0 when it was fixed by errata release for older releases. This means anyone updating to 8.0 winds up with a broken system.
It's unbelievable that RedHat does not consider this issue as an actual and critical problem. I trusted Psyche on a server installation with MySQL and this was a mistake. I have also some random problem with the resolver with PTR records (ftp login delays [not an indent issue!], utmp *sometimes* lacks the reverse address etc.) anyone too?
I found this on others forums.... We also have the same problem on Red Hat 8.0 We don't know if it works but we'll try it. ---------------------------- Author: Peter (---.telenet-ops.be) Date: 11-07-02 16:14 Yes the same for my on a linux 8.0 system downgrade to which version of glibc ??? --------------------------- (some others replys before...) Reply by Peter: Author: Peter (---.telenet-ops.be) Date: 11-12-02 20:10 Upgrade from MySQL 3.23.52-3 to Mysql 3.23.53a-1 and all problems are gone :-))) Thanks!!
Success on a stock RH8 install. I was running into the same problems. Tried a couple of things suggested in 7518. Adding 'set-variable=thread_stack=256k' to /etc/my.cnf did, in fact, solve the problem. Adding that option to the startup command /etc/rc.d/init.d/mysqld caused the MySQL server to die. I am now able to connect to MySQL remotely. So many problems with RH8...php-snmp, mysql, glibc...geez! what happened to you guys, redhat?!
*** This bug has been marked as a duplicate of 77467 ***