nfs mount: RPC: Rpcbind failure - RPC: Timed out
Carroll, Jim P
jcarro10 at sprintspectrum.com
Fri May 24 01:51:00 EST 2002
I still wouldn't expect it to be a problem. In my environment, I have both
a Solaris and a Linux NIS+ client which mount NFS from a non-NIS+ host.
Granted, the server's name is defined in hosts.org_dir, but I still don't
think that should be a reason.
Have you tried running snoop?
> -----Original Message-----
> From: Mauricio Brigato [mailto:mauricio at gordon.fmrp.usp.br]
> Sent: Thursday, May 23, 2002 10:38 AM
> To: Carroll, Jim P
> Cc: John Aasen; linux-nisplus at lists.samba.org; Jose Augusto
> Baranauskas
> Subject: RE: nfs mount: RPC: Rpcbind failure - RPC: Timed out
>
>
> Yes, from a linux client, runnig NIS (YP), I mount from a server 1.
> From E450, I can't do it. I tested from the replica root master NIS+
> and I mounted it. I've made snoop observation, rpcinfo and nfsstat and
> I've really have a rpcbind communication problem.
> I think I've to add it like a NIS+ host client to get credentials and
> permissions, haven't I?
>
> -------------------------------------------
> Mauricio Brigato
> Suporte BIT - BioInformatic Team
> Fone: +55 16 3963-9300 Ramal: 9603
> E-mail: mauricio at bit.fmrp.usp.br
> Homepage: http://bit.fmrp.usp.br/
> -------------------------------------------
>
> On Thu, 23 May 2002, Carroll, Jim P wrote:
>
> > My first guess would be to ask whether the E450 is properly
> configured to
> > NFS serve.
> >
> > Can you successfully mount from a client which is *not*
> running NIS+?
> >
> > > -----Original Message-----
> > > From: Mauricio Brigato [mailto:mauricio at gordon.fmrp.usp.br]
> > > Sent: Thursday, May 23, 2002 9:04 AM
> > > To: John Aasen
> > > Cc: linux-nisplus at lists.samba.org; Jose Augusto Baranauskas
> > > Subject: nfs mount: RPC: Rpcbind failure - RPC: Timed out
> > >
> > >
> > > I had to left, for a while, the NIS+ linux R.Hat client
> instalation
> > > due to some new server instalation. But I almost got it
> ... I think
> > > I'm getting there !
> > > But, I've got a new solaris server, E450, where I'm
> trying, simply,
> > > mount a NFS directory from another one solaris server and
> > > I'm having that message:
> > > "nfs mount: <server>: RPC: Rpcbind failure - RPC: Timed out"
> > > The detail is that I didn't put this E450 host on the NIS+ server.
> > > May this the cause of the problem ?
> > > Thanx in advance.
> > >
> > > -------------------------------------------
> > > Mauricio Brigato
> > > Suporte BIT - BioInformatic Team
> > > Fone: +55 16 3963-9300 Ramal: 9603
> > > E-mail: mauricio at bit.fmrp.usp.br
> > > Homepage: http://bit.fmrp.usp.br/
> > > -------------------------------------------
> > >
> > > On Tue, 14 May 2002, John Aasen wrote:
> > >
> > > > The NIS+ support was originally written for the SUSE
> > > distribution. killproc
> > > > and startproc are shell functions that are available in the
> > > SUSE startup
> > > > scripts. The /etc/rc.config is also a SUSE specific file.
> > > >
> > > > I think you should start the NIS+ deamons before running
> > > the nisclient script.
> > > > I have found that the following procedure works for getting
> > > a Linux NIS+
> > > > client up and running:
> > > > 1. Copy the start script [nis+ source
> directory]/etc/redhat.rc to
> > > > /etc/rc.d/init.d/nscd
> > > > 2. Make sure the clients time is synchronized with the NIS+
> > > server, either
> > > > with rdate or the time service.
> > > > 3. Run nisinit -c -H [nisserver]
> > > > 4. Run service nscd start
> > > > 5. Run /usr/lib/nisclient -i -d [nis domain name] -h
> [nis+ server]
> > > > This script is written for a SuSE distribution, but
> even though
> > > > there are some warnings about missing rc.config,
> > > > killproc and startproc, it seems they can be safely ignored.
> > > > 6. Add + to the end of /etc/passwd, /etc/shadow and /etc/group.
> > > > 7. Install the new /etc/nsswitch file. The
> > > > main points is a line "publickey : nisplus" and that
> the entries for
> > > > services, protocols and rpc are "files" only, as they are
> > > different for Linux
> > > > and the Solaris NIS+ server.
> > > >
> > > > You should now be able to run "niscat passwd.org_dir"
> and get the
> > > > contents of the NIS+ password table.
> > > > It might be necessary to reboot before you get NIS+ up
> and running.
> > > >
> > > >
> > > > On Monday 13 May 2002 21:26, Mauricio Brigato wrote:
> > > > > I've got a NIS+ server SUN solaris 2.8 running fine.
> > > > > When a try to install a client on linux R.HAT 7.2 client
> > > machine, by
> > > > > running
> > > > > the script "nisclient", as seem bellow, I got a error message:
> > > > > "
> > > > >
> > > > > nisclient -v -i -h SERVER -a ip -d domain.
> > > > > initializing client machine...
> > > > >
> > > > > Initializing client machine for domain
> > > > > "domain.".
> > > > > Once initialization is done, you will need to reboot your
> > > > > machine.
> > > > >
> > > > > Do you want to continue? (type 'y' to continue, 'n' to
> > > exit this script) Y
> > > > >
> > > > > killing NIS and/or NIS+ processes...
> > > > > /usr/lib/nis/nisclient: killproc: command not found
> > > > > /usr/lib/nis/nisclient: killproc: command not found
> > > > >
> > > > > setting up backup files...
> > > > > setting up NIS+ server information...
> > > > > setting up domain information "bit.fmrp.usp.br."...
> > > > > /usr/lib/nis/nisclient: /etc/rc.config: Arquivo ou
> > > diretrio no encontrado
> > > > > cp: cannot stat `/etc/rc.config': Arquivo ou diretrio no
> > > encontrado
> > > > > grep: /etc/rc.config: Arquivo ou diretrio no encontrado
> > > > >
> > > > > setting up the name service switch information...
> > > > > /usr/lib/nis/nisclient: killproc: command not found
> > > > > /usr/lib/nis/nisclient: startproc: command not found
> > > > >
> > > > > running nisinit command ...
> > > > > nisinit -c -H ip ...
> > > > > Couldn't connect to rpc.nisd on ip
> > > > > **ERROR: nisinit failed.
> > > > >
> > > > > Restoring your network service...
> > > > >
> > > > > /usr/lib/nis/nisclient: killproc: command not found
> > > > > /usr/lib/nis/nisclient: killproc: command not found
> > > > > /usr/lib/nis/nisclient: killproc: command not found
> > > > > File /etc/nsswitch.conf restored!
> > > > > /usr/lib/nis/nisclient: /etc/rc.config: Arquivo ou
> > > diretrio no encontrado
> > > > > restoring domain to ...
> > > > > bit.fmrp.usp.br
> > > > >
> > > > >
> > > > > /usr/lib/nis/nisclient: killproc: command not found
> > > > > /usr/lib/nis/nisclient: startproc: command not found
> > > > > restarting nis_cachemgr process...
> > > > > /usr/lib/nis/nisclient: killproc: command not found
> > > > > /usr/lib/nis/nisclient: startproc: command not found
> > > > > Client files restored!"
> > > > >
> > > > > Anyone has any ideas ?
> > > > > Thanks,
> > > > >
> > > > >
> > > > >
> > > > > -------------------------------------------
> > > > > Mauricio Brigato
> > > > > Suporte BIT - BioInformatic Team
> > > > > Fone: +55 16 3963-9603
> > > > > E-mail: mauricio at bit.fmrp.usp.br
> > > > > -------------------------------------------
> > > >
> > > > --
> > > > John Aasen john.aasen at alcatel.no
> > > > Alcatel Norway Tel: +47 22 63 83 09
> > > > Norkrets - Electronics Design Fax: +47 22 63 81 80
> > > >
> > > >
> > > >
> > >
> > >
> >
>
More information about the linux-nisplus
mailing list