Bug 76111
Summary: | glibc-2.2.4-30 cause crash of mysqld and lotus domino | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jan Polak <honzap> |
Component: | mysql | Assignee: | Patrick Macdonald <patrickm> |
Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
Severity: | low | Docs Contact: | |
Priority: | high | ||
Version: | 7.2 | ||
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: | 2002-10-18 11:55:25 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
Jan Polak
2002-10-16 22:00:52 UTC
mysql and lotus domino works fine after upgrade to glibc 2.2.4-31 from ftp://people.redhat.com/jakub/glibc/errata/7.2/i386/ If you have a limited number of hosts that connect, you can add the clients to /etc/hosts - this works around the problem. This also affects RedHat 7.3 I was getting intermittent problems from samba users. Putting their IP addresses into /etc/hosts cured the problem. So this problem also seems to affect samba. This is serious. |