nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OpenLDAP users get removed from Jira, sporadically

Dee Heffemm

We've been testing Jira for a month or so with users provisioned via OpenLDAP (Read Only, with Local Groups). It's been working well, however from time-to-time (maybe every couple days) users are getting sporadically removed from either/or the local groups in Jira, or their User account is displayed in a Strike-Through text attribute. We suspect a synchronization issue since manually synchronizing seems to correct the problem.

I've looked in the atlassian-jira.log on our Jira server and it seems that the LDAP communications are OK (below). What would some possible causes of this be? Is this a known issue? Would an LDAP/Network issue turn up in a different logfile somewhere?

Thanks!

2017-10-31 00:07:56,196 Caesium-1-4 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 57 ms ]
2017-10-31 00:07:56,259 Caesium-1-4 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 55 ms ]
2017-10-31 00:07:56,266 Caesium-1-4 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 3ms ]
2017-10-31 01:07:56,193 Caesium-1-3 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 55 ms ]
2017-10-31 01:07:56,247 Caesium-1-3 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 49 ms ]
2017-10-31 01:07:56,255 Caesium-1-3 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 3ms ]
2017-10-31 02:07:56,215 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 76 ms ]
2017-10-31 02:07:56,269 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 48 ms ]
2017-10-31 02:07:56,278 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 2ms ]
2017-10-31 03:07:56,187 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 59 ms ]
2017-10-31 03:07:56,243 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 51 ms ]
2017-10-31 03:07:56,249 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 2ms ]
2017-10-31 04:07:56,187 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 56 ms ]
2017-10-31 04:07:56,244 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 50 ms ]
2017-10-31 04:07:56,251 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 2ms ]
2017-10-31 05:07:56,190 Caesium-1-1 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 60 ms ]
2017-10-31 05:07:56,247 Caesium-1-1 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 49 ms ]
2017-10-31 05:07:56,255 Caesium-1-1 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 3ms ]
2017-10-31 06:07:56,196 Caesium-1-3 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 60 ms ]
2017-10-31 06:07:56,249 Caesium-1-3 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 47 ms ]
2017-10-31 06:07:56,256 Caesium-1-3 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 3ms ]
2017-10-31 07:07:56,191 Caesium-1-1 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 54 ms ]
2017-10-31 07:07:56,356 Caesium-1-1 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 49 ms ]
2017-10-31 07:07:56,363 Caesium-1-1 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 3ms ]
2017-10-31 08:07:56,195 Caesium-1-4 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 60 ms ]
2017-10-31 08:07:56,357 Caesium-1-4 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 50 ms ]
2017-10-31 08:07:56,367 Caesium-1-4 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 3ms ]
2017-10-31 09:07:56,193 Caesium-1-4 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 59 ms ]
2017-10-31 09:07:56,249 Caesium-1-4 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 51 ms ]
2017-10-31 09:07:56,257 Caesium-1-4 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 4ms ]
2017-10-31 10:07:56,192 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 57 ms ]
2017-10-31 10:07:56,250 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 49 ms ]
2017-10-31 10:07:56,257 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 3ms ]
2017-10-31 11:07:56,192 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 61 ms ]
2017-10-31 11:07:56,249 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 51 ms ]
2017-10-31 11:07:56,256 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 3ms ]
2017-10-31 12:07:56,200 Caesium-1-4 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 54 ms ]
2017-10-31 12:07:56,254 Caesium-1-4 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 48 ms ]
2017-10-31 12:07:56,262 Caesium-1-4 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 3ms ]
2017-10-31 13:07:56,199 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 59 ms ]
2017-10-31 13:07:56,255 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 51 ms ]
2017-10-31 13:07:56,261 Caesium-1-2 INFO ServiceRunner [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 3ms ]

Accepted answers

All comments

Andy Heinzer

Hi Dave,

