Bug 178957
Summary: | up2date takes several minutes to time-out and cannot be killed when server is unreachable | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Beth Nackashi <bnackash> |
Component: | up2date | Assignee: | Bret McMillan <bretm> |
Status: | CLOSED WONTFIX | QA Contact: | Brandon Perkins <bperkins> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | ||
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-10-19 18:48:11 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: | |||
Bug Depends On: | |||
Bug Blocks: | 179652 |
Description
Beth Nackashi
2006-01-25 19:28:50 UTC
With the host blocked: [root@test05-64 root]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination BLOCK_HOST_TABLE all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination BLOCK_HOST_TABLE all -- anywhere anywhere Chain BLOCK_HOST_TABLE (2 references) target prot opt source destination LOGGED_DROP udp -- anywhere xmlrpc.rhn.webqa.redhat.com LOGGED_DROP tcp -- anywhere xmlrpc.rhn.webqa.redhat.com Chain LOGGED_DROP (2 references) target prot opt source destination LOG all -- anywhere anywhere LOG level info DROP all -- anywhere anywhere *** Bug 178956 has been marked as a duplicate of this bug. *** User bnackash's account has been closed This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |