Including NFSRestart resources in Storage Foundaion HA 5.1 SP1
When you run an offline service group offline in
The output shows the following error messages on the NFS resource.

─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─
2011/03/07 10:32:35 VCS ERROR V-16-10031-7029 (node1) NFS: nfs: monitor:
Daemon [rpc.nfsd] is not running.
─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─
※ This phenomenon, please see below for details of the output message.

NFS resource monitor from 5.1 SP1 Support your answer with
The message that is to be output is changed by the process
If no error occurs I understand that we can ignore the message.

In addition, the above error message is detected that there is no process for NFS
Or if a message is output, to clarify the process did not exist
We intended to be briefed.

Therefore, for the following reasons, the severity of the message as to NOTICE improvement plan
We proposed to change.

[Reasons on ways to improve]
(1) to clarify the process did not present any of the NFS
    A message, even if you do not have the NFS process is aborted
    Is output.

(2) If a process is aborted for NFS, except this error message
    You can also check the error messages abnormalities.

(3) In order to stop the process off-line processing of NFS NFSRestart,
    Both messages are printed without any problems.

(4) and group services for NFS cluster even without a temporary process
    And does not necessarily affect.

(5) to be just an error message to stop the service group
    log monitoring tools such as swatch and the engine_A.log Centric Manager
    If you are monitoring an abnormality is detected even if no abnormality has occurred.

(6) If no abnormal process termination message can be ignored for NFS
    But because it is a message of severity ERROR, if there is no explanation
    The message can be ignored and customers can not tell.

(7) severity ERROR or WARNING messages can not be concerned about your
    Because there are probably more to your inquiry.

─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ output message details

Dependencies Resource

        <Parents>
  ┌ ─ ─ ─ ─ ─ ─ ─ ┐
  │ NFSRestart │
  │ (nfs_restart2) │
  └ ─ ─ ─ ┬ ─ ─ ─ ┘
  ┌ ─ ─ ─ ┴ ─ ─ ─ ┐
  │ IP │
  │ (ip) │
  └ ─ ─ ─ ┬ ─ ─ ─ ┘
  ┌ ─ ─ ─ ┴ ─ ─ ─ ┐
  │ Share │
  │ (share) │
  └ ─ ─ ─ ┬ ─ ─ ─ ┘
  ┌ ─ ─ ─ ┴ ─ ─ ─ ┐
  │ NFSRestart │
  │ (nfs_restart1) │
  └ ─ ─ ─ ┬ ─ ─ ─ ┘
  ┌ ─ ─ ─ ┴ ─ ─ ─ ┐
  │ NFS │
  │ (nfs) │
  └ ─ ─ ─ ─ ─ ─ ─ ┘
        <Child>

[An error processing flow of the message]

1. Perform the service group offline

2. Offline top NFSRestart resources.

  Process ★ NFS (nfsd, mountd, statd, lockd, smsyncd) to stop

3. The monitor is running the NFS resource.
  (Existence of a process to monitor NFS)

  This message is output ★.

4. NFSRestart resource offline subordinate.

  Restart the NFS process has stopped all top-level resource NFSRestart ★
─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─

Is over.