Martin Pitt wrote:
>Hi Jeff!
>
>Jeff Williams [2005-06-20 12:03 +0200]:
>
>
>>Package: postgresql
>>Version: 7.5.6
>>Severity: normal
>>
>>
>>My postgresql.conf seems to have been lost on the transition to 7.5. I'm
>>pretty sure I had the default postgresql.conf in /etc/postgresql/ but
>>after the transition the file /etc/postgresql/7.4/main/postgresql.conf
>>(which I assume should be the same file) was empty. As a result the
>>server stopped listening for tcp/ip connections.
>>
>>
>
>Can you still reproduce/see the exact output of the package
>installation process by any change? Did it succeed?
>
>
I can't still see the output as I did the upgrade on Saturday after
being away for two weeks. But thinking back, I remember that the upgrade
of postgresql failed. But I'm pretty sure it gave the message:
"Not migrating invalid PostgreSQL data directory /usr/lib/postgres/data
(no PG_VERSION)."
Which I ignored at the time thinking I could fix it later if necessary.
I just re-ran "apt-get upgrade" and it then ran to completion. I didn't
notice anything until today when I could not access the database via tcp/ip.
>
>
>>The only cause I can think of is that my disk usage has been pushing the
>>100% mark and maybe it filled up?
>>
>>
>
>Hmm, can you please check for this? Look at the output of "df".
>
>
There is plenty of room now since I ran "apt-get clean" to get some
space back. However, just after the upgrade I shut down the computer and
later had problems on restart due to a lack of space.
>Actually the package installation is supposed to fail if the file
>cannot be installed, and leave the original file where it is. I'll try
>to reproduce this condition and introduce additional checks. In the
>meantime, you can create an additional dummy 7.4 cluster, copy its
>postgresql.conf and remove the dummy 7.4 cluster again:
>
> pg_createcluster 7.4 dummy
> cp /etc/postgresql/7.4/{dummy,main}/postgresql.con
> pg_dropcluster 7.4
> /etc/init.d/postgresql-7.4 restart
>
>
I just copied /usr/share/postgresql/7.4/postgresql.conf.sample to
/etc/postgresql/7.4/main/postgresql.conf which I assume does more or
less the same thing.
Interesting thing though, this morning when I couldn't access postgres
over tcp/ip, I remembered that it failed first on update. So I ran
"apt-get install --reinstall postgresql" to see if it gave the error
again, which it did not. However, it appears that stuff from the
postinst script was run which previously hadn't been. For example the
file /etc/init.d/postgresql existed until after the reinstall. I
remember being confused as to why "/etc/init.d/postgresql restart"
didn't work before the reinstall and why the file wasn't there afterwards.
Sorry about being so vauge, but everything seemed to work after the
second "apt-get upgrade" on Saturday so I didn't take much notice at the
time.
Jeff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
