search for: statd

...FS 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 mount a newly booted machine and systemd via listening sockets (1) starts rpc.statd (fails) (2) starts rpcbind (3) rpc.statd timesout after 60 seconds and then starts sucessfully (3) performs the nfs mount I see that rpc.statd is attempted to start at the time that I perform the mount request - it just takes 60 seconds to start. I think this is because it tries to start before...

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 in /etc/sysconfig/nfs, which is where the statd-callout script is passed to statd. In our case, this means that statd is running as rpc.statd -p 662 -o 2020 instead of rpc.statd -n gfs...

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...

...hat 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 mount > a newly booted machine and systemd via listening sockets > > (1) starts rpc.statd (fails) > (2) starts rpcbind > (3) rpc.statd timesout after 60 seconds and then starts sucessfully > (3) performs the nfs mount > > I see that rpc.statd is attempted to start at the time that I perform > the mount request - it just takes 60 seconds to start. I think this is >...

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 #...

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 > #echo 10 > /proc/sys/net/ipv4/tcp_fin_timeout > #echo 0 > /proc/sys/net/ipv4/t...

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 /usr/sbin/start-statd

...culties. During the last fail-back procedure (12/09), clients experienced instability (mounts not responding, bizarre permissions errors) while the CTDB hosts continued to complain their logs about timed out event scripts (IP take or release) related. Finally, CTDB seems to get fed up and restart statd and nfsd and all goes back to normal. 4) During two of these failure events, CTDB on one of the nodes has actually *died* and had to be restarted for fail-back to occur. So, in broad strokes, those are the kind of events that I've been seeing in this cluster. My theory about the cause of th...

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.

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 was scrubbed...

...localhost failed (Error NT_STATUS_CONNECTION_REFUSED) dnl at storestone:~$ sudo netstat -tulpn | egrep "53|88|135|137|138|139|389|445|464|636" tcp 0 0 0.0.0.0:464 0.0.0.0:* LISTEN 2255/kadmind tcp 0 0 0.0.0.0:48336 0.0.0.0:* LISTEN 1536/rpc.statd tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 15607/samba tcp6 0 0 :::464 :::* LISTEN 2255/kadmind tcp6 0 0 :::33968 :::* LISTEN 1536/rpc.statd udp 0 0 127.0.0.1:864 0.0.0.0:* 1536/rpc.statd...

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

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 Drodofsk...

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 its way. Stopping the mail server services drops rpc.statd fr...

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 wrong with the hosts setup, though - the gethostbyname call...

...------------------ Red Hat, Inc. Security Advisory Synopsis: Revised advisory: Updated package for nfs-utils available Advisory ID: RHSA-2000:043-03 Issue date: 2000-07-17 Updated on: 2000-07-21 Product: Red Hat Linux Keywords: rpc.statd root compromise Cross references: N/A --------------------------------------------------------------------- 1. Topic: This is an updated of RHSA-2000:043 that contains further upgrade instructions. The rpc.statd daemon in the nfs-utils package shipped in Red Hat Linux 6.0, 6.1, and 6.2 contains...

Hai, ? If updated the repo's for amd64/i386 . ? Buster????samba 4.10.10 Stretch???samba 4.9.15 + 4.10.10 Bionic??? samba 4.9.15 + 4.10.10 ? No changes made by me. ? Repo info : https://apt.van-belle.nl/ ? Have fun with these.. ? ? Greetz, ? Louis ? ?

...module from being pre-loaded #NFSD_MODULE="noload" # Set V4 grace period in seconds #NFSD_V4_GRACE=90 # # # # Optional arguments passed to rpc.mountd. See rpc.mountd(8) #RPCMOUNTDOPTS="" # Port rpc.mountd should listen on. #MOUNTD_PORT=892 # # # Optional arguments passed to rpc.statd. See rpc.statd(8) #STATDARG="" # Port rpc.statd should listen on. #STATD_PORT=662 # Outgoing port statd should used. The default is port # is random #STATD_OUTGOING_PORT=2020 # Specify callout program #STATD_HA_CALLOUT="/usr/local/bin/foo" # # # Optional arguments passed to rpc....

Hello, I am attempting to get flock/file locking working between my -stable (updated ~19 may) nfs file server and -current desktop; the server is running lockd/statd, and both my mail client (mutt) and a simple perl program complain that files on the nfs server cannot be locked. I am aware that there has been work on the nfs locking code in current, and have a vague recollection of a workaround required for the situation I am in, but cannot remember it (and can...