HSF-0019 indicates that a whitelist rule or transactions per second (TPS) throttling rule failed to parse due to invalid formatting.
Error messages
HSF reports one of the following messages depending on the rule type:
| Rule type | Error message |
|---|---|
| Whitelist | [WhiteListRuleParser Component] Invalid rule: ${ruleContent} |
| Whitelist | [WhiteListRuleParser Component] Parsing failed, raw rule: ${ruleContent}, parser: ${parser}. |
| TPS throttling | [TPSRule Component] Invalid rule: ${ruleContent} |
| TPS throttling | [TPSRule Component] Parsing failed, raw rule: ${ruleContent}, parser: ${parser}. |
${ruleContent} is the rule string that failed validation. ${parser} is the parser that rejected it.
Possible causes
The whitelist or TPS throttling rule format is incorrect.
The rule format does not match what the corresponding parser expects.
Resolution
Log in to the instance where the error occurred.
Open
/home/admin/logs/hsf/hsf-config.logand locate theInvalid ruleorParsing failedentry. The${ruleContent}value in the log shows the exact rule that failed.Check whether the format of the configured rule is correct. You can also refer to other information in the error message to locate the issue.
Correct the rule configuration.
Verify the fix
After you update the rule, check hsf-config.log for the following success message:
[TPSRule Component] Parsing OK: ${rule}This message confirms that the rule was parsed successfully. If the error recurs, compare the new ${ruleContent} value in the error entry against the expected rule format.