Re: [dspace-tech] Re: Problem importing SAF package: defined by the key 'org.dspace.app.batchitemimport.work.dir' in dspace.cfg is not a valid directory
Thanks Tim,
problem was due to a wrong byte in the contents file. Now it is working
fine,
wbr,
Ricardo
El mar, 25 jun 2024 a las 23:25, DSpace Technical Support (<
dspace-tech@googlegroups.com>) escribió:
> Hi Ricardo,
>
> Before performing an Import, DSpace will attempt to create the directory
> defined by the "org.dspace.app.batchitemimport.work.dir" configuration,
> which is in your dspace.cfg and defaults to "${dspace.dir}/imports":
> https://github.com/DSpace/DSpace/blob/main/dspace/config/dspace.cfg#L904
>
> If DSpace is unable to create that directory (or the directory just
> doesn't exist), then it will throw that error which says:
> "[full-directory-path] as defined by
> key 'org.dspace.app.batchitemimport.work.dir' in dspace.cfg is not a valid
> directory"
>
> So, the first step to solving this issue is to make sure that directory
> *exists* on your system, or verify that the Tomcat user has permissions to
> create this directory (if they do not, then DSpace cannot create this on
> your behalf).
>
> If that doesn't help, then we may need more information about your setup
> (especially the version of DSpace you are running). It is possible that
> you are also encountering a bug in an older release.
>
> Tim
>
> On Wednesday, June 19, 2024 at 6:20:22 AM UTC-5 re...@bib.uc3m.es wrote:
>
>> Dear colleagues,
>> I am trying to execute a batch SAF import both from the user interface
>> and the command line, and I am getting this error:
>>
>> "...defined by the key 'org.dspace.app.batchitemimport.work.dir' in
>> dspace.cfg is not a valid directory"
>>
>> I have seen the same problem reported by other colleagues.
>>
>> One point: I am making some tests in a Windows machine, so I understand
>> this may be the reason for the problem.
>>
>> Any info is welcome,
>>
>> Ricardo
>>
>> --
>> RICARDO EITO BRUN
>> Universidad Carlos III de Madrid
>>
> --
> 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/5f5cba08-0083-46d6-8a0f-69b10b3c1623n%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/5f5cba08-0083-46d6-8a0f-69b10b3c1623n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
--
RICARDO EITO BRUN
Universidad Carlos III de Madrid
--
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/CAK0P-rTwYCRQ7ErAaeBCp9DQG1%3DHLyKcCz75AutWw4dqZ%3D0DNA%40mail.gmail.com.
[dspace-tech] Problem importing SAF package: defined by the key 'org.dspace.app.batchitemimport.work.dir' in dspace.cfg is not a valid directory
Dear colleagues, I am trying to execute a batch SAF import both from the user interface and the command line, and I am getting this error: "...defined by the key 'org.dspace.app.batchitemimport.work.dir' in dspace.cfg is not a valid directory" I have seen the same problem reported by other colleagues. One point: I am making some tests in a Windows machine, so I understand this may be the reason for the problem. Any info is welcome, Ricardo -- RICARDO EITO BRUN Universidad Carlos III de Madrid -- 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/CAK0P-rSWzV6a7NOAHd9HmH%3Dtj%2Bryd3-YbC4WOTNNm_P8t5BT5Q%40mail.gmail.com.
[dspace-tech] Installing Solr in a separate, dedicated server
Dear colleagues, I am considering the feasibility and potential benefits of installing the Solr server in a separate, dedicated computer, instead of deploying it in the same server running dspace. Do you have some experience / recommendation on that? wbr, Ricardo -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] SWORDV2 - submitted items from OJS not displayed in dspace
Dear colleagues, I am trying to submit items to dspace from OJS. I have set up dspace according to the recommendations in the manual (swordv2.cfg file), and from OJS, I can select the collection and I got the message that the submission went ok. The problem is that I cannot see the items in dspace, and the submission does not seem to be fully completed (even if I log in dspace as dspace administrator) Any idea on the reason for this issue? thanks in advance, Ricardo -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] classical problem with dspace 5.x - browse lists display "Expected mime type application/octet-stream but got text/html"
Dear colleagues , I have installed dspace 5.2 on Debian and Postgresql. After installing everything with no problems - aparently - when I click on the link to browse the list of titles, authors, subjects..., I am getting the error "Expected mime type application/octet-stream but got text/html" I have seen in previous posts that this is related to a misconfiguration of Solr/Discovery, but I tried to do what other colleagues explained (changes in the /dspace/config/modules/discovery.cfg) and nothing happens... Would it be possible to get a clear pathway to solve this issue? Thanks in advance, Ricardo -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] problem with SOLR Statistics (showing 0 visits for the last months)
Hi, I have found an issue with SOLR statistics (dspace 4.x). When clicking on the Usage statistics menu entry for a specific collection, page or community, I got the page with the list of hits for the last 6 months. The problem is that - for the last two months -, these pages are always showing 0, what is really strange -. It was working with no problem and - for the previous months - the stats were being collected. No specific change has been done in the configuraiton of the site. Any idea on how to solve this issue? Thanks, Ricardo -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] Lucene misteries in v4.2
Hi friends, following with my indexing/retrieval problems in dspace 4.2, I have some additional info that my be useful. 1. according to the documentation, I have configured dspace to use the Postgresql browsing for titles, authors, etc. This is done by means of these variables: # PostgreSQL: browseDAO.class = org.dspace.browse.BrowseDAOPostgres browseCreateDAO.class = org.dspace.browse.BrowseCreateDAOPostgres (I have commented the lines for solr): #browseDAO.class = org.dspace.browse.SolrBrowseDAO #browseCreateDAO.class = org.dspace.browse.SolrBrowseCreateDAO According to that, dspace should use the Postgresql for browsing and the Lucene for searching / discovery, isn't it? I also created the Lucene index with the index-lucene-init command. After checking them with Luke, the index is correct (and it is in the v4.2.0 format). With Luke, it is possible to search in the index with no problems (Documents are retrieved). In spite of that, when searching the documents, not all the documents matching the search conditions are retrieved (although they are actually indexed). I have realized something that it is interesting: when I go to the Advanced search page, http://mysite.com/xmlui/discover?es, I get a list of documents (Around 2000), just a part of the documents in the collection. If I run the index-discovery -f command, I can observe that the number of documents in the list changes (from 0 to 2000). My surprise is that: a) I understand that the index-discovery command is used to update the solr search index, not the lucene index. b) In fact, although dspace is configured to use Lucene, it is in fact using Solr (any other way, how can we explain that the number of documents changes as the index-discovery command progresses?) c) It seems that changing the browseDAO.class and browseCreateDAO.class params is not enough to use the Lucene search instead of Solr search, as described in the documentation. d) the dspace.cfg file includes other lines related to the use of Lucene instead of Solr, but they are not mentioned in the documenation. This is the case of: # uncomment below and comment out original property to enable the legacy lucene indexing event.dispatcher.default.consumers = versioning, search, browse, eperson, harvester XMLUI Discovery (extra Discovery setting that applies only to XMLUI) # uncomment the following configuration if you want to restore the legacy Lucene # search provider with XMLUI (be sure to re-enable also the search consumer) plugin.single.org.dspace.app.xmlui.aspect.administrative.mapper.SearchRequestProcessor = \ org.dspace.app.xmlui.aspect.administrative.mapper.LuceneSearchRequestProcessor Anyway, after uncommenting these other properties and restarting Tomcat, the behaviour of dspace does not change (it still uses the Solr discovery index, as may be observed in the page http://mysite.com/xmlui/discover when you run the index-discover-f command) I would appreciate any idea about this issue, or at least to know whether this is a known bug (or may be I am missing something in my configuration). The problem seems to be that dspace 4.2 is not actually using Lucene, although the dspace.cfg is updated in order to do that..) Thanks in advance, Ricardo -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] problem when indexing
Hi, I am working with dspace 4.2 with Postgresql browsing (and Lucene for indexing). When running the index-lucene-update command I am getting this error: Started: 1444500126912 Ended: 1444500160647 Elapsed time: 33 secs (33735 msecs) Started: 1444500161531 Ended: 1444500161760 Elapsed time: 0 secs (229 msecs) Exception: null java.lang.NullPointerException at org.dspace.search.DSIndexer.cleanIndex(DSIndexer.java:604) at org.dspace.search.DSIndexer.main(DSIndexer.java:507) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56) at java.lang.reflect.Method.invoke(Method.java:620) at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:225) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:77) Any idea on that issue? Thanks in advance, Ricardo -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
