Bug 75664
Summary: | glibc-2.2.4-30 and mysql-3.23.xx are not working together | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Cyril Zlachevsky <mazay> |
Component: | mysql | Assignee: | Patrick Macdonald <patrickm> |
Status: | CLOSED ERRATA | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | edoutreleau, herrold, holger, jn |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-11-04 05:48:32 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
Cyril Zlachevsky
2002-10-10 20:31:29 UTC
RHN users who have applied all recent 'critical' patches may experience segmentation faults when accessing MySQL via a remote client (accessing databases @localhost seems OK) as described by mazay.ua/bug75664. I have experienced this issue with MySQL3.23.41-1 and 3.23.49-3 on RedHat 7.2 and 8.0 The solution is to upgrade to MySQL version 3.23.53. There are currently no RedHat rpms available for this new release, but linux binaries are available at mysql.com. Please supply a RedHat MySQL3.23.53 rpm via the RedHat network as soon as possible. This problem caused me a lot of headaches today and I had to spend a lot of time diagnosing what turned out to be a bot very obvious fault with mysql. The problem was thta I upgraded glibc last week, but mysql only displayed the symptons today ??? Why has it taken so long for redhat to produce the new rpms for mysql and release a bugfix ??? This problem is really widespread - seacrh in google groups for 'Lost connection to MySQL server during query' ... Lance I test newest MySQL 3.23.53 (build from sources). Problem with glibc-2.2.4-30 in version MySQL 3.23.53 still exist. I have had this exact same problem and adding the client machines to /etc/hosts as suggested in bug number 76111 fixed the problem (obviously temporarily). This is a 7.2 machine fully patched running mysqld from Red Hat RPMS. Jason in glibc-2.2.4-31 problem resolved |