X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C80B5C.672CF3D3@onstor-exch02.onstor.net>; Wed, 10 Oct 2007 08:41:27 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C80B5C.672CF3D3"
Content-class: urn:content-classes:message
Subject: RE: RPC program not registered error messages - case 6092
Date: Wed, 10 Oct 2007 08:41:27 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E05EF1089@onstor-exch02.onstor.net>
In-Reply-To: <200710101416.l9AEGJl02081@mailhost-rtp.css.glasshouse.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RPC program not registered error messages - case 6092
Thread-Index: AcgLSFP8vPffP0LVRPqvBKe+oJvNqAAE1n7w
References: <200710101416.l9AEGJl02081@mailhost-rtp.css.glasshouse.com>
From: "Eric Barrett" <eric.barrett@onstor.com>
To: "Alan Cooke (Glasshouse)" <acooke@css.glasshouse.com>,
	"dl-cstech" <dl-cstech@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C80B5C.672CF3D3
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Alan & Andy,
=20
I've seen this message in the past when lockd on a client is
unregistered or otherwise misbehaving, and it only needed a kick in the
pants to work again.
=20
Run this on the Linux box and make sure all nlockmgr services are
registered for versions 1, 3, 4, and both tcp and udp.  If one of them
isn't, have the customer either restart lockd or reboot.
=20
=20
linux$ rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100021    1   udp  32768  nlockmgr
    100021    3   udp  32768  nlockmgr
    100021    4   udp  32768  nlockmgr
    100021    1   tcp  32770  nlockmgr
    100021    3   tcp  32770  nlockmgr
    100021    4   tcp  32770  nlockmgr
    100007    2   udp    657  ypbind
    100007    1   udp    657  ypbind
    100007    2   tcp    660  ypbind
    100007    1   tcp    660  ypbind
    100024    1   udp  32769  status
    100024    1   tcp  32779  status

If you DO see all of the above, then it's probably something weirder and
you'll need to go the packet trace route Andy described.
=20
(rpcinfo -p can take an IP address, but if you don't specify one it runs
against the local host.)

=20
________________________________

From: Alan Cooke (Glasshouse)=20
Sent: Wednesday, October 10, 2007 7:18 AM
To: dl-cstech
Subject: RPC program not registered error messages - case 6092



Hi All,

Case 6092:

Customer DIR.bv is an ISP in Bulgaria.

They have  a 3 node cluster and have Debian linux clients running Debian
"Lenny" whatever release that is.

=20

They are getting various error messages they are concerned about.

From the Bobcats they are getting:

=20

Oct 9 10:02:08 dir-nfs-2 : 1:1:unused:WARNING: 5019: rpc: program 100021
not registered on 10.100.0.82

=20

From the Onstor wiki for this I find

=20

NLM 100021 Classify up to NLM version and command type and mark as slow
path in RX Descriptor.

So presumably this is a process the Onstor wants to see that the linux
client does not have a response to?

=20

Another set of error messages:

=20

From the client they are getting:

Oct 8 10:14:16 www8 kernel: rpcbind: server 10.100.0.157 not responding,
timed out=20
Oct 8 10:14:19 www8 kernel: nfs: server 10.100.0.157 not responding,
still trying=20
Oct 8 10:14:27 www8 kernel: lockd: server 10.100.0.157 OK=20
Oct 8 10:14:27 www8 kernel: nfs: server 10.100.0.157 OK=20
Oct 8 10:14:27 www8 kernel: lockd: server 10.100.0.157 OK=20
Oct 8 10:14:30 www8 last message repeated 14 times=20
Oct 8 10:15:38 www8 kernel: lockd: server 10.100.0.157 not responding,
still trying=20
Oct 8 10:15:57 www8 last message repeated 15 times=20
Oct 8 10:16:48 www8 kernel: lockd: server 10.100.0.157 OK=20
Oct 8 10:16:48 www8 last message repeated 15 times=20
Oct 8 10:19:23 www8 kernel: lockd: weird return 9 for CANCEL call=20
Oct 8 10:19:24 www8 last message repeated 32 times

