How to expose details from a Postgres startup failure?
Article ID: KB0077072
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | All supported versions |
Description
Scenario:
The Postgres service will not start. This may be concluded either from witnessing a startup failure from a console, or in the TDV server log's failed bootup routine that shows that the server was unable to connect to an active Repository service.
The Postgres service will not start. This may be concluded either from witnessing a startup failure from a console, or in the TDV server log's failed bootup routine that shows that the server was unable to connect to an active Repository service.
Issue/Introduction
This concerns the use of TIBCO Data Virtualization's (TDV) Postgres meta-db platform (aka the Repository).
Resolution
If there is nothing logged in our /logs/cs_repository-<day of the week>.log, you can then attempt to start the Postgres service from the command line.
Run this command to start Postgres in a foreground mode:
<install dir>/repository/bin/postgres -D <path of TDV install dir>/repository/data
Any systemic issues can potentially be displayed in this foreground session. A successful start will simply leave the cursor hanging in the foreground, requiring you to use a "Ctrl-C" (Control-c)to stop the running Postgres processes.
Run this command to start Postgres in a foreground mode:
<install dir>/repository/bin/postgres -D <path of TDV install dir>/repository/data
Any systemic issues can potentially be displayed in this foreground session. A successful start will simply leave the cursor hanging in the foreground, requiring you to use a "Ctrl-C" (Control-c)to stop the running Postgres processes.
Feedback
Yes
No
Powered by
