Directory Sync between Jira and Crowd failed after reboot docker

We have Docker images for Crowd , JIRA and Confluence.

Our Host machines disk space gets full So mounted additional space and restarted Docker.

All docker Images started fine , All existing Users can able to login .

However when we create new user on crowd  it doesn't get sync with JIRA and confluence.

On JIRA we can see below logs


6-10-27 09:05:42,031 Caesium-1-3 INFO ServiceRunner     [] failed synchronisation complete for directory [ 10000 ] in [ 0ms ]
2016-10-27 09:05:42,046 Caesium-1-3 ERROR ServiceRunner     [c.atlassian.scheduler.JobRunnerResponse] Unable to synchronise directory
com.atlassian.crowd.exception.OperationFailedException: Failed to create remote crowd client
        at com.atlassian.jira.crowd.embedded.JiraDirectorySynchroniser.synchronizeDirectory(
        at com.atlassian.jira.crowd.embedded.JiraDirectorySynchroniser.runJob(
        at com.atlassian.scheduler.core.JobLauncher.runJob(
        at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(
        at com.atlassian.scheduler.core.JobLauncher.launch(
        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(
        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(
        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(
        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(
        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(
        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(
        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(
Caused by: java.lang.NullPointerException
        at com.atlassian.util.concurrent.LazyReference$
        at com.atlassian.util.concurrent.LazyReference.getInterruptibly(
        at com.atlassian.util.concurrent.LazyReference.get(
        ... 21 more


Further check we found that IP of crowd has been changes.

Please suggest what can be done.

1 answer

I had the same error, wasn't using docker and IP didn't change tho.

I was able to fix by

  • setting "JIRA Internal Directory" as main one
  • logging in as internal user
  • disabling crowd
  • re-applying all settings (URL/etc)
  • enabling crowd
  • setting crowd as main directory again

I had the same problem and I've fixed it following your suggestions.

Just a note on the point "logging in as internal user", if you use SSO, you have to disable it in .../atlassian-jira/WEB-INF/classes/seraph-config.xml as described in Integrating Crowd with Atlassian JIRA otherwise you can't log in with internal users.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,492 views 15 20
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you