Hi Matthias, It's not the SAF files but my guess it's happening because of a corrupted zip file so check it using the 7zip package. Have it install in the server and check the zip file for its integrity.
*** You can force the extraction of the zip file using 7zip even with the issue it has ( Watch for any errors during the extraction phase ) and then import the SAF files from a directory. Good luck, Mo. On Friday, February 2, 2024 at 4:04:13 PM UTC+3 Matthias Letsch wrote: > Hi there, > > I am trying to import prepared SAF files via batch import. With another > subset in other collections, this worked wonderfully just yesterday. So it > can't be the SAF files, they follow exactly the same pattern (zip with > folders containing xyz.pdf, dublin_core.xml and contents referring to pdf > file. > > Today, however, I get an error message (This is now a dedicated test > import into a newly created collection TEST): > > ###:~/dspace-backend/bin$ ./dspace import -a -e ###@###.de -s ~/ojs-import > -z 10.zip -c 12345678 > 9/5103 -m ~/ojs-import/mapfiles/test10; > The script has started > Destination collections: > Owning Collection: TEST > '/home/dspace/dspace-backend/imports' as defined by the key > 'org.dspace.app.batchitemimport.work.dir' in dspace.cfg is not a valid > directory > Started: 1706876840214 > Ended: 1706876846622 > Elapsed time: 6 secs (6408 msecs) > java.lang.Exception: Error committing changes to database: Error, cannot > open source directory > /home/dspace/dspace-backend/imports/importSAF/43013a47-6076-432a-959d-9805240a43ae/10.zip, > > aborting most recent changes > at > org.dspace.app.itemimport.ItemImport.internalRun(ItemImport.java:233) > at org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:150) > at > org.dspace.app.launcher.ScriptLauncher.executeScript(ScriptLauncher.java:154) > at > org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:132) > at > org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:99) > Caused by: java.lang.Exception: Error, cannot open source directory > /home/dspace/dspace-backend/imports/importSAF/43013a47-6076-432a-959d-9805240a43ae/10.zip > at > org.dspace.app.itemimport.ItemImportServiceImpl.addItems(ItemImportServiceImpl.java:278) > at > org.dspace.app.itemimport.ItemImportCLI.process(ItemImportCLI.java:92) > at > org.dspace.app.itemimport.ItemImport.internalRun(ItemImport.java:226) > ... 4 more > > As I understand it, there is some problem with the folder > (dspace-dir)/imports, which exists exactly as it is defined in dspace.cfg. > > If I create a new, different folder in the backend and then change this in > dspace.cfg (plus restart tomcat), the result unfortunately looks exactly > the same. > > Does anyone know how to fix this problem? > > Thank you and kind regards > Matthias > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/cea4f41e-a75e-4abb-bb0f-0c918c680712n%40googlegroups.com.
