rpc.idmapd hangs after 'bad type in upcall'

Stirling, Ashley ashley at mun.ca
Thu May 1 14:23:27 EDT 2008


We have recently been experiencing a problem where idmapd will log a 'bad
type in upcall' message and thereafter the nfs server will respond to all
requests with NFS4ERR_DELAY.  Restarting rpc.idmapd returns nfs to a
functioning state.

The nfs server is running RedHat Enterprise Linux 4:
  kernel 2.6.9-42
  nfs-utils 1.0.6-80

Attached are:
  -  the syslogs around the time of the most recent hang
  -  output from strace of the idmapd daemon
  -  packet capture around the time of idmapd hanging
(user names are blanked out to comply with our privacy policy)


I don't really know what to look for in the attached logs.  Any assistance
or direction you could provide would be greatly appreciated.

Thanks,
- Ash

-- 
Ash Stirling
System Administrator
Computing and Communications
Memorial University of Newfoundland
Office: (709) 737-7588
Mobile: (709) 691-5664
Fax   : (709) 737-3514

-- 
Ash Stirling
System Administrator
Computing and Communications
Memorial University of Newfoundland
Office: (709) 737-7588
Mobile: (709) 691-5664
Fax   : (709) 737-3514

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://linux-nfs.org/pipermail/nfsv4/attachments/20080501/a1936bdd/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: traffic.pcap
Type: application/octet-stream
Size: 2692 bytes
Desc: traffic.pcap
Url : http://linux-nfs.org/pipermail/nfsv4/attachments/20080501/a1936bdd/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: messages.txt
Type: application/octet-stream
Size: 261382 bytes
Desc: messages.txt
Url : http://linux-nfs.org/pipermail/nfsv4/attachments/20080501/a1936bdd/attachment-0001.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: trace.txt
Type: application/octet-stream
Size: 29762 bytes
Desc: trace.txt
Url : http://linux-nfs.org/pipermail/nfsv4/attachments/20080501/a1936bdd/attachment-0002.obj 


More information about the NFSv4 mailing list