Your message dated Sun, 24 Sep 2006 22:57:42 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369368: postgresql: fails to upgrade because of missing 
configuration file
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: postgresql
Version: 7.5.19

I'm getting the following error after upgrading from stabel to testing:

Richte postgresql ein (7.5.19) ...
Configuring already existing cluster (configuration: 
/etc/postgresql/7.4/transition, data: /home/postgres/data/, owner: 111:109)
Moving configuration file /etc/postgresql/7.4/main/pg_hba.conf to 
/etc/postgresql/7.4/transition...
Moving configuration file /etc/postgresql/7.4/main/pg_ident.conf to 
/etc/postgresql/7.4/transition...
Moving configuration file /etc/postgresql/7.4/main/postgresql.conf to 
/etc/postgresql/7.4/transition...
Configuring postgresql.conf to use port 5433...
Adding custom settings from /etc/postgresql/postmaster.conf to 
/etc/postgresql/7.4/transition/environment...
Adding custom settings from /etc/postgresql/postgresql.env to 
/etc/postgresql/7.4/transition/environment...
The PostgreSQL server failed to start. Please check the log output:
FATAL:  could not open configuration file "/home/postgres/data/pg_hba.conf": No 
such file or directory
dpkg: Fehler beim Bearbeiten von postgresql (--configure):
 Unterprozess post-installation script gab den Fehlerwert 1 zurück

--

This is the file layout befor upgrade. It is from another PC but with the same 
layout of files and symlinks.
This PC is running under testing for quite some time with regular updates and 
no problems with postgresql transitions.
The installed version on this PC is also 7.5.19. The only differnce IMHO is 
that this PC was upgraded from stable to testing
quite some time ago while the other PC was upgraded from stable to testing last 
week.

--

Orion:/etc/postgresql/7.4# ls -l
insgesamt 4
drwxr-xr-x 2 root root 4096 2005-10-13 10:03 main

Orion:/etc/postgresql/7.4# ls -l main/
insgesamt 24
lrwxrwxrwx 1 root     root       46 2005-10-13 10:03 autovacuum_log -> 
/var/log/postgresql/pg_autovacuum-7.4-main.log
lrwxrwxrwx 1 root     root       43 2005-10-13 10:03 log -> 
/var/log/postgresql/postgresql-7.4-main.log
lrwxrwxrwx 1 root     root       19 2005-10-13 10:03 pgdata -> 
/home/postgres/data
-rw-r----- 1 postgres postgres 4986 2005-10-13 10:03 pg_hba.conf
-rw-r----- 1 postgres postgres 1441 2005-10-13 10:03 pg_ident.conf
-rw-r--r-- 1 postgres postgres 9085 2006-05-02 15:28 postgresql.conf

Orion:/etc/postgresql/7.4# ls -l /home/postgres/data/
insgesamt 24
drwx------ 10 postgres postgres 4096 2005-12-28 19:58 base
drwx------  2 postgres postgres 4096 2005-12-28 20:02 global
drwx------  2 postgres postgres 4096 2004-07-28 10:05 pg_clog
lrwxrwxrwx  1 postgres postgres   36 2005-10-13 10:03 pg_hba.conf -> 
/etc/postgresql/7.4/main/pg_hba.conf
lrwxrwxrwx  1 postgres postgres   38 2005-10-13 10:03 pg_ident.conf -> 
/etc/postgresql/7.4/main/pg_ident.conf
-rw-------  1 postgres postgres    4 2004-07-28 10:05 PG_VERSION
drwx------  2 postgres postgres 4096 2005-12-27 12:46 pg_xlog
lrwxrwxrwx  1 postgres postgres   40 2005-10-13 10:03 postgresql.conf -> 
/etc/postgresql/7.4/main/postgresql.conf
-rw-------  1 postgres postgres  115 2005-12-28 18:30 postmaster.opts

--

and this is the file layout after the incomplete upgrade:

--

gatekeeper:/home$ ls -l /etc/postgresql/7.4
insgesamt 12
drwxr-xr-x 2 root root 4096 2006-05-29 12:33 legacy
drwxr-xr-x 2 root root 4096 2006-05-29 12:33 main
drwxr-xr-x 2 root root 4096 2006-05-29 12:33 transition

gatekeeper:/home$ ls -l /etc/postgresql/7.4/legacy/
insgesamt 4
lrwxrwxrwx 1 root root  20 2006-05-29 12:33 pgdata -> /home/server/db_data
-rw-r--r-- 1 root root 378 2006-05-29 12:33 start.conf

gatekeeper:/home$ ls -l /etc/postgresql/7.4/main/
insgesamt 0
lrwxrwxrwx 1 root root 46 2006-05-24 15:14 autovacuum_log -> 
/var/log/postgresql/pg_autovacuum-7.4-main.log
lrwxrwxrwx 1 root root 43 2006-05-24 15:14 log -> 
/var/log/postgresql/postgresql-7.4-main.log
lrwxrwxrwx 1 root root 20 2006-05-24 15:14 pgdata -> /home/server/db_data

gatekeeper:/home$ ls -l /etc/postgresql/7.4/transition/
insgesamt 32
lrwxrwxrwx 1 root     root       52 2006-05-29 12:33 autovacuum_log -> 
/var/log/postgresql/pg_autovacuum-7.4-transition.log
-rw-r--r-- 1 root     root      316 2006-05-29 12:33 environment
lrwxrwxrwx 1 root     root       49 2006-05-29 12:33 log -> 
/var/log/postgresql/postgresql-7.4-transition.log
lrwxrwxrwx 1 root     root       20 2006-05-29 12:33 pgdata -> 
/home/server/db_data
-rw-r----- 1 postgres postgres 4957 2006-05-29 12:33 pg_hba.conf
-rw-r----- 1 postgres postgres 1441 2006-05-29 12:33 pg_ident.conf
-rw-r--r-- 1 postgres postgres 9085 2006-05-29 12:33 postgresql.conf
-rw-r--r-- 1 root     root      378 2006-05-29 12:33 start.conf

gatekeeper:/home$ ls -l /home/postgres/data/
insgesamt 24
drwx------ 18 postgres postgres 4096 2006-04-05 17:37 base
drwx------  2 postgres postgres 4096 2006-05-29 12:33 global
drwx------  2 postgres postgres 4096 2006-04-06 15:13 pg_clog
-rw-------  1 postgres postgres    4 2006-01-02 09:31 PG_VERSION
drwx------  2 postgres postgres 4096 2006-05-27 20:11 pg_xlog
-rw-------  1 postgres postgres  116 2006-05-29 12:33 postmaster.opts


Yours,

Andreas


--- End Message ---
--- Begin Message ---
Hallo Andreas,

Andreas Koch [2006-09-22 12:15 +0200]:
> > Do you have any further information about this bug? In the current
> > state there is nothing I can do about it.
> 
> No, sorry. I'm not able to reproduce the initial problem, since I don't 
> remember which upgrade did cause the problem and which was the inital state 
> of the system at that point (this was the first problem I had with an upgrade 
> so I normaly don't bother remembering what was done). 

OK, so I'm closing this bug since the only other thing that I could do
with it is to perpetual bitrotting. :/

Thank you for your report and your patience!

Martin

-- 
Martin Pitt        http://www.piware.de
Ubuntu Developer   http://www.ubuntu.com
Debian Developer   http://www.debian.org

In a world without walls and fences, who needs Windows and Gates?

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to