[Exist-open] Node x not found in document sanity assertion again

[Brad C. <bk...@mu...>]

Hi all,

I think I reported  this a month or two ago.

Now using 1.0-dev-20051203

I suddenly got 4 documents that give this sanity assertion error. They were 
working, and suddenly eXist fell down.

I'm looking at the logs to figure out what happened. The server is up, not out of 
memory, no power outage or anything.

At best I have in the minute or two before the appearance of corruption a lot of 
xupdate calls in a different section of the database.

After that, I get

org.exist.util.sanity.AssertFailure: TRACE: 
org.exist.storage.NativeBroker_exist_1: tid 0 not found on page: 176; file = 
dom.dbx; address = b1000; page header = 64; data start = b1040. Loading -1; 
contents: Page 176: ; records in page: 0; nextTID: -1; length: 0


followed by:


2006-01-31 14:24:47,407 [P1-9] WARN  (SanityCheck.java [showTrace]:93) - 
Stacktrace:
org.exist.util.sanity.AssertFailure: TRACE: object at 176:0 not found.


and

2006-01-31 14:24:47,408 [P1-9] DEBUG (NativeBroker.java [start]:1878) - Node 
1 not found in document /db/orgs/lou/customs/invoices/055846.xml; docId = 113


I am doing a REST xslt transform over the contents of a collection.

At this point, I am planning to

1. delete the four documents that are causing problems.

2. backup the entire db

3. whipe out the WEB-INF/data directory

4. make an empty WEB-INF directory

5. restore backup

----

Does anyone want the contents of the current data directory for analysis?

Should I move to a newer snapshot?

I am concerned about recent bug reports  on this list.. but I'm not in a position to 
compile from cvs right now.

anyway.. does anyone want the corrupted db?




-- 
Brad Clements,                bk...@mu...    (315)268-1000
http://www.murkworks.com                          
AOL-IM or SKYPE: BKClements