Confluence Space XML Import procedure fails with timeout

Still need help?

The Atlassian Community is here for you.

Ask the community

 

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

When trying to import a Space via XML file, it fails. The window shows the following message:

Import failed. Check your server logs for more information. Error putting scheduler on standby just prior to backup restore. Please wait a few minutes before trying again. If this error persists, please try restarting the server

Diagnosis

Environment

  • Confluence with Crowd for User Management.

The following messages should appear in the logs:

2017-02-26 13:02:03,380 ERROR [Long running task: Importing data] [confluence.importexport.xmlimport.BackupImporter] preImport Timed out waiting for atlassian-scheduler currently executing jobs to complete: [RunningJobImpl[startTime=1488113916899,jobId=com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerManager.1146881,jobConfig=JobConfig[jobRunnerKey=com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerManager,runMode=RUN_LOCALLY,schedule=Schedule[type=INTERVAL,intervalScheduleInfo=IntervalScheduleInfo[firstRunTime=Sun Feb 26 12:58:36 UTC 2017,intervalInMillis=3600000]],parameters={DIRECTORY_ID=1146881}],cancelled=true]]
 -- url: /admin/restore-local-file.action | traceId: 6097777ec646d1bc | userName: root | action: restore-local-file

And...

-- url: /admin/restore-local-file.action | traceId: 6097777ec646d1bc | userName: root | action: restore-local-file
com.atlassian.confluence.importexport.ImportExportException: Error putting scheduler on standby just prior to backup restore. Please wait a few minutes before trying again. If this error persists, please try restarting the server.

Cause

The Restore procedure triggers an LDAP sync (Crowd) which adds much more time to the process, so it exceeds the configured timeout and the import fails. This is a known issue that is being tracked at  CONFSERVER-53197 - Getting issue details... STATUS

Workaround

As a workaround for this issue, you should disable the user management platform and try the import again. This should solve this issue.

 

Last modified on Nov 7, 2017

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.