topic Re: [Solved] registry synchronization already running in another in Alfresco Archive

[Solved] registry synchronization already running in another

vasisualy — Thu, 17 Dec 2009 14:30:11 GMT

Dear all,after ldap synchronization attempts I got strange message in catalina.out log file. Userystem WARN [security.sync.ChainingUserRegistrySynchronizer] User registry synchronization already running in another thread. Synchronize abortedWhat does it mean?I cleared all previous ldap-authentica

Re: [Solved] registry synchronization already running in another

vasisualy — Sat, 19 Dec 2009 00:26:24 GMT

Hope I fixed it and problem is gone by setting options
index.recovery.mode=FULL
authentication.chain=alfrescoNtlm1:alfrescoNtlm

After this tomcat server was restarted.

To be honest I undeployed alfresco.war through tomcat manager and cleared all custom settings files/folders.
Than I deployed WAR file again and set few basic settings (datadir, mysql, etc.) including settings mentioned in this post.

Anyway few server restarts shown that message is gone.
Hope so. 🙂

Re: [Solved] registry synchronization already running in another

gyro_gearless — Thu, 04 Mar 2010 10:55:23 GMT

FWIW, i just found that Alfresco sometimes seems to "forget" to clean up some locks.

I just cured the very same symptom by deleting the stale locks:

– Only do this when Alfresco is shut down!
delete from alf_lock;

delete from alf_lock_resource;‍‍‍‍

Way faster than a full index rebuild, but of course i cant take any responsibilty for collateral damages :mrgreen:

Cheers
Gyro

Re: [Solved] registry synchronization already running in another

memnochmuc — Thu, 05 Aug 2010 09:00:04 GMT

I had the same issue with my installation.

Rebuild of index wouldn't help.

But I did take a look in the alf_lock table. With alfresco service stopped there was still 1 lock entry with start/expiry time.

I didn't want to delete something, so I just made the expiry time equal the start time.

After startup of the alfresco service sync works again …

Thanks Gyro for the hint

Re: [Solved] registry synchronization already running in another

mrogers — Thu, 05 Aug 2010 09:20:56 GMT

Alfresco will not "forget" about the locks in the lock table. What you are probably doing is shutting down alfresco while a lock is held, for example in the middle of a registry sync.

In this situation the locks all have a timeout. So typically the registry sync will go ahead tomorrow.

Your work-around of clearing the lock table is safe as long as alfresco is not running.

Re: [Solved] registry synchronization already running in another

memnochmuc — Tue, 10 Aug 2010 11:02:57 GMT

Well, - what caused it on our site was that the guy who set up the backup for the installation created following script:



net stop mysql

net stop Tomcat6‍‍‍‍‍

… 😉

Re: [Solved] registry synchronization already running in another

gluck113 — Fri, 09 Feb 2018 13:28:59 GMT

Mine wasn't in a stale state but was still locking the job. I deleted the line in

alf_lock

with the id corresponding to :

chaininguserregistrysynchronizer

in the table

alf_lock_resource