subject:"\[dspace\-tech\] Re\: FAIL \- Application at context path \[\/server\] could not be started"

Re: [dspace-tech] Re: FAIL - Application at context path [/server] could not be started

2023-06-15 Thread Edilton Danniken

Hi, Thanks for your reply again.
I have created a context.xml file in Catalina/localhost/ folder togther
server.xml and that works well.
I would like to suggest a mention in documentation about in some cases
where is needing a file 'context.xml', for the reason that some people like
me who try to install dspace with no expericente with java and tomcat
environments.

Em qui., 15 de jun. de 2023 às 15:17, DSpace Technical Support <
dspace-tech@googlegroups.com> escreveu:

> The DSpace build process won't generate a Tomcat "context" for you.  You
> are expected to create one.  See step 11 of the Installation Process for
> the Backend (Technique A)
>
>
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-BackendInstallation
>
> Basically, it sounds like your Tomcat setup is not able to find or load
> the "server" webapp because it's expecting you to have a context.xml.
>
> Tim
>
> On Thursday, June 15, 2023 at 12:52:06 PM UTC-5 edilton...@gmail.com
> wrote:
>
>> Hi,
>> Thanks for your reply.
>>
>> So, the tomcat logs completely are.
>>
>> 15-Jun-2023 14:48:02.611 GRAVE [http-nio-8080-exec-14]
>> org.apache.catalina.core.ApplicationContext.log HTMLManager: Error starting
>> [/server]
>>
>> org.apache.catalina.LifecycleException: Failed to process either the
>> global, per-host or context-specific context.xml file therefore the
>> [/server] Context cannot be started.
>> at
>> org.apache.catalina.startup.FailedContext.startInternal(FailedContext.java:200)
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
>> at
>> org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1438)
>> at
>> org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:702)
>> at
>> org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:220)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:555)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:623)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:209)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
>> at
>> org.apache.catalina.filters.CsrfPreventionFilter.doFilter(CsrfPreventionFilter.java:190)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
>> at
>> org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:129)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:167)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
>> at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:596)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
>> at
>> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:673)
>> 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:390)
>> at
>> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
>> at
>> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:926)
>> at
>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791)
>> at
>> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
>> at
>> org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
>> at
>> org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
>> at
>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>> at java.base/java.lang.Thread.run(Thread.java:833)
>>
>>
>> Basically, as context.xml file was not found. But the command *mvn
>> package* or ant *fresh_install* didn't generate it. I don't know how to
>> solve this.
>>
>> Em qui., 15 de jun. de 2023 às 14:00, DSpace Technical Support <
>> dspac...@googlegroups.com> escreveu:
>>
>>> Hi,
>>>
>>> This sounds like you are encountering an error in Tomcat.  I'd recommend
>>> checking the Tomcat

Re: [dspace-tech] Re: FAIL - Application at context path [/server] could not be started

2023-06-15 Thread DSpace Technical Support

The DSpace build process won't generate a Tomcat "context" for you.  You 
are expected to create one.  See step 11 of the Installation Process for 
the Backend (Technique A)  

https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-BackendInstallation

Basically, it sounds like your Tomcat setup is not able to find or load the 
"server" webapp because it's expecting you to have a context.xml.

Tim

On Thursday, June 15, 2023 at 12:52:06 PM UTC-5 edilton...@gmail.com wrote:

> Hi,
> Thanks for your reply.
>
> So, the tomcat logs completely are.
>
> 15-Jun-2023 14:48:02.611 GRAVE [http-nio-8080-exec-14] 
> org.apache.catalina.core.ApplicationContext.log HTMLManager: Error starting 
> [/server]
>
> org.apache.catalina.LifecycleException: Failed to process either the 
> global, per-host or context-specific context.xml file therefore the 
> [/server] Context cannot be started.
> at 
> org.apache.catalina.startup.FailedContext.startInternal(FailedContext.java:200)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at 
> org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1438)
> at 
> org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:702)
> at 
> org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:220)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:555)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:623)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:209)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
> at 
> org.apache.catalina.filters.CsrfPreventionFilter.doFilter(CsrfPreventionFilter.java:190)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
> at 
> org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:129)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:167)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
> at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:596)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
> at 
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:673)
> 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:390)
> at 
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
> at 
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:926)
> at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791)
> at 
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
> at 
> org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
> at 
> org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
> at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.base/java.lang.Thread.run(Thread.java:833)
>
>
> Basically, as context.xml file was not found. But the command *mvn 
> package* or ant *fresh_install* didn't generate it. I don't know how to 
> solve this. 
>
> Em qui., 15 de jun. de 2023 às 14:00, DSpace Technical Support <
> dspac...@googlegroups.com> escreveu:
>
>> Hi,
>>
>> This sounds like you are encountering an error in Tomcat.  I'd recommend 
>> checking the Tomcat logs for details of the error.  See also our 
>> Troubleshooting guide: 
>> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>>
>> It's important to share the full details of any error you find, as that 
>> will let others know what the core problem is.  The error you've shared so 
>> far just says that the "/server" webapp failed to start... but it gives no 
>> hints as to why it failed.
>>
>> Tim
>>
>> On Thursday, June 15, 2023 at 10:09:29 AM UTC-5 edilton...@gmail.com 
>> wrote:
>>
>>>

