Posted: 29 Aug 2018 10:00 EDT Last activity: 30 Aug 2018 9:12 EDT
install.sh timout during rule migration
Hello, Pega community -
I wonder if anyone has seen this, and can perhaps help.
We're trying to install the Pega platform for a customer.
We've got two redhat linux VMs on a VMWare stack, and in fact they're on the same host. One is the app server (on which we've installed Tomcat and oracle jre 8), the other a postgres db server.
(can supply more system details if required)
We've set jdbc connection parameters in the setupDatabase.properties files, and initiated the install.sh script.
This duly creates all of the tables and such, and then begins what looks like a series of bulk imports of the rule database.
It gets to step "54 of 100" and stops with a big stack trace, at the top of which is a line indicating some sort of time out.
Now, at the end of the "setupDatabase.properties" file is a mysterious setting:
"automatic.resume=true" ...that indicates that, if you run the script again, it should resume at the point of failure.
This doesn't work, though. Running the script again stops immediately, because it's trying to create all the tables again, and those objects already exist from the prior run.
So: Is there a way to indicate to install.sh that it should skip table creation (and whatever other intermediate steps there may be) and go right to the rule database import, starting at the place where it previously failed?
***Edited by Moderator Marissa to update platform capability tags****
As an update, if anyone else encounters this: my postgres dba adjusted timeout settings on the postgres db server side, which seems to have resolved this specific issue. I believe there's a setting in the postgres config file that he set to disable timeouts completely.