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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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

Error on start up



We are trying to migrate crowd from an old server running CentOS6 to a new server running Oracle Linux. Here is what I did:

1) Stopped crowd on current server.

2) Copied over the application and data directories to the new server.

3) Dumped the database and imported it to the new server.

4) Updated the configs on the server to reflect the new DB and server name.


When I start the crowd application on the new server I get an error of:

2021-06-06 20:22:54fatalCrowd has encountered errors while upgrading. Please resolve these errors and restart Crowd.

An error occurred when querying the database <ERROR: relation "REMOTEGROUP" does not exist Position: 26 Location: File: parse_relation.c, Routine: parserOpenTable, Line: 1160 Server SQLState: 42P01>



I am not doing an upgrade. I am merely moving it from one server to another. Any idea what I can be doing wrong?

1 answer

0 votes
Craig Castle-Mead
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jul 19, 2021

Hey @Dovid Bender 

It looks like you may be seeing this issue -

Follow the Resolution steps from above and see if that helps


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events