You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
After migrating from crowd 3.1.4 to 3.2.0, viewing the audit log fails with the message:
"Error when loading the audit log. See error logs for details.".
But the logs don't show any errors. Even after a fresh install of the 3.2.0 version, the error occurred.
We use Postgresql 9.5, OpenJDK 1.8 and run crowd behind an nginx reverse proxy. The OS we use is ubuntu 16.04
Any ideas would be greatly appreciated!
Hi @Patrick Wolf,
Adding to @Marcin Kempa 's answer, you can try capturing the HAR requests while you are on Audit Log View.
Here's the way how to generate HAR files
Once you generate HAR files, it would be helpful to search for the reason since the tables exist in database.
while capturing the HAR requests I noticed, that requests against '/auditlog/query' endpoint resulted in 401 errors, due to XSRF protection. I followed the recommended changes from https://confluence.atlassian.com/kb/cross-site-request-forgery-csrf-protection-changes-in-atlassian-rest-779294918.html.
Now the audit logs are displayed correctly!
Thanks for your support!
HI @Patrick Wolf,
You've mentioned that there are no errors in the log, but is it only at the time which correlates with admin accessing the Audit Log? Can you double check if there are no ERRORS at the time when the upgrade happened?
As Audit log was not present in Crowd 2.1.4, I believe it might be an issue with creating DB tables for audit log itself. Can you check in the DB if following tables were created:
Sorry, it was version 3.1.4 from where I migrated. In this version the audit log page worked as expected.
I double-checked the logs and there appeared no error messages neither during the upgrade step, nor while accessing the audit log.
All three audit log tables exist in our database, although cwd_audit_log_entity does not contain any data.