Created attachment 111245 [details]
strace of statd crashing at startup

This shows statd crashing after recvmsg().

Reading interface information seems to be a regular cause of bugs in a variety
of packages (i've reported bugs in things like krb5 before, where it crashed
reading interface information), it'd be a really nice nice idea to try
standardise this interface state into a library...

Same happen to me (also an IPv6 enabled box), it's a show stopper for running
KDE on a remote host with a mounted home directory.

Looks like no one cares about this bug, so pls. can one change the priority to
"high"? The crash of rpc.statd prevent NFS client/server from proper file locking.

I'm changing this to high.

This bug is high impact to clients of a server affected, locking doesn't work,
GNOME desktops hosted out of NFS mounted /home dirs become painful to use. I've
had to downgrade nfs-utils to -44 and pin it to that version in my apt preferences.

I can confirm this bug, and it is causing havoc for me.  I'm reverting to the
old version.

Has anyone had the chance to try nfs-utils 1.0.7-1 from development?  I'll give
it a try later today to see if it fixes the problem.

I've updated here and restarted nfs. rpc.statd stays alive, so this version works.

To @redhat -> pls. push that version to FC3 updates.

I too have updated to 1.0.7-1 and it doesn't crash on startup.  I've done some
basic testing on it, and it appears to work fine.  I agree with comment 10 in
that this really needs to be put through as an FC3 update.

Strange, after a reboot this issue comes up again:

03/29/2005 22:53:22 rpc.statd[15146]: Version 1.0.7 Starting
03/29/2005 22:53:22 rpc.statd[15146]: Flags: No-Daemon Log-STDERR
03/29/2005 22:53:22 rpc.statd[15146]: New state: 655
Segmentation fault


bind(8, {sa_family=AF_INET, sin_port=htons(921), sin_addr=inet_addr("0.0.0.0")},
16) = -1 EACCES (Permission denied)
ioctl(8, FIONBIO, [1])                  = 0
setsockopt(8, SOL_IP, IP_RECVERR, [1], 4) = 0
sendto(8, "#\325?`\0\0\0\0\0\0\0\2\0\1\206\240\0\0\0\2\0\0\0\1\0\0"..., 56, 0,
{sa_family=AF_INET, sin_port=htons(111), sin_addr=inet_addr("127.0.0.1")}, 16) = 56
poll([{fd=8, events=POLLIN, revents=POLLIN}], 1, 5000) = 1
recvfrom(8, "#\325?`\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1"..., 400,
0, {sa_family=AF_INET, sin_port=htons(111), sin_addr=inet_addr("127.0.0.1")},
[16]) = 28
close(8)                                = 0
time([1112129621])                      = 1112129621
time([1112129621])                      = 1112129621
socket(PF_NETLINK, SOCK_RAW, 0)         = 8
bind(8, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
getsockname(8, {sa_family=AF_NETLINK, pid=15153, groups=00000000}, [12]) = 0
time(NULL)                              = 1112129621
sendto(8, "\24\0\0\0\22\0\1\3U\300IB\0\0\0\0\0\0\0\0", 20, 0,
{sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20
recvmsg(8, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"\344\0\0\0\20\0\2\0U\300IB1;\0\0\0\0\4\3\1\0\0\0I\0\0\0"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 3012
recvmsg(8, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"\24\0\0\0\3\0\2\0U\300IB1;\0\0\0\0\0\0\1\0\0\0I\0\0\0\0"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 20
sendto(8, "\24\0\0\0\26\0\1\3V\300IB\0\0\0\0\0\0\0\0", 20, 0,
{sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20
recvmsg(8, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"D\0\0\0\24\0\2\0V\300IB1;\0\0\2\10\200\376\1\0\0\0\10\0"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 536
recvmsg(8, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"@\0\0\0\24\0\2\0V\300IB1;\0\0\n\200\200\376\1\0\0\0\24"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 1024
recvmsg(8, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
msg_iov(1)=[{"\24\0\0\0\3\0\2\0V\300IB1;\0\0\0\0\0\0\1\0\0\0\24\0\1\0"...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 20
close(8)                                = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++


I have nothing special changed on the system.

This appears to be the same problem at in bz151828.
Please down the the nfs-utils in http://people.redhat.com/steved/bz151828/
to see if they solve the problem.

1.0.6-55 starts up for me.  However, so did 1.0.7-1 for a bit (comment 11), then
it stopped working (I can't work out why).  I'll post any progress.

1.0.6-55 starts for me, too.

I've installed 1.0.6-55 here, and it does appear to have started up without
crashing.

thanks for all the help!!!

*** This bug has been marked as a duplicate of 151828 ***

Not quite a dupe if it doesn't apply to the same OS/release.  We'll never get an
update for FC3 if there isn't at least an open bugzilla that applies to FC3 on
this, are we?

The nfs-utils is fixed in FC4 which should work just fine on an FC3 machine.

Then it should be pretty easy to address the problem for FC3 by releasing an
update for it, no?

Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!

Fedora Core 3 is not maintained anymore.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release please reopen this bug and assign it to the corresponding
Fedora version.