Re: [dspace-tech] Re: FAIL - Application at context path [/server] could not be started

2023-06-15 Thread Edilton Danniken

Hi,
Thanks for your reply.

So, the tomcat logs completely are.

15-Jun-2023 14:48:02.611 GRAVE [http-nio-8080-exec-14]
org.apache.catalina.core.ApplicationContext.log HTMLManager: Error starting
[/server]
org.apache.catalina.LifecycleException: Failed to process either the
global, per-host or context-specific context.xml file therefore the
[/server] Context cannot be started.
at
org.apache.catalina.startup.FailedContext.startInternal(FailedContext.java:200)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at
org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1438)
at
org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:702)
at
org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:220)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:555)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:623)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:209)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
at
org.apache.catalina.filters.CsrfPreventionFilter.doFilter(CsrfPreventionFilter.java:190)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
at
org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:129)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:167)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:596)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:673)
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:390)
at
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:926)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791)
at
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at
org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at
org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.base/java.lang.Thread.run(Thread.java:833)

Basically, as context.xml file was not found. But the command *mvn package*
or ant *fresh_install* didn't generate it. I don't know how to solve this.

Em qui., 15 de jun. de 2023 às 14:00, DSpace Technical Support <
dspace-tech@googlegroups.com> escreveu:

> Hi,
>
> This sounds like you are encountering an error in Tomcat.  I'd recommend
> checking the Tomcat logs for details of the error.  See also our
> Troubleshooting guide:
> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>
> It's important to share the full details of any error you find, as that
> will let others know what the core problem is.  The error you've shared so
> far just says that the "/server" webapp failed to start... but it gives no
> hints as to why it failed.
>
> Tim
>
> On Thursday, June 15, 2023 at 10:09:29 AM UTC-5 edilton...@gmail.com
> wrote:
>
>> Dear,
>>
>> Someone help me,
>>
>> I followed the documentation to install dspace 7.5 (
>> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-InstallationOverview
>> )
>> However, when start tomcat, I always receive the error below:
>> FAIL - Application at context path [/server] could not be started FAIL -
>> Encountered exception [org.apache.catalina.LifecycleException: Failed to
>> process either the global, per-host or context-specific context.xml file
>> therefore the [/server] Context cannot be started.]
>>
>>
>>
> --
> 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

[dspace-tech] Re: FAIL - Application at context path [/server] could not be started

2023-06-15 Thread DSpace Technical Support

Hi,

This sounds like you are encountering an error in Tomcat.  I'd recommend 
checking the Tomcat logs for details of the error.  See also our 
Troubleshooting 
guide: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

It's important to share the full details of any error you find, as that 
will let others know what the core problem is.  The error you've shared so 
far just says that the "/server" webapp failed to start... but it gives no 
hints as to why it failed.

Tim

On Thursday, June 15, 2023 at 10:09:29 AM UTC-5 edilton...@gmail.com wrote:

> Dear, 
>
> Someone help me,
>
> I followed the documentation to install dspace 7.5 (
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-InstallationOverview
> )
> However, when start tomcat, I always receive the error below:
> FAIL - Application at context path [/server] could not be started FAIL - 
> Encountered exception [org.apache.catalina.LifecycleException: Failed to 
> process either the global, per-host or context-specific context.xml file 
> therefore the [/server] Context cannot be started.]
>
>  
>

-- 
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/8ec3e9b5-10b5-4eb6-bf2e-ba5fe04ab8ddn%40googlegroups.com.

Re: [dspace-tech] Re: FAIL - Application at context path [/server] could not be started

2022-04-01 Thread 'Tim Donohue' via DSpace Technical Support

Hi,

In the "localhost_log" you attached, there's a major error at the very top of 
that file.  It ends with this text:


Initialization of bean failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'sessionFactory' defined in file 
[/dspace/config/spring/api/core-hibernate.xml]: Invocation of init method 
failed; nested exception is 
org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: 
missing column [uuid] in table [public.bitstream]

Notice that final line says that your database table "bitstream" is missing the 
required "uuid" column. This implies to me that you have skipped the Database 
setup step, or it failed in some other way.  See step #5 and #10 of the 
installation instructions: 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-BackendInstallation

