[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: probable broken tomcat6 package on wheezy



On 12/17/2016 07:40 AM, John Naggets wrote:
> Hi,
>
> Since today the tomcat6 package on Debian 7.11 seems to be broken as
> the tomcat6 service does not start anymore. Here is the relevant
> output of catalina.out:
>
> Dec 17, 2016 6:35:15 AM org.apache.catalina.startup.ClassLoaderFactory
> validateFile
> WARNING: Problem with directory [/usr/share/tomcat6/server/classes],
> exists: [false], isDirectory: [false], canRead: [false]
> Dec 17, 2016 6:35:15 AM org.apache.catalina.startup.ClassLoaderFactory
> validateFile
> WARNING: Problem with directory [/usr/share/tomcat6/server], exists:
> [false], isDirectory: [false], canRead: [false]
> Dec 17, 2016 6:35:15 AM org.apache.catalina.startup.ClassLoaderFactory
> validateFile
> WARNING: Problem with directory [/usr/share/tomcat6/shared/classes],
> exists: [false], isDirectory: [false], canRead: [false]
> Dec 17, 2016 6:35:15 AM org.apache.catalina.startup.ClassLoaderFactory
> validateFile
> WARNING: Problem with directory [/usr/share/tomcat6/shared], exists:
> [false], isDirectory: [false], canRead: [false]
> Dec 17, 2016 6:35:16 AM org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on http-8080
> Dec 17, 2016 6:35:16 AM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 438 ms
> java.lang.reflect.InvocationTargetException
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:606)
>     at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
>     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
> Caused by: java.lang.ExceptionInInitializerError
>     at org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingContextListener.java:262)
>     at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
>     at org.apache.catalina.core.StandardServer.start(StandardServer.java:752)
>     at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
>     ... 6 more
> Caused by: java.util.MissingResourceException: Can't find bundle for
> base name org.apache.naming.factory.LocalStrings, locale en_US
>     at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1499)
>     at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1322)
>     at java.util.ResourceBundle.getBundle(ResourceBundle.java:721)
>     at org.apache.naming.StringManager.<init>(StringManager.java:68)
>     at org.apache.naming.StringManager.getManager(StringManager.java:213)
>     at org.apache.naming.factory.ResourceLinkFactory.<clinit>(ResourceLinkFactory.java:44)
>     ... 10 more
>
> Using the following tomcat:
>
> $ dpkg -l|grep tomcat
> ii  libtomcat6-java                    6.0.45+dfsg-1~deb7u4
> all          Servlet and JSP engine -- core libraries
> ii  tomcat6                            6.0.45+dfsg-1~deb7u4
> all          Servlet and JSP engine
> ii  tomcat6-common                     6.0.45+dfsg-1~deb7u4
> all          Servlet and JSP engine -- common files
>
> and JRE:
>
> dpkg -l|grep jre
> ii  default-jre-headless               1:1.7-47+deb7u2
> amd64        Standard Java or Java compatible Runtime (headless)
> ii  openjdk-7-jre-headless:amd64       7u111-2.6.7-2~deb7u1
> amd64        OpenJDK Java runtime, using Hotspot JIT (headless)
>
> The following package updates have been performed this early morning
> and I suspect one of these following packages to be broken:
>
> libicu-dev libicu48 libservlet2.5-java libtomcat6-java  tomcat6
> tomcat6-admin tomcat6-common
>
> Any ideas? I can't find anything yet on any debian mailing lists...
>
> Best regards
> H.N.
>

Hi,
As a temporary workaround disable the unattended-upgrades, and
try to install the previous version from /var/cache/apt/archives.
It solved the problem for me. ( of course if you don't clean the apt
archives )

Best,
Alex




Reply to: