[Solved] registry synchronization already running in another

[vasisualy]

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 aborted

What does it mean?

I cleared all previous ldap-authentication.properties files
I set in my ldap-authentication.properties file  only internal auth.
authentication.chain=alfrescoNtlm1

But this message not gone.

Imho there is something in Alfresco caches. I'm I right?

Thank you.

[vasisualy]

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. 🙂

[gyro_gearless]

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

[gluck113]

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

[memnochmuc]

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

[mrogers]

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.

[memnochmuc]

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‍‍‍‍‍

… 😉