Bug 3959
| Summary: | Ping "-c" now hangs on downed servers. | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | jafo-redhat |
| Component: | netkit-base | Assignee: | Jeff Johnson <jbj> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | CC: | fahnoe |
| 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: | 1999-08-09 20:14:14 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
jafo-redhat
1999-07-09 07:49:13 UTC
*** Bug 4082 has been marked as a duplicate of this bug. *** On the alpha, netkit-base-0.10-29 had the unaligned trap bug, but after installing netkit-base-0.10-31 (which fixed the unaligned trap) ping -c does not work properly. Specifically, "ping -c x unreachable-host" causes ping to start a stream of pings (as seen by tcpdump) that does not stop after "x" pings. Pinging a host that is reachable with the -c option works properly. In this case, I use ping -c to bring up a demand ppp link so I have reverted to the 0.10-29 kit shipped with 6.0 Alpha. --Larry ------- Additional Comments From dkl 07/22/99 11:33 ------- I was able to replicate this problem on an alpha and intel machine in our test lab with this update. I tried to ping www.redhat.com and ftp.redhat.com which are set up to reject ping requests so therefore I get the unreachable errors. It seems the -c <some num> option is ignored when used and a host is unreachable. This is being assigned to a developer for further review. ------- Additional Comments From jbj 07/23/99 04:09 ------- *** Bug 4169 has been marked as a duplicate of this bug. *** Here is the transcript of my session notice that I installed the original rpm ran my test then ran the new rpm and it failed! Transcript follows: [root@jab-linux RPMS]# rpm -U --oldpackage netkit-base-0.10-29.i386.rpm [root@jab-linux RPMS]# ls -l /bin/ping -rwsr-xr-x 1 root root 14804 Apr 7 17:21 /bin/ping [root@jab-linux RPMS]# ping -c 1 130.110.238.4 PING 130.110.238.4 (130.110.238.4): 56 data bytes --- 130.110.238.4 ping statistics --- 1 packets transmitted, 0 packets received, 100% packet loss [root@jab-linux RPMS]# cd /jbrown/linux/errata [root@jab-linux errata]# rpm -U netkit-base-0.10-31.i386.rpm [root@jab-linux errata]# ls -l /biin/ping ls: /biin/ping: No such file or directory [root@jab-linux errata]# ls -l /bin/ping -rwsr-xr-x 1 root root 17652 Jul 6 09:33 /bin/ping [root@jab-linux errata]# ping -c 1 130.110.238.4 PING 130.110.238.4 (130.110.238.4) from 130.110.238.80 : 56 data bytes From jab-linux.isd.ustra.abb.com (130.110.238.80): Destination Host Unreachable From jab-linux.isd.ustra.abb.com (130.110.238.80): Destination Host Unreachable --- 130.110.238.4 ping statistics --- 2 packets transmitted, 0 packets received, +2 errors, 100% packet loss [root@jab-linux errata]# ------- Additional Comments From jbj 07/23/99 04:11 ------- *** Bug 4149 has been marked as a duplicate of this bug. *** I beleive there is a problem with netkit-base-0.10-31.is86.rpm I have a script that pings hosts and ever since I applied the errata ping now fails with this error message : jab-linux.isd.ustra.abb.com:/jbrown/linux/errata$ ping 130.110.238.4 PING 130.110.238.4 (130.110.238.4) from 130.110.238.80 : 56 data bytes >From jab-linux.isd.ustra.abb.com (130.110.238.80): Destination Host Unreachable >From jab-linux.isd.ustra.abb.com (130.110.238.80): Destination Host Unreachable >From jab-linux.isd.ustra.abb.com (130.110.238.80): Destination Host Unreachable There is no host the at that address and I should not be getting this error. I have an original 6.0 install which has a different date and size from the original. The dates on the original install is: 14804 Apr 7 ping and the new one is: 17652 Jul 6 ping This effectivly breaks ping. Which is vital to my script. Meanwhile I have moved the older version onto this computer and I have changed my script to refernece the old version of ping. If someone could please look into why this is happening. Oh the platform is Intel. Thanks Jim Brown ------- Additional Comments From dkl 07/22/99 11:10 ------- I could not get this update to fail on a test lab machine running standard 6.0 with updates. Fixed in netkit-base-0.10-33. |