You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that there are more and more glitches that are somewhere deep in the index and reemerge after each reboot
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
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
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?
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)
The text was updated successfully, but these errors were encountered:
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
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
It seems that there are more and more glitches that are somewhere deep in the index and reemerge after each reboot
works
after reboot counts 14517 as maximum ID (actually belonging toPRS14517WaldaGiyorgis
, which is correctly stored inpersons/new
) and assigns IDs beginning with14518
. 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 #2694BerOrOct59.xml
keeps appearing inexpanded/manuscripts/VaticanBAV/et
(and is also present inexpanded/manuscripts/Berlin
where it belongs) "Walatta" search error #2736; the deletion is revoked upon each emergency rebootadd/exist/exist2/data/sanity
(?) in addition to the regular backup inadd/backups
(and manual backups in /data/export) - too many backups filling disk space?and possibly in exist.log on reboot
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)
The text was updated successfully, but these errors were encountered: