Re: [dspace-tech] Re: Log4J and DSpace 6.x
Just a quick follow up to this. I'm leaving my current role tomorrow, but in case anyone comes across this thread, this approach did actually work, although it was certainly not an easy job at all. Regards, Sarah On Tue, 11 Jan 2022 at 15:05, 'Tim Donohue' via DSpace Technical Support < dspace-tech@googlegroups.com> wrote: > Hi Sarah, > > Good to know you are working on something. If you *do* manage to find a > way to upgrade DSpace 6.4 to use log4j v2, please send us a PR. We'd be > open to making this fix for everyone in a new 6.x release. However, as > previously implied, I'm not aware of anyone who has managed to get this to > work properly yetdoesn't mean it's impossible, just that it's not an > easy fix to make (as it sounds like you've discovered). > > If others are also interested in collaborating with you (and it sounds > like they might be), you are also welcome to create a *draft* PR in our > https://github.com/DSpace/DSpace (dspace-6_x branch) and invite others to > collaborate on it with you. We obviously won't merge anything into the > core code until it's proven to work (i.e. fully tested/reviewed), but we > welcome anyone to create draft PRs if they are looking for collaborators / > early feedback, etc. > > Good luck & please do let us know how it goes! > > Tim > On Tuesday, January 11, 2022 at 4:25:27 AM UTC-6 mount...@gmail.com wrote: > >> Hi Tim, >> >> Many thanks for this. For reasons that I won't go into here, it looks >> like trying to patch 6.4 is something that we need to try. It may be that >> the v1->v2 bridge that's been mentioned will be a better option for us, but >> we're looking at both choices right now. >> >> Currently, I have a version of 6.4 that does not directly use log4j v1, >> but it does still have a handful (<20) of transitive imports of v1 from >> slf4 and Solr. The patched 6.4 can compile all the front-ends and pass the >> unit/integration tests, and I can run DSpace locally in a container -- but >> I haven't tackled converting the configuration files in earnest yet, and >> I've noticed that the PR for v7 uses XML for some configuration files. >> >> My local PR for this is already approx. 1kloc larger than the PR to >> upgrade log4j in DSpace v7, and no doubt it'll get larger still before we >> take a decision to either merge or abandon it. >> >> Sarah >> >> >> >> On Mon, 10 Jan 2022 at 16:28, 'Tim Donohue' via DSpace Technical Support < >> dspac...@googlegroups.com> wrote: >> >>> Hi Sarah, >>> >>> Just wanted to note that I'm not aware of anyone who has tried updating >>> DSpace 6.x (or any prior release) to log4j v2. As I initially noted in >>> this log4j summary email ( >>> https://groups.google.com/g/dspace-tech/c/QR59bS4nIT0/m/Ze2hyOhhAgAJ), >>> I believe this upgrade would be extremely complex (and I'm not even sure if >>> it's possible). >>> >>> Unfortunately, most of the other dependencies which DSpace 6.x (and >>> 5.x/4.x or any prior release) use all also rely on log4j v1 (especially >>> Solr) . Attempting to upgrade DSpace 6.x to log4j v2 therefore may also >>> require finding ways to upgrade or patch *all other dependencies which >>> also rely on log4j v1*and that likely would be a massive >>> undertaking (possibly similar effort to a new major release of DSpace). >>> >>> This is why I recommend that anyone who wants to be on log4j v2 please >>> consider upgrading to DSpace 7.x in the near future (version 7.2 is right >>> around the corner & due on Feb 7). It is not always easy (or even >>> possible) to update dependencies in the DSpace 6.x/5.x platforms, as we are >>> sometimes blocked / or hampered by the age of the User Interface >>> technologies (especially Apache Cocoon for XMLUI) and other core >>> dependencies (older Solr, Spring technologies, etc.) >>> >>> If you or anyone else has further questions on this, let us know on this >>> list, >>> >>> Tim >>> >>> On Wednesday, January 5, 2022 at 12:42:34 PM UTC-6 mount...@gmail.com >>> wrote: >>> >>>> Hello all, >>>> >>>> I'm aware that DSpace 6.x is not going to get a patch that would allow >>>> end-users to upgrade to Log4Jv2, but I was wondering whether anyone else is >>>> likely to be working on this? >>>> >>>> Thanks, >>>> >>>> Sara
Re: [dspace-tech] Re: Log4J and DSpace 6.x
Hi Tim, Many thanks for this. For reasons that I won't go into here, it looks like trying to patch 6.4 is something that we need to try. It may be that the v1->v2 bridge that's been mentioned will be a better option for us, but we're looking at both choices right now. Currently, I have a version of 6.4 that does not directly use log4j v1, but it does still have a handful (<20) of transitive imports of v1 from slf4 and Solr. The patched 6.4 can compile all the front-ends and pass the unit/integration tests, and I can run DSpace locally in a container -- but I haven't tackled converting the configuration files in earnest yet, and I've noticed that the PR for v7 uses XML for some configuration files. My local PR for this is already approx. 1kloc larger than the PR to upgrade log4j in DSpace v7, and no doubt it'll get larger still before we take a decision to either merge or abandon it. Sarah On Mon, 10 Jan 2022 at 16:28, 'Tim Donohue' via DSpace Technical Support < dspace-tech@googlegroups.com> wrote: > Hi Sarah, > > Just wanted to note that I'm not aware of anyone who has tried updating > DSpace 6.x (or any prior release) to log4j v2. As I initially noted in > this log4j summary email ( > https://groups.google.com/g/dspace-tech/c/QR59bS4nIT0/m/Ze2hyOhhAgAJ), I > believe this upgrade would be extremely complex (and I'm not even sure if > it's possible). > > Unfortunately, most of the other dependencies which DSpace 6.x (and > 5.x/4.x or any prior release) use all also rely on log4j v1 (especially > Solr) . Attempting to upgrade DSpace 6.x to log4j v2 therefore may also > require finding ways to upgrade or patch *all other dependencies which > also rely on log4j v1*and that likely would be a massive undertaking > (possibly similar effort to a new major release of DSpace). > > This is why I recommend that anyone who wants to be on log4j v2 please > consider upgrading to DSpace 7.x in the near future (version 7.2 is right > around the corner & due on Feb 7). It is not always easy (or even > possible) to update dependencies in the DSpace 6.x/5.x platforms, as we are > sometimes blocked / or hampered by the age of the User Interface > technologies (especially Apache Cocoon for XMLUI) and other core > dependencies (older Solr, Spring technologies, etc.) > > If you or anyone else has further questions on this, let us know on this > list, > > Tim > > On Wednesday, January 5, 2022 at 12:42:34 PM UTC-6 mount...@gmail.com > wrote: > >> Hello all, >> >> I'm aware that DSpace 6.x is not going to get a patch that would allow >> end-users to upgrade to Log4Jv2, but I was wondering whether anyone else is >> likely to be working on this? >> >> Thanks, >> >> Sarah >> > -- > 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/f81811b6-886c-4947-8234-636a6dba8493n%40googlegroups.com > <https://groups.google.com/d/msgid/dspace-tech/f81811b6-886c-4947-8234-636a6dba8493n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Dr. Sarah Mount Technical Lead, Beautiful Canoe Fellow of the Software Sustainability Institute twitter: @snim2 -- 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/CALG3WZ%3D6FLLQSvYO%3DsB%2BgB42rsDNLvo%3DcmqQdQhtBYNkJK7BZw%40mail.gmail.com.
[dspace-tech] Log4J and DSpace 6.x
Hello all, I'm aware that DSpace 6.x is not going to get a patch that would allow end-users to upgrade to Log4Jv2, but I was wondering whether anyone else is likely to be working on this? Thanks, Sarah -- 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/CALG3WZ%3D-4BHYJT9T82fa0n1SEy%3DTqZ%3DsiznyoDvhRzN14aFy2A%40mail.gmail.com.
Re: [dspace-tech] DSpace Usage Statistics not working
Hi there, if you search back through the archives of this list there are answers to this question (the company that produces this dataset has changed the way it distributes the files). Regards, Sarah On Sat, 17 Apr 2021 at 15:08, SFIT Library wrote: > Our DSpace does not generate Usage Statistics Report. Can someone help > with this? We need a file whose location is given below. Please share. > Screenshot is attached herewith. > > Location of file [dspace home folder]/conf/GeoLiteCity.mmdb > > Regards, > Chinmayee Bhange > Librarian > St. Francis Institute of Technology > > -- > All messages to this mailing list should adhere to the 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 view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/CAKu85KKOxaZrEmZgsRxN-K%3D0ux0zfk4N6-J80q6u5uN7zLZLxA%40mail.gmail.com > <https://groups.google.com/d/msgid/dspace-tech/CAKu85KKOxaZrEmZgsRxN-K%3D0ux0zfk4N6-J80q6u5uN7zLZLxA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- Dr. Sarah Mount Technical Lead, Beautiful Canoe Fellow of the Software Sustainability Institute twitter: @snim2 -- All messages to this mailing list should adhere to the 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CALG3WZnVgk-y_2WvPa4cyxUpv7zfOBpKiJS1YswLA8Q9fF1Otg%40mail.gmail.com.
Re: [dspace-tech] Re: No such file or directory
pache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
>>> at
>>> org.dspace.rdf.negotiation.NegotiationFilter.doFilter(NegotiationFilter.java:52)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
>>> at
>>> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
>>> at
>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)
>>> at
>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
>>> at
>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)
>>> at
>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
>>> at
>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
>>> at
>>> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688)
>>> at
>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
>>> at
>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
>>> at
>>> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367)
>>> at
>>> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
>>> at
>>> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868)
>>> at
>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639)
>>> at
>>> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>> at
>>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>>> at java.lang.Thread.run(Thread.java:748)
>>>
>>> Στις Τετάρτη, 7 Απριλίου 2021 στις 3:39:23 μ.μ. UTC+3, ο χρήστης
>>> mount...@gmail.com έγραψε:
>>>
>>>> If you are on a Debian-based system (or maybe just if you are using
>>>> systemd) you might need to add ReadWritePaths to your tomcat.service file.
>>>>
>>>> Otherwise, I think it's hard to say more without a stacktrace and some
>>>> more information.
>>>>
>>>> Best wishes,
>>>>
>>>> Sarah
>>>>
>>>> On Wed, 7 Apr 2021 at 10:27, kpet wrote:
>>>>
>>>>> I have the same problem on Dspace 6.3 and I have verified that the
>>>>> user that tomcat runs as, is also the owner of the directory pointed by
>>>>> the
>>>>> {assetstore.dir} in local.cfg. Any ideas?
>>>>>
>>>>> Στις Δευτέρα, 5 Απριλίου 2021 στις 9:38:19 μ.μ. UTC+3, ο χρήστης
>>>>> daniel.fern...@gmail.com έγραψε:
>>>>>
>>>>>> Hi, Haimanot:
>>>>>>
>>>>>> The user running Tomcat has to be the owner of dspace directories. By
>>>>>> default, this user is tomcat. Check if the owner of Tomcat and Dspace is
>>>>>> the same user.
>>>>>>
>>>>>> Kind regards,
>>>>>> dfm
>>>>>>
>>>>>> El jueves, 1 de abril de 2021 a las 13:01:48 UTC+2,
>>>>>> haiman...@gmail.com escribió:
>>>>>>
>>>>>>> I have Installed dspace 6.3 on ubuntu 20.04 successfully but while I
>>>>>>> started Item submission on localhost:8080/xmlui and uploaded item it
>>>>>>> says
>>>>>>> No such file or directory ? how can I address or fix this problem.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Kind regards,
>>>>>>> Haimanot,
>>>>>>>
>>>>>> --
>>>>> All messages to this mailing list should adhere to the 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...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/dspace-tech/cf53e200-47e6-4f28-8f54-e26de73e9648n%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/dspace-tech/cf53e200-47e6-4f28-8f54-e26de73e9648n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>
>>>>
>>>> --
>>>> Dr. Sarah Mount
>>>> Technical Lead, Beautiful Canoe
>>>> Fellow of the Software Sustainability Institute
>>>> twitter: @snim2
>>>>
>>> --
>>> All messages to this mailing list should adhere to the 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...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/dspace-tech/27b6c47b-2f61-4675-8cae-fc92c725a981n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/dspace-tech/27b6c47b-2f61-4675-8cae-fc92c725a981n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>
>>
>> --
>> Dr. Sarah Mount
>> Technical Lead, Beautiful Canoe
>> Fellow of the Software Sustainability Institute
>> twitter: @snim2
>>
> --
> All messages to this mailing list should adhere to the 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/c1c71a73-3d6d-4610-aaf0-d7f7446810acn%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/c1c71a73-3d6d-4610-aaf0-d7f7446810acn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
Dr. Sarah Mount
Technical Lead, Beautiful Canoe
Fellow of the Software Sustainability Institute
twitter: @snim2
--
All messages to this mailing list should adhere to the 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 view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/CALG3WZkBXkjOanGhSA6p-wWK6qnOOm_V_v2-Ecgm3%3DRA_vfmaQ%40mail.gmail.com.
Re: [dspace-tech] Re: No such file or directory
ache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> at
> org.dspace.app.xmlui.cocoon.DSpaceCocoonServletFilter.doFilter(DSpaceCocoonServletFilter.java:160)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> at
> org.dspace.app.xmlui.cocoon.servlet.multipart.DSpaceMultipartFilter.doFilter(DSpaceMultipartFilter.java:119)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> at
> org.dspace.rdf.negotiation.NegotiationFilter.doFilter(NegotiationFilter.java:52)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> at
> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
> at
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
> at
> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367)
> at
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
> at
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639)
> at
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.lang.Thread.run(Thread.java:748)
>
> Στις Τετάρτη, 7 Απριλίου 2021 στις 3:39:23 μ.μ. UTC+3, ο χρήστης
> mount...@gmail.com έγραψε:
>
>> If you are on a Debian-based system (or maybe just if you are using
>> systemd) you might need to add ReadWritePaths to your tomcat.service file.
>>
>> Otherwise, I think it's hard to say more without a stacktrace and some
>> more information.
>>
>> Best wishes,
>>
>> Sarah
>>
>> On Wed, 7 Apr 2021 at 10:27, kpet wrote:
>>
>>> I have the same problem on Dspace 6.3 and I have verified that the user
>>> that tomcat runs as, is also the owner of the directory pointed by the
>>> {assetstore.dir} in local.cfg. Any ideas?
>>>
>>> Στις Δευτέρα, 5 Απριλίου 2021 στις 9:38:19 μ.μ. UTC+3, ο χρήστης
>>> daniel.fern...@gmail.com έγραψε:
>>>
>>>> Hi, Haimanot:
>>>>
>>>> The user running Tomcat has to be the owner of dspace directories. By
>>>> default, this user is tomcat. Check if the owner of Tomcat and Dspace is
>>>> the same user.
>>>>
>>>> Kind regards,
>>>> dfm
>>>>
>>>> El jueves, 1 de abril de 2021 a las 13:01:48 UTC+2, haiman...@gmail.com
>>>> escribió:
>>>>
>>>>> I have Installed dspace 6.3 on ubuntu 20.04 successfully but while I
>>>>> started Item submission on localhost:8080/xmlui and uploaded item it says
>>>>> No such file or directory ? how can I address or fix this problem.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Kind regards,
>>>>
Re: [dspace-tech] Re: No such file or directory
If you are on a Debian-based system (or maybe just if you are using
systemd) you might need to add ReadWritePaths to your tomcat.service file.
Otherwise, I think it's hard to say more without a stacktrace and some more
information.
Best wishes,
Sarah
On Wed, 7 Apr 2021 at 10:27, kpet wrote:
> I have the same problem on Dspace 6.3 and I have verified that the user
> that tomcat runs as, is also the owner of the directory pointed by the
> {assetstore.dir} in local.cfg. Any ideas?
>
> Στις Δευτέρα, 5 Απριλίου 2021 στις 9:38:19 μ.μ. UTC+3, ο χρήστης
> daniel.fern...@gmail.com έγραψε:
>
>> Hi, Haimanot:
>>
>> The user running Tomcat has to be the owner of dspace directories. By
>> default, this user is tomcat. Check if the owner of Tomcat and Dspace is
>> the same user.
>>
>> Kind regards,
>> dfm
>>
>> El jueves, 1 de abril de 2021 a las 13:01:48 UTC+2, haiman...@gmail.com
>> escribió:
>>
>>> I have Installed dspace 6.3 on ubuntu 20.04 successfully but while I
>>> started Item submission on localhost:8080/xmlui and uploaded item it says
>>> No such file or directory ? how can I address or fix this problem.
>>>
>>>
>>>
>>>
>>> Kind regards,
>>> Haimanot,
>>>
>> --
> All messages to this mailing list should adhere to the 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/cf53e200-47e6-4f28-8f54-e26de73e9648n%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/cf53e200-47e6-4f28-8f54-e26de73e9648n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
Dr. Sarah Mount
Technical Lead, Beautiful Canoe
Fellow of the Software Sustainability Institute
twitter: @snim2
--
All messages to this mailing list should adhere to the 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 view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/CALG3WZ%3DNQx%2BaRjBSFJUKU8WN54VT4fV5cggfftHXNmKjC%3DkM2A%40mail.gmail.com.
Re: [dspace-tech] Solr permissions error after fresh install (DSpace 6.3)
"Cannot create directory" does sound like a permissions issue. Have you listed the relevant ReadWritePaths in your tomcat.service file? Sarah On Tue, 6 Apr 2021 at 20:46, gonza...@gmail.com wrote: > Hi, > > I've installed DSpace 6.x a couple of times but never faced this problem > before and I'm kinda lost. There must be something quite simple to solve it > just in front of me... > > Context: > Debian 10 > DSpace 6.3 fresh install > OpenJDK 1.8 > Tomcat 9.0.31.0 > > After a fresh install, I'm getting some permissions related errors while > using Solr, for instance trying to browse by author, titles, etc. > > org.apache.solr.common.SolrException: SolrCore 'search' is > not available due to init failure: > Cannot create directory: > /var/www/dspace/solr/search/data/index > > (I don't like those html entities either) > > Full stacktrace here: https://pastebin.pl/view/c58da1d2 > > I get the same error using Solr via the dspace command line, for instance > $ sudo ./bin/dspace index-discovery > > The [dspace] folder has read and write permissions for tomcat:tomcat > User dspace is in tomcat group > > Any help is appreciated! > > -- > All messages to this mailing list should adhere to the 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 view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/217a966d-4049-4f43-9fbb-c0c2d44e5aa6n%40googlegroups.com > <https://groups.google.com/d/msgid/dspace-tech/217a966d-4049-4f43-9fbb-c0c2d44e5aa6n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Dr. Sarah Mount Technical Lead, Beautiful Canoe Fellow of the Software Sustainability Institute twitter: @snim2 -- All messages to this mailing list should adhere to the 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CALG3WZk%2Br7Vz7d_p-WLDhy0Mjnri%3DHx0u4%3DvT937bVu1aQQSKQ%40mail.gmail.com.
[dspace-tech] Question about DSpace 6.3 statistics links
Hello all, I have a DSpace 6.3 / Tomcat 9 installation and it's not clear to me whether I've set Solr up correctly. The dashboard at: http://server.domain:8080/solr/ is working (although the logging tab shows lots of deprecation warnings) and currently, these pages seem to work: http://server.domain:8080/search-statistics http://server.domain:8080/statistics-home http://server.domain:8080/workflow-statistics But this page: http://server.domain:8080/statistics seems to permanently say "There are currently no reports available for this service. Please check back later.". Is /statistics the page for legacy statistics or should this be showing some data? Many thanks, Sarah -- All messages to this mailing list should adhere to the 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CALG3WZkgOGv%3DxYmtv3v-fE9XkeTEQsXVdY20TX4aGka2vnVaaA%40mail.gmail.com.
Re: [dspace-tech] Issue with log4j after starting dspace
It looks like the core of your issue is "Read-only file system". I would start by checking to see whether the disk is full. If that's not the case, then maybe the disk is not mounted read-write. Regards, Sarah On Tue, Oct 20, 2020 at 7:26 PM Marco Cristobal wrote: > i have an installation, i have trouble starting it > i start the service tomcat and it try to starts all webapps... > when i check the tomcat log i see this > im using this instance with the tomcat user, this user have all the > permissions in this directory, i already search this problem and i cant > find any solution... > > > tomcat9[514315]: log4j:ERROR setFile(null,true) call failed. > tomcat9[514315]: java.io.FileNotFoundException: > /dspace/log/checker.log.2020-10-20 (Read-only file system) > tomcat9[514315]: at java.io.FileOutputStream.open0(Native Method) > tomcat9[514315]: at > java.io.FileOutputStream.open(FileOutputStream.java:270) > tomcat9[514315]: at > java.io.FileOutputStream.(FileOutputStream.java:213) > tomcat9[514315]: at > java.io.FileOutputStream.(FileOutputStream.java:133) > tomcat9[514315]: at > org.apache.log4j.FileAppender.setFile(FileAppender.java:294) > tomcat9[514315]: at > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165) > tomcat9[514315]: at > org.dspace.app.util.DailyFileAppender.activateOptions(DailyFileAppender.java:94) > tomcat9[514315]: at > org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307) > tomcat9[514315]: at > org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172) > tomcat9[514315]: at > org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104) > tomcat9[514315]: at > org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842) > tomcat9[514315]: at > org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768) > tomcat9[514315]: at > org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672) > tomcat9[514315]: at > org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:516) > tomcat9[514315]: at > org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580) > tomcat9[514315]: at > org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526) > tomcat9[514315]: at > org.dspace.core.ConfigurationManager.loadConfig(ConfigurationManager.java:805) > tomcat9[514315]: at > org.dspace.app.util.DSpaceContextListener.contextInitialized(DSpaceContextListener.java:102) > tomcat9[514315]: at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4685) > tomcat9[514315]: at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5146) > tomcat9[514315]: at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) > tomcat9[514315]: at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:717) > tomcat9[514315]: at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690) > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/7983c121-f1f2-431c-b93d-a0c1f2dccb63n%40googlegroups.com > <https://groups.google.com/d/msgid/dspace-tech/7983c121-f1f2-431c-b93d-a0c1f2dccb63n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Dr. Sarah Mount Technical Lead, Beautiful Canoe Fellow of the Software Sustainability Institute twitter: @snim2 -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CALG3WZn2fdsPjW9Xp2tqCL%2B1B4roPqijC8SVUzjdNwtm9FbSLA%40mail.gmail.com.
[dspace-tech] Using the example AIP-files in a new DSpace instance
Hello DSpace people! I have a new instance of DSpace, and I'd like to upload the example DogsAndPhotos AIP files [here: https://github.com/DSpace-Labs/AIP-Files] to the instance. I've unzipped the files, and tried to import the contents with packager: $ PATH/dspace/bin/dspace packager -s -a -t AIP -e MYEMAIL@ADDRESS commun...@123456789-1.zip Ingesting package located at commun...@123456789-1.zip Also ingesting all referenced packages (recursive mode).. This may take a while, please check your logs for ongoing status while we process each package. java.lang.UnsupportedOperationException: Could not find a parent DSpaceObject referenced as '123456789/1' in the METS Manifest for object hdl:123456789/3. A parent DSpaceObject must be specified from either the 'packager' command or noted in the METS Manifest itself. at org.dspace.content.packager.AbstractMETSIngester.getParentObject(AbstractMETSIngester.java:1379) at org.dspace.content.packager.AbstractMETSIngester.ingestObject(AbstractMETSIngester.java:402) at org.dspace.content.packager.AbstractMETSIngester.ingest(AbstractMETSIngester.java:243) at org.dspace.content.packager.AbstractPackageIngester.ingestAll(AbstractPackageIngester.java:147) at org.dspace.content.packager.AbstractPackageIngester.ingestAll(AbstractPackageIngester.java:197) at org.dspace.app.packager.Packager.ingest(Packager.java:517) at org.dspace.app.packager.Packager.main(Packager.java:426) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81) java.lang.UnsupportedOperationException: Could not find a parent DSpaceObject referenced as '123456789/1' in the METS Manifest for object hdl:123456789/3. A parent DSpaceObject must be specified from either the 'packager' command or noted in the METS Manifest itself. Clearly I've missed something obvious here, maybe `-p ` but I'm not sure what that handle should be? Also, is it really necessary to import each community, collection and item one by one, or is it possible to import the whole .ZIP file in one go? Very many thanks! Sarah -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/86ceaf7c-ede3-4f6f-a22e-bab8318ee0f5o%40googlegroups.com.
