I've wriiten some terraform that deploys an AWS ELB, EC2 and RDS database for CROWD. Whilst it completes end-to-end, it doesn't squirt in my specfic database parameters, although it does create the RDS instance and implement the schema. I have to manually click on 'set up' on the splash page, and put the licence in and the URL/Port, etc. My terraform creates a crowd.cfg.xml and puts it in place so i expected it to pick all this info up from there, without me having to maunually input the info. Help!!!!!
Hi @Naveed Ashraf,
You've mentioned that your automation creates the schema, does it also populate the database from backup? I believe the issue may be that your database is there, but it is empty.
Additionally what is the contents of your crowd.cfg.xml I mean properties like:
<application-configuration>
<setupStep>complete</setupStep>
<setupType>install.new</setupType>
<buildNumber>892</buildNumber>
since Crowd 3.0.0 crowd.cfg.xml should be placed in {crowd-home}/shared
Hope that helps,
Marcin Kempa
hi Marcin
we do have those details in our crowd.cfg.xml. We put 917 for the build number as we are using 3.2.0., and we have it in the {crowd home}/shared directory.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
also it doesn't populate the database as it is a 'greenfield' installation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Naveed Ashraf Cloud you try to restore the backup first in the database before starting Crowd?
Crowd assumes that there is some data like Crowd application in the database and it won't recreate this on startup.
Best Regards
Marcin Kempa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
looks like it's duplicate question ; though posting the answer if someone follow's this thread instead.
Hi @Naveed Ashraf @Marcin Kempa /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 !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.