Bringing an NFS Resource In‑Service (Restore)
| 106003 | restore: Unable to create the export entry file for “EXPORT POINT” in LifeKeeper | Possible causes:
|
| 106007 | Cannot bring “NFS or HA-NFS” resource “TAG” In Service on server “SERVER” | Review other error messages to determine the action to take. After correcting the problem, try bringing the resource in service manually. |
| 106010 | NFS is not running on server “SERVER”. LifeKeeper will attempt to restart NFS. | This message is for information only. LifeKeeper will try to restart the NFS daemons automatically. If LifeKeeper encounters problems while restarting one of the daemons, you will receive a message that starting NFS failed. |
| 106011 | Starting NFS on server "SERVER" failed | There was a problem while restarting the NFS daemons. Try manually restarting NFS. |
| 106012 | The export point "EXPORT POINT" is not exported on server "SERVER". LifeKeeper will attempt to export the entry | LifeKeeper has detected that the export point is no longer exported, and will try to export it. |
| 106013 | Unable to export "EXPORT POINT" on server "SERVER" | Try manually exporting the file system. |
| 106019 | Executing command: "COMMAND" | This message is displayed when LifeKeeper restarts an NFS daemon or exports/unexports an export point. It provides additional information that can be useful if there is a problem. |
| 106024 | Unable to stop and restart rpc.mountd on "SERVER" | During a hierarchy restore the rpc.mountd daemon process needed to be restarted and this process failed. Manually attempt to stop and restart the process to determine the error and the action to take. |
| 106027 | Open of "FILE NAME" on server "SERVER" failed: "ERROR MSG" | The attempted open failed for the reason listed. |
| 106028 | Mount of /proc/fs/nfsd failed on server "SERVER" | In 2.6 and later kernels /proc/fs/nfsd is used for client authentication and an attempt to mount it failed. Manually attempt to mount /proc/fs/nfsd to determine the failure. |
| 106030 | Unable to restore client info for "CLIENT" on server "SERVER": "ERROR MSG" | Client lock failover failed. Correct the failure condition and attempt to restore the hierarchy again. |
| 106039 | Open of "FILE" on server "SERVER" failed: "ERROR MSG" or Attempt to get exclusive lock on "FILE" on server "SERVER" failed: "ERROR MSG" |
An attempt to open or obtain an exclusive lock on a file has failed. See the error message for the cause. |
| 106040 | Multiple virtual IP addresses detected. In this release NFS lock failover only supports one virtual IP address. | Recreate the NFS resource hierarchies to use only one virtual IP address or set FAILOVERNFSLOCKS to false in the LifeKeeper defaults file. |
| 106052 | Unable to mount rpc_pipefs on "SERVER". Reason: "REASON". | rpc_pipefs was not mounted on SERVER and the mount attempt failed for REASON. |
| 106053 | rpc_pipefs successfully mounted on "SERVER" | rpc_pipefs was successfully mounted on SERVER. |
| 106054 | Ping test of the nfsd processes on “SERVER” failed. | Ping to the NFS server failed. |
| 106055 | The attempted restart of the nfsd processes on “SERVER” failed. | The nfsd process is restarted but the NFS server is not responding. |
| 106056 | Attempting to kill hung nfsd processes on “SERVER”. | Since the NFS server was not responding, kill the nfsd process and restart it. |
| 106057 | Failed to open new exportInfo file “TMP FILENAME”. Reason: “ERROR MSG”. | Failed to open a temporary file for the reason listed. |
| 106058 | Failed to add the entry “ENTRY” to “TMP FILENAME”. Reason: “ERROR MSG”. | Failed to write to the temporary file for the reason listed. |
| 106059 | Failed to close new exportInfo file “TMP FILENAME”. Reason: “ERROR MSG”. | Failed to close the temporary file for the reason listed. |
| 106060 | Failed to create the new exportInfo file “TMP FILENAME” as it’s size of “NEW SIZE” is less than the size of the current exportInfo with a size of “OLD SIZE”. The size should be at least the same as the old file size. | The newly created exportinfo file is not the expected size. |
| 106061 | Failed to rename temp exportInfo file from “TMP FILENAME” to “FILENAME”. Reason: “ERROR MSG”. | Failed to rename the file for the reason listed. |
| 106062 | fsid(FSID) does not match between resource info and etab on “SERVER”. | The expected fsid is not included in etab. |
| 106063 | Failed due to mismatch between InfoFile and etab on “SERVER”. | The export is not working as expected. |
| 106064 | Pseudo file system (fsid=0) protected by NFS RK is not supported in LifeKeeper v9.6.0 and later. Please delete the “TAG” resource whose export point is “EXPORT POINT”. | Pseudo file system is not supported in LifeKeeper v9.6.0 and later. Please delete the resource hierarchy. |
| 106065 | The exportfs command appears to have hung during the “restore” action. Aborting the “restore”. | Restore was aborted because the exportfs command hung. Please resolve the exportfs hang. If the hang persists, reboot the system. Please refer to NFSEXPORTFSTIMER in the NFS Parameters List for determining exportfs command hang. |
| 106066 | Forcefully killing hung process:ps=“PROCESS REPORT”. | The exportfs command hung and a KILL signal was sent. The PROCESS REPORT shown is the output of the “ps -f” command before the KILL signal was sent. |
Taking an NFS Resource Out of Service (Remove)
| 106008 | Unable to unexport the export point "EXPORT POINT" on server "SERVER" | Use the exportfs(8) command to unexport it. |
| 106014 | Usage: USAGE STRING | Usage of command run with incorrect arguments. Command line only. |
| 106019 | Executing command: "COMMAND" | This message is displayed when LifeKeeper restarts an NFS daemon or exports/unexports an export point. It provides additional information that can be useful if there is a problem. |
| 106047 | nfsd stalled on “SERVER”. | Failed to stop nfsd process. |
| 106065 | The exportfs command appears to have hung during the “remove” action. Aborting the “remove”. | Remove was aborted because the exportfs command hung. Please fix the exportfs hang. If the hang persists, reboot the system. Please refer to NFSEXPORTFSTIMER in the NFS Parameters List for determining exportfs command hang. |
| 106066 | Forcefully killing hung process:ps=“PROCESS REPORT”. | The exportfs command hung and a KILL signal was sent. The PROCESS REPORT shown is the output of the “ps -f” command before the KILL signal was sent. |
NFS Resource quickCheck
| 106040 | Multiple virtual IP addresses detected. In this release NFS lock failover only supports one virtual IP address. | Recreate the NFS resource hierarchies to use only one virtual IP address or set FAILOVERNFSLOCKS to false in the LifeKeeper defaults file. |
| 106054 | Ping test of the nfsd processes on “SERVER” failed. | Ping to the NFS server failed. |
| 106063 | Failed due to mismatch between InfoFile and etab on “SERVER”. | The export is not working as expected. |
Bringing an NFS Resource Back In Service (Recover)
| 106010 | NFS is not running on server “SERVER”. LifeKeeper will attempt to restart NFS | This message is for information only. LifeKeeper will try to restart the NFS daemons automatically. If LifeKeeper encounters problems while restarting one of the daemons, you will receive a message that starting NFS failed. |
| 106011 | Starting NFS on server “SERVER” failed | There was a problem while restarting the NFS daemons. Try manually restarting NFS. |
| 106012 | The export point “EXPORT POINT” is not exported on server “SERVER”. LifeKeeper will attempt to export the entry | LifeKeeper has detected that the export point is no longer exported, and will try to export it. |
| 106013 | Unable to export “EXPORT POINT” on server “SERVER” | Try manually exporting the file system. |
| 106019 | Executing command: “COMMAND” | This message is displayed when LifeKeeper restarts an NFS daemon or exports/unexports an export point. It provides additional information that can be useful if there is a problem. |
| 106027 | Open of “FILE NAME” on server “SERVER” failed: “ERROR MSG” | The attempted open failed for the reason listed |
| 106028 | Mount of /proc/fs/nfsd failed on server “SERVER” | In 2.6 and later kernels /proc/fs/nfsd is used for client authentication and an attempt to mount it failed. Manually attempt to mount /proc/fs/nfsd to determine the failure. |
| 106030 | Unable to restore client info for “CLIENT” on server “SERVER”: “ERROR MSG” | Client lock failover failed. Correct the failure condition and attempt to restore the hierarchy again. |
| 106039 | Open of “FILE” on server “SERVER” failed: “ERROR MSG” or Attempt to get exclusive lock on “FILE” on server “SERVER” failed: “ERROR MSG” |
An attempt to open or obtain an exclusive lock on a file has failed. See the error message for the cause. |
| 106040 | Multiple virtual IP addresses detected. In this release NFS lock failover only supports one virtual IP address. | Recreate the NFS resource hierarchies to use only one virtual IP address or set FAILOVERNFSLOCKS to false in the LifeKeeper defaults file. |
| 106052 | Unable to mount rpc_pipefs on “SERVER”. Reason: “REASON”. | rpc_pipefs was not mounted on SERVER and the mount attempt failed for REASON. |
| 106053 | rpc_pipefs successfully mounted on “SERVER” | rpc_pipefs was successfully mounted on SERVER. |
| 106054 | Ping test of the nfsd processes on “SERVER” failed. | Ping to the NFS server failed. |
| 106055 | The attempted restart of the nfsd processes on “SERVER” failed. | The nfsd process is restarted but the NFS server is not responding. |
| 106056 | Attempting to kill hung nfsd processes on “SERVER”. | Since the NFS server was not responding, kill the nfsd process and restart it. |
| 106063 | Failed due to mismatch between InfoFile and etab on “SERVER”. | The export is not working as expected. |
| 106065 | The exportfs command appears to have hung during the “recover” action. Aborting the “recover”. | Recover was aborted because the exportfs command hung . Please resolve the exportfs hang. If the hang persists, reboot the system. Please refer to NFSEXPORTFSTIMER in the NFS Parameters List for determining exportfs command hang. |
| 106066 | Forcefully killing hung process:ps=“PROCESS REPORT”. | The exportfs command hung and a KILL signal was sent. The PROCESS REPORT shown is the output of the “ps -f” command before the KILL signal was sent. |
Post your comment on this topic.