Bug 75297
| Summary: | glibc-2.2.5-40 and mysql-3.23.49-3 are not working together | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | R P Herrold <herrold> |
| Component: | mysql | Assignee: | Patrick Macdonald <patrickm> |
| Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | acox, adler, bgwhite, chris.ricker, claudio.rossi, doliver, edoutreleau, elliotp, gbailey, holger, hps, jim, jn, mk, pacman128, ramses, rcgraves, rdieter, sean, shishz, stk, yiango |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-02-21 18:49:46 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
R P Herrold
2002-10-07 00:23:31 UTC
It may be that this should be filed against glibc -- I am trying to reproduce on a non-SMP processessor (the one with the problem is a Dell 2450 with two processessors ... I am having a similar problem. After the glibc patch: 1) I can connect to mysqld (using localhost) as usual 2) I CANNOT connect to mysqld (using IP address) with the following message: ERROR 2013: Lost connection to MySQL server during query The mysql log file says: Number of processes running now: 1 mysqld process hanging, pid 30656 - killed 021009 23:29:22 mysqld restarted /usr/libexec/mysqld: ready for connections This is the same as 75290. I also experienced this on a uni-processor system. However, I did not have to do an ldconfig or reboot to fix it. I simply downgraded to glibc-2.2.5-39 and restarted mysql. Remote connections kill mysql, but local connections (TCP or UNIX socket) do not cause MySQL to die. Same here. Server i686 Uniprocessor, Client i686 Uniprocessor, both on RHL 7.3 with all upgrades. Definitely reproduceable. glibc-2.2.5-40.i686.rpm We were able to fix this on our SMP box by replacing the glibc-common and glibc packages from the RH 7.3 disk 1 CD. rpm -i --replacefiles --oldpackage glibc-common-2.2.5-34.i386.rpm rpm -i --replacefiles --oldpackage glibc-2.2.5-34.i686.rpm We DID NOT have to restart MySQL. It worked immediately after the replace. However, it would probably be good to restart. Lenz with mysql.com said that RedHat is investigating this issue. It seems clear that there is something conflicting with the glibc*-2.2.5-40.* packages. I have 4 servers with nearly identical setup, 1 of them is SMP while the others only have one processor, I only have the problem on the SMP machine. Where can I find the -39 rpms? I wasn't able to find them so I'm going back to the ones on the 7.3 cd On a machine with 1 processor, local mysql connections work fine, but remote ones cause the mysql server to restart just as reported above. i use a portforwarding from external ip to 127.0.0.1:3306 as a workaround... Mysql 3.23.53a works with the latest mess of a glibc. Of course this isn't a current Red Hat RPM but the standard mysql.com version. [jhood@corduroy tmp]$ rpm -q MySQL MySQL-3.23.53a-1 [jhood@shrubbery SPECS]$ mysql -p -h corduroy Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 to server version: 3.23.53a Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> Caution, I do have a modified glibc to have Red Hat work with PostgreSQL -- mktime bug fix: [jhood@corduroy tmp]$ rpm -q glibc glibc-2.2.5-40_mktime_pre_epoch_ok I have a single-processor MySQL server being accessed by a single remote client. As previous people stated, all connections over loopback worked just fine, all remote connections caused an immediate seg fault. The workaround: rpm -Uvh --oldpackage glibc-common-2.2.5-39.i386.rpm glibc-2.2.5-39.i686.rpm glibc-devel-2.2.5-39.i386.rpm To RH: Please issue either a fixed glibc or one of the newer (and by all accounts) working MySQLs! This effects _all_ MySQL users, not just SMP boxes. We are running 7.2 with a 2.4.18-17.7.x kernel on a single processor. glibc- 2.2.4-30 as per Red Hat Erata along with mysql-server-3.23.41-1. We are experiencing a problem already posted regarding not being able to connect remotly. The server is running and answering on the local host. but no remote connection can be established. Is there a workaround without going back to an older version of glibc ? I concur that the issue is the glibc expectations, not being the same as the serer applications already extant -- it is not a SMB issue so far as I can tell. I have just filed as to TFTP server a similar bug in RHL 8.0 see: 77794 I don't know how this bug has still not been marked as a duplicate They closed a bug like this when they released the new glibc package last week. I can't find the bug number now, but it's in the RHSA for the new glibc. This was possibly SMP related; and on a differing RHL version -- it is not clear that it is fixed -- it is in my queue for testing. This may explain the non-close for the moment ... I will close it myself if/when my testing concludes it _is_ resolved on the host in question -- but the host houses a production database, and I need to travel to that site before I possibly hork it up -- I am scheduled to do so next week. Just going through the existing backlog and noticed this was not marked as a duplicate of 75128. There was a problem with MySQL interation with the updage glibc (which has been fixed). Please look at 75128 for more information. *** This bug has been marked as a duplicate of 75128 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |