Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

crowd upgrade on linux fails

We unsuccessfully attempted to upgrade crowd to 2.7.2

I feel like we followed the instructions carefully, and tailing the apache-tomcat.catalina.out log file, it shows it coming up (eventually) - but we cannot access on port 8080

I'm very new to Atlassian, so I'm not sure the best way to ask this question.

here is the server.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<Server port="8020" shutdown="SHUTDOWN">

<Service name="Catalina">

<Connector acceptCount="100" connectionTimeout="20000"
disableUploadTimeout="true" enableLookups="false"
maxHttpHeaderSize="8192" maxThreads="150"
minSpareThreads="25" port="8095" redirectPort="8080"
useBodyEncodingForURI="true" URIEncoding="UTF-8"/>

<Engine defaultHost="localhost" name="Catalina">
<Host appBase="webapps" autoDeploy="true" name="localhost" unpackWARs="true"/>

<!-- To connect to an external web server (typically Apache) -->
<!-- Define an AJP 1.3 Connector on port 8009 -->
<Connector port="8080"
scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" SSLEnabled="true"
keystoreFile="/opt/data/aviva/ssl/.keystore" keystorePass="hmpssl" />


<!-- Security listener. Documentation at /docs/config/listeners.html
<Listener className="" />
<!--APR library loader. Documentation at /docs/apr.html -->
<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
<!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
<Listener className="org.apache.catalina.core.JasperListener" />
<!-- Prevent memory leaks due to use of particular java/javax APIs-->
<Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
<Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />


What else can I show you that might help solve this?

4 answers

Is the port blocked on linux? Maybe stop iptables if it is running and check after that? Another thing is to check if selinux is enabled or not.

Thank you for your quick response -

Port is not blocked - when we 'roll back' to the previous version (2.4 I think) by renaming the folder, we can get in just fine to that port.

Are you using a proxyName? What happens when you do wget on localhost:8080/crowd from the server itself?

I've opened a ticket with Atlassian support on this - once there is a resolution, I will post it here. Possibly with a better description of the problem.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Statuspage

New feature: Slack notifications for Statuspage

We're excited to announce the release of a long-requested feature on Statuspage. Now visitors to your status page can subscribe to get notified in Slack when you report an incident or maintenance. Th...

67 views 0 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you