similar to: mountd and statd at specific ports - nfs firewall

I have changed /etc/sysconfig/nfs to specify port numbers for NFS daemons. Somehow statd is still starting up at random port number. Other damons are starting at properly at specified port numbers Any clues on what might be wrong? Any other location/setting that takes precedence over sysconfig/nfs ? It's CentOS 5.5 64bit with nfs-utils 1.0.9-44.el5. -- Thanks, CS

After getting a reasonably configured NFS4 setup working on my Scientific Linux server, I spent a majority of my evening trying to do the same with my Centos 5 box, with fruitless results. Most attempts to mount that server returns the following message: [root at sl01 log]# mount -t nfs4 192.168.15.200:/opt/company_data /mnt mount.nfs4: Operation not permitted As nearest as I can tell, I was

Hi all, I have setup a CentOS6.3 x86_64 host to act as a nfs server. According to RHEL6 docs, portmap is not needed when you use NFSv4, but in my host I need to start rpcbind service to make NFSv4 works. My /etc/sysconfig/nfs # # Define which protocol versions mountd # will advertise. The values are "no" or "yes" # with yes being the default MOUNTD_NFS_V2="no"

This removes the appliance configuration bits from the installer and associated files since it has been deprecated --- installer/modules/ovirt/files/cobbler-import | 6 - .../modules/ovirt/files/ovirt-appliance-setup | 4 - installer/modules/ovirt/files/ovirt-storage | 73 ---------- installer/modules/ovirt/manifests/appliance.pp | 152 -------------------- 4 files

Hi all, Which ports do I need to have open on an NFS client's firewall to allow it to connect to a remote NFS servers? When I disable iptables (using ConfigServerFirewall), it connects fine, but as soon as I enable it, NFS gives me this error: root at saturn:[~]$ mount master1.mydomain.co.za:/saturn /bck mount: mount to NFS server 'master1.mydomain.co.za' failed: RPC Error: Unable to

I have two RHEL4 email servers running postfix/MailScanner which use dovecot. They work great. But during bootup the nfslock script in my init.d loads rpc.statd and calls portmap to get a port number. Portmap keeps giving rpc.statd the imaps port number (993). I then have to stop my mail server services, manually start dovecot, then restart the mail server services and everything goes merrily on

Hello, booting starts /etc/init.d/nfslock. today, rpc.statd used port 873. later starting xinetd finds port used and disabled rsync daemon. So its more or less a lucky break, to boot CentOS and have rsync running? In /etc/rc3.d is S14nfslock S56xinetd so by design xinetd starts always after nfslock!!!! Best regards -- Viele Gr??e i.V. Helmut Drodofsky ________________________________

I've got a newly installed Centos 5.0 box, planned to replace an ageing server (solaris box). I've set up the nfs shares, but the other solaris boxes won't mount them, unless I turn of iptables on the Centos box. If I do that, they mount, and all operations tested to date work fine. Iptables is allowing the 2049 tcp and udp ports already. What else needs to be opened up in

Hi Everyone, I have been trying to setup an NFS v4 File Server but have come across an odd issue. Mounting the /nfs4exports/share appears to be successful and the information displayed about partition size and free space seem correct but if I try to do anything inside the mounted directory the client will just hang. Does anyone have any idea what I am missing?? I have try disabling all

Below is my firewall rules for iptables. everything is working fine except for NFS I cannot mount my drive. If I turn off iptables I can mount. Looking at this : http://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-nfs.html Important In order for NFS to work with a default installation of Red Hat Enterprise Linux with a firewall enabled, IPTables with the default TCP port 2049

On Fri, Nov 20, 2020 at 12:18 PM Frank Cox <theatre at sasktel.net> wrote: > > On Fri, 20 Nov 2020 12:07:40 -0500 > Michael B Allen wrote: > > > So TCP src 760 to 41285. What's that? > > Apparently "that" is what you need to allow in order for your desktop to work. > > What it is actually doing, I'm not sure. Google tells me that port 760 has

Hi all, I have a requirement to run NFS read-only in an Internet-facing colocation environment. I am not happy with packet filters alone around rpcbind, call me paranoid, so I just spent the last few minutes cutting this patch. As you are aware, RPC applications can be forced to listen on a known port through the sin/sa argument to bindresvport[_sa](). Why several Linux distributions have this

Hello, First and foremost, thanks *very* much for ctdb. It's a joy to use after banging around with other HA solutions. We're planning to use it to export Samba and NFS shares throughout campus. I'm having one problem with the NFS part though. When ctdbd first starts statd (we're using CTDB_MANAGES_NFS=yes), it does so without appending the stuff in the STATD_HOSTNAME variable

I have seen some talk about this but have not seen any answers. I know this is a problem on CentOS 7.1 and I also think it is a problem on CentOS 7.0. Basically if I have an NFS client only config - meaning that the nfs-server.service is not enabled then I have to wait 60 seconds after boot for the 1st NFSV3 mount to succeed. What I can surmise is the following. I attempt to perform a NFS

Hello I'm trying to mount a nfs system. But i receive this message: mount -t nfs <IP>:/backup /backupnfs mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified After a fews searchs on google i tried to execute the files: sbin/rpc.statd

That is the thing - rpc.statd does have rpcbind a pre-req. It looks like systemd is not handling this correctly. Just wondering if anyone knows a good way to fix. root at ls2 /usr/lib/systemd/system 110# grep Requires rpc-statd.service Requires=nss-lookup.target rpcbind.target On 8/30/15 7:45 PM, Rob Kampen wrote: > On 08/31/2015 01:39 PM, Mark Selby wrote: >> I have seen some talk

Hi, What is the magic juju that I have to put in /etc/sysconfig/autofs to get autofs to default to using NFSv4, rather than NFSv3, for mounting file systems? I don't want to place these flags into the automount maps themselves because we have a varied network with Sun, CentOS, RedHat and Macintosh systems, and the flags that have to get added to automount maps (which we distribute centrally

I''m curious if anybody else has seen this behavior.... Right now I have puppetd making sure that NFS and NTP services are running across a group of hosts, and if for some reason those services are not running, puppet will happily start them up for me. The catch is, in my environment we''re pushing towards IPv6 except for customer facing equipment. So when puppet comes along and

Hi, I'm trying to setup a firewalled NFS server. I've configured my server (CentOS 5) using the following parameters /etc/sysconfig/nfs MOUNTD_NFS_V1="no" MOUNTD_NFS_V2="no" RQUOTAD_PORT=875 LOCKD_TCPPORT=32803 LOCKD_UDPPORT=32769 RPCNFSDCOUNT=64 MOUNTD_PORT=892 STATD_PORT=662 STATD_OUTGOING_PORT=2020 SECURE_NFS="yes" modprobe.conf: options lockd

I run chkrootkit daily. For the first time I've got reports of a problem - Checking `bindshell'... INFECTED (PORTS: 1008) The page http://fatpenguinblog.com/scott-rippee/checking-bindshell-infected- ports-1008/ suggests that this might be a false positive, so I ran 'netstat - tanup' but unlike the report, it wasn't famd on the port. It was tcp 0 0 0.0.0.0:1008