EventStore 2.0 - ExtraneousFileFoundException when starting Event Store

EventStoreDB
1

Good morning,
I’m receiving the following error messages when trying to start a backup of a customer’s Event Store 2.0 database. I’m assuming that he probably did not stop the SingleNode.exe and attempted a hot-backup out of order, but wanted to ask for confirmation before sending him off on a wild-goose chase.

Thanks,

[PID:20596:001 2015.05.29 12:39:27.740 FATAL ProgramBase`1 ] Unhandled exception while starting application:
Corrupt database detected.
Unexpected files: E:\ESO\Source\ELEMENTSPR\chunk-000001.000000, E:\ESO\Source\ELEMENTSPR\chunk-000002.000000, E:\ESO\Source\ELEMENTSPR\chunk-000003.000000, E:\ESO\Source\ELEMENTSPR\chunk-000004.000000, E:\ESO\Source\ELEMENTSPR\chunk-000005.000000, E:\ESO\Source\ELEMENTSPR\chunk-000006.000000, E:\ESO\Source\ELEMENTSPR\chunk-000007.000000, E:\ESO\Source\ELEMENTSPR\chunk-000008.000000, E:\ESO\Source\ELEMENTSPR\chunk-000009.000000, E:\ESO\Source\ELEMENTSPR\chunk-000010.000000, E:\ESO\Source\ELEMENTSPR\chunk-000011.000000, E:\ESO\Source\ELEMENTSPR\chunk-000012.000000, E:\ESO\Source\ELEMENTSPR\chunk-000013.000000, E:\ESO\Source\ELEMENTSPR\chunk-000014.000000, E:\ESO\Source\ELEMENTSPR\chunk-000015.000000, E:\ESO\Source\ELEMENTSPR\chunk-000016.000000, E:\ESO\Source\ELEMENTSPR\chunk-000017.000000, E:\ESO\Source\ELEMENTSPR\chunk-000018.000000, E:\ESO\Source\ELEMENTSPR\chunk-000019.000000, E:\ESO\Source\ELEMENTSPR\chunk-000020.000000, E:\ESO\Source\ELEMENTSPR\chunk-000021.000000, E:\ESO\Source\ELEMENTSPR\chunk-000022.000000, E:\ESO\Source\ELEMENTSPR\chunk-000023.000000, E:\ESO\Source\ELEMENTSPR\chunk-000024.000000, E:\ESO\Source\ELEMENTSPR\chunk-000025.000000, E:\ESO\Source\ELEMENTSPR\chunk-000026.000000, E:\ESO\Source\ELEMENTSPR\chunk-000027.000000, E:\ESO\Source\ELEMENTSPR\chunk-000028.000000, E:\ESO\Source\ELEMENTSPR\chunk-000029.000000, E:\ESO\Source\ELEMENTSPR\chunk-000030.000000.
EventStore.Core.Exceptions.CorruptDatabaseException: Corrupt database detected. —> EventStore.Core.Exceptions.ExtraneousFileFoundException: Unexpected files: E:\ESO\Source\ELEMENTSPR\chunk-000001.000000, E:\ESO\Source\ELEMENTSPR\chunk-000002.000000, E:\ESO\Source\ELEMENTSPR\chunk-000003.000000, E:\ESO\Source\ELEMENTSPR\chunk-000004.000000, E:\ESO\Source\ELEMENTSPR\chunk-000005.000000, E:\ESO\Source\ELEMENTSPR\chunk-000006.000000, E:\ESO\Source\ELEMENTSPR\chunk-000007.000000, E:\ESO\Source\ELEMENTSPR\chunk-000008.000000, E:\ESO\Source\ELEMENTSPR\chunk-000009.000000, E:\ESO\Source\ELEMENTSPR\chunk-000010.000000, E:\ESO\Source\ELEMENTSPR\chunk-000011.000000, E:\ESO\Source\ELEMENTSPR\chunk-000012.000000, E:\ESO\Source\ELEMENTSPR\chunk-000013.000000, E:\ESO\Source\ELEMENTSPR\chunk-000014.000000, E:\ESO\Source\ELEMENTSPR\chunk-000015.000000, E:\ESO\Source\ELEMENTSPR\chunk-000016.000000, E:\ESO\Source\ELEMENTSPR\chunk-000017.000000, E:\ESO\Source\ELEMENTSPR\chunk-000018.000000, E:\ESO\Source\ELEMENTSPR\chunk-000019.000000, E:\ESO\Source\ELEMENTSPR\chunk-000020.000000, E:\ESO\Source\ELEMENTSPR\chunk-000021.000000, E:\ESO\Source\ELEMENTSPR\chunk-000022.000000, E:\ESO\Source\ELEMENTSPR\chunk-000023.000000, E:\ESO\Source\ELEMENTSPR\chunk-000024.000000, E:\ESO\Source\ELEMENTSPR\chunk-000025.000000, E:\ESO\Source\ELEMENTSPR\chunk-000026.000000, E:\ESO\Source\ELEMENTSPR\chunk-000027.000000, E:\ESO\Source\ELEMENTSPR\chunk-000028.000000, E:\ESO\Source\ELEMENTSPR\chunk-000029.000000, E:\ESO\Source\ELEMENTSPR\chunk-000030.000000.

2

Sounds like a missing/bad checkpoint

3

In the backup are there .chk files? Whats in them (they have only 8 bytes)

4

Chaser.chk, epoch.chk, truncate.chk and writer.chk all are 1kb (all binary, but epoch and writer both look to contain “nul”).

Modified dates on these files predates any of the chunk files. My guess is that their backup routine is not overwriting the chk files.

5

That would be he issue.

With a nil checkpoint any data being there would be odd.

6

This is the kind of thing we could likely resolve with the database files, but it is too time consuming to do for users without a commercial support agreement. If this is something you need, please get in touch with [email protected]

Thanks,

James

7

Thanks folks. So far as I know, this is just an issue with their backups (we asked for a copy of their data to research another issue and they gave us the evening backup). So it’s a flag for us to review their backup procedures with them.

Right now, all of my production clients are on GES 2.0, and we are learning to support them. I think we have looked at the commercial support agreement option before, but I am not one of the decision makers on that.

The troubleshooting guide will go a long way towards helping us support it, and there are a couple of other outstanding issues with 2.0 that we need to ask about. However, those need further research before actually posting as questions.

8

The answer to all questions about 2.0 - upgrade to 3.0.4. There won't be another service release of the 2.x series.