[2337] in linux-net channel archive
Damaged rpc subsystem -- revisited
daemon@ATHENA.MIT.EDU (Mark S. Petrovic)
Thu Apr 4 05:56:20 1996
From: msp@carpediem.org (Mark S. Petrovic)
To: linux-net@vger.rutgers.edu (Linux Net Channel)
Date: Wed, 3 Apr 1996 06:34:27 -0600 (CST)
Cc: msp@carpediem.org (Mark S. Petrovic)
Reply-to: msp@carpediem.org (M.S. Petrovic)
Here's what I said a month or so ago. The problem persists, and I repeat
my post here:
> I believe I've hosed up my rpc software subsystem in the course of playing
> with NIS and ypbind on a linux 1.2.13 box. I obtain the following messages,
> origin and cure unknown, in the course of rsh'ing and telnet'ing to a
> neighboring machine:
>
> eeyore:/home/msp/tmp> rsh zool
> lnttcp_create: RPC: Program not registered
>
> eeyore:/home/msp/tmp> telnet zool
> Trying xxx.x.xxx.x ...
> Connected to zool.
> Escape character is '^]'.
> clnttcp_create: RPC: Program not registered
> clnttcp_create: RPC: Program not registered
> clnttcp_create: RPC: Program not registered
> clnttcp_create: RPC: Program not registered
>
> Linux 1.2.13 (zool) (ttyp0)
>
>
> zool login:
> ...
>
> Can someone suggest why the rpc messages are emitted and how to fix them?
> Note that the rsh attempt fails altogether, while telnet complains but
> ultimately does function.
I've done a bit more work on the problem, with this new information: If
I start rpc.portmap in the foreground with verbose messaging and
debugging turned on (rpc.portmap -v -d), I see portmap emit a message to
the controlling tty similar to the following when I telnet into zool
from a peer (# comments are mine)
portmap[xxx]: ... getport(ypbind) # syslog-type message
server: about do a switch # Huh?
Now the server message means nothing to me, but the reference to ypbind
is intriguing (ypbind is *not* running during all this -- I've removed
/var/yp). Recall from above that this whole ordeal started when I
installed YP services on zool (I have subsequently withdrawn zool from
the auspices of YP), thinking it would be fun to experiment ;-)
Finally, a recap on the symptoms: 1) I get a clntcp-type message (see
above) once on booting (when rpc.portmap starts?), 2) ftp and rsh to
zool flat out don't work, failing with similar "RPC program not
registered types of messages, 3) netstat -rn also produces one of the
"RPC program not registered" messages.
Any observations or comments on my problem would be much appreciated.
--
Mark S. Petrovic
Kansas City, MO USA
msp@carpediem.org