Looking at that part of the log, I don't see a problem that clearly explains the behavior you report. But given what you are reporting happening I have a theory that Jira might be stuck doing a sync, in which case either the account is missing or the group membership is missing or both. Either way, it could account for why those users can't login when this happens.

I would be interested to learn if the logs you show here correspond to a time when this problem happened. If it did, then it might help to increase the verbosity of the logs Jira is creating. To do this you can go into Logging and Profiling in Jira. From there I would recommend finding the entry for:

 com.atlassian.crowd.directory

and you can then set this entry to DEBUG. By doing so, you should be able to see more detailed information of what Jira is doing when this problem happens again.

Regards,
Andy

Dee Heffemm

Thanks Andy. I checked the logs last Friday and noticed the log entries below (have not enabled DEBUG logging yet). Is there some LDAP setting that would cause this? I had everything fixed up Friday morning (after re-adding users to their correct groups/re-synching manually) around 9am but then again around 10:22am, there is "INCREMENTAL synchronisation for directory [ 10000 ] was not successful, attempting FULL"

2017-11-03 06:37:58,891 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteDirectory] FULL synchronisation complete for directory [ 10000 ] in [ 654ms ]
2017-11-03 07:25:23,741 Caesium-1-3 INFO ServiceRunner     [c.a.j.p.h.service.connect.InstallGlancesJobHandler] Running InstallGlancesJobHandler...
2017-11-03 07:25:23,741 Caesium-1-3 INFO ServiceRunner     [c.a.j.p.h.service.connect.InstallGlancesJobHandler] There is no link to HipChat, no need to install glances.
2017-11-03 07:25:26,574 Caesium-1-2 INFO ServiceRunner     [c.a.j.p.h.service.ping.RefreshConnectionStatusJobHandler] Running RefreshConnectionStatusJobHandler...
2017-11-03 07:28:07,660 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteDirectory] INCREMENTAL synchronisation for directory [ 10000 ] starting
2017-11-03 07:28:07,661 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteDirectory] Attempting INCREMENTAL synchronisation for directory [ 10000 ]
2017-11-03 07:28:07,661 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteDirectory] Incremental synchronisation for directory [ 10000 ] was not completed, falling back to a full synchronisation
2017-11-03 07:28:07,661 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteDirectory] INCREMENTAL synchronisation for directory [ 10000 ] was not successful, attempting FULL
2017-11-03 07:28:07,720 Caesium-1-4 INFO ServiceRunner     [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 59 ms ]
2017-11-03 07:28:07,723 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 10 ] users for delete in DB cache in [ 2ms ]
2017-11-03 07:28:07,723 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] deleting [ 9 ] users
2017-11-03 07:28:07,806 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] deleted [ 9 ] users in [ 83ms ]
2017-11-03 07:28:07,806 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] scanned for deleted users in [ 85ms ]
2017-11-03 07:28:07,808 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] scanning [ 10 ] users to add or update
2017-11-03 07:28:07,808 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DirectoryCacheImplUsingChangeOperations] scanned and compared [ 10 ] users for update in DB cache in [ 2ms ]
2017-11-03 07:28:07,808 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] adding [ 3 ] users
2017-11-03 07:28:07,838 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] added [ 3 ] users successfully in [ 30ms ]
2017-11-03 07:28:07,838 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DirectoryCacheImplUsingChangeOperations] synchronised [ 10 ] users in [ 32ms ]
2017-11-03 07:28:07,888 Caesium-1-4 INFO ServiceRunner     [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 8 ] remote groups in [ 50 ms ]
2017-11-03 07:28:07,896 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 8 ] groups for delete in DB cache in [ 3ms ]
2017-11-03 07:28:07,896 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DirectoryCacheImplUsingChangeOperations] scanning [ 8 ] groups to add or update
2017-11-03 07:28:07,897 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 8 ] groups for update in DB cache in [ 1ms ]
2017-11-03 07:28:07,897 Caesium-1-4 INFO ServiceRunner     [c.a.crowd.directory.DirectoryCacheImplUsingChangeOperations] synchronized [ 8 ] groups in [ 1ms ]
2017-11-03 07:28:07,900 Caesium-1-4 INFO ServiceRunner     [c.a.c.d.ldap.cache.AbstractCacheRefresher] finished group attribute sync with 0 failures in [ 3ms ]

