-
Bug
-
Resolution: Fixed
-
None
-
High
-
Fix logging for some t5memory errors
-
Emptyshow more show less
Problem
Please check those error messages in the screenshots
Are they false positives, then we must enhance our check, or are they a problem?
Talking of "Match rate is not 103" and "Got old result".
Also t5memory quite often writes logs with error 5005 during concordance search
Also in case t5memory returns 8009 error t5 triggers reorganize for that memory, but affected language resource is not added to the log record, thus reorganize warning is not added to the language resource log in the UI.
Solution
If all of those messages are false positives: Remove them (check those in large production instances of the last few weeks).
Else communicate the source of the problems to Marc
Fix 5005 error
Add language resource to the reorganize warning log