|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.
Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...
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