Andy Heinzer

Hi Dave,

The failed incremental sync is not uncommon to see with Jira. That by itself is not really an indication of a problem here. I would be interested to learn if there have been other reported problems with users being unable to login since Friday. I can't say yet if this might be something to do with a setting in LDAP, or a performance problem in LDAP and/or Jira. But if we can reproduce this problem with the debug logging enabled, it might tell us more about what is happening from Jira's side when these users get in a stuck state where they cannot login.

Andy

Dee Heffemm

Hi Andrew,

I have some debug logs (snippet below). What I suspect is happening is our HR import is running at 7am to refresh user accounts in LDAP. These accounts may or may not be available for a couple minutes while the process is running.

Under 'User Directories -> Advanced Settings' I see there are some options regarding sychronization. Perhaps adjusting some of these could help? Wondering if there's a way to tell Jira to not sync with LDAP for 5 minutes after 7am?

...
2017-11-07 07:07:58,243 Caesium-1-1 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] INCREMENTAL synchronisation for directory [ 10000 ] starting
2017-11-07 07:07:58,243 Caesium-1-1 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] Attempting INCREMENTAL synchronisation for directory [ 10000 ]
2017-11-07 07:07:58,243 Caesium-1-1 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] Incremental synchronisation for directory [ 10000 ] was not completed, falling back to a full synchronisation
2017-11-07 07:07:58,243 Caesium-1-1 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] INCREMENTAL synchronisation for directory [ 10000 ] was not successful, attempting FULL
2017-11-07 07:07:58,243 Caesium-1-1 DEBUG ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] loading remote users
2017-11-07 07:07:58,244 Caesium-1-1 DEBUG ServiceRunner [c.a.crowd.directory.SpringLDAPConnector] Performing user search: baseDN = ou=people,dc=my,dc=org - filter = (memberof=cn=jira-ldap,ou=groups,dc=my,dc=org)
2017-11-07 07:07:58,245 Caesium-1-1 DEBUG ServiceRunner [c.a.c.directory.ssl.LdapHostnameVerificationSSLSocketFactory] Name checking SSLSocketFactory created
2017-11-07 07:07:58,247 Caesium-1-1 DEBUG ServiceRunner [c.a.c.directory.ssl.LdapHostnameVerificationSSLSocketFactory] Creating disconnected socket
2017-11-07 07:07:58,295 Caesium-1-1 DEBUG ServiceRunner [c.a.crowd.directory.SpringLDAPConnector] Paged results are enabled with a paging size of: 500
2017-11-07 07:07:58,299 Caesium-1-1 DEBUG ServiceRunner [c.a.c.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on ou=people,dc=my,dc=org took 3ms
2017-11-07 07:07:58,299 Caesium-1-1 DEBUG ServiceRunner [c.a.crowd.directory.SpringLDAPConnector] Iterating a search result size of: 500
2017-11-07 07:07:58,300 Caesium-1-1 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 57 ms ]
2017-11-07 07:07:58,304 Caesium-1-1 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ csmith ] not found, deleting
2017-11-07 07:07:58,304 Caesium-1-1 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ jdavidson ] not found, deleting
2017-11-07 07:07:58,304 Caesium-1-1 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ ljohnson ] not found, deleting
2017-11-07 07:07:58,304 Caesium-1-1 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ jwilson ] not found, deleting
2017-11-07 07:07:58,304 Caesium-1-1 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ aarcher ] not found, deleting
2017-11-07 07:07:58,304 Caesium-1-1 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ avermont ] not found, deleting
2017-11-07 07:07:58,304 Caesium-1-1 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ jericson ] not found, deleting
2017-11-07 07:07:58,304 Caesium-1-1 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ jklaus ] not found, deleting
2017-11-07 07:07:58,304 Caesium-1-1 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ tbrown ] not found, deleting
2017-11-07 07:07:58,304 Caesium-1-1 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ mfarmer ] not found, deleting
2017-11-07 07:07:58,304 Caesium-1-1 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 10 ] users for delete in DB cache in [ 4ms ]
2017-11-07 07:07:58,304 Caesium-1-1 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] deleting [ 10 ] users
2017-11-07 07:07:58,403 Caesium-1-1 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] deleted [ 10 ] users in [ 99ms ]
2017-11-07 07:07:58,403 Caesium-1-1 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] scanned for deleted users in [ 103ms ]
2017-11-07 07:07:58,405 Caesium-1-1 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] scanning [ 10 ] users to add or update 
...

