Hi Martin,

> This indeed looks severely wrecked. It looks like you attempted the
> upgrade three times (first it created the 'main' cluster, then
> 'legacy', then 'transition'), and all three failed at some point. Now
> 'main' and 'legacy' are bogus clusters and 'transition' actually looks
> good, but the symlinks in /home/postgres/data/ to the configuration
> files in /etc/postgresql/7.4/transition/ are missing (please add them
> to get it working again).
>
> Can you please describe me how you attempted the first upgrade and
> what failed? Any recipe for reproducing this?

As far as I remember I made an dist-upgrade from stable to etch and 
ended up with the problem describted. I fixed the data structure from
hand and started apt-get upgrade again ending with the same result. 
Since the only error message I got was from apt that something had failed 
and the only evidence was the broken data structure I have no Idear what 
caused this. Since then I have not done any upgrade. After your message 
I tryed another run today. The upgrade still don't work but the data structure
was untouched this time:

gatekeeper:/home/andreas# date
Mo Jul  3 09:35:39 CEST 2006
[EMAIL PROTECTED]:/etc/postgresql/7.4$ ls
main
[EMAIL PROTECTED]:/etc/postgresql/7.4$ ls -lh main/
insgesamt 32K
lrwxrwxrwx 1 root        root           52 2006-06-07 17:21 autovacuum_log -> 
/var/log/postgresql/pg_autovacuum-7.4-transition.log
-rw-r--r-- 1      root        root         316 2006-06-07 17:21 environment
lrwxrwxrwx 1 root        root           49 2006-06-07 17:21 log -> 
/var/log/postgresql/postgresql-7.4-transition.log
lrwxrwxrwx 1 root        root           20 2006-06-07 17:21 pgdata -> 
/home/server/db_data
-rw-r----- 1      postgres postgres 4,9K 2006-06-07 17:21 pg_hba.conf
-rw-r----- 1      postgres postgres 1,5K 2006-06-07 17:21 pg_ident.conf
-rw-r--r-- 1      postgres postgres 8,9K 2006-06-07 18:38 postgresql.conf
-rw-r--r-- 1      root        root         378 2006-06-07 17:21 start.conf

gatekeeper:/etc/postgresql/7.4# apt-get update
gatekeeper:/etc/postgresql/7.4# apt-get dist-upgrade
[...]
The following packages will be upgraded:
  [...] postgresql-client-common postgresql-common [...]
144 upgraded, 10 newly installed, 1 to remove and 3 not upgraded.
1 not fully installed or removed. // <--- postgresql from last attempt
Need to get 80.6MB of archives.
After unpacking 3465kB disk space will be freed.
Do you want to continue [Y/n]? Y
[...]
Preparing to replace postgresql-client-common 53 (using 
.../postgresql-client-common_55_all.deb) ...
Unpacking replacement postgresql-client-common ...
Preparing to replace postgresql-common 53 (using 
.../postgresql-common_55_all.deb) ...
Unpacking replacement postgresql-common ...
[...]
Setting up postgresql (7.5.19) ...
dpkg: error processing postgresql (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 postgresql
gatekeeper:/etc/postgresql/7.4# ls -lh
total 4.0K
drwxr-xr-x 2 root root 4.0K Jun  7 18:38 main

Is there a way to find out why the post-installation script returned
with an error ?
Can I put some debug lines into /var/lib/dpkg/info/postgresql.postinst
and run it by hand ? (what parameters ?)

Yours,

Andreas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to