=20

I have done a search on the web for "lockd: weird return 9" and get a
few non Debian ( suse ) hits but nothing I can make any sense from.

=20

Can anyone help with these please?

=20

Thanks ... Alan.


------_=_NextPart_001_01C80B5C.672CF3D3
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16525" =
name=3DGENERATOR><o:SmartTagType=20
name=3D"country-region"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><o:SmartTagType=20
name=3D"place"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@page Section1 {size: 612.0pt 792.0pt; margin: 45.1pt 45.0pt =
35.95pt 53.85pt; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D910163616-10102007><FONT =
face=3DArial=20
size=3D2>Alan &amp; Andy,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D910163616-10102007><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D910163616-10102007><FONT =
face=3DArial=20
size=3D2>I've seen this message in the past when lockd on a client is =
unregistered=20
or otherwise misbehaving, and it only needed a kick in the pants to work =

again.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D910163616-10102007><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D910163616-10102007><FONT =
face=3DArial=20
size=3D2>Run this on the Linux box and make sure all nlockmgr services =
are=20
registered for versions 1, 3, 4, and both tcp and udp.&nbsp; If one of =
them=20
isn't, have the customer either restart lockd or =
reboot.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D910163616-10102007><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D910163616-10102007><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D910163616-10102007><FONT =
size=3D2><FONT=20
face=3D"Courier New">linux$</FONT><FONT face=3D"Courier New"> rpcinfo=20
-p<BR>&nbsp;&nbsp; program vers proto&nbsp;&nbsp; =
port<BR>&nbsp;&nbsp;&nbsp;=20
100000&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp; tcp&nbsp;&nbsp;&nbsp; 111&nbsp;=20
portmapper<BR>&nbsp;&nbsp;&nbsp; 100000&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;=20
udp&nbsp;&nbsp;&nbsp; 111&nbsp; portmapper<BR><STRONG><FONT=20
color=3D#0000ff>&nbsp;&nbsp;&nbsp; 100021&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;=20
udp&nbsp; 32768&nbsp; nlockmgr<BR>&nbsp;&nbsp;&nbsp; =
100021&nbsp;&nbsp;&nbsp;=20
3&nbsp;&nbsp; udp&nbsp; 32768&nbsp; nlockmgr<BR>&nbsp;&nbsp;&nbsp;=20
100021&nbsp;&nbsp;&nbsp; 4&nbsp;&nbsp; udp&nbsp; 32768&nbsp;=20
nlockmgr<BR>&nbsp;&nbsp;&nbsp; 100021&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp; =
tcp&nbsp;=20
32770&nbsp; nlockmgr<BR>&nbsp;&nbsp;&nbsp; 100021&nbsp;&nbsp;&nbsp;=20
3&nbsp;&nbsp; tcp&nbsp; 32770&nbsp; nlockmgr<BR>&nbsp;&nbsp;&nbsp;=20
100021&nbsp;&nbsp;&nbsp; 4&nbsp;&nbsp; tcp&nbsp; 32770&nbsp;=20
nlockmgr<BR></FONT></STRONG>&nbsp;&nbsp;&nbsp; 100007&nbsp;&nbsp;&nbsp;=20
2&nbsp;&nbsp; udp&nbsp;&nbsp;&nbsp; 657&nbsp; =
ypbind<BR>&nbsp;&nbsp;&nbsp;=20
100007&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp; udp&nbsp;&nbsp;&nbsp; 657&nbsp;=20
ypbind<BR>&nbsp;&nbsp;&nbsp; 100007&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;=20
tcp&nbsp;&nbsp;&nbsp; 660&nbsp; ypbind<BR>&nbsp;&nbsp;&nbsp;=20
100007&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp; tcp&nbsp;&nbsp;&nbsp; 660&nbsp;=20
ypbind<BR>&nbsp;&nbsp;&nbsp; 100024&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp; =
udp&nbsp;=20
32769&nbsp; status<BR>&nbsp;&nbsp;&nbsp; 100024&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;=20
tcp&nbsp; 32779&nbsp; status<BR></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D910163616-10102007><FONT face=3DArial size=3D2>If you =
DO see all of=20
the above, then it's probably something weirder and you'll need to go =
the packet=20
trace route Andy described.</FONT></SPAN></DIV>
<DIV><SPAN class=3D910163616-10102007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D910163616-10102007><FONT face=3DArial =
size=3D2>(rpcinfo -p can take=20
an IP address, but if you don't specify one it runs against the local=20
host.)</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
size=3D2></FONT><FONT=20
face=3DArial size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT =
face=3DArial=20
size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
size=3D2></FONT><FONT face=3DArial size=3D2></FONT><BR>&nbsp;</DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Alan Cooke (Glasshouse) =
<BR><B>Sent:</B>=20
Wednesday, October 10, 2007 7:18 AM<BR><B>To:</B> =
dl-cstech<BR><B>Subject:</B>=20
RPC program not registered error messages - case =
6092<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">Hi All,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">Case 6092:<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">Customer DIR.bv is an ISP in <st1:place=20
w:st=3D"on"><st1:country-region=20
w:st=3D"on">Bulgaria</st1:country-region></st1:place>.<o:p></o:p></SPAN><=
/FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">They have&nbsp; a 3 node cluster and have =
Debian linux=20
clients running Debian &#8220;Lenny&#8221; whatever release that=20
is.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">They are getting various error messages they =
are=20
concerned about.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">From the Bobcats they are=20
getting:<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">Oct 9 10:02:08 dir-nfs-2 : 1:1:unused:WARNING: =
5019:=20
rpc: program 100021 not registered on =
10.100.0.82<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">From the Onstor wiki for this I=20
find<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">NLM 100021 Classify up to NLM version and =
command type=20
and mark as slow path in RX Descriptor.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">So presumably this is a process the Onstor =
wants to see=20
that the linux client does not have a response =
to?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">Another set of error=20
messages:<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">From the client they are=20
getting:<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">Oct 8 10:14:16 www8 kernel: rpcbind: server =
10.100.0.157=20
not responding, timed out <BR>Oct 8 10:14:19 www8 kernel: nfs: server=20
10.100.0.157 not responding, still trying <BR>Oct 8 10:14:27 www8 =
kernel: lockd:=20
server 10.100.0.157 OK <BR>Oct 8 10:14:27 www8 kernel: nfs: server =
10.100.0.157=20
OK <BR>Oct 8 10:14:27 www8 kernel: lockd: server 10.100.0.157 OK <BR>Oct =
8=20
10:14:30 www8 last message repeated 14 times <BR>Oct 8 10:15:38 www8 =
kernel:=20
lockd: server 10.100.0.157 not responding, still trying <BR>Oct 8 =
10:15:57 www8=20
last message repeated 15 times <BR>Oct 8 10:16:48 www8 kernel: lockd: =
server=20
10.100.0.157 OK <BR>Oct 8 10:16:48 www8 last message repeated 15 times =
<BR>Oct 8=20
10:19:23 www8 kernel: lockd: weird return 9 for CANCEL call <BR>Oct 8 =
10:19:24=20
www8 last message repeated 32 times<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">I have done a search on the web for =
&#8220;lockd: weird return=20
9&#8221; and get a few non Debian ( suse ) hits but nothing I can make =
any sense=20
from.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">Can anyone help with these=20
please?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-GB=20
style=3D"FONT-SIZE: 12pt">Thanks &#8230; Alan.</SPAN></FONT><FONT =
face=3DArial=20
size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P></DIV></BODY></HTML>

------_=_NextPart_001_01C80B5C.672CF3D3--
