similar to: NFS static ports configuration

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"

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

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

This is the latest stable release of CTDB. CTDB 2.5.5 can be used with Samba releases prior to Samba 4.2.x (i.e. Samba releases 3.6.x, 4.0.x and 4.1.x). Changes in CTDB 2.5.5 ===================== User-visible changes -------------------- * Dump stack traces for hung RPC processes (mountd, rquotad, statd) * Add vaccuming latency to database statistics * Add -X option to ctdb tool that uses

Martin Schwenke schrieb am 15.02.2023 23:23: > Hi Uli, > > [Sorry for slow response, life is busy...] Thanks for answering anyway! > On Mon, 13 Feb 2023 15:06:26 +0000, Ulrich Sibiller via samba > OK, this part looks kind-of good. It would be interesting to know how > long the entire failover process is taking. What exactly would you define as the begin and end of the

Hi, I am trying to mount the windows NT share to solaris 8.0 using Redhat 8.0 nfs. Using smbmount I mounted windows share in Linux as /home/percipia/smb. I setup Linux as NFS Server and exported /home as nfs export. [root@ldap root]# cat /etc/exports /home 192.168.1.0/255.255.255.0(ro,nohide,insecure,sync) [root@ldap root]# rpcinfo -p program vers proto port 100000 2 tcp 111

Hi, I am configuring firewall for NFS. I see that statd and mountd start at random port. Is there any way to force it to start at specific port each time. The '-p ' option would work, but how do I configure it to start at specific port number each time. I mean where do statd and mountd look for default configuration options? Any clues? - CS.

Fresh install of 4.0.6 from source on CentOS 6 minimal. Provisioning worked fine as did adding a Win7 Pro machine to the domain. Now trying to use the RSAT (Remote System Administration Tools), specifically the Active Directory Users and Computers tool. When looking at the properties for the "Administrator" account, clicking on the "Member Of" tab results in a 30 second

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

I would appreciate any ideas on how to correct the problem that we are having that is outlined below. Thanks for your help. I have been running samba for a long time. Currently we are having problems with it filling up /var/log/messages with Feb 7 10:45:02 servername smbd[2157]: Can't become connected user! Feb 7 10:45:02 servername smbd[2158]: [2008/02/07 10:45:02, 0] smbd/

I would appreciate any ideas on how to correct the problem that we are having that is outlined below. Thanks for your help. I have been running samba for a long time. Currently we are having problems with it filling up /var/log/messages with Feb 7 10:45:02 servername smbd[2157]: Can't become connected user! Feb 7 10:45:02 servername smbd[2158]: [2008/02/07 10:45:02, 0] smbd/

Is it possible that Samba4 includes a large PAC on the kerberos credential and you're going over the limit in kernel? Against AD you have to disable this PAC inclusion via the userAccountControl attribute to make kerberised NFSv4 work correctly. You /sometimes/ find that testing with a user who is a member of as close to no groups as possible works in this case, but users in many groups

Is it possible that Samba4 includes a large PAC on the kerberos credential and you're going over the limit in kernel? Against AD you have to disable this PAC inclusion via the userAccountControl attribute to make kerberised NFSv4 work correctly. You /sometimes/ find that testing with a user who is a member of as close to no groups as possible works in this case, but users in many groups

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

On 11/20/20 2:31 PM, Michael B Allen wrote: > On Fri, Nov 20, 2020 at 2:06 PM Michael B Allen <ioplex at gmail.com> wrote: >> Apparently I don't know how to do "that" because this: >> >> # iptables -A INPUT -p tcp --sport 760 -m conntrack --ctstate >> NEW,ESTABLISHED -j ACCEPT >> >> still doesn't allow the traffic through (not that I

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

Hi, I have Xen (unstable) on two Debian Sarge 2.4.27 systems, one of which is an nfs server and the other the nfs client. I am trying to set up NFS root so that I can live migrate my domains from one to another. My /etc/exports on N1(10.5.144.29) /myfs1/foo 10.5.144.27(rw,sync,no_root_squash) 10.5.144.29(rw,sync,no_root_squash) 10.5.144.30(rw,sync,no_root_squash) My /hosts.allow on N1

Hello I find the following email form internet, and I have the same problem, can you share your information about this issue? [Samba] ctdb issue: existing header for db_id 0xf2a58948 has larger RSN 1 than new RSN 1 in ctdb_persistent_store Nate Hardt nate at scalecomputing.com

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