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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,559,126
Community Members
 
Community Events
184
Community Groups

crowd version 3.2 not starting

Description .... Crowd has encountered errors while upgrading. Please resolve these errors and restart Crowd.

Exception ..... Could not find application to update: crowd

terraform provisions and configs crowd install but throws the above exception. Not sure why it says upgrading when it is a straight install. 

Also this from the catalina.out

2018-05-03 13:30:32,230 localhost-startStop-1 INFO [atlassian.crowd.config.CrowdApplicationConfig] Using config directory : /var/atlassian/application-data/crowd/shared
2018-05-03 13:30:32,231 localhost-startStop-1 INFO [crowd.manager.upgrade.UpgradeManagerImpl] Clearing caches after upgrade
2018-05-03 13:30:32,233 localhost-startStop-1 ERROR [crowd.console.listener.StartupListener] Errors experienced during the Crowd upgrade process: [Could not find application to update: crowd]
2018-05-03 13:30:32,233 localhost-startStop-1 INFO [com.atlassian.crowd.startup] System Information:
2018-05-03 13:30:32,234 localhost-startStop-1 INFO [com.atlassian.crowd.startup] Timezone: Greenwich Mean Time
2018-05-03 13:30:32,234 localhost-startStop-1 INFO [com.atlassian.crowd.startup] Java Version: 1.8.0_171
2018-05-03 13:30:32,234 localhost-startStop-1 INFO [com.atlassian.crowd.startup] Java Vendor: Oracle Corporation
2018-05-03 13:30:32,234 localhost-startStop-1 INFO [com.atlassian.crowd.startup] JVM Version: 25.171-b10

 

Any help, very gratefully received.

2 answers

Hi @Naveed Ashraf /anyone still looking for answer on this :

Just delete the "crowd.cfg.xml" present in your "crowd_home/shared" directory and restart crowd ; it should solve the issue posted in this thread.

So basically it would take you to /setup step and "crowd.cfg.xml" gets regenerated automatically when you follow the setup steps.

hope it helps , Thanks !

0 votes
Marcin Kempa
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 09, 2018

Hi @Naveed Ashraf,

 

This error is thrown during the upgrade process and this particular upgrade task is a fairly old one. Which version of Crowd are you upgrading from?

 

Best Regards,

Marcin Kempa

Hi Marcin

We're actually trying to stand up crowd 3.2 from scratch so there should be no upgrade as it is a new install. That's why we can't figure out why it's trying to do an upgrade. We are using terraform to manage the deployment. Any help, gratefully received.

Marcin Kempa
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 09, 2018

That's interesting, maybe your crowd.cfg.xml is pointing to an old database?

so below is my crowd.cfg.xml

The build number doesn't update to 971 although that's what it shows on the splash screen but when you click on the setup crowd button, you get 

Bootstrap error

TimeLevelDescriptionException

2018-05-09 14:46:24fatalCrowd has encountered errors while upgrading. Please resolve these errors and restart Crowd.Could not find application to update: crowd

 

<?xml version="1.0" encoding="UTF-8"?>

<application-configuration>
<setupStep>complete</setupStep>
<setupType>install.new</setupType>
<buildNumber>0</buildNumber>
<properties>
<property name="crowd.server.id">BO4C-XXXX-XXXX-BSR2</property>
<property name="hibernate.c3p0.acquire_increment">1</property>
<property name="hibernate.c3p0.idle_test_period">100</property>
<property name="hibernate.c3p0.max_size">30</property>
<property name="hibernate.c3p0.max_statements">0</property>
<property name="hibernate.c3p0.min_size">0</property>
<property name="hibernate.c3p0.timeout">30</property>
<property name="hibernate.connection.driver_class">com.mysql.jdbc.Driver</property>
<property name="hibernate.connection.password">xxxxxxxxxx</property>
<property name="hibernate.connection.url">jdbc:mysql://AWSRDSURL.com:3306/crowd?autoReconnect=true&amp;characterEncoding=utf8&amp;useUnicode=true&amp;useSSL=false&amp;rewriteBatchedStatements=true</property>
<property name="hibernate.connection.username">crowd</property>
<property name="hibernate.dialect">org.hibernate.dialect.MySQL5InnoDBDialect</property>
<property name="hibernate.setup">true</property>
<property name="license">AAABOQ0ODAoPeNqFkEtvgzAQhO/+FUi9tAcjQIQ8JEttDEojQYgCfRx6cekmsUpMtDa0+feFQNWHKvXgy87u55m5yGuwEnGynInljGd+MPOnFg9zy3PcCQlBFyiPRlaXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXRqA9kzvUWyv9wcs7J2W9q5q7Pp1YGZGoAFkW1FqGGaxLEBpyE9HOHN4miTRhi9v4k98lAhZ/sP/st87LnvqPaDuZh5pGcqAEqqA6P0o8fQtS0CdMUlxJ5TUPeM22fC2uAXpC1qGbJ76nI7mi0f64AdrOs82HsmiFWsfjV03GHujaTBEWtWHZ8B0e6fb7xl1yZCxxcTL8OfFIP3taV1jsRcafvf+ARd9n3EwLAIUNnCmGCtKzWi00nlGbZ0QlbfKPeoCFBk3O283JV2lUKjCQB1S5l3mKa/IX02fj</property>
</properties>
</application-configuration>

Marcin Kempa
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 09, 2018

So I assume that this question is related to the one you posted here,

The database schema is probably setup, what about the data in that database I think that you should restore the backup in that database first in order to do this kind of setup? Right now Crowd assumes that this is an upgrade as the database config is there and  also the crowd.cfg.xml indicates that the install is complete hence it tries to lookup for the data in database.

 

Hope that helps,

Marcin Kempa

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events