Menu
▾
▴
Re: [Exist-open] Journal can only support 32767 log files
|
From: Craig B. <cra...@ma...> - 2023-02-11 17:42:38
|
> On Feb 11, 2023, at 10:59 AM, Nick Sincaglia <nsi...@nu...> wrote: > > I just have 1 file in $EXIST_HOME/data called 0000008002.log. There is nothing in this file when I look inside. 8002 in hex is 32770 in decimal, so my theory about an embedded version number in the filename that exceeds what a short integer can hold is not necessarily wrong. Not necessarily right, either, but I don't think it can be ruled out just yet. > > Does anyone know what the Journal is checking and where it is these log files might be? > > Nick > > On 2/11/23 10:44 AM, Craig Berry wrote: >> Do you by any chance have more than 32,767 transaction log files in your eXist data directory with names like 0000000001.log? Or do you have one file with a name like 0000032767.log where the highest-allowed version number is embedded in the name and something fails when it tries to increment? These are wild guesses, but seeing what's there might be the beginning of finding out what's actually going on. >> >> If you have a good backup and/or you can rebuild your data if necessary, then you'll probably want to rename those file(s) out of the way while eXist is shut down and then try to restart. If it comes up cleanly, then you've likely solved your problem. I believe there is some chance using this method that you could lose data from whatever transaction was in flight when eXist crashed. I've never had that happen but almost all my data are read-only so don't even really need transactions. >> >> Note that I've never seen the exact error you describe -- more commonly when it detects an unclean shutdown it tries to reindex everything, which takes forever, so I delete the log file before restarting. >> >> >>> On Feb 11, 2023, at 9:28 AM, Nick Sincaglia <nsi...@nu...> >>> wrote: >>> >>> I have eXist-db v5.2 instance running and it is failing to launch due to the below error. I am wondering if anyone might have some suggestions on how to resolve this issue. >>> >>> 2023-02-11 15:12:46,631 [db.exist.prepare-quartz-scheduler] INFO (QuartzSchedulerImpl.java [getQuartzProperties]:134) - Successfully loaded quartz.properties >>> 2023-02-11 15:12:47,269 [main] INFO (IndexManager.java [initIndex]:149) - Registered index org.exist.indexing.ngram.NGramIndex as ngram-index >>> 2023-02-11 15:12:47,817 [main] INFO (IndexManager.java [initIndex]:149) - Registered index org.exist.indexing.lucene.LuceneIndex as lucene-index >>> 2023-02-11 15:12:47,819 [main] INFO (IndexManager.java [initIndex]:149) - Registered index org.exist.indexing.sort.SortIndex as sort-index >>> 2023-02-11 15:12:47,927 [main] INFO (IndexManager.java [initIndex]:149) - Registered index org.exist.indexing.range.RangeIndex as range-index >>> 2023-02-11 15:12:47,930 [main] INFO (IndexManager.java [initIndex]:149) - Registered index org.exist.storage.structural.NativeStructuralIndex as structural-index >>> 2023-02-11 15:12:47,931 [main] INFO (SyncTask.java [configure]:77) - Using DATA_DIR: /mnt/data/exist-5.2.0/data. Minimal disk space required for database to continue operations: 1024mb >>> 2023-02-11 15:12:47,935 [main] INFO (SyncTask.java [configure]:80) - Usable space on partition containing DATA_DIR: /mnt/data/exist-5.2.0/data: 113117mb >>> 2023-02-11 15:12:48,138 [main] INFO (RecoveryManager.java [recover]:118) - Unclean shutdown detected. Scanning journal... >>> 2023-02-11 15:12:48,144 [main] INFO (RecoveryManager.java [recover]:193) - Database is in clean state. Nothing to recover from the journal. >>> 2023-02-11 15:12:48,212 [main] ERROR (TransactionManager.java [doBeginTransaction]:197) - Failed to create transaction. Error writing to Journal >>> org.exist.storage.journal.JournalException: Journal can only support 32767 log files >>> at org.exist.storage.journal.Journal.writeToLog(Journal.java:342) ~[exist-core-5.2.0.jar:5.2.0] >>> at org.exist.storage.journal.JournalManager.journal(JournalManager.java:90) ~[exist-core-5.2.0.jar:5.2.0] >>> at org.exist.storage.txn.TransactionManager.doBeginTransaction(TransactionManager.java:195) [exist-core-5.2.0.jar:5.2.0] >>> at org.exist.storage.txn.TransactionManager.beginTransaction(TransactionManager.java:180) [exist-core-5.2.0.jar:5.2.0] >>> >>> Here is information about my eXist-db system >>> eXist Version: 5.2.0 >>> eXist Build: 20200123133609 >>> Operating System: Linux 4.14.203-156.332.amzn2.x86_64 amd64 >>> Java Version: 11.0.17 >>> Default Encoding: UTF8 >>> Instance ID: exist >>> System CPU Load: 0.979516 >>> Process CPU Load: 0.975791 >>> Free Physical Memory: 2608074752 >>> Total Physical Memory: 33244393472 >>> >>> -- >>> Nick Sincaglia >>> President/Founder >>> NueMeta, LLC >>> Digital Media & Technology >>> Phone: +1-630-303-7035 >>> >>> >>> nsi...@nu... >>> >>> >>> >>> >>> http://www.nuemeta.com >>> >>> >>> Skype: nsincaglia >>> >>> _______________________________________________ >>> Exist-open mailing list >>> >>> Exi...@li... >>> https://lists.sourceforge.net/lists/listinfo/exist-open >> ________________________________________ >> Craig A. Berry >> >> "... getting out of a sonnet is much more >> difficult than getting in." >> Brad Leithauser >> >> > > -- > Nick Sincaglia > President/Founder > NueMeta, LLC > Digital Media & Technology > Phone: +1-630-303-7035 > > nsi...@nu... > > > http://www.nuemeta.com > > Skype: nsincaglia > ________________________________________ Craig A. Berry "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser |
