Watchfolder events
The following table lists the events that are created for the Watchfolder component.
| Event | Event Type |
Severity | Call Home | Details |
|---|---|---|---|---|
| watchc_service_failed | STATE_CHANGE | ERROR | no | Message: Watchfolder consumer {1} for file system {0} is not running. |
| Description: Watchfolder consumer service is not running. | ||||
| Cause: N/A | ||||
| User Action: For more information, run the systemctl status <consumername> and check '/var/adm/ras/mmwatch.log'. | ||||
| watchc_service_ok | STATE_CHANGE | INFO | no | Message: Watchfolder consumer service for file system {0} is running. |
| Description: Watchfolder consumer service is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| watchc_warn | STATE_CHANGE | WARNING | no | Message: Warning is encountered in watchfolder consumer for file system {0}. |
| Description: Warning is encountered in the watchfolder consumer. | ||||
| Cause: N/A | ||||
| User Action: For more information, check '/var/adm/ras/mmwatch.log'. | ||||
| watchconduit_err | STATE_CHANGE | ERROR | no | Message: {0} error: {1} is encountered in GPFS Watch Conduit for watch id {id}. |
| Description: Error is encountered in GPFS Watch Conduit. | ||||
| Cause: N/A | ||||
| User Action: For more information, check '/var/adm/ras/mmwatch.log'. | ||||
| watchconduit_found | INFO_ADD_ENTITY | INFO | no | Message: Watch conduit for watch id {id} was found. |
| Description: A watch conduit that is listed in the IBM Storage Scale configuration was detected. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| watchconduit_ok | STATE_CHANGE | INFO | no | Message: GPFS Watch Conduit for watch id {id} is running. |
| Description: GPFS Watch Conduit is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| watchconduit_replay_done | STATE_CHANGE | INFO | no | Message: Conduit has finished replaying {0} events for watch id {id}. |
| Description: Conduit replay has finished replaying the events. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| watchconduit_resume | STATE_CHANGE | INFO | no | Message: Conduit has finished producing {0} events to secondary sink for watch id {id}. |
| Description: Conduit is resuming from a suspended state. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| watchconduit_suspended | STATE_CHANGE | INFO | no | Message: GPFS Watch Conduit for watch id {id} is suspended. |
| Description: GPFS Watch Conduit is suspended. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| watchconduit_vanished | INFO_DELETE_ENTITY | INFO | no | Message: GPFS Watch Conduit for watch id {id} has vanished. |
| Description: GPFS Watch Conduit, which is listed in the IBM Storage Scale configuration, has been removed. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| watchconduit_warn | STATE_CHANGE | WARNING | no | Message: {0} warning: {1} is encountered for watch id {id}. |
| Description: Warning is encountered in GPFS watch conduit. | ||||
| Cause: N/A | ||||
| User Action: For more information, check '/var/adm/ras/mmwatch.log'. | ||||
| watchfolder_service_err | STATE_CHANGE | ERROR | no | Message: Error is loading the librdkafka library for watchfolder producers. |
| Description: librdkafka is not installed on the current node. | ||||
| Cause: N/A | ||||
| User Action: Verify that 'gpfs.librdkafka' package is correctly installed. | ||||
| watchfolder_service_ok | STATE_CHANGE | INFO | no | Message: Watchfolder service is running. |
| Description: Watchfolder service is running. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| watchfolderp_auth_err | STATE_CHANGE | ERROR | no | Message: Error obtaining authentication credentials for Kafka authentication. Error message: {2}. |
| Description: Authentication error encountered in event producer. | ||||
| Cause: N/A | ||||
| User Action: Verify that Watchfolder is properly configured. | ||||
| watchfolderp_auth_info | TIP | TIP | no | Message: Authentication information for Kafka is not present or outdated. Request to update credentials has been started and new credentials are used on next event. Message: {2}. |
| Description: Event producer has no or outdated authentication information. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| watchfolderp_auth_warn | STATE_CHANGE | WARNING | no | Message: Authentication credentials for Kafka could not be obtained. Attempt to update credentials are made later. Message: {2}. |
| Description: Event producer failed to obtain authentication information. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| watchfolderp_create_err | STATE_CHANGE | ERROR | no | Message: Error is encountered while creating a new loading or configuring event producer. Error message: {2}. |
| Description: error encountered when creating a new event producer. | ||||
| Cause: N/A | ||||
| User Action: Verify that correct gpfs.librdkafka is installed. For more information, check '/var/adm/ras/mmfs.log.latest'. | ||||
| watchfolderp_found | INFO_ADD_ENTITY | INFO | no | Message: New event producer for {id} was configured. |
| Description: A new event producer was configured. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| watchfolderp_log_err | STATE_CHANGE | ERROR | no | Message: Error opening or writing to event producer log file. |
| Description: Log error encountered in event producer. | ||||
| Cause: N/A | ||||
| User Action: Verify that log directory and file /var/adm/ras/mmwf.log is present and writeable. For more information, check the '/var/adm/ras/mmfs.log.latest'. | ||||
| watchfolderp_msg_send_err | STATE_CHANGE | ERROR | no | Message: Failed to send Kafka message for file system {2}. Error message: {3}. |
| Description: Error while sending messages is encountered in the event producer. | ||||
| Cause: N/A | ||||
| User Action: Check the connectivity to Kafka broker and topic, and whether a broker can accept new messages for the given topic. For more information, check '/var/adm/ras/mmfs.log.latest' and '/var/adm/ras/mmmsgqueue.log'. | ||||
| watchfolderp_msg_send_stop | STATE_CHANGE | ERROR | no | Message: Failed to send more than {2} kafka messages. Producer is now shutdown and no more messages are sent. |
| Description: Producer has reached an error threshold. The producer no longer attempts to send messages. | ||||
| Cause: N/A | ||||
| User Action: To re-enable events, run the mmaudit all producerRestart -N <Node> command. If that does not succeed, then disable and re-enable the watchfolder. Use the mmwatch <device> disable/enable command. However, if watchfolder fails again, then disable and re-enable the message queue if you are running the message queue. Run the mmmsgqueue enable/disable command, and then enable the watchfolder. If the watchfolder continues to fail, then run the mmmsgqueue config --remove command, then enable the message queue, followed by enabling the watchfolder. If you are running with no message queue, then ensure that the external sink is up and reachable from this IBM Storage Scale node. | ||||
| watchfolderp_msgq_unsupported | STATE_CHANGE | ERROR | no | Message: Message queue is no longer supported and no clustered watch folder or file audit logging commands can run until the message queue is removed. |
| Description: Message queue is no longer supported in IBM Storage Scale and must be removed. | ||||
| Cause: N/A | ||||
| User Action: For more information, see the mmmsgqueue config --remove-msgqueue command page in the Command Reference Guide. | ||||
| watchfolderp_ok | STATE_CHANGE | INFO | no | Message: Event producer for file system {2} is OK. |
| Description: Event producer is OK. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| watchfolderp_vanished | INFO_DELETE_ENTITY | INFO | no | Message: An event producer for {id} has been removed. |
| Description: An event producer has been removed. | ||||
| Cause: N/A | ||||
| User Action: N/A |