Dear Tim, I tried to narrow down based the log location you have pointed out. The following SEVERE errors look more alarming. So, I increased DEBUG level to get more idea. I have attached the logs for the reference.
One error which I noticed is below:
INFO [org.dspace.servicemanager.DSpaceKernelInit] Created new kernel:
DSpaceKernel:org.dspace:name=3ef28cec-58f0-4d20-a3e5-899d1c1168ce,type=DSpaceKernel:lastLoad=null:loadTime=0:running=false:kernel=null
Failure during filter init: DSpace home directory could not be determined.
It MUST include a subpath of '/config/config-definition.xml'. Please
consider setting the 'dspace.dir' system property or ensure the
dspace-api.jar is being run from [dspace]/lib/.:java.lang.RuntimeException:
DSpace home directory could not be determined. It MUST include a subpath of
'/config/config-definition.xml'. Please consider setting the 'dspace.dir'
system property or ensure the dspace-api.jar is being run from
[dspace]/lib/.
13-Jul-2019 12:42:58.538 SEVERE [localhost-startStop-1]
org.apache.catalina.core.StandardContext.listenerStart Exception sending
context initialized event to listener instance of class
org.dspace.servicemanager.servlet.DSpaceKernelServletContextListener
java.lang.RuntimeException: Failure during filter init: DSpace home
directory could not be determined. It MUST include a subpath of
'/config/config-definition.xml'. Please consider setting the 'dspace.dir'
system property or ensure the dspace-api.jar is being run from
[dspace]/lib/.
at
org.dspace.servicemanager.servlet.DSpaceKernelServletContextListener.contextInitialized(DSpaceKernelServletContextListener.java:92)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4853)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
I could not find the local.cfg under my installation. So, I freshly created
local.cfg under /home/libraryserver/dspace/DSpace/dspace/config/ with the
below content:
Regards
Yesudian Rajkumar
On Monday, July 8, 2019 at 9:52:04 PM UTC+5:30, Tim Donohue wrote:
>
> Since you are performing both an upgrade and a migration at the same time,
> I'd recommend *first* doing a fresh installation of DSpace 6.3 following
> the Installation Instructions at:
> https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace , then you
> can move over your old data from 4.x into 6.x. It can sometimes be
> difficult to do both a migration of data and an upgrade simultaneously.
> So, if you can start from a "working" fresh installation, it'll be much
> easier to then move your old data / configuration over and get up and
> running quickly.
>
> In any case, from the error, it sounds like you have not properly setup
> Tomcat to load the DSpace webapps (as Tomcat responds with a 404 error if
> the webapp isn't found or won't load). It's also possible that your DSpace
> webapp is throwing an error behind the scenes -- so, you should check the
> Tomcat logs and DSpace logs (see
> https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error for how
> to find errors in logs).
>
> If you find an error in the logs and cannot figure out what it means, you
> may try searching this email list (or search Google) to see if others have
> had the same problem. If you cannot find a solution, please send it to
> this email list and we'll see if we can help you.
>
> Tim
>
> On Thu, Jul 4, 2019 at 1:57 AM Yesudian <[email protected] <javascript:>>
> wrote:
>
>> Dear Tim,
>>
>> As per the suggestion -
>> https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace, I followed
>> the step 10) Deploy DSpace Web Applications [ recursively copied all the
>> files, folders under webapps]. Now, I am not able to view the
>> http://localhost:8080/xmlui and http://localhost:8080/xmlui. I are
>> getting 404 error.
>>
>> So, I followed the steps mentioned in
>> https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-deployment
>>
>> in step 10. I created the xmlui.xml and jspui.xml under
>> [tomcat]/conf/Catalina/localhost. Then I restarted Tomcat & Apache. But
>> still, I see the 404 error.
>>
>> Am I missing any steps? Could you please let me know?
>>
>> Regards
>> Yesudian Rajkumar
>>
>> On Thursday, June 27, 2019 at 8:27:41 AM UTC+5:30, Yesudian wrote:
>>>
>>> Hi Tim,
>>>
>>> Thanks a lot for your inputs. I will try them during next week and
>>> update you how it goes.
>>>
>>> Regards
>>> Yesudian Rajkumar
>>>
>>> On Wednesday, June 26, 2019 at 11:10:21 PM UTC+5:30, Tim Donohue wrote:
>>>>
>>>> Hello,
>>>>
>>>> DSpace 6.3 supports upgrading from any prior version of DSpace. So,
>>>> you should not need to use any special import process, provided that you
>>>> were able to retain a copy of the main [dspace] folder (especially the
>>>> "assetstore") and retain a copy of the database (where all the metadata is
>>>> stored). Here's the DSpace 6.x upgrade instructions, and these should
>>>> work
>>>> fine when pointed at a database from DSpace 4.x and an old [dspace]
>>>> folder.
>>>> https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace
>>>>
>>>> If you have more specific questions, let us know on this mailing list.
>>>>
>>>> Tim
>>>>
>>>> On Tue, Jun 25, 2019 at 7:40 AM Yesudian <[email protected]> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>> Greeting to you.
>>>>>
>>>>> In our college, we were using DSpace 4.2 on Ubuntu 14.04. Because of
>>>>> some unknown hardware failures, we could not boot into the system. But we
>>>>> could take the copy of the $DSPACE folder with contents. (Please see the
>>>>> attachment)
>>>>>
>>>>> Now, we have installed Ubuntu 18.04 and brought up DSpace 6.3. Would
>>>>> you tell us the set of procedures for us to import the old Dspace 4.2
>>>>> into
>>>>> Dspace 6.3?
>>>>>
>>>>> Regards
>>>>> Yesudian Rajkumar
>>>>>
>>>>> --
>>>>> 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 [email protected].
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/dspace-tech/2940f325-7e2f-4558-87f5-3b31e5670856%40googlegroups.com
>>>>>
>>>>> <https://groups.google.com/d/msgid/dspace-tech/2940f325-7e2f-4558-87f5-3b31e5670856%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Tim Donohue
>>>> Technical Lead for DSpace & DSpaceDirect
>>>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>>>>
>>>> --
>> 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 [email protected] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/dspace-tech/cf63644b-33be-45e2-81b4-fc29523b0fe8%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/dspace-tech/cf63644b-33be-45e2-81b4-fc29523b0fe8%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> --
>
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/3bcfcf09-6f9b-41db-b906-2159d05cba99%40googlegroups.com.
dspace-more-logs-July14
Description: Binary data
