Unix Technical Forum

rpcinfo not available

This is a discussion on rpcinfo not available within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hello, I am setting up an NFS server in slackware 9.0. All looks okay (hosts.allow, etc/exports) but on my ...


Go Back   Unix Technical Forum > Unix Operating Systems > Slackware Linux Support

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 02-19-2008, 10:18 AM
edward hage
 
Posts: n/a
Default rpcinfo not available

Hello,

I am setting up an NFS server in slackware 9.0.

All looks okay (hosts.allow, etc/exports) but on my other computer I get
the error:
# mount 192.168.0.3:/home /nfs
mount: RPC: Remote systeem fout (FIXME) - Verbinding geweigerd

For those who don't speak Dutch , this means connection refused.

I want to check the status of the server with rpcinfo, but this is not
available. I am right about that this wasn't included in the package, or
did I install the package wrongly??

I know the changelog for vs. 9.0 says:

Mon Oct 21 17:51:04 PDT 2002
a/smartmontools-5.0_10-i386-1.tgz: Replaces smartsuite package.
n/nfs-utils-0.3.3-i386-3.tgz: In /etc/rc.d/rc.nfsd, don't test for
NFSv3 with rpcinfo, as this does not work with new development kernels.


So I assume that they deliberetely did not put the rpcinfo in . So okay,
what other ways are there to check the status of the NFS server ????


Greetings, Edward Hage

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 02-19-2008, 10:19 AM
Alan Hicks
 
Posts: n/a
Default Re: rpcinfo not available

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, edward hage dared to utter,
> All looks okay (hosts.allow, etc/exports) but on my other computer I get
> the error:
> # mount 192.168.0.3:/home /nfs
> mount: RPC: Remote systeem fout (FIXME) - Verbinding geweigerd


Could you perhaps show us what you've got in those files so we can
ensure that the syntax is correct? Also, do you have /etc/rc.d/rc.nfsd
executable? Did you restart nfsd with /etc/rc.d/rc.nfsd restart? A
little more information here is required to fully diagnose the problem.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAdAfDL3KiNGOqr6ERAjFNAJ97VmqzdKDpJDOnMElUS1 y9OuKS1gCfWO4l
SWWcwrg9IOQhWmMxffOgNe0=
=e3FS
-----END PGP SIGNATURE-----
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 02-19-2008, 10:19 AM
edward hage
 
Posts: n/a
Default Re: rpcinfo not available

Hello Alan,

Thanks for the reply. Here more info:
192.168.0.3 = number computer with problems
192.168.0.2 = number computer no problems

I did a '/etc/rc.d/rc.nfsd restart' and the following message was
printed on screen:

Starting NFS services:
/usr/sbin/exportfs -r
exportfs: No 'sync' or 'async' option specified for export
"192.168.0.0/255.255.255.0:/home".
Assuming default behaviour ('sync').
NOTE: this default has changed from previous versions
/usr/sbin/rpc.rquotad
Cannot register service: RPC: Unable to receive; errno = Connection refused
rpc.quoatad: unable to register (RQUOTAPROG, RQUOTAVERS, udp).
/usr/sbin/rpc.nfsd 8

And then it 'hangs' itself for a few minutes!!!!
Then it resumes with the text:

Cannot register service: RPC: Unable to receive; errno = Connection refused
/usr/sbin/rpc.lockd
/usr/sbin/rpc.statd

And the prompt again.

When I do 'showmount' the following message appears:
mount clntudp_create: RPC: Port mapper failure - RPC: Unable to receive

My /etc/exports:
/home 192.168.0.0/255.255.255.0(rw)

My /etc/hosts.allow:
portmap: 192.168.0.1 , 192.168.0.2
lockd: 192.168.0.1 , 192.168.0.2
rquotad: 192.168.0.1 , 192.168.0.2
mountd: 192.168.0.1 , 192.168.0.2
statd: 192.168.0.1 , 192.168.0.2

My /etc/hosts.deny is empty

I hope this is enough info to understand the problem.
My consern is that I don't have rpcinfo and that it may be because of a
poor installation ?!

Greetings, Edward Hage

