Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 234450 - Every (ave) 3000th ping fails "segmentation fault"
Summary: Every (ave) 3000th ping fails "segmentation fault"
Alias: None
Product: Fedora
Classification: Fedora
Component: iputils
Version: 6
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Martin Bacovsky
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-29 12:19 UTC by Mike Yates
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-05-10 11:59:46 UTC

Attachments (Terms of Use)

Description Mike Yates 2007-03-29 12:19:23 UTC
Description of problem:
Fall-over clustering bash-script pings virtual server on other box up to 4 times
per second (usually much less if mirrored app data not idle) and fails
"segmentation fault" at random (30-30000 pings) intervals. Since the segv fails
are indistinguishable from "server down" failures, "second try" pings work
around this problem, but far from satisfactorily!  
Both physical servers in the cluster show this behaviour, with very different
hardware but identical FC6 installed.

Version-Release number of selected component (if applicable):

I'm using the latest ping (ss020927)for Fedora 6, in

Currently running same test on Fedora-4 server and on "ZenWalk Linux" VMware box
within that server. Neither have thrown segmentation errors after over 30,000 pings.

How reproducible:
See script below

Steps to Reproduce:
1. Install FC6 and bring up-to-date
2. Run script below 

#! /bin/bash
echo `date +%T` Starting testping
while [ 0 ]
	if ! ping -c 1 -w 1 &> /dev/null
		echo `date +%T` Ping failed after $COUNT operations
COUNT=$(( COUNT + 1 ))
echo -n -e "$COUNT \\r"
sleep 0.2
Actual results:

[root@mysvr5a cluster]# ./testping
11:08:31 Starting testping
./testping: line 12: 21716 Segmentation fault      ping -c 1 -w 1
11:24:12 Ping failed after 4028 operations
./testping: line 12:  5216 Segmentation fault      ping -c 1 -w 1
11:40:17 Ping failed after 8304 operations
./testping: line 12: 20132 Segmentation fault      ping -c 1 -w 1
11:52:51 Ping failed after 11401 operations
./testping: line 12: 29971 Segmentation fault      ping -c 1 -w 1
12:00:32 Ping failed after 13392 operations
./testping: line 12: 11050 Segmentation fault      ping -c 1 -w 1
12:12:36 Ping failed after 16479 operations
./testping: line 12: 14748 Segmentation fault      ping -c 1 -w 1
12:15:30 Ping failed after 17167 operations
./testping: line 12: 29969 Segmentation fault      ping -c 1 -w 1
12:22:38 Ping failed after 18896 operations
./testping: line 12: 18937 Segmentation fault      ping -c 1 -w 1
12:31:43 Ping failed after 21047 operations
./testping: line 12:  6129 Segmentation fault      ping -c 1 -w 1
12:49:29 Ping failed after 25611 operations
./testping: line 12: 24498 Segmentation fault      ping -c 1 -w 1
13:01:26 Ping failed after 28516 operations

N.B. note reversal of &>  -- could be actually stdout/stderr problem, but I've
tried not hiding the (voluminous) ping output and still got segv's.

The working scripts sometimes go up to 3 hours or 50,000 pings without a segv.

Expected results:

[root@mysvr5a cluster]# ./testping
11:08:31 Starting testping

Additional info:
Please advise how to delve deeper...

Comment 1 Mike Yates 2007-03-29 13:52:26 UTC
Another test: running "testping" alone on one server, two instances on other.
Both threw segv's, so not due to simultaneous pinging.

Fedora4, Zenwalk and Knoppix (Debian) have run two instances of testping for
over 60,000 now with no segv's

Comment 2 Mike Yates 2007-04-02 13:15:08 UTC
On repeatability:-
Temporary install of FC6 in a third physical PC reproduced the fault immediately.
Installed FC6 in a VMware box and got 246559 pings, in 54546 secs, before it
suddenly started throwing segv's every 87 to 6804 (random) pings.
Meanwhile, the testpings on the 2 servers had several periods of less than a
minute, spaced many hours apart, when pinging the router failed every 1 to 30
pings without segv's - very strange. I would guess during DHCP renewal, except
that the servers are fixed-ip!

