Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1450906

Summary: tomcat failed with: One or more listeners failed to start
Product: [Community] Spacewalk Reporter: sgux
Component: InstallationAssignee: Jan Dobes <jdobes>
Status: CLOSED WORKSFORME QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.6CC: jhutar, satqe-list, sheepdestroyer, user_cco
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-28 07:19:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1484117    
Attachments:
Description Flags
catalina.<date>.out and localhost.<date>.log none

Description sgux 2017-05-15 11:33:57 UTC
Created attachment 1278929 [details]
catalina.<date>.out and localhost.<date>.log

Description of problem:
There are critical failure after spacewalk-setup in /var/log/tomcat/catalina.*.log and /var/log/tomcat/localhost.*.log after setup and on restart of spacewalk-services

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 7.3 (Maipo)
spacewalk-postgresql-2.6.1-1 (spacewalk with embedded postgresql)
postgresql-9.2.18-1
c3p0-0.9.2.1-5

output:
java -cp /usr/share/java/tomcat/catalina.jar org.apache.catalina.util.ServerInfo
Server version: Apache Tomcat/7.0.69
Server built:   Mar 29 2017 12:27:41 UTC
Server number:  7.0.69.0
OS Name:        Linux
OS Version:     3.10.0-514.16.1.el7.x86_64
Architecture:   amd64
JVM Version:    1.7.0_131-mockbuild_2017_02_07_02_14-b00
JVM Vendor:     Oracle Corporation

How reproducible:
reproducible after fresh install

Steps to Reproduce:
(1. failure solved: Don't found c3p0.jar --> create a link:
ln -s /usr/share/java/c3p0/c3p0.jar /usr/share/java/c3p0.jar)


Actual results:
spacewalk Web-UI --> blank page

Expected results:


Additional info:

Comment 1 user_cco 2017-06-14 12:40:11 UTC
Same behaviour using centos 7.3 1611
(sames version for spacewalk / c3p0 / tomcat with java 7 or java 8)

There is no web access to spacewalk, i guess you can set Severity to "blocking production"

Comment 2 sgux 2017-06-20 10:37:57 UTC
If you need some additional information, please write a comment or a mail

Comment 3 sgux 2017-07-28 07:19:02 UTC
I'm sorry.
We don't use RHEL7 any more because we need the new spacewalk running. There was an additional problem with "Optional-Repo" and cglib2.2
Now we use RHEL6.9 and it works.

Comment 4 user_cco 2017-08-04 09:11:43 UTC
here is a work around :

update the centos machine to last version then :
- spacewalk-service stop
-  yum downgrade c3p0
   ...
   removed:
      c3p0.noarch 0:0.9.2.1-6.el7

   installed:
     c3p0.noarch 0:0.9.1.2-2.jpp5
    ...
- cd /usr/share/tomcat/webapps/rhn/WEB-INF/lib
  ls -l c3p0.jar
  c3p0.jar -> /usr/share/java/c3p0.jar
- yum versionlock cglib (if not already lock, normally it does)
- yum versionlock c3p0
- spacewalk-service restart

at this step the web interface of spacewalk is normally fully functional.

(this procedure have been tested over an already installed server an d un new one installed from scratch)

Comment 5 Jan Hutař 2017-08-10 13:08:05 UTC
I do not se any question associated with needinfo request, so assume it was raised in error.

Comment 6 sheepdestroyer 2017-08-24 09:17:27 UTC
Why was this bug closed?

The workaround is to stop updating two packages? 
Either spacewalk needs to be fixed, or cglib and c3p0 from epel need to.

I encounter the same bug on centos 7.3

Comment 7 Jan Hutař 2017-08-24 11:28:33 UTC
Hello. It was closed by the reporter - see comment #3 for his reasoning. Feel free to reopen or create new bug with clean/fresh info please.

Comment 8 Eric Herget 2017-09-28 18:05:57 UTC
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.