TokenServer returned Error 6: General error (EvalRiskTask)
Article ID: 201355
Updated On:
Products
Issue/Introduction
AFM logs show a LDAP+RISK flow failing with this footprint
020-10-09 14:57:44,090 [http-nio-8080-exec-7] ERROR integrations.frontend.LifeCycleStateData(704) -> 707029046: Server request result unexpected: TokenServer returned Error 6: General error (EvalRiskTask)
Environment
Release : 9.0
Component : AuthMinder(Arcot WebFort)
RiskMinder(Arcot RiskFort)
Cause
The root cause of this issue is not due to any communication failure with Arcot State Manager (aka Token Server). This issue is due to rules data discrepancy in the Arcot Riskfort tables. Hence the Risk Evaluation fails with such footprints in the arcotriskfort.log. Essentially, a rule like MODELSCORE could no be loaded and then all subsequent rules cannot be loaded. Note is this example the first rule with a DB discrepancy is MODELSCORE.
Tue Sep 01 10:46:03.662 2020 WARNING: pid 1136 tid 6336: 5: 10:35002: Couldn't load library []
Tue Sep 01 10:46:03.662 2020 WARNING: pid 1136 tid 6336: 8: 10:35002: Detected unloadable addon rule lib [] for rule mnemonic [MODELSCORE]. This rule will be deactivated until the problem is fixed. To fix the problem, either delete the rule, or ensure the library is present in the correct location on the system and refresh the cache or restart the server.
Tue Sep 01 10:46:03.662 2020 WARNING: pid 1136 tid 6336: 5: 10:35002: Couldn't load library []
Tue Sep 01 10:46:03.662 2020 WARNING: pid 1136 tid 6336: 8: 10:35002: Detected unloadable addon rule lib [] for rule mnemonic [DEVICEVELOCITY]. This rule will be deactivated until the problem is fixed. To fix the problem, either delete the rule, or ensure the library is present in the correct location on the system and refresh the cache or restart the server.
Tue Sep 01 10:46:03.662 2020 WARNING: pid 1136 tid 6336: 5: 10:35002: Couldn't load library []
Resolution
Essentially, there is a mismatch in the latest CONFIGVERSION of rules identified by CONFIGTYPE. This configversion needs to be same for all rules
Essentially, take the following steps:
1. Take DB snapshot before making any changes so that you can revert back to the previous state if any of the SQL queries suggested do no help address this issue.
2. You may want to review the data output using these two select queries.
SELECT * FROM ARRFSYSRULEEXECCONFIG WHERE RULEMNEMONIC = 'MODELSCORE'
SELECT * FROM ARRFSYSORGCONFIG WHERE CONFIGTYPE = 'MODELSCORE'
3. The above two select queries will show that ALL of the rules have the same CONFIGVERSION (say for example 59) except the offending rule which is MODELSCORE in this example will show a different CONFIGVERSION (in this example that CONFIGVERSION is 47). Given the data in the example these two deletes will help you correct the Riskfort's Risk Evaluation processing.
DELETE FROM ARRFSYSRULEEXECCONFIG WHERE RULEMNEMONIC = 'MODELSCORE'
DELETE FROM ARRFSYSORGCONFIG WHERE CONFIGTYPE = 'MODELSCORE' AND CONFIGVERSION = 47
Additional Information
None.
Feedback
