From: Michael W. <wes...@ja...> - 2025-07-22 11:26:29
|
Hi Tony, Thanks, but still no luck. I don't have a 'run.sh'. [1] That's odd. I have eXist 3.x and the EXIST_HOME/bin directory has the following: backup.bat batch.d client.sh eXist_32x32.ico run.bat server.bat shutdown.bat startup.bat backup.sh client.bat deprecated functions.d *run.sh* server.sh shutdown.sh startup.sh These shell scripts make sure that all of the CLASS_PATH stuff gets setup properly for running the utilities like `org.exist.backup.ExportMain`. If you're on Windows, you would use `run.bat`. > After I made a > script that no longer bombed out from missing dependencies, I ran > 'org.exist.backup.ExportMain'. > > I got multiple messages of the form: > > INFO: None of content dirs exist: > '/usr/local/src/exist3-data/expathrepo/doc-0.4.7/content' and > '/usr/local/src/exist3-data/expathrepo/doc-0.4.7/doc' > Are you trying to execute from the build directory? Did you not run the installer to place it all in a user's directory? Are you running it from a container and pointing to a data directory on the host machine? > then I got: > > 17:09:17.550 [main] ERROR org.exist.storage.DBBroker - no data found at > tid 25; page 60995 > java.io.IOException: no data found at tid 25; page 60995 > at org.exist.storage.index.BFile.getAsStream(BFile.java:492) > ~[exist.jar:?] > at org.exist.storage.index.BFile.getAsStream(BFile.java:462) > ~[exist.jar:?] > at > org.exist.storage.NativeBroker.openCollection(NativeBroker.java:928) > [exist.jar:?] > ... > 17:09:17.554 [main] ERROR org.exist.storage.DBBroker - Collection > '/db/system/security/exist/accounts' found in subCollections set but is > missing from collections.dbx! > 17:09:17.569 [main] ERROR org.exist.storage.BrokerPools - Unable to > initialize database instance 'exist': > org.exist.storage.BrokerPoolServiceException: org.exist.EXistException: > java.io.IOException: Collection /db/system/security/exist/accounts > cannot be created. Before doing anything -- like bringing the eXist server back up, you want to make an emergency backup. Be sure to make the target a local directory that exists and that you have write permission for. I use "~/backup/date-reason" (where "date" is the date that it shut down and "reason" is "locked" or "out-of-memory"). The "backup" directory exists in my exist user's home directory. /usr/local/* is not usually writable by ordinary users. Let's start by locating where the EXIST_HOME/bin directory is. -- Michael Westbay Writer/System Administrator http://www.japanesebaseball.com/ |