Hi,
thank you for your reply. It seems to be a problem with the systemd unit files for nfs-server - specifically a timing issue. [root@centos7-n1 ~]# systemctl list-unit-files --type=service | grep rpcbind rpcbind.service static rpcbind is set to static - should be started on demand by other units. Invoking systemctl start nfs-server is pulling in rpcbind and nfs-lock rpcbind is started - but nfs-lock is maybe trying to start too early: Invoking manually systemctl start rpcbind and then systemctl start nfs-lock works within a second. Invoking manually systemctl start rpcbind and then sytemctl start nfs-server works within a few seconds as well. Invoking manually systemctl start nfs-server is only working randomly due to some timing issues. My current workaround is to also start rpcbind by the cluster - just before nfsserver. I also tried /usr/lib/ocf/resource.d/heartbeat/nfsserver - it is capable of handling systemd systems but start nfs-lock and nfs-server manually - hence hit the same problem in my case. Cheers, Stefan -----Ursprüngliche Nachricht----- Von: Ulrich Windl <ulrich.wi...@rz.uni-regensburg.de> > [root@centos7-n1 ˜]# time systemctl start nfs-server > > real 1m0.480s Probably time to look into syslog. I suspect a name/address resolving issue...
_______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
