Pastebin

Paste #2336: pg upgrade clusters

< previous paste - next paste>

Pasted by tdn

Download View as text

(postgres@syrah) (12-03-26 14:55) (P:0 L:1) [0]
~ $ pg_dropcluster --stop 8.4 main                                                                                               [pts/1 - 10H 0J 0R - 2012-03-26 14:55:42 - 0+00:15 - 0.02 0.13 0.08]
(postgres@syrah) (12-03-26 15:01) (P:0 L:1) [0]
~ $ pg_upgradecluster 8.3 main                                                                                                   [pts/1 - 11H 0J 0R - 2012-03-26 15:01:47 - 0+00:21 - 0.00 0.03 0.04]
Stopping old cluster...
Disabling connections to the old cluster during upgrade...
Restarting old cluster with restricted connections...

Could not connect to database

Could not connect to database

Could not connect to database
Creating new cluster (configuration: /etc/postgresql/8.4/main, data: /var/lib/postgresql/8.4/main)...

Could not connect to database

Could not connect to database

Could not connect to database

Could not connect to database
Moving configuration file /var/lib/postgresql/8.4/main/postgresql.conf to /etc/postgresql/8.4/main...

Could not connect to database

Could not connect to database
Moving configuration file /var/lib/postgresql/8.4/main/pg_hba.conf to /etc/postgresql/8.4/main...

Could not connect to database

Could not connect to database
Moving configuration file /var/lib/postgresql/8.4/main/pg_ident.conf to /etc/postgresql/8.4/main...

Could not connect to database

Could not connect to database

Could not connect to database
Configuring postgresql.conf to use port 5433...

Could not connect to database

Could not connect to database
Disabling connections to the new cluster during upgrade...

Could not connect to database

Could not connect to database
Roles, databases, schemas, ACLs...

[....]

Fixing hardcoded library paths for stored procedures...
Upgrading database mailbigfile...
Analyzing database mailbigfile...
Fixing hardcoded library paths for stored procedures...
Upgrading database uptimetracker...
Analyzing database uptimetracker...
Fixing hardcoded library paths for stored procedures...
Upgrading database tdndev...
Analyzing database tdndev...
Fixing hardcoded library paths for stored procedures...
Upgrading database shorturl...
Analyzing database shorturl...
Fixing hardcoded library paths for stored procedures...
Upgrading database bcap...
Analyzing database bcap...
Fixing hardcoded library paths for stored procedures...
Upgrading database template1...
Analyzing database template1...
Re-enabling connections to the old cluster...
Re-enabling connections to the new cluster...
Copying old configuration files...

Could not connect to database

Could not connect to database

Could not connect to database

Could not connect to database

Could not connect to database

Could not connect to database
Copying old start.conf...

Could not connect to database

Could not connect to database
Stopping target cluster...
Stopping old cluster...
Disabling automatic startup of old cluster...
Configuring old cluster to use a different port (5433)...
Starting target cluster on the original port...
The PostgreSQL server failed to start. Please check the log output:
2012-03-26 15:02:25 CEST LOG:  hostssl requires SSL to be turned on
2012-03-26 15:02:25 CEST HINT:  Set ssl = on in postgresql.conf.
2012-03-26 15:02:25 CEST CONTEXT:  line 12 of configuration file "/etc/postgresql/8.4/main/pg_hba.conf"
2012-03-26 15:02:25 CEST FATAL:  could not load pg_hba.conf
Error: Could not start target cluster; please check configuration and log files

New Paste


Do not write anything in this field if you're a human.

Go to most recent paste.