Alan Hicks wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In alt.os.linux.slackware, edward hage dared to utter,
>
>>All looks okay (hosts.allow, etc/exports) but on my other computer I get
>>the error:
>># mount 192.168.0.3:/home /nfs
>>mount: RPC: Remote systeem fout (FIXME) - Verbinding geweigerd

>
>
> Could you perhaps show us what you've got in those files so we can
> ensure that the syntax is correct? Also, do you have /etc/rc.d/rc.nfsd
> executable? Did you restart nfsd with /etc/rc.d/rc.nfsd restart? A
> little more information here is required to fully diagnose the problem.
>
> - --
> It is better to hear the rebuke of the wise,
> Than for a man to hear the song of fools.
> Ecclesiastes 7:5
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQFAdAfDL3KiNGOqr6ERAjFNAJ97VmqzdKDpJDOnMElUS1 y9OuKS1gCfWO4l
> SWWcwrg9IOQhWmMxffOgNe0=
> =e3FS
> -----END PGP SIGNATURE-----


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 02-19-2008, 10:19 AM
Alan Hicks
 
Posts: n/a
Default Re: rpcinfo not available

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stop top posting. It's rude and unappreciated, as is failing to trim
your replies. Post your replies in-line to the message content as I do
below.

In alt.os.linux.slackware, edward hage dared to utter,
> I did a '/etc/rc.d/rc.nfsd restart' and the following message was
> printed on screen:
>
> Starting NFS services:
> /usr/sbin/exportfs -r
> exportfs: No 'sync' or 'async' option specified for export
> "192.168.0.0/255.255.255.0:/home".
> Assuming default behaviour ('sync').
> NOTE: this default has changed from previous versions
> /usr/sbin/rpc.rquotad
> Cannot register service: RPC: Unable to receive; errno = Connection refused
> rpc.quoatad: unable to register (RQUOTAPROG, RQUOTAVERS, udp).
> /usr/sbin/rpc.nfsd 8


http://www.google.com/search?hl=en&l...22&btnG=Search

Fifth or sixth link from the top. Always always always google any error
messages you see.

> When I do 'showmount' the following message appears:
> mount clntudp_create: RPC: Port mapper failure - RPC: Unable to receive


If I had to venture a guess, port mapper isn't running.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAdFcGL3KiNGOqr6ERAvoOAJ0ZmxR6Q06NW+Xkk2kj/c0jHs72OQCguJG8
0Cm4CQjA+6QV7XUo97PQbcY=
=Giyv
-----END PGP SIGNATURE-----
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 02-19-2008, 10:21 AM
Eef Hartman
 
Posts: n/a
Default Re: rpcinfo not available

edward hage <edha@xs4all.nl> wrote:
> /usr/sbin/exportfs -r
> exportfs: No 'sync' or 'async' option specified for export
> "192.168.0.0/255.255.255.0:/home".
> Assuming default behaviour ('sync').


Add a "sync" option to your exports file to eliminate this warning.

> Cannot register service: RPC: Unable to receive; errno = Connection refused
> rpc.quoatad: unable to register (RQUOTAPROG, RQUOTAVERS, udp).


That sounds like your portmapper (rpc.portmap) isn't running, and then you
DON'T have got any rpc services (so no NFS, no remote quota, etc.).

> My /etc/exports:
> /home 192.168.0.0/255.255.255.0(rw)


As I said, make that (rw,sync)

> My /etc/hosts.allow:
> portmap: 192.168.0.1 , 192.168.0.2


NO , between IP addresses !!
Seeing your "exports" I would make it 192.168.0.
(which means .* ) or otherwise just a list of IP addresses:
portmap: 192.168.0.1 192.168.0.2
and the same for the other ones. Probably the "scan" of the wrappers
now ends at the , and they never see the .2 address.
We mostly do it this way, as it's a private net anyway:
ALL: 192.168.0.

> I hope this is enough info to understand the problem.
> My consern is that I don't have rpcinfo and that it may be because of a
> poor installation ?!


/usr/sbin/rpcinfo should be in your "glibc-2.*" package, if you _only_
installed "glibc-solibs-2.*" you will not have got it (that package only
installes the shared libraries, not "the rest").
--
************************************************** ******************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M.Hartman@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** ******************
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 07:11 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.2.0
www.UnixAdminTalk.com