If you are performing an upgrade, see step #7 of the upgrade process: 
https://wiki.lyrasis.org/display/DSDOC7x/Upgrading+DSpace#UpgradingDSpace-UpgradingtheBackendSteps

After running the "dspace database migrate" command to initialize your 
database, you should check your dspace.log to make sure no errors are listed 
there.  If there are errors, they need to be resolved before your site will 
work.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Night Librarian 
Sent: Thursday, March 31, 2022 9:34 PM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: FAIL - Application at context path [/server] could 
not be started

Thank you, Tim.

There is nothing in Dspace logs, but Tomcat has it logged in two files. 
Catalina.log has this:

31-Mar-2022 23:11:01.216 WARNING [http-nio-8080-exec-15] 
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web 
application [server] appears to have started a thread named 
[org.dspace.services] but has failed to stop it. This is very likely to create 
a memory leak. Stack trace of thread:
java.base@11.0.14/java.lang.Object.wait(Native Method)
java.base@11.0.14/java.lang.Object.wait(Object.java:328)
java.base@11.0.14/java.util.TimerThread.mainLoop(Timer.java:527)
java.base@11.0.14/java.util.TimerThread.run(Timer.java:506)
31-Mar-2022 23:11:01.239 WARNING [http-nio-8080-exec-15] 
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web 
application [server] appears to have started a thread named [Thread-18] but has 
failed to stop it. This is very likely to create a memory leak. Stack trace of 
thread:
java.base@11.0.14/java.lang.Object.wait(Native Method)
org.dspace.service.impl.HttpConnectionPoolService$IdleConnectionMonitorThread.run(HttpConnectionPoolService.java:176)
31-Mar-2022 23:11:30.963 INFO [http-nio-8080-exec-15] 
org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for 
TLDs yet contained no TLDs. Enable debug logging for this logger for a complete 
list of JARs that were scanned but no TLDs were found in them. Skipping 
unneeded JARs during scanning can improve startup time and JSP compilation time.

There is also localhost.log, but it is over 200 lines long, so I copy/pasted it 
into a text file, if that is OK.
On Wednesday, March 30, 2022 at 4:51:58 p.m. UTC-3 Tim Donohue wrote:
Hi,

You'd need to check the DSpace and Tomcat logs for information about the error. 
 The message you shared just shows that it failed to start, but it doesn't tell 
us "why".  The "why" part is usually in the logs.  Here's our troubleshooting 
guide for information on finding errors in logs (and elsewhere): 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim

On Monday, March 28, 2022 at 2:57:45 PM UTC-5 Night Librarian wrote:

I am trying to install DSpace 7.2 on Ubuntu 20.04.3 LTS.  According to the 
instructions in step 11 here: Installing DSpace - DSpace 7.x Documentation - 
LYRASIS Wiki<https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace>, I 
copied the "server" webapp from /dspace/webapps to /var/lib/tomcat9/webapps.  
Now, "server" is showing in Tomcat Web Application Manager, but when I click on 
start next to it, the Manager says:

FAIL - Application at context path [/server] could not be started

FAIL - Encountered exception [org.apache.catalina.LifecycleException: Failed to 
start component 
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/server]]]


What could be the problem here?

--
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 a topic in the Google 
Groups "DSpace Technical Support" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/dspace-tech/j0XgHkeLxQM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
ds

[dspace-tech] Re: FAIL - Application at context path [/server] could not be started

2022-03-31 Thread Night Librarian

Thank you, Tim.

There is nothing in Dspace logs, but Tomcat has it logged in two files. 
Catalina.log has this:

31-Mar-2022 23:11:01.216 WARNING [http-nio-8080-exec-15] 
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The 
web application [server] appears to have started a thread named 
[org.dspace.services] but has failed to stop it. This is very likely to 
create a memory leak. Stack trace of thread: 
java.base@11.0.14/java.lang.Object.wait(Native Method) 
java.base@11.0.14/java.lang.Object.wait(Object.java:328) 
java.base@11.0.14/java.util.TimerThread.mainLoop(Timer.java:527) 
java.base@11.0.14/java.util.TimerThread.run(Timer.java:506) 
31-Mar-2022 23:11:01.239 WARNING [http-nio-8080-exec-15] 
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The 
web application [server] appears to have started a thread named [Thread-18] 
but has failed to stop it. This is very likely to create a memory leak. 
Stack trace of thread: 
java.base@11.0.14/java.lang.Object.wait(Native Method) 
org.dspace.service.impl.HttpConnectionPoolService$IdleConnectionMonitorThread.run(HttpConnectionPoolService.java:176)

31-Mar-2022 23:11:30.963 INFO [http-nio-8080-exec-15] 
org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned 
for TLDs yet contained no TLDs. Enable debug logging for this logger for a 
complete list of JARs that were scanned but no TLDs were found in them. 
Skipping unneeded JARs during scanning can improve startup time and JSP 
compilation time. 

