NFS events
The following table lists the events that are created for the NFS component.
| Event | EventType | Severity | Message | Description | Cause | User Action |
|---|---|---|---|---|---|---|
| dbus_error | STATE_CHANGE | WARNING | DBus availability check failed. | Failed to query DBus, if the NFS service is registered. | The DBus was detected as down. This might cause several issues on the local node. | Stop the NFS service, restart the DBus, and start the NFS service again. |
| disable_nfs_service | INFO | INFO | CES NFS service is disabled. | The NFS service is disabled on this node. Disabling a service also removes all configuration files. This is different from stopping a service. | The user has executed themmces service disable nfs command. | N/A |
| enable_nfs_service | INFO | INFO | CES NFS service is enabled. | The NFS service is enabled on this node. Enabling a protocol service also automatically installs the required configuration files with the current valid configuration settings. | The user has executed the mmces service enable nfs command. | N/A |
| ganeshaexit | INFO | INFO | CES NFS is stopped. | An NFS server instance has terminated. | An NFS instance terminated or was killed. | Restart the NFS service when the root cause for this issue is solved. |
| ganeshagrace | INFO | INFO | CES NFS is set to grace mode. | The NFS server is set to grace mode for a limited time. This gives time to the previously connected clients to recover their file locks. | The grace period is always cluster wide. NFS export configurations might have changed, and one or more NFS servers were restarted. | N/A |
| nfs3_down | INFO | WARNING |  NFSD
process could not be restarted. Reason: {0} |
The NFS v3 NULL check failed when expected it to be functioning. This check verifies if the NFS server reacts to NFS v3 requests. The NFS v3 protocol must be enabled for this check. If this down state is detected, further checks are done to figure out if the NFS server is still working. If the NFS server seems not to be working, then a failover is triggered. If NFS v3 and NFS v4 protocols are configured, then only the v3 NULL test is performed. | The NFS server might hang or is under high load so that the request might not be processed. | Check the health state of the NFS server and restart, if necessary.Check the issues which lead to the unexpected failure. Make sure the kernel NFS server is
not running. |
| nfs3_up | INFO | INFO | NFS v3 check is successful. | The NFS v3 NULL check works as expected. | ||
| nfs4_down | INFO | WARNING | NFS v4 check is failed. | The NFS v4 NULL check failed. This check verifies if the NFS server reacts to NFS v4 requests. The NFS v4 protocol must be enabled for this check. If this down state is detected, further checks are done to figure out if the NFS server is still working. If the NFS server seems to be not working, then a failover is triggered. | The NFS server may hang or is under high load, so that the request could not be processed. | Check the health state of the NFS server and restart, if necessary. |
| nfs4_up | INFO | INFO | NFS v4 check is successful. | The NFS v4 NULL check was successful. | N/A | |
| nfs_active | STATE_CHANGE | INFO | NFS service is now active. | The NFS service must be up and running, and in a healthy state to provide the configured file exports. | The NFS server is detected as active. | N/A |
| nfs_dbus_error | STATE_CHANGE | WARNING | NFS check via DBus failed. | The NFS service must be registered on DBus to be fully working. This is currently not the case. | The NFS service is registered on DBus, but there was a problem accessing it. | Check the health state of the NFS service and restart the NFS service. Check the log files for reported issues. |
| nfs_dbus_failed | STATE_CHANGE | WARNING | NFS check via DBus did not return expected message. | NFS service configuration settings (log configuration settings) are queried through DBus. The result is checked for expected keywords. | The NFS service is registered on DBus, but the check via DBus did not return the expected result. | Stop the NFS service and start it again. Check the log configuration of the NFS service. |
| nfs_dbus_ok | STATE_CHANGE | INFO | NFS check via DBus is successful. | The check if the NFS service is registered on DBus and working, was successful. | The NFS service is registered on DBus and working. | N/A |
| nfs_in_grace | STATE_CHANGE | WARNING | NFS is in grace mode. | The monitor detected that CES NFS is in grace mode. During this time the NFS state is shown as degraded. | The NFS service was started or restarted. | N/A |
| nfs_not_active | STATE_CHANGE | ERROR | NFS service is not active. | A check showed that the CES NFS service, which is supposed to be running is not active. | Process might have hung. | Restart the CES NFS. |
| nfs_not_dbus | STATE_CHANGE | WARNING | NFS service not available as DBus service. | The NFS service is currently not registered on DBus. In this mode, the NFS service is not fully working. Exports cannot be added or removed, and not set in grace mode, which is important for data consistency. | The NFS service might have been started while the DBus was down. | Stop the NFS service, restart the DBus, and start the NFS service again. |
| nfs_sensors_active | TIP | INFO | The NFS perfmon sensor {0} is active. | The NFS perfmon sensors are active. This event's monitor is only running once an hour. | The NFS perfmon sensors' period attribute is greater than 0. | |
| nfs_sensors_inactive | TIP | TIP | The following NFS perfmon sensor {0} is inactive. | The NFS perfmon sensors are inactive. This event's monitor is only running once an hour. | The NFS perfmon sensors' period attribute is 0. | Set the period attribute of the NFS sensors to a value greater than 0. For this use the command mmperfmon config update SensorName.period =N, where SensorName is the name of a specific NFS sensor, and N is a natural number greater 0. Please consider, that this TIP monitor is running only once per hour, and it might take up to one hour in the worst case to detect the changes in the configuration. |
| nfsd_down | STATE_CHANGE | ERROR | NFSD process is not running. | Checks for an NFS service process. | The NFS server process was not detected. | Check the health state of the NFS server and restart, if necessary. The process might hang or is in failed state. |
| nfsd_up | STATE_CHANGE | INFO | NFSD process is running. | The NFS server process was detected. | N/A | |
| nfsd_warn | INFO | WARNING | NFSD process monitoring returned unknown result. | The NFS server process monitoring returned an unknown result. | The NFS server process state could not be determined due to a problem. | Check the health state of the NFS server and restart, if necessary. The process might hang or is in a defunct state. Make sure the kernel NFS server is not running. |
| nfsd_restart | INFO | WARNING | NFSD process restarted. | An expected NFS service process was not running and then restarted. | The NFS server process was not detected and restarted. | Check the health state of the NFS server and restart, if necessary. Check the issues which lead to the unexpected failure. Make sure kernel NFS server is not running. |
| portmapper_down | STATE_CHANGE | ERROR | Portmapper port 111 is not active. | The portmapper is needed to provide the NFS services to clients. | The portmapper is not running on port 111. | Check if the portmapper service is running, and if any services are conflicting with the portmapper service on this system. |
| portmapper_up | STATE_CHANGE | INFO | Portmapper port is now active. | The portmapper is running on port 111. | N/A | |
| portmapper_warn | INFO | WARNING | Portmapper port monitoring (111) returned unknown result. | The portmapper process monitoring returned an unknown result. | The portmapper status could not be determined due to a problem. | Restart the portmapper, if necessary. |
| postIpChange_info | INFO | INFO | IP addresses modified (post change). | The portmapper process monitoring returned an unknown result | CES IP addresses were moved or added to the node, and activated. | N/A |
| rquotad_down | INFO | INFO | The rpc.rquotad process is not running. | Currently not in use. Future. | N/A | N/A |
| rquotad_up | INFO | INFO | The rpc.rquotad process is running. | Currently not in use. Future. | N/A | N/A |
| start_nfs_service | INFO | INFO | CES NFS service is started. | Notification about a NFS service start. | The NFS service was started by issuing the mmces service start nfs command. | N/A |
| statd_down | STATE_CHANGE | ERROR | The rpc.statd process is not running. | The statd process is used by NFSv3 to handle file locks. | The statd process is not running. | Stop and start the NFS service. This also attempts to start the statd process. |
| statd_up | STATE_CHANGE | INFO | The rpc.statd process is running. | The statd process is used by NFS v3 to handle file locks. | N/A | |
| stop_nfs_service | INFO | INFO | CES NFS service is stopped. | Notification about an NFS service stop. | The NFS service was stopped (e.g. by using the mmces service stop nfs). | N/A |