Tomcat7 applications not running after unattended security-upgrade to 7.0.52-1ubuntu0.6 (over 7.0.52-1ubuntu0.3) on Ubuntu 14.04.4 LTS

Bug #1599496 reported by Dieter Van Houtte
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tomcat7 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Description: Ubuntu 14.04.3 LTS
Release: 14.04
--

As from this morning, our Tomcat7 application servers stopped working and the application went offline.

After troubleshooting, the time of the events notifying us about our application being offline, matches the unattended update impacting the tomcat7 package group.

-- unattended-upgrades-dpkg_2016-07-06_06:42:45.544782.log
Preconfiguring packages ...
(Reading database ... 29889 files and directories currently installed.)
Preparing to unpack .../libservlet3.0-java_7.0.52-1ubuntu0.6_all.deb ...
Unpacking libservlet3.0-java (7.0.52-1ubuntu0.6) over (7.0.52-1ubuntu0.3) ...
Preparing to unpack .../libtomcat7-java_7.0.52-1ubuntu0.6_all.deb ...
Unpacking libtomcat7-java (7.0.52-1ubuntu0.6) over (7.0.52-1ubuntu0.3) ...
Preparing to unpack .../tomcat7-common_7.0.52-1ubuntu0.6_all.deb ...
Unpacking tomcat7-common (7.0.52-1ubuntu0.6) over (7.0.52-1ubuntu0.3) ...
Preparing to unpack .../tomcat7_7.0.52-1ubuntu0.6_all.deb ...
 * Stopping Tomcat servlet engine tomcat7
   ...done.
Unpacking tomcat7 (7.0.52-1ubuntu0.6) over (7.0.52-1ubuntu0.3) ...
Preparing to unpack .../tomcat7-admin_7.0.52-1ubuntu0.6_all.deb ...
Unpacking tomcat7-admin (7.0.52-1ubuntu0.6) over (7.0.52-1ubuntu0.3) ...
Processing triggers for ureadahead (0.100.0-16) ...
ureadahead will be reprofiled on next reboot
Setting up libservlet3.0-java (7.0.52-1ubuntu0.6) ...
Setting up libtomcat7-java (7.0.52-1ubuntu0.6) ...
Setting up tomcat7-common (7.0.52-1ubuntu0.6) ...
Setting up tomcat7 (7.0.52-1ubuntu0.6) ...
 * Starting Tomcat servlet engine tomcat7
   ...done.
Setting up tomcat7-admin (7.0.52-1ubuntu0.6) ...
--

We've tried to revert the upgrade without success ;

--
tomcat7:
  Installed: 7.0.52-1ubuntu0.3
  Candidate: 7.0.52-1ubuntu0.6
  Version table:
     7.0.52-1ubuntu0.6 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
 *** 7.0.52-1ubuntu0.3 0
        100 /var/lib/dpkg/status
     7.0.52-1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
--

No other changes happened on application level and we're unable to restore the state as from 05/07.

What other changes are applied with this upgrade which could cause these issues?

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Do you have any logs of the failure your application is getting?

Revision history for this message
Dieter Van Houtte (dietervanhoutte) wrote :

We're seeing a lot of ;

"java.lang.OutOfMemoryError" errors.

We're looking with the application developers to receive more information on this topic and we'll get back with more details on the errors later on.

Revision history for this message
Dieter Van Houtte (dietervanhoutte) wrote :

PS : we now have all services back online by doing system restores where 7.0.52-1ubuntu0.3 was still installed. On top of this, we've blacklisted tomcat in the unattended upgrades to avoid having the same issue till further notice.

Revision history for this message
Felix Ruiz de Arcaute (ruiz-felixruiz) wrote :

About restoring and blacklisting, the same situation here.

What log files would you need?

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Something that shows the failure you're experiencing. A reproducer would be ideal.

Revision history for this message
Dieter Van Houtte (dietervanhoutte) wrote :
Download full text (6.3 KiB)

"Caused by: java.lang.OutOfMemoryError: Java heap space" is something we see on different Tomcat application servers. Below a log example ;

Felix Ruiz : can you confirm the same behaviour?

--

06:40:05,828 ERROR [org.springframework.web.context.ContextLoader] Context initialization failed
org.alfresco.error.AlfrescoRuntimeException: 06060002 Reindex failure for org.alfresco.repo.node.index.FullIndexRecoveryComponent
 at org.alfresco.repo.node.index.AbstractReindexComponent.reindex(AbstractReindexComponent.java:315)
 at org.alfresco.repo.node.index.IndexRecoveryBootstrapBean.onBootstrap(IndexRecoveryBootstrapBean.java:37)
 at org.springframework.extensions.surf.util.AbstractLifecycleBean.onApplicationEvent(AbstractLifecycleBean.java:56)
 at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:97)
 at org.alfresco.repo.management.SafeApplicationEventMulticaster.multicastEvent(SafeApplicationEventMulticaster.java:78)
 at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:294)
 at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:858)
 at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:419)
 at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261)
 at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:192)
 at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
 at org.alfresco.web.app.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:63)
 at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5068)
 at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5584)
 at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
 at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:677)
 at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1962)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
Caused by: org.alfresco.error.AlfrescoRuntimeException: 06060001 Exception in Transaction.
 at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:466)
 at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:272)
 at org.alfresco.repo.node.index.AbstractReindexComponent.reindex(AbstractReindexComponent.java:306)
 ... 24 more
Caused by: java.lang.OutO...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tomcat7 (Ubuntu):
status: New → Confirmed
Revision history for this message
siloko (siloko1) wrote :

There is also a question related to path redirects which have been effected by this upgrade:

https://answers.launchpad.net/ubuntu/+source/tomcat7/+question/296145

Revision history for this message
Dieter Van Houtte (dietervanhoutte) wrote :

After further troubleshooting, we've discovered that the catalina.sh file has been changed upon the upgrade where some of our Java specific settings were configured (for example memory).

We will now use setenv.sh

Can someone confirm the catalina.sh has been adjusted upon the upgrade?
As understood from the https://tomcat.apache.org/tomcat-7.0-doc/RUNNING.txt documentation, it's better to have these settings set in the setenv.sh. Could someone confirm this as well and confirm this file won't be updated in the future?

Revision history for this message
Dieter Van Houtte (dietervanhoutte) wrote :

Could someone confirm the above statements who can lead to the resolution of this issue?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.