Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Index corrupted or similar glitches in exist #2752

Open
eu-genia opened this issue Dec 24, 2024 · 2 comments
Open

Index corrupted or similar glitches in exist #2752

eu-genia opened this issue Dec 24, 2024 · 2 comments
Labels
bug problem with the live applicaiton at betamasaheft.eu

Comments

@eu-genia
Copy link
Contributor

It seems that there are more and more glitches that are somewhere deep in the index and reemerge after each reboot

  1. repository works after reboot counts 14517 as maximum ID (actually belonging to PRS14517WaldaGiyorgis, which is correctly stored in persons/new) and assigns IDs beginning with 14518. reindexing (xmldb:reindex) works/new fixes this, but after each emergency reboot (because of java heap space error) the glitch is back and has to be refixed Number assigned to a new work too high #2694
  2. an expanded file BerOrOct59.xml keeps appearing in expanded/manuscripts/VaticanBAV/et (and is also present in expanded/manuscripts/Berlin where it belongs) "Walatta" search error #2736; the deletion is revoked upon each emergency reboot
  3. NullPointerException #2750 (a new type of error)
  4. emergency reboot triggers backup export in add/exist/exist2/data/sanity (?) in addition to the regular backup in add/backups (and manual backups in /data/export) - too many backups filling disk space?
  5. could (some of the) errors be connected to the issues reported in the data/sanity backup report
RESOURCE_ACCESS_FAILED:
no data found at tid 45; page 5288
Document ID: 275659
................
RESOURCE_ACCESS_FAILED:
no data found at tid 71; page 3070
Document ID: 38209
..............
RESOURCE_ACCESS_FAILED:
Failed to access document data
Document ID: 170237
----------------------------------------------
RESOURCE_ACCESS_FAILED:
Failed to access document data
Document ID: 170237
----------------------------------------------
RESOURCE_ACCESS_FAILED:
Failed to access document data
Document ID: 291804

and possibly in exist.log on reboot

2024-12-24 11:53:15,980 [main] ERROR (ConsistencyCheckTask.java [error]:249) - EXPORT: Found an orphaned document: BerOrOct59.xml 
2024-12-24 11:53:15,982 [main] ERROR (ConsistencyCheckTask.java [error]:249) - EXPORT: Found an orphaned document: LIT7081NamesGod.xml 
2024-12-24 11:53:15,993 [main] ERROR (ConsistencyCheckTask.java [error]:249) - EXPORT: Found an orphaned document: item.xqm 
2024-12-24 11:53:16,001 [main] ERROR (ConsistencyCheckTask.java [error]:249) - EXPORT: Caught an exception while scanning documents: no data found at tid 71; page 3070 
java.io.IOException: no data found at tid 71; page 3070
2024-12-24 11:53:16,002 [main] ERROR (ConsistencyCheckTask.java [error]:249) - EXPORT: Found an orphaned document: BMLacq776.rdf 
2024-12-24 11:53:16,002 [main] ERROR (ConsistencyCheckTask.java [error]:249) - EXPORT: Found an orphaned document: bm-log20241223.xml 
2024-12-24 11:53:16,005 [main] ERROR (ConsistencyCheckTask.java [error]:249) - EXPORT: Found an orphaned document: BNFabb9.xml 

indeed I cannot access LIT7081NamesGod, manual expansion from BetMasData result is "expanded 2 file(s) in 1.904 seconds" but could not open LIT7081NamesGod, had to rename the file

@duncdrum @DrRataplan @HelenaSabel @line-o any advice or should I just hope that it will all be fine in the new release and not bother for the momen? (but new glitches seem to appear all the time)

@eu-genia eu-genia added the bug problem with the live applicaiton at betamasaheft.eu label Dec 24, 2024
@eu-genia
Copy link
Contributor Author

had to restore the index
still get the message

2024-12-27 23:43:41,282 [qtp2079100080-26] INFO  (NativeBroker.java [removeXMLResource]:2763) - Removing document BerOrOct59.xml (170237) ... 
2024-12-27 23:43:41,288 [qtp2079100080-26] ERROR (NativeBroker.java [dropDomNodes]:2819) - Caught NPE in DOMTransaction to actually be able to remove the document. 

there is a null pointer error somewhere in the code

@eu-genia
Copy link
Contributor Author

eu-genia commented Jan 4, 2025

2025-01-04 20:39:02,492 [qtp1144539978-272] ERROR (ZipArchiveBackupDescriptor.java [countFileEntries]:248) - Unable to count number of files in /media/add/exist/exist2/data/export/full20220308-1305.zip. java.util.zip.ZipException: zip END header not found

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug problem with the live applicaiton at betamasaheft.eu
Projects
None yet
Development

No branches or pull requests

1 participant