Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Could not replicate the entire batch using the BatchProcessor

William Wells
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 5, 2012

I am cloning a production server for a staging, test with 4.1.2 to start a major upgrade of all of our Atlassian tools. I followed the instructions in https://confluence.atlassian.com/display/CROWD020/Migrating+Crowd+between+Servers and everything seemed to be working fine until I got to the import portion. It starts off fine, but as it is importing I get the error in my subject line. I'm using MySQL for both of the backend databases for test and production. The only difference between the two systems is that the original seems to have been installed as a WAR and the test is a standalone.

4 answers

1 accepted

2 votes
Answer accepted
William Wells
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 14, 2012

The problem I found was there was a duplicate user account created with the same user login. The account was for the same person, and it should have been identifiable by Crowd as a separate entity due to the assignment of a uuid to each account, but it didn't. I went into the backup xml file and removed one of the instances completely and was able to move forward in the import process.

2 votes
David Feig August 23, 2012

I had the same experience. I manually deleted duplicate users from the xml backup file. These were breaking database unique constraints. I just don't understand how these got into the backup.

I used the following bash command to find dups:

grep '<name>' atlassian-crowd-2.3.4-backup-2012-08-22-200326.xml.edited|sort|uniq -d|less

This finds more than just users but it was pretty easy to tell the wheat from the chaff.

0 votes
David Feig August 23, 2012

I had the same experience. I manually deleted repeat users. These were breaking database unique constraints. I just don't understand how these got into the backup.

0 votes
JustinK
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 5, 2012

Will,

Could you provide the complete stacktrace here so we could get a little more context 'in code' of what the problem is during the upgrade process.

Cheers,

Justin

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events