SLES 11 SP1 rpcstat.d crashing after network scan

SUSE Product Topics SLES Configure-Administer
1

Our company performs network scans and everytime our NFS server processes become stale, basically resulting in rpcbind having to be restarted.

I am running SLES 11 SP1
Linux dfssl60 2.6.32.54-0.3-default #1 SMP 2012-01-27 17:38:56 +0100 x86_64 x86_64 x86_64 GNU/Linux

rpm -qa | grep rpc

librpcsecgss-0.18-1.15
libtirpc1-0.2.1-1.5.1
rpcbind-0.1.6+git20080930-6.15

rpm -qa | grep nfs

yast2-nfs-server-2.17.7-1.1.2
nfsidmap-0.20-1.20
limal-nfs-server-1.5.3-0.2.11
yast2-nfs-common-2.17.7-1.1.2
nfs-client-1.2.1-2.20.1
nfs-kernel-server-1.2.1-2.20.1
yast2-nfs-client-2.17.12-0.1.81
nfs-doc-1.2.1-2.20.1
limal-nfs-server-perl-1.5.3-0.2.11

rpcbind is dated in the change log as being from 2008!

Further I get the following messages logged in the syslog

rpc.statd[9952]: recv_rply: cant decode RPC message!

and

kernel: [245710.510940] RPC: multiple fragments per record not supported

and

kernel: [245722.049180] RPC: fragment too large: 0x633f0000

How can I stop this from happening on the SLES boxes. (I cannot remove them from the scan - not under my control)

Thanks

2

On 12/06/2012 18:14, stumacgee wrote:
[color=blue]

Our company performs network scans and everytime our NFS server
processes become stale, basically resulting in rpcbind having to be
restarted.

I am running SLES 11 SP1
Linux dfssl60 2.6.32.54-0.3-default #1 SMP 2012-01-27 17:38:56 +0100
x86_64 x86_64 x86_64 GNU/Linux

rpm -qa | grep rpc

librpcsecgss-0.18-1.15
libtirpc1-0.2.1-1.5.1
RPCBIND-0.1.6+GIT20080930-6.15

rpm -qa | grep nfs

yast2-nfs-server-2.17.7-1.1.2
nfsidmap-0.20-1.20
limal-nfs-server-1.5.3-0.2.11
yast2-nfs-common-2.17.7-1.1.2
nfs-client-1.2.1-2.20.1
nfs-kernel-server-1.2.1-2.20.1
yast2-nfs-client-2.17.12-0.1.81
nfs-doc-1.2.1-2.20.1
limal-nfs-server-perl-1.5.3-0.2.11

rpcbind is dated in the change log as being from 2008![/color]

Is upgrading to SLES11 SP2 an option as that has updated nfs-related
packages (1.2.3 vs 1.2.1) although rpcbind is still the same version.

HTH.

Simon
Novell/SUSE/NetIQ Knowledge Partner

Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See TTP Organization | Micro Focus for more details.