LockException: Could not acquire change log lock

[Hari]

Hi Team,

I have an issue wit bringing up Rundeck containerized environment and the error says
"LockException: Could not acquire change log lock". Tried many ways to fix the issue as per the reference in the web. But the same issue is coming up. Does anyone faced this issue in the past? I see a thread related to this in the group, does not have a resolution provided. Thank you.


2025-05-13T14:05:57.262Z [INFO]  target config out of sync: config=/home/rundeck/server/config/log4j2.properties prefix=remco[18] resource=log4j2.properties.toml
2025-05-13T10:05:57.262393595-04:00 2025-05-13T14:05:57.262Z [INFO]  target config has been updated: config=/home/rundeck/server/config/log4j2.properties prefix=remco[18] resource=log4j2.properties.toml
2025-05-13T10:06:10.422485736-04:00 [2025-05-13T14:06:10,419] INFO  rundeckapp.Application - The following 1 profile is active: "production"
2025-05-13T10:07:24.446421040-04:00 [2025-05-13T14:07:24,445] INFO  liquibase.database - Set default schema name to dbo
2025-05-13T10:07:24.727730493-04:00 [2025-05-13T14:07:24,727] INFO  liquibase.lockservice - Waiting for changelog lock....
[2025-05-13T14:07:34,737] INFO  liquibase.lockservice - Waiting for changelog lock....
2025-05-13T10:07:44.746708165-04:00 [2025-05-13T14:07:44,746] INFO  liquibase.lockservice - Waiting for changelog lock....
2025-05-13T10:07:54.753897362-04:00 [2025-05-13T14:07:54,753] INFO  liquibase.lockservice - Waiting for changelog lock....
2025-05-13T10:08:04.760595090-04:00 [2025-05-13T14:08:04,760] INFO  liquibase.lockservice - Waiting for changelog lock....

[rac...@rundeck.com]

Hi,

It seems that your database is locked by another process/instance. Please take a look at this.

Regards.

[Harikrishnan Gopalakrishnan]

Thank you. I followed the same instructions. But nothing helped. The new version of rundeck I am using is 5.11.1. I am trying to upgrade from 3.4.8 to 5.11.1 or 5.12.0 and I am using Microsoft® SQL Server 2022 as a database backend.

As part of triaging, when I downgraded to the 3.4.8 version, the issue looks resolved. Is there an issue with migrating directly from 3.4.x --> 5.11.x at this point ?

Thanks.

--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/rundeck-discuss/a1def0e5-b10a-4541-8f00-e74b4841b657n%40googlegroups.com.

[rac...@rundeck.com]

Hi,

As part of triaging, when I downgraded to the 3.4.8 version, the issue looks resolved. Is there an issue with migrating directly from 3.4.x → 5.11.x at this point ?

That is a common issue when the backend is locked by another instance/process. In a wider view, the gap between 3.4 and 5.11 is huge (even at the backend level). The main advice here is to create a fresh 5.11 instance and then import the project/keys. Please take a look at this.

Greetings!

​

[Harikrishnan Gopalakrishnan]

Thank you. I went with a fresh install and export/import. During import, rundeck is throwing "413 Request Entity Too Large - nginx". The average size of an archive file is 100 KB. I have set RUNDECK_GRAILS_UPLOAD_MAXSIZE to the value of 262144000 (250 Mib) but still the 413 error showing up. Is that the right value to set for these issues? Please advise.

 

Thank you,

To view this discussion visit https://groups.google.com/d/msgid/rundeck-discuss/b9939d28-d04b-492d-9914-ececef5400dan%40googlegroups.com.

[rac...@rundeck.com]

Hi,

It seems to be an NGINX LB issue. Take a look at this. Anyway, keep the Rundeck env var.

To import quickly, try importing without executions.

Regards.