Bug 191403
Summary: | Local Loopback starts misbehaving after awhile. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Bob Doan <bdoan> |
Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | urgent | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | petrides |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-09-13 12:37:48 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
Bob Doan
2006-05-11 17:36:56 UTC
RHEL3 is now closed. Does this mean you will not fix the bug? Most likely, that's correct. You might want to try the RHEL3 U8 beta kernel when it shows up in the RHN beta channels (probably in a couple of weeks) to see whether the problem still occurs, but it doesn't sound familiar (as something that might have gotten fixed). You might also want to try RHEL4. I really don't want to have to upgrade all my servers because of a silly LO bug. Who do I need to contact in order to get someone to take a look at this? I suggest starting with Customer Support, so that they can open an Issue Tracker ticket. Please let them know that you already created a Bugzilla report directly (so they can link the two together). I'm pretty sure other customers have this problem. It may have been reported as clientmqueue problems with sendmail or "Connection timed out with [127.0.0.1]" Look At Bug 154802 for example. It's might be the same thing as this. Closing re: comment #7. P. |