Trying to start PostgresSQL server failed - While Upgrading
Error Trace.
Trying to start PostgresSQL server failed java.net.ConnectException: Trying to start PostgresSQL server failed at com.adventnet.db.adapter.postgres.DefaultPostgresDBInitializer.startDBServer(DefaultPostgresDBInitializer.java:177) at com.adventnet.db.adapter.postgres.PostgresDBAdapter.startAndCheckDBServer(PostgresDBAdapter.java:781)
Trouble Shooting:
-> Path to the (application folder / bin) and execute ChangeDBserver and Save the configurations
-> Execute InitPGSQL.bat
-> Start stop the application once.
Make sure the Application is stopped, and no PGSQL or Java programs are running behind.
Now initiate the upgrade again.
If the upgrade still fails, please share the logs for further analysis.
New to ADSelfService Plus?
Related Articles
Upgrade failure - Trying to start PostgresSQL server failed
Traces within the logs: [SYSERR] [INFO] : java.lang.Exception: java.net.ConnectException: Trying to start PostgresSQL server failed Please follow the steps below to address the same : 1. Stop the ServiceDesk Plus MSP service. 2. Open the command ...solution for postgres 11 upgrade issues
When Supportcenter Plus is upgraded to 14300 or later, postgres is also upgraded to 11.17. If you are using bundled postgres, data migration through pgdump and restore mechanism also happens. To ensure efficiency in Postgres 11.17, make sure your ...SDP MSP solution for postgres 11 upgrade issues
When ServiceDesk Plus MSP is upgraded to 14300 or later, postgres is also upgraded to 11.17. If you are using bundled postgres, data migration through pgdump and restore mechanism also happens. To ensure efficiency in Postgres 11.17, make sure your ...su: cannot open session: Module is unknown
The upgrade issue arises in several linux editions such as RHEL and CentOS when the bundled postgres database needs to be upgraded in that particular patch and the upgrade is triggered by the root user. The highlighted line in the traces below (su: ...Upgrade Failure due to the presence of CtrlZ Failure
This issue (SD-118352) in fixed in version 14710. Post this release, these characters are handled in the migration itself. If you are planning to migrate from version less than 14610 to 14610, then you can directly migrate to 14710, to handle this ...