search for: statd_hostnam

...se 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 -H /etc/ctdb/statd-callout -p 662 -o 2020 I could be wrong, but it looks to me that ctdb is using t...

...for this and were wondering what other people in similar environments are doing with the their CTDB shared files. Specifically, I'm referring to the locations supplied for <shared_dir> in these variables: /etc/sysconfig/ctdb: CTDB_RECOVERY_LOCK=<shared_dir> /etc/sysconfig/nfs: STATD_HOSTNAME=$NFS_HOSTNAME -P <shared_dir> -H /etc/ctdb/statd-callout /etc/sysconfig/nfs: NFS_TICKLE_SHARED_DIRECTORY=<shared_dir> /etc/sysconfig/nfs: STATD_SHARED_DIRECTORY=<shared_dir> Thanks! Stewart

...oblematic, follow the reboot of some client on the network while failovers that are successful happen after the connections of all rebooted clients have been reset. The specific configuration option that makes me think statd is misconfigured is this one from /etc/sysconfig/nfs: """ STATD_HOSTNAME="$NFS_HOSTNAME -H /etc/ctdb/statd-callout -p 97" """ ...I notice that the -P parameter is missing from this string, which is described in `man rpc.statd` as follows: """ -P, --state-directory-path pathname Specifies the pathname of the...