NFS : how to specify a port number for rpc.statd ?
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
NFS : how to specify a port number for rpc.statd ?
My system has been running nfs-utils-1.2.0 for a few years.
Recently I proceed to upgrade to the latest nfs-utils-1.2.5.
My configure options are "--disable-nfsv4 --disable-nfsv41 --disable-gss --disable-uuid --enable-mount --enable-shared --with-statduser=statd --with-rpcgen=internal --without-tcp-wrappers".
There is no problem in building it, but rpc.statd refuses to start.
> rpc.statd[875]: Version 1.2.5 starting
> rpc.statd[875]: Flags:
> rpc.statd[875]: Could not bind name to socket: Permission denied
The same steps worked well for the old version.
It is started by root in the init script and I'm sure that all the ports (tcp & udp) 1011, 1013 & 1014 are available on my system.
Then I've tried different combinations of values for -o and -p, found that the port number for -p must be at least 1024.
It seems that -p requires an un-privileged port, but there is no mention in the ChangeLog's of the releases from 1.2.1 through 1.2.5.
Since the daemons will run along with a firewall, is there any way to make rpc.statd listening on the specified ports ?
Is SELinux in enforcing mode on your machine?
If yes, try putting it in permissive mode.
If it works, then add SELinux manage rules to allow rpc.statd to listen on required ports, and then put SELinux back in enforcing mode.
To start give the output of
Is SELinux in enforcing mode on your machine?
If yes, try putting it in permissive mode.
If it works, then add SELinux manage rules to allow rpc.statd to listen on required ports, and then put SELinux back in enforcing mode.
To start give the output of
Code:
sestatus
Thanks for your hint.
As far as I know, I'm not using SELinux features and "sestatus" is not yet available on my system.
It was initially a LFS system installed some years ago, but with constant kernel & packages updates.
The current kernel is version 2.6.39.2 . The SELinux-related kernel configs are just the defaults :
Code:
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
# CONFIG_SECURITY_DMESG_RESTRICT is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
# CONFIG_DEFAULT_SECURITY_SELINUX is not set
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_DEFAULT_SECURITY=""
CONFIG_CRYPTO=y
I am sorry, but I haven't really any hint.
Can you have a look at the log files while trying to launch the service?
I've mentioned the log contents in the first post :
> rpc.statd[875]: Version 1.2.5 starting
> rpc.statd[875]: Flags:
> rpc.statd[875]: Could not bind name to socket: Permission denied
It can start if the value of -p is at least 1024.
I guess the nfs-utils developers should have changed something in rpc.statd, but I can't find where this is documented.
Also, I'd like to know if some hack on the codes can restore its original behaviour.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.