Error: o_eep_check_file_resource quantifier operand invalid

Products

• CA Automic Dollar Universe

Issue/Introduction

The universe.log contains repeated errors indicating a failure in the External Event Processor (EEP) when compiling regular expressions for File Resource checks.

Symptoms

The following error appears every few minutes in the universe.log: 

|ERROR|X|EEP|pid=####.####| o_eep_check_file_resource | Error while compiling regular expression: quantifier operand invalid.

Environment

• Dollar Universe 6.x and 7.x
• Component: EEP (External Event Processor)

Cause

A File Resource definition contains a malformed regular expression. The "quantifier operand invalid" error specifically occurs when a regex quantifier (such as *, +, or ?) is used incorrectly at the start of a pattern or without a preceding literal (e.g., using *log instead of .*log).

Resolution

Identify and correct the malformed File Resource definition by following these steps:

1. Enable Enhanced Tracing: In the Node Settings under Logging, set the Main log level to 0,SURCYCLE. This allows the node to log which specific resources are being checked.
2. Identify the Resource: Monitor the universe.log. Locate the trace lines immediately preceding the "quantifier operand invalid" error. These lines will identify the Resource name being processed.

   |TRACE|A|IO |pid=####.####| o_sur_check_supervisor | Resource [RESOURCE_NAME] not found by EEP
   |ERROR|X|EEP|pid=####.####| o_eep_check_file_resource | Error while compiling regular expression: quantifier operand invalid.

3. Correct the Definition: Open the identified Resource definition in the Univiewer Console (UVC). Check the Filename or Filter field for regex syntax errors. Ensure that all quantifiers have valid operands (e.g., change *filename to .*filename).
4. Verify: Save the changes. The errors should cease in the universe.log. Revert the log level to its original state once confirmed

Additional Information

In case the particular resource cannot be identified with 0,SURCYCLE please open a case with Broadcom referring to this article so that we can deliver a modified EEP process that will add additional tracing in case of this error, displaying both the resource and the regex that generate the errors, see below:

|ERROR|X|EEP|pid=###.###| o_eep_check_file_resource | Error with resource [RESOURCE_NAME].
|ERROR|X|EEP|pid=###.###| o_eep_check_file_resource | Error while compiling regular expression [REGEX_ON_RESOURCE_NAME]: quantifier operand invalid.

Changes in the product will be done in the future to enhance the traces for this particular error, this will be done via S528193.