similar to: rpc.statd is not running but is required for remote locking.

greetings, is there any reason i would want any of these daemons active in memory on a simple DNS server if i do not use NFS and... of course, the unit is not being used as a workstation. 1712 ? Ss 0:00 rpc.statd 1745 ? Ss 0:00 rpc.idmapd 1813 ? Ss 0:00 /usr/sbin/acpid tia - rh

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

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

Hello, after upgrade from CentOS 5 to 5.1 I see the following error in /var/log/messages: 'rpc.idmapd[2330]: main: open(/var/lib/nfs/rpc_pipefs/nfs): No such file or directory' The directory exists with the permissions dr-xr-xr-x 2 root root 0 Dec 7 10:21 nfs So is this an owner/permisson problem? Should /var/lib/nfs/rpc_pipefs/nfs be owned by rpcuser? # ls -al /var/lib/nfs/ total

Hi, Few days a go one of my rsync server stop respond. When I tried to figure out way, I discover that rpc.statd is listen to port 873. Killing the rpc.statd process bypass the problem. I'm using an update version CentOS 4.* rsync start via xinetd. Do you have any idea how it happen? Regards, Milutin Voinivich NasBackup -------------- next part -------------- A non-text attachment

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 ________________________________

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"

On 08/31/2015 01:39 PM, Mark Selby wrote: > 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

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.

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, In current (6140c3177a0330f42411618c3fca28930ea02a21) samba's ctdb/tools/statd_callout_helper I find this comment: notify) ... # we need these settings to make sure that no tcp connections survive # across a very fast failover/failback #echo 10 > /proc/sys/net/ipv4/tcp_fin_timeout #echo 0 > /proc/sys/net/ipv4/tcp_max_tw_buckets #echo 0 >

Hi, Lately, the system log on my CentOS 5 box, with all the latest updates, have started filling up with messages of the form: Jan 24 09:47:26 i58524 rpc.statd[3452]: gethostbyname error for i58524 Jan 24 09:47:26 i58524 rpc.statd[3452]: STAT_FAIL to i58524 for SM_MON of 10.30.39.59 Jan 24 09:47:26 i58524 kernel: lockd: cannot monitor 10.30.39.59 It does not seem like there is really anything

Any help here? I have included all of the output of the suggested diags that Thomas said I should run, but I admit that I'm not sure what I'm looking for, as I'm not familiar with RPC functionality on Linux. Something is not working with RPC on my Samba 4.0.3 server. (FWIW, it doesn't work with IPTables stopped either.) > On Mon, Feb 25, 2013 at 2:21 PM, Mike Stroven wrote:

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

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

Hello Rowland, >> --- >> # Global parameters >> [global] >> >> username map = /etc/samba/user.map >> > > I am sure this has nothing to do with your problem, but you should > remove the 'username map' line, it has no place on a DC. > ok, did so. >> >> It really does not listen: >> >> root at dc2:~# netstat

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

Hi Ulrich, On Tue, 15 Oct 2024 15:22:51 +0000, Ulrich Sibiller via samba <samba at lists.samba.org> wrote: > In current (6140c3177a0330f42411618c3fca28930ea02a21) samba's > ctdb/tools/statd_callout_helper I find this comment: > > notify) > ... > # we need these settings to make sure that no tcp connections > survive # across a very fast failover/failback

Hello there, I installed a dc1 using debian jessie-packages strictly following the samba-manual "Setting up Samba as an Active Directory Domain Controller". I installed a dc2 using debian jessie-packages, also strictly following the manual for "Joining a Samba DC to an Existing Active Directory". It worked for a few weeks but then it quit working without having changed the

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