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,083
Community Members
 
Community Events
184
Community Groups

Crowd 2.7.0 won't start apache or the configurator. etchedit

Ok, started out with 10-user licenses for Confluence and JIRA. Now, Management is drooling and getting anxious to get 25user licenses except I took 2.6.2 apart to install Crowd and took out the entire system.

Prefer Solaris but stuck in a Windows-only place. Launched start_crowd.bat from a command tool with admin privs. I can only do screen shots at this point since it's not happy enough to start logging anything.

INFO: Deploying configuration descriptor C:\Program Files\Atlassian\atlassian-crowd-2.7.0\apache-tomcat\conf\Catalina\localhost\crowd.html

No Spring WebApplicationInitializer types detected on classpath

then

Unable to move C:\Program Files\Atlassian\atlassian-crowd-2.7.0\crowd.cfg.xml7724346764409221781tmp to c:\Program Files\atlassian\atlassian-crowd-2.7.0\crowd.cfg.xml

Something is running in the background. But, Apache is clearly not working.

2 answers

0 votes
Caspar Krieger
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 27, 2013

Glad you got it sorted; my guess would have been that the process may not have had write permissions to the directory.. but launching it as an admin should have worked around that. Anyway, next time you run into a "I give up, who knows what's going on" blocker like this, please feel free to raise a support request (especially if it's caused your system to be down!).

*rubs eyes* ok, now configurator is talking. Wish I had a better reason why than I left it running overnight.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events