nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Tomcat auto shutdown

henrychoi_yw

Dear All,
I am having issue with the tomcat my Alfresco using. It auto shutdown the service randomly.
I need to SSH in and start the service manually every time when the service shutdown.

OS: CentOS
Alfresco Ver: 4.0.d

Can someone tell me why it auto shutdown and how do I prevent that happen again.

Henry

Find more posts tagged with

Comments

s_palyukh

Hi,

You need to attach your log file ({alfresco}/tomcat/logs/catalina.out) to take a look at errors. I think you are getting out of memory exception

henrychoi_yw

I am getting a log missing between 10:16 and 10:30

02-Mar-2015 10:16:45 org.alfresco.solr.tracker.CoreTracker trackRepository
SEVERE: First transaction was not found with the correct timestamp.
02-Mar-2015 10:16:45 org.alfresco.solr.tracker.CoreTracker trackRepository
SEVERE: SOLR has successfully connected to your repository however the SOLR indexes and repository database do not match.
02-Mar-2015 10:16:45 org.alfresco.solr.tracker.CoreTracker trackRepository
SEVERE: If this is a new or rebuilt database you SOLR indexes also need to be re-built to match the database.
02-Mar-2015 10:16:45 org.alfresco.solr.tracker.CoreTracker trackRepository
SEVERE: You can also check your SOLR connection details in solrcore.properties.
02-Mar-2015 10:16:45 org.alfresco.solr.tracker.CoreTracker trackRepository
SEVERE: Tracking failed
org.alfresco.error.AlfrescoRuntimeException: 02020153 Initial transaction not found with correct timestamp
   at org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1243)
   at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:491)
   at org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
   at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
   at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
02-Mar-2015 10:30:30 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /opt/alfresco-4.0.d/java/jre/lib/amd64/server:/opt/alfresco-4.0.d/java/jre/lib/amd64:/opt/alfresco-4.0.d/java/jre/../lib/amd64:/opt/alfresco-4.0.d/postgresql/lib:/opt/alfresco-4.0.d/common/lib::/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
02-Mar-2015 10:30:31 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-80
02-Mar-2015 10:30:31 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8443
02-Mar-2015 10:30:31 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 844 ms
02-Mar-2015 10:30:31 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
02-Mar-2015 10:30:31 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.29

I got a message from my colleague told me cannot access Alfresco at 10:24, I started the service at 10:30. So there are 14 mins log went missing after tomcat shutdown.
Please give me a hand and see how's the log goes. It does not seems any memory error causing the issue.
I am just layman to Alfresco. My ex-colleague who has setup Alfresco left the company already.

s_palyukh

Can you attach log file, because there is no a reason of the problem in your part of the log?

mrogers

Sometimes CentOs can randomly kill a process to free up resources. The so called OOM killer. Nothing to do with Alfresco either.

So your process is either crashing in which case there should be some diagnostics that you need to post here, or its being killed from the OS level which you need to diagnose and understand.