[SOLVED] LockException: Could not acquire change log lock

[Xavier Humbert]

Hi,

I ran into a strange error while upgrading my production instances from 3.3.12 to 3.4 :

On two of the three instances, Rundeck won't start, with the message : 

Could not acquire change log lock.  Currently locked by (same machine)

I found this useful : https://faqs.cascadecms.com/en/articles/2029861-could-not-acquire-change-log-lock-or-waiting-for-changelog-lock

Worth opening an issue ?

Regards,

Xavier

-- 
Xavier Humbert
CRT Supervision et Exploitation de Niveau 1
Rectorat de Nancy-Metz
03 83 86 27 39

[rac...@rundeck.com]

Hi Xavier,

Which steps did you follow to upgrade your instances? It seems that the upgrade process was interrupted at some point.

Regards.

[Xavier Humbert]

Hi Rainer,

I followed the same Ansible playbook on the 3 instances. It's strange.

Nevertheless, I posted that more for a reference for those who will face this problem one day

Cheers

Xavier

--
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 on the web visit https://groups.google.com/d/msgid/rundeck-discuss/e23dc6c8-0a0c-4790-88ed-1b0629fa7e82n%40googlegroups.com.