Description of problem: If up2date cannot reach the host, the 'up2date' command cannot be ctrl-c'd and it takes many minutes to come back with a response: [root@test01-ia64 tmp]# up2date Error communicating with server. The message was: Connection timed out Version-Release number of selected component (if applicable): up2date-4.4.63-3 How reproducible: always Steps to Reproduce: 1- ks a client to rhel 3 u6, include @ Everything in ks profile 2- ssh -Y <client> 3- on client: install latest up2date from /nfs/redhat/beehive/comps/dist/3.0E-qu-candidate/ 4- register the client to webqa 5- on client: run block-host.sh script to block firstboot's connections to webqa: ./block-host.sh xmlrpc.rhn.webqa.redhat.com (NOTE: block-host.sh needs to be loaded on the client from wherever it's stored -- maybe /usr/local/bin locally?) This will allow pings to the host but will prevent udp/tcp connections. 6- run 'update' on client Actual results: 'up2date' sits for many minutes. It cannot be killed by ctrl-c. You have to open a new session to kill it, and even then it requires kill -9. If you don't kill it, it will eventually return a 'Connection timed out message.' Expected results: Either make up2date killable via ctrl-c or reduce the time-out period. Additional info:
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.