The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Any help on fixing this error would be appreciated.

Kyrian Washington
January 18, 2019

System errors

Bootstrap error

TimeLevelDescriptionException

2019-01-19 00:09:03fatalError 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:03fatalThis Crowd instance was unable to start the scheduler CrowdSchedulerService, and will not be usable. Please check the log for details.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 19, 2019

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.

TAGS
AUG Leaders

Atlassian Community Events