Forums : Technical Issue Help

Due to security issues the repository for

https://www.ohloh.net/p/efaps

was rebuild. The enlistment update now fails.

Might be the different UUID of the repository?

Thanks for checking

Jan Moxter almost 16 years ago

Hi Jan,

Our servers are attempting to use svnsync to create a local mirror of the repository, but it appears that there is some kind of data corruption issue in the repository.

Svnsync consistently fails with the following error:

svnsync: Base checksum mismatch on '/eFapsApp-CRM/trunk/contacts/src/main/efaps/Wiki/Contacts.wiki'
expected: 56a4bd76fa4db73697074731380a57b4
actual: 396a2240a4d0163399183a4a4d8671d7

I think this error can only be repaired on the repository server itself, and I don't know of any workaround on our end.

Thanks,
Robin

Robin Luckey almost 16 years ago

Hallo Robin,

I svnsync the whole repository to another server and it does not fail. But for ohloh I made enlistments that only represent parts of the projects. The idea was to only use the active parts of the project inside ohloh and not the ones that are not worked on any more.

Would the error also appear if i cancel the enlistment which tries to get the above file??
Or might it be better to just use the root of the svn server as the one and only enlistment??

Thanks a lot
Jan

Jan Moxter almost 16 years ago

In this case, it does not matter which subdirectories of the repository you enlist in Ohloh.

Our servers use svnsync to create a local mirror of the entire repository, and then afterwards filter the repository to focus only on the directories you enlisted. So svnsync will always be used on the entire repository, no matter which directories you enlist.

Robin Luckey almost 16 years ago

Hello Robin,

i created a new repository on another server and synced the actual repository (for ohloh) to the new repository. The sync also did not fail. That means that i cannot repeat the error you got and cannot find anything wrong in the repository also.

Some investigation in the internet brought this up:

link

I still don't know what caused this, but further investigation shows that there is nothing wrong with the master repository ... it is fine.

It's the mirrors which were broken...

It was necessary to delete the mirror repositories, recreate empty ones, and resync all revisions to these new empty repositories.

The first one has completed now and is fully synced, so I expect the other to sync up too.

This means that svnsync corrupted the mirror repositories: all of them. (well, ok, in this case all = both, since I just have have two. But these are two on different sites. Actually in different countries.)

Syncs are done sequentially triggered by both cron and post-commit hook. So svnsync prepared sync data, and sent it, and this sync data broke the mirrors in such a way as this was not immediately obvious.*

Maybe something like this happend??

Thank you for taking car about my issue and i hope that we do find a solution for this problem soon.

Jan

Jan Moxter almost 16 years ago

Hi Jan,

I have scheduled clean downloads of each enlistment, and this appears to be resolving the problem.

It may take several days to complete the new downloads. I'll keep an eye on them.

I am hopeful that this will fix the problem!

Robin

Robin Luckey almost 16 years ago

Yeaahh!! It seems like everything is working again like normal.

Thanks a lot Robin

Jan

Jan Moxter almost 16 years ago