Comment 3 Martin Bacovsky 2007-04-03 13:04:52 UTC
ok, i've tried to reproduce this, but was unsucessfull. I tried about 5 times up
to 60000 pings and the bug did not occured. 
First of all i update iputils to new upstream also in fc6.
If it does not help then we have to find simpliest and as default as possible
enviroment where this is reporoducible. I will let you know when new iputils
will be available.

Comment 4 Martin Bacovsky 2007-04-03 18:14:12 UTC
iputils-20070202-1.fc6 should be pushed to fc6 testing. Can you, please, test
whether this bug is still reproducible after update?

Comment 5 Mike Yates 2007-04-04 12:08:45 UTC
I'm afraid it is!

10:54:07 Ping failed after 5529 ops, 1201 secs
./testping: line 15:  3628 Segmentation fault      ping -c 1 -w 1
11:20:59 Ping failed after 7418 ops, 1612 secs
./testping: line 15:  6423 Segmentation fault      ping -c 1 -w 1
11:25:58 Ping failed after 1375 ops, 299 secs
./testping: line 15: 20049 Segmentation fault      ping -c 1 -w 1
11:50:29 Ping failed after 6775 ops, 1471 secs
[root@localhost ~]# rpm -Uv iputils-20070202-1.fc7.i386.rpm 
warning: iputils-20070202-1.fc7.i386.rpm: Header V3 DSA signature: NOKEY, key ID
Preparing packages for installation...
[root@localhost ~]# ping -V
ping utility, iputils-sss20070202
[root@localhost ~]# ./testping 
12:06:09 Starting testping
./testping: line 15: 29596 Segmentation fault      ping -c 1 -w 1
12:19:58 Ping failed after 3820 ops, 829 secs
./testping: line 15: 31216 Segmentation fault      ping -c 1 -w 1
12:22:53 Ping failed after 806 ops, 175 secs
./testping: line 15: 32641 Segmentation fault      ping -c 1 -w 1
12:25:27 Ping failed after 709 ops, 154 secs

Comment 6 Mike Yates 2007-04-04 13:31:06 UTC
Further "elimination" tests:-
In minimal (Gnome Desktop but no apps) FC6, fully updated, in VMware,
1) Changed ping address from router (Smoothwall) to VMware Zenwalk.
2) In another console, at same time, pinged eth0:1
Both average about 3000 pings per segv, as usual.

Comment 7 Martin Bacovsky 2007-05-09 13:25:53 UTC
I'm still not able to reproduce this. Can you provide me core dump?

Comment 8 Martin Bacovsky 2007-05-09 14:41:21 UTC
And pls, also output of rpm -qa to compare installed packages versions?

Comment 9 Mike Yates 2007-05-10 10:59:37 UTC
Well, it seems to have gone away with yum updates.
I now have
and, as I write, 9000 pings have succeeded.
So, unless anyone else complains (I'll check with the one I know of)
you can close this off.

Comment 10 Martin Bacovsky 2007-05-10 11:59:46 UTC
Thanks for info. According to comment #9 I am closing this as notabug. If it
appears again feel free to reopen this bug.

Comment 11 Stepan Kasal 2007-05-11 08:04:18 UTC
Well, I had the script running for 2 days on an FC4/i386 and an FC6/x86_64 and
in both cases experianced 7 failures out of 740k pings.
Now its time to fix the script so that it generates and saves some core dumps.  ;-)

Comment 12 Mike Yates 2007-05-11 08:23:01 UTC
Mine has reached 320000 with no failures this morning, in up-to-date FC6-i386

Note You need to log in before you can comment on or make changes to this bug.