Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 867
  • Last Modified:

Unable to relocate NFS Service

My Cluster is configured in an Active/Passive configuration. When there is a problem with the active node and the attempt is made to failover, there is a failure to relocate the service. Please see below.

Is there a solution to this?




Oct 15 23:28:44 ttecprodnfs2 kernel: Out of Memory: Killed process 31568 (clurgmgrd).
Oct 15 23:28:44 ttecprodnfs2 clurgmgrd: [31568]: <info> Removing IPv4 address 10.33.2.37 from bond0.102
Oct 15 23:28:54 ttecprodnfs2 clurgmgrd: [31568]: <info> Removing export: *:/T24
Oct 15 23:28:55 ttecprodnfs2 last message repeated 10 times
Oct 15 23:28:55 ttecprodnfs2 clurgmgrd: [31568]: <info> unmounting /T24
Oct 15 23:28:56 ttecprodnfs2 clurgmgrd: [31568]: <notice> Forcefully unmounting /T24
Oct 15 23:28:56 ttecprodnfs2 clurgmgrd: [31568]: <warning> Dropping node-wide NFS locks
Oct 15 23:29:06 ttecprodnfs2 clurgmgrd: [31568]: <info> unmounting /T24
Oct 15 23:29:06 ttecprodnfs2 clurgmgrd: [31568]: <notice> Forcefully unmounting /T24
Oct 15 23:29:07 ttecprodnfs2 clurgmgrd: [31568]: <info> Sending reclaim notifications via ttecprodnfs2
Oct 15 23:29:07 ttecprodnfs2 rpc.statd[24171]: Version 1.0.6 Starting
Oct 15 23:29:07 ttecprodnfs2 rpc.statd[24171]: Flags: No-Daemon Notify-Only
Oct 15 23:29:07 ttecprodnfs2 rpc.statd[24171]: statd running as root. chown /tmp/statd-ttecprodnfs2.23993/sm to choose different use
r
Oct 15 23:29:10 ttecprodnfs2 rpc.statd[24171]: Caught signal 15, un-registering and exiting.
Oct 15 23:29:10 ttecprodnfs2 clurgmgrd: [31568]: <err> 'umount /T24' failed, error=0
Oct 15 23:29:10 ttecprodnfs2 clurgmgrd[31568]: <notice> stop on fs "T24" returned 2 (invalid argument(s))
Oct 15 23:29:10 ttecprodnfs2 clurgmgrd[31568]: <crit> #12: RG NFS failed to stop; intervention required
Oct 15 23:29:10 ttecprodnfs2 clurgmgrd[31568]: <notice> Service NFS is failed
Oct 15 23:29:32 ttecprodnfs2 clurgmgrd[31568]: <notice> Shutdown complete, exiting
Oct 16 00:10:19 ttecprodnfs2 sshd(pam_unix)[24196]: session opened for user thomasr by (uid=0)
0
rbtt
Asked:
rbtt
  • 3
1 Solution
 
cjl7Commented:
it woun't relocate because it can't unmount the filesystem. The "manual intervention is needed" line is there so that you know that you need to do manual stuff (eg. unmount the nfs-filesystem) before relocating.


0
 
sjm_eeCommented:
Check to see if any process on the cluster node is using the filesystem - check for open files or processes with a current directory within the filesystem using "lsof".
0
 
cjl7Commented:
NFS is still capable of totally hanging a system, to the point that a reboot is the only solution.

0
 
rbttAuthor Commented:
A force unmount is being done to relocate the NFS service. Will this be sufficient to prevent the unmount from failing?

0
 
cjl7Commented:
In my experience, no not all the times.

But it will behave better.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now