Bug 473755 - missing symlinks after update f9->f10 (postinstall problem?)
Summary: missing symlinks after update f9->f10 (postinstall problem?)
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: tomcat5
Version: 10
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Devrim Gündüz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-30 09:44 UTC by Maurizio Paolini
Modified: 2009-04-20 22:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-11 08:04:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Maurizio Paolini 2008-11-30 09:44:13 UTC
Description of problem:

Missing essential symlinks when updating from tomcat5-5.5.27-0jpp.2.fc9.i386
to tomcat5-5.5.27-4.9.fc10.noarch

Version-Release number of selected component (if applicable):

tomcat5 5.5.27-4.9

How reproducible:

Upgrade a fedora 9 with updated packages to fedora 10

Steps to Reproduce:
1. start from fedora 9 with tomcat5 from fedora-updates
2. upgrade to fedora 10
3. (in particular update tomcat5 to indicated version
  
Actual results:

"/etc/init.d/tomcat5 start" does not start tomcat5

Expected results:

"/etc/init.d/tomcat5 start" should start a java process which it
doesn't

Additional info:

This seems a problem in the postinstall script of the new rpm

Comment 1 Christoph Breitkopf 2008-12-02 17:33:50 UTC
Same thing happed to me today after update via preupgrade.

Tomcat won't start. Catalina.log shows that commons-logging is not found:

Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
	at org.apache.catalina.startup.Bootstrap.<clinit>(Bootstrap.java:54)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory
	at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:323)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:268)
	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:336)
	... 1 more
Could not find the main class: org.apache.catalina.startup.Bootstrap. Program will exit.

Comment 2 Fedora Update System 2008-12-10 19:01:35 UTC
tomcat5-5.5.27-6.1.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/tomcat5-5.5.27-6.1.fc10

Comment 3 Fedora Update System 2008-12-11 08:04:13 UTC
tomcat5-5.5.27-6.1.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 4 Thomas Schweikle 2009-04-20 22:09:38 UTC
Problem still persists:
upgraded from Fedora 9 to Fedora 10 today, after all tomcat5 did not start anymore. Error message (from catalina.out):

Using CATALINA_BASE:   /usr/share/tomcat5
Using CATALINA_HOME:   /usr/share/tomcat5
Using CATALINA_TMPDIR: /usr/share/tomcat5/temp
Using JRE_HOME:       
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
	at org.apache.catalina.startup.Bootstrap.<clinit>(Bootstrap.java:54)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory
	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
	... 1 more

In /usr/share/tomcat5/common/lib I could find:
[commons-collections-tomcat5].jar ->
   /usr/share/java/commons-collections-tomcat5.jar
[commons-dbcp-tomcat5].jar ->
   /usr/share/java/commons-dbcp-tomcat5.jar
[commons-el].jar ->
   /usr/share/java/commons-el.jar
[commons-pool-tomcat5].jar ->
   /usr/share/java/commons-pool-tomcat5.jar
[ecj].jar ->
   /usr/share/java/ecj.jar
[jaf].jar ->
   /usr/share/java/jaf.jar
[jasper5-compiler].jar ->
   /usr/share/java/jasper5-compiler.jar
[jasper5-runtime].jar ->
   /usr/share/java/jasper5-runtime.jar
[javamail].jar ->
   /usr/share/java/javamail.jar
[jsp].jar ->
   /usr/share/java/jsp.jar
[servlet].jar ->
   /usr/share/java/servlet.jar
[tomcat5][naming-factory].jar ->
   /usr/share/java/tomcat5/naming-factory.jar
[tomcat5][naming-resources].jar ->
   /usr/share/java/tomcat5/naming-resources.jar

All links dated from Apr. 20, 2008 19:21 --- the date the System was set up. No links where created, but some destroied (think these where those the target changed).

Comment 5 Thomas Schweikle 2009-04-20 22:22:40 UTC
I could solve the problem by removing all tomcat related packages, then reinstalling them. Looks like some postinstall script does not find what it expects while upgrading ... !


Note You need to log in before you can comment on or make changes to this bug.