UPDATE: After posting, I noticed these same log entries happening again at 7:43am. This is long after the HR import has finished. Not sure why that is (second snippet below).

2017-11-07 07:43:15,647 Caesium-1-3 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] INCREMENTAL synchronisation for directory [ 10000 ] starting
2017-11-07 07:43:15,648 Caesium-1-3 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] Attempting INCREMENTAL synchronisation for directory [ 10000 ]
2017-11-07 07:43:15,648 Caesium-1-3 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] Incremental synchronisation for directory [ 10000 ] was not completed, falling back to a full synchronisation
2017-11-07 07:43:15,648 Caesium-1-3 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] INCREMENTAL synchronisation for directory [ 10000 ] was not successful, attempting FULL
2017-11-07 07:43:15,648 Caesium-1-3 DEBUG ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] loading remote users
2017-11-07 07:43:15,648 Caesium-1-3 DEBUG ServiceRunner [c.a.crowd.directory.SpringLDAPConnector] Performing user search: baseDN = ou=people,dc=my,dc=org - filter = (memberof=cn=jira-ldap,ou=groups,dc=my,dc=org)
2017-11-07 07:43:15,649 Caesium-1-3 DEBUG ServiceRunner [c.a.c.directory.ssl.LdapHostnameVerificationSSLSocketFactory] Name checking SSLSocketFactory created
2017-11-07 07:43:15,650 Caesium-1-3 DEBUG ServiceRunner [c.a.c.directory.ssl.LdapHostnameVerificationSSLSocketFactory] Creating disconnected socket
2017-11-07 07:43:15,699 Caesium-1-3 DEBUG ServiceRunner [c.a.crowd.directory.SpringLDAPConnector] Paged results are enabled with a paging size of: 500
2017-11-07 07:43:15,703 Caesium-1-3 DEBUG ServiceRunner [c.a.c.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on ou=people,dc=my,dc=org took 3ms
2017-11-07 07:43:15,703 Caesium-1-3 DEBUG ServiceRunner [c.a.crowd.directory.SpringLDAPConnector] Iterating a search result size of: 500
2017-11-07 07:43:15,704 Caesium-1-3 INFO ServiceRunner [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 10 ] remote users in [ 56 ms ]
2017-11-07 07:43:15,706 Caesium-1-3 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ csmith ] not found, deleting
2017-11-07 07:43:15,707 Caesium-1-3 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ jdavidson ] not found, deleting
2017-11-07 07:43:15,707 Caesium-1-3 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ jwilson ] not found, deleting
2017-11-07 07:43:15,707 Caesium-1-3 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ avermont ] not found, deleting
2017-11-07 07:43:15,707 Caesium-1-3 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ jericson ] not found, deleting
2017-11-07 07:43:15,707 Caesium-1-3 DEBUG ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] user [ jklaus ] not found, deleting
2017-11-07 07:43:15,707 Caesium-1-3 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 10 ] users for delete in DB cache in [ 3ms ]

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

ldap