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
Next: Root
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.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
TimeLevelDescriptionException
2019-01-19 00:09:03 | fatal | Error while trying to initialise Crowd Container. liquibase.exception.LockException: liquibase.exception.DatabaseException: Error executing SQL UPDATE public.cwd_databasechangeloglock SET LOCKED = TRUE, LOCKEDBY = 'ip-10-0-0-193.ec2.internal (10.0.0.193)', LOCKGRANTED = '2019-01-19 00:09:03.280' WHERE ID = 1 AND LOCKED = FALSE: ERROR: cannot execute UPDATE in a read-only transaction Location: File: utility.c, Routine: PreventCommandIfReadOnly, Line: 236 Server SQLState: 25006 | |
2019-01-19 00:09:03 | fatal | This Crowd instance was unable to start the scheduler CrowdSchedulerService, and will not be usable. Please check the log for details. |
This usually means that the database is in a read-only mode, either at a server, database or user level. I've seen it when people were running backup scripts (make it read-only to force a consistent data set to be taken). You'll need to check the state of the crowd database.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.