There is also localhost.log, but it is over 200 lines long, so I 
copy/pasted it into a text file, if that is OK.
On Wednesday, March 30, 2022 at 4:51:58 p.m. UTC-3 Tim Donohue wrote:

> Hi,
>
> You'd need to check the DSpace and Tomcat logs for information about the 
> error.  The message you shared just shows that it failed to start, but it 
> doesn't tell us "why".  The "why" part is usually in the logs.  Here's our 
> troubleshooting guide for information on finding errors in logs (and 
> elsewhere): 
> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>
> Tim
>
> On Monday, March 28, 2022 at 2:57:45 PM UTC-5 Night Librarian wrote:
>
>> I am trying to install DSpace 7.2 on Ubuntu 20.04.3 LTS.  According to 
>> the instructions in step 11 here: Installing DSpace - DSpace 7.x 
>> Documentation - LYRASIS Wiki 
>> , I copied 
>> the "server" webapp from /dspace/webapps to /var/lib/tomcat9/webapps.  Now, 
>> "server" is showing in Tomcat Web Application Manager, but when I click on 
>> start next to it, the Manager says:
>>
>> FAIL - Application at context path [/server] could not be started 
>>
>> FAIL - Encountered exception [org.apache.catalina.LifecycleException: 
>> Failed to start component 
>> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/server]]] 
>>  
>>
>>
>> What could be the problem here?
>>
>

-- 
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/bad97042-e3d6-453d-8874-7f1fe65fd9cfn%40googlegroups.com.
31-Mar-2022 23:10:30.412 INFO [http-nio-8080-exec-21] 
org.apache.catalina.core.ApplicationContext.log HTMLManager: list: Listing 
contexts for virtual host 'localhost'
31-Mar-2022 23:11:01.155 INFO [http-nio-8080-exec-15] 
org.apache.catalina.core.ApplicationContext.log HTMLManager: start: Starting 
web application '/server'
31-Mar-2022 23:11:33.559 INFO [http-nio-8080-exec-15] 
org.apache.catalina.core.ApplicationContext.log 2 Spring 
WebApplicationInitializers detected on classpath
31-Mar-2022 23:12:16.062 INFO [http-nio-8080-exec-15] 
org.apache.catalina.core.ApplicationContext.log Initializing Spring embedded 
WebApplicationContext
31-Mar-2022 23:12:52.645 SEVERE [http-nio-8080-exec-15] 
org.apache.catalina.core.ApplicationContext.log HTMLManager: Error starting 
[/server]
org.apache.catalina.LifecycleException: Failed to start component 
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/server]]
at 
org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)
at org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1415)
at 
org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:700)
at 
org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:223)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
at

[dspace-tech] Re: FAIL - Application at context path [/server] could not be started

2022-03-30 Thread 'Tim Donohue' via DSpace Technical Support

Hi,

You'd need to check the DSpace and Tomcat logs for information about the 
error.  The message you shared just shows that it failed to start, but it 
doesn't tell us "why".  The "why" part is usually in the logs.  Here's our 
troubleshooting guide for information on finding errors in logs (and 
elsewhere): 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim

On Monday, March 28, 2022 at 2:57:45 PM UTC-5 Night Librarian wrote:

> I am trying to install DSpace 7.2 on Ubuntu 20.04.3 LTS.  According to the 
> instructions in step 11 here: Installing DSpace - DSpace 7.x 
> Documentation - LYRASIS Wiki 
> , I copied 
> the "server" webapp from /dspace/webapps to /var/lib/tomcat9/webapps.  Now, 
> "server" is showing in Tomcat Web Application Manager, but when I click on 
> start next to it, the Manager says:
>
> FAIL - Application at context path [/server] could not be started 
>
> FAIL - Encountered exception [org.apache.catalina.LifecycleException: 
> Failed to start component 
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/server]]]  
>
>
> What could be the problem here?
>

-- 
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/85bda887-d097-4917-a656-0d1d63f1702an%40googlegroups.com.

Re: [dspace-tech] Re: FAIL - Application at context path [/server] could not be started

Re: [dspace-tech] Re: FAIL - Application at context path [/server] could not be started

Re: [dspace-tech] Re: FAIL - Application at context path [/server] could not be started

[dspace-tech] Re: FAIL - Application at context path [/server] could not be started

Re: [dspace-tech] Re: FAIL - Application at context path [/server] could not be started

[dspace-tech] Re: FAIL - Application at context path [/server] could not be started

[dspace-tech] Re: FAIL - Application at context path [/server] could not be started

7 matches

Site Navigation

Mail list logo

Footer information