Actions
Bug #8288
closedMany WARN messages after upgrade about JSON deserialisation error
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
See attached log file for all the messages.
A bit of background: I had a server running 3.1.4 that I upgraded to 3.2.2. Right after the upgrade finished, all these messages appeared in the webapp log.
Several issues to note:
1) These messages are pretty worrying, but seem to be only about invalid cache - maybe just silently ignore the cache if it's broken, and only log one human readable warning?
2) There are a bunch of errors that appear on lines all by themselves in the file, with no prefix, just like "stdout" style stuff
I'm not sure if this is related, but at the same time all my rules seemed to suddenly go into "Applying" compliance state.
Note: targeting to 3.2 because that's where I saw this but it could be older.
Files
Actions