Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Error when loading the audit log in crowd. Edited

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!

2 answers

1 accepted

1 vote
Answer accepted

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.

Hi @Gaurav,

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

Now the audit logs are displayed correctly!

Thanks for your support!

1 vote
Marcin Kempa Atlassian Team Jul 26, 2018

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:

  • cwd_audit_log_changeset
  • cwd_audit_log_entity
  • cwd_audit_log_entry



Marcin Kempa

Hi @Marcin Kempa

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

306 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you