Thread: Have problems with 7.1 -> 7.2 upgrade
I'm having problems upgrading from 7.1 to 7.2. I'm using a Debian package,
which says to run:
su - postgres
postgresql-dump -t db.out -dcivlp $PGDATA/../data.save
When I run this, I get the following:
$ postgresql-dump -t /billing/dump_database/db.out -dcivlp
$PGDATA/../data.save
Stopping and restarting the postmaster
/usr/lib/postgresql/dumpall/7.1/postmaster -D /var/lib/postgres/data -p
5431 -o -d0
/usr/lib/postgresql/dumpall/7.1/postmaster: PostmasterMain: initial environ
dump:
-----------------------------------------
PWD=/var/lib/postgres
PAGER=less
HZ=100
USER=postgres
MAIL=/var/spool/mail/postgres
BINDIR=/usr/lib/postgresql/dumpall/7.1
EDITOR=vim
LOGNAME=postgres
SHLVL=2
SHELL=/bin/sh
PGLIB=/usr/lib/postgresql
TERM=screen-w
HOME=/var/lib/postgres
PGDATA=/var/lib/postgres/data
PATH=/usr/lib/postgresql/bin:/bin:/usr/bin
PGDATESTYLE=EURO
_=/usr/lib/postgresql/dumpall/7.1/postmaster
-----------------------------------------
invoking IpcMemoryCreate(size=534396928)
FindExec: found "/usr/lib/postgresql/dumpall/7.1/postmaster" using argv[0]
/usr/lib/postgresql/dumpall/7.1/postmaster: reaping dead processes...
Dumping the database to /billing/dump_database/db.out
/usr/lib/postgresql/bin/pg_dumpall
connected to template1...
/usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: handling
reading 5
/usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: handling
reading 5
/usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: handling
reading 5
/usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: handling
reading 5
process_hba_record: invalid syntax in pg_hba.conf file
Missing or erroneous pg_hba.conf file, see postmaster log for details
/usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: handling
writing 5
psql: Missing or erroneous pg_hba.conf file, see postmaster log for details
Finding the default encoding
/usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: handling
reading 5
/usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: handling
reading 5
/usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: handling
reading 5
/usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: handling
reading 5
process_hba_record: invalid syntax in pg_hba.conf file
Missing or erroneous pg_hba.conf file, see postmaster log for details
/usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: handling
writing 5
psql: Missing or erroneous pg_hba.conf file, see postmaster log for details
Usage: pg_encoding [options] encoding_name | encoding_number
options: -b check if encoding is valid for backend
Killing the postmaster
Smart Shutdown request at Thu Mar 7 10:36:06 2002
This is the ASCII output of the dump for you to check:
-- postgresql-dump on Thu Mar 7 10:36:06 EST 2002 from version 7.1
--
-- pg_dumpall (7.2)
--
\connect template1
DELETE FROM pg_shadow WHERE usesysid <> (SELECT datdba FROM pg_database
WHERE datname = 'template0');
/usr/lib/postgresql/dumpall/7.1/postmaster: reaping dead processes...
On the basis of this dump, is it OK to delete the old database? [y/n] n
My pg_hba.conf file is the stock one supplied with the package. Any ideas
on how to fix this?
Andrew Clark
90East (Asia Pacific) Pty Ltd
Canberra, Australia
02 6272 3700 (switch)
02 6272 3010 (facsimile)
andrew.clark@sge.net
www.90East.com
**********************************************************************
Notice: This e-mail may contain personal information as defined in the
Privacy Act 1988, or confidential information. Please do not disclose
personal information in this e-mail, other than that of the sender, to
another party without the consent of the sender. If you are not the
intended recipient, or believe that you have received this e-mail in error,
please do not print, copy, retransmit, disseminate, or otherwise use the
information. Also, please notify the sender that you have received this
e-mail in error, and delete the copy you received. Thank you.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: PGP 7.1
mQGiBDwirksRBADcDwp1Ufx9DXVaZIIt36nOvQNl+0LhDQ/vDFIhAl6uzywXVEy/
v5oITQcbSjwOHNzRCqdcln+1JPgAIf0uL1npk1cWiwwhTEZ7orGF+rxzAizjuwwz
LXN81Vo/swHPe0EMHdmPJaCwgmIKzJxN5QEL7MdLKfW800NgruhfafqH9QCg/7Br
0CmVmnqHI77mvqMzD60M3XUD/1gUvQIjaBT35K32r8by5DaLtamiok9dvtq/rUQE
6yFQOiHrLWYkI1tStjiggc4ph+kEJOcuy/vLFIyrmXtaBRKLvf9G79S14nEjAoXJ
Gbrkx5nD6V5sSzkWdWAvjs+by5WTmLx4EkKJn34Cb+zY7m/arb03EW+/X4y+jMFz
RqxMBACFmagdfleGIQDWG8Nk7a31USDmuXyK33ex1x5MWGfx3Jl40mKMxRqEBG7Z
Em+Tiw0t8BSk+9lJEXITAWYY/8sE9Tr12bAhDGwiCRHK4MilrRiHti87ooZ4Neaf
6beTTedgIaVrdEmCR7DPpNuyxYYWeVfKTSrz2R/MqgbPJx4UK7QuQW5kcmV3IEph
bWVzIEZlbm4gQ2xhcmsgPGFuZHJldy5jbGFya0BzZ2UubmV0PokAWAQQEQIAGAUC
PCKuSwgLAwkIBwIBCgIZAQUbAwAAAAAKCRBYTWlYuV6jywqgAKDg7t6dvJytVrtq
Po95v/+jKqO32gCgylAJ9mW4ON+5OYoBM61uTR4GSdS5Ag0EPCKuSxAIAPZCV7cI
fwgXcqK61qlC8wXo+VMROU+28W65Szgg2gGnVqMU6Y9AVfPQB8bLQ6mUrfdMZIZJ
+AyDvWXpF9Sh01D49Vlf3HZSTz09jdvOmeFXklnN/biudE/F/Ha8g8VHMGHOfMlm
/xX5u/2RXscBqtNbno2gpXI61Brwv0YAWCvl9Ij9WE5J280gtJ3kkQc2azNsOA1F
HQ98iLMcfFstjvbzySPAQ/ClWxiNjrtVjLhdONM0/XwXV0OjHRhs3jMhLLUq/zzh
sSlAGBGNfISnCnLWhsQDGcgHKXrKlQzZlp+r0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZ
Jrqrol7DVekyCzsAAgIIAMADIRLh9SEV25Kvec/MwMVcFXkSKgUOO8DnSTuf0mIP
Trl6ikx0doCauSbMh/6ASUJIBNFfy+n56j7Zw7b4r91Mk4RFbe0noGjSeb5TKUD6
imZCcfBYCfLuotCekEUAok7Ac+XWBO05HSKSFenDqZkk2UHqwqBTz2sSyKYqtmzl
YURrXeCgOVYlQqbPLLdnSQkdwJ4go7fLjVPKQ8aaJw3AmxTdRpaD9x29DCMiKvxK
ZHNLjS7+f+0VxRDgZLf2HorVMMAXt3apR9PmR4pquvk+oGRSSI6q2gx50MwJfzkl
Sytjb/enSejEHOZZMT4dYpJjIFet+BXQmSIawwJXLgeJAEwEGBECAAwFAjwirksF
GwwAAAAACgkQWE1pWLleo8v0RgCfZ3Xt43lblTCSw3e1JeWjfrltKZEAn1sNTNaS
LNQgT7pD11ifhyFhhpuS
=v+xm
-----END PGP PUBLIC KEY BLOCK-----
The first thing i notice is that the default port for postgres is wrong unless you have changed it. You have it looking -p 5431 instead of 5432. As for the pg_hba.confcould you post it to the list so we can look at it. Remove any security information that may be in the file about your system :-) Thanks Darren Ferguson > I'm having problems upgrading from 7.1 to 7.2. I'm using a Debian > package, which says to run: > > su - postgres > postgresql-dump -t db.out -dcivlp $PGDATA/../data.save > > When I run this, I get the following: > > $ postgresql-dump -t /billing/dump_database/db.out -dcivlp > $PGDATA/../data.save > Stopping and restarting the postmaster > /usr/lib/postgresql/dumpall/7.1/postmaster -D /var/lib/postgres/data > -p 5431 -o -d0 > /usr/lib/postgresql/dumpall/7.1/postmaster: PostmasterMain: initial > environ dump: > ----------------------------------------- > PWD=/var/lib/postgres > PAGER=less > HZ=100 > USER=postgres > MAIL=/var/spool/mail/postgres > BINDIR=/usr/lib/postgresql/dumpall/7.1 > EDITOR=vim > LOGNAME=postgres > SHLVL=2 > SHELL=/bin/sh > PGLIB=/usr/lib/postgresql > TERM=screen-w > HOME=/var/lib/postgres > PGDATA=/var/lib/postgres/data > PATH=/usr/lib/postgresql/bin:/bin:/usr/bin > PGDATESTYLE=EURO > _=/usr/lib/postgresql/dumpall/7.1/postmaster > ----------------------------------------- > invoking IpcMemoryCreate(size=534396928) > FindExec: found "/usr/lib/postgresql/dumpall/7.1/postmaster" using > argv[0] /usr/lib/postgresql/dumpall/7.1/postmaster: reaping dead > processes... Dumping the database to /billing/dump_database/db.out > /usr/lib/postgresql/bin/pg_dumpall > connected to template1... > /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: > handling reading 5 > /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: > handling reading 5 > /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: > handling reading 5 > /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: > handling reading 5 > process_hba_record: invalid syntax in pg_hba.conf file > Missing or erroneous pg_hba.conf file, see postmaster log for details > /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: > handling writing 5 > psql: Missing or erroneous pg_hba.conf file, see postmaster log for > details Finding the default encoding > /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: > handling reading 5 > /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: > handling reading 5 > /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: > handling reading 5 > /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: > handling reading 5 > process_hba_record: invalid syntax in pg_hba.conf file > Missing or erroneous pg_hba.conf file, see postmaster log for details > /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop: > handling writing 5 > psql: Missing or erroneous pg_hba.conf file, see postmaster log for > details > > Usage: pg_encoding [options] encoding_name | encoding_number > > options: -b check if encoding is valid for backend > > Killing the postmaster > Smart Shutdown request at Thu Mar 7 10:36:06 2002 > This is the ASCII output of the dump for you to check: > > -- postgresql-dump on Thu Mar 7 10:36:06 EST 2002 from version 7.1 -- > -- pg_dumpall (7.2) > -- > \connect template1 > DELETE FROM pg_shadow WHERE usesysid <> (SELECT datdba FROM pg_database > WHERE datname = 'template0'); > > /usr/lib/postgresql/dumpall/7.1/postmaster: reaping dead processes... > On the basis of this dump, is it OK to delete the old database? [y/n] n > > > My pg_hba.conf file is the stock one supplied with the package. Any > ideas on how to fix this? > > Andrew Clark > 90East (Asia Pacific) Pty Ltd > Canberra, Australia > > > 02 6272 3700 (switch) > 02 6272 3010 (facsimile) > > > andrew.clark@sge.net > www.90East.com > > > ********************************************************************** > Notice: This e-mail may contain personal information as defined in the > Privacy Act 1988, or confidential information. Please do not disclose > personal information in this e-mail, other than that of the sender, to > another party without the consent of the sender. If you are not the > intended recipient, or believe that you have received this e-mail in > error, please do not print, copy, retransmit, disseminate, or otherwise > use the information. Also, please notify the sender that you have > received this e-mail in error, and delete the copy you received. Thank > you. > > > > -----BEGIN PGP PUBLIC KEY BLOCK----- > Version: PGP 7.1 > > mQGiBDwirksRBADcDwp1Ufx9DXVaZIIt36nOvQNl+0LhDQ/vDFIhAl6uzywXVEy/ > v5oITQcbSjwOHNzRCqdcln+1JPgAIf0uL1npk1cWiwwhTEZ7orGF+rxzAizjuwwz > LXN81Vo/swHPe0EMHdmPJaCwgmIKzJxN5QEL7MdLKfW800NgruhfafqH9QCg/7Br > 0CmVmnqHI77mvqMzD60M3XUD/1gUvQIjaBT35K32r8by5DaLtamiok9dvtq/rUQE > 6yFQOiHrLWYkI1tStjiggc4ph+kEJOcuy/vLFIyrmXtaBRKLvf9G79S14nEjAoXJ > Gbrkx5nD6V5sSzkWdWAvjs+by5WTmLx4EkKJn34Cb+zY7m/arb03EW+/X4y+jMFz > RqxMBACFmagdfleGIQDWG8Nk7a31USDmuXyK33ex1x5MWGfx3Jl40mKMxRqEBG7Z > Em+Tiw0t8BSk+9lJEXITAWYY/8sE9Tr12bAhDGwiCRHK4MilrRiHti87ooZ4Neaf > 6beTTedgIaVrdEmCR7DPpNuyxYYWeVfKTSrz2R/MqgbPJx4UK7QuQW5kcmV3IEph > bWVzIEZlbm4gQ2xhcmsgPGFuZHJldy5jbGFya0BzZ2UubmV0PokAWAQQEQIAGAUC > PCKuSwgLAwkIBwIBCgIZAQUbAwAAAAAKCRBYTWlYuV6jywqgAKDg7t6dvJytVrtq > Po95v/+jKqO32gCgylAJ9mW4ON+5OYoBM61uTR4GSdS5Ag0EPCKuSxAIAPZCV7cI > fwgXcqK61qlC8wXo+VMROU+28W65Szgg2gGnVqMU6Y9AVfPQB8bLQ6mUrfdMZIZJ > +AyDvWXpF9Sh01D49Vlf3HZSTz09jdvOmeFXklnN/biudE/F/Ha8g8VHMGHOfMlm > /xX5u/2RXscBqtNbno2gpXI61Brwv0YAWCvl9Ij9WE5J280gtJ3kkQc2azNsOA1F > HQ98iLMcfFstjvbzySPAQ/ClWxiNjrtVjLhdONM0/XwXV0OjHRhs3jMhLLUq/zzh > sSlAGBGNfISnCnLWhsQDGcgHKXrKlQzZlp+r0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZ > Jrqrol7DVekyCzsAAgIIAMADIRLh9SEV25Kvec/MwMVcFXkSKgUOO8DnSTuf0mIP > Trl6ikx0doCauSbMh/6ASUJIBNFfy+n56j7Zw7b4r91Mk4RFbe0noGjSeb5TKUD6 > imZCcfBYCfLuotCekEUAok7Ac+XWBO05HSKSFenDqZkk2UHqwqBTz2sSyKYqtmzl > YURrXeCgOVYlQqbPLLdnSQkdwJ4go7fLjVPKQ8aaJw3AmxTdRpaD9x29DCMiKvxK > ZHNLjS7+f+0VxRDgZLf2HorVMMAXt3apR9PmR4pquvk+oGRSSI6q2gx50MwJfzkl > Sytjb/enSejEHOZZMT4dYpJjIFet+BXQmSIawwJXLgeJAEwEGBECAAwFAjwirksF > GwwAAAAACgkQWE1pWLleo8v0RgCfZ3Xt43lblTCSw3e1JeWjfrltKZEAn1sNTNaS > LNQgT7pD11ifhyFhhpuS > =v+xm > -----END PGP PUBLIC KEY BLOCK----- > > > > > ---------------------------(end of > broadcast)--------------------------- TIP 6: Have you searched our list > archives? > > http://archives.postgresql.org
Don't worry, fixed it... Copied /etc/postgresql/pg_hba.conf.dpkg-old over
/etc/postgresql/pg_hba.conf and everything started working... I'm a bit
confused as to why though, seeing as they both contain the same three
lines...
Andrew Clark
90East (Asia Pacific) Pty Ltd
Canberra, Australia
02 6272 3700 (switch)
02 6272 3010 (facsimile)
andrew.clark@sge.net
www.90East.com
**********************************************************************
Notice: This e-mail may contain personal information as defined in the
Privacy Act 1988, or confidential information. Please do not disclose
personal information in this e-mail, other than that of the sender, to
another party without the consent of the sender. If you are not the
intended recipient, or believe that you have received this e-mail in error,
please do not print, copy, retransmit, disseminate, or otherwise use the
information. Also, please notify the sender that you have received this
e-mail in error, and delete the copy you received. Thank you.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: PGP 7.1
mQGiBDwirksRBADcDwp1Ufx9DXVaZIIt36nOvQNl+0LhDQ/vDFIhAl6uzywXVEy/
v5oITQcbSjwOHNzRCqdcln+1JPgAIf0uL1npk1cWiwwhTEZ7orGF+rxzAizjuwwz
LXN81Vo/swHPe0EMHdmPJaCwgmIKzJxN5QEL7MdLKfW800NgruhfafqH9QCg/7Br
0CmVmnqHI77mvqMzD60M3XUD/1gUvQIjaBT35K32r8by5DaLtamiok9dvtq/rUQE
6yFQOiHrLWYkI1tStjiggc4ph+kEJOcuy/vLFIyrmXtaBRKLvf9G79S14nEjAoXJ
Gbrkx5nD6V5sSzkWdWAvjs+by5WTmLx4EkKJn34Cb+zY7m/arb03EW+/X4y+jMFz
RqxMBACFmagdfleGIQDWG8Nk7a31USDmuXyK33ex1x5MWGfx3Jl40mKMxRqEBG7Z
Em+Tiw0t8BSk+9lJEXITAWYY/8sE9Tr12bAhDGwiCRHK4MilrRiHti87ooZ4Neaf
6beTTedgIaVrdEmCR7DPpNuyxYYWeVfKTSrz2R/MqgbPJx4UK7QuQW5kcmV3IEph
bWVzIEZlbm4gQ2xhcmsgPGFuZHJldy5jbGFya0BzZ2UubmV0PokAWAQQEQIAGAUC
PCKuSwgLAwkIBwIBCgIZAQUbAwAAAAAKCRBYTWlYuV6jywqgAKDg7t6dvJytVrtq
Po95v/+jKqO32gCgylAJ9mW4ON+5OYoBM61uTR4GSdS5Ag0EPCKuSxAIAPZCV7cI
fwgXcqK61qlC8wXo+VMROU+28W65Szgg2gGnVqMU6Y9AVfPQB8bLQ6mUrfdMZIZJ
+AyDvWXpF9Sh01D49Vlf3HZSTz09jdvOmeFXklnN/biudE/F/Ha8g8VHMGHOfMlm
/xX5u/2RXscBqtNbno2gpXI61Brwv0YAWCvl9Ij9WE5J280gtJ3kkQc2azNsOA1F
HQ98iLMcfFstjvbzySPAQ/ClWxiNjrtVjLhdONM0/XwXV0OjHRhs3jMhLLUq/zzh
sSlAGBGNfISnCnLWhsQDGcgHKXrKlQzZlp+r0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZ
Jrqrol7DVekyCzsAAgIIAMADIRLh9SEV25Kvec/MwMVcFXkSKgUOO8DnSTuf0mIP
Trl6ikx0doCauSbMh/6ASUJIBNFfy+n56j7Zw7b4r91Mk4RFbe0noGjSeb5TKUD6
imZCcfBYCfLuotCekEUAok7Ac+XWBO05HSKSFenDqZkk2UHqwqBTz2sSyKYqtmzl
YURrXeCgOVYlQqbPLLdnSQkdwJ4go7fLjVPKQ8aaJw3AmxTdRpaD9x29DCMiKvxK
ZHNLjS7+f+0VxRDgZLf2HorVMMAXt3apR9PmR4pquvk+oGRSSI6q2gx50MwJfzkl
Sytjb/enSejEHOZZMT4dYpJjIFet+BXQmSIawwJXLgeJAEwEGBECAAwFAjwirksF
GwwAAAAACgkQWE1pWLleo8v0RgCfZ3Xt43lblTCSw3e1JeWjfrltKZEAn1sNTNaS
LNQgT7pD11ifhyFhhpuS
=v+xm
-----END PGP PUBLIC KEY BLOCK-----
|---------+---------------------------------->
| | Darren Ferguson |
| | <darren@crystalballinc.|
| | com> |
| | Sent by: |
| | pgsql-general-owner@pos|
| | tgresql.org |
| | |
| | |
| | 07/03/2002 11:18 |
| | |
|---------+---------------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: <andrew.clark@sge.net>
|
| cc: <pgsql-general@postgresql.org>
|
| Subject: Re: [GENERAL] Have problems with 7.1 -> 7.2 upgrade
|
>------------------------------------------------------------------------------------------------------------------------------|
The first thing i notice is that the default port for postgres is wrong
unless you have changed it.
You have it looking -p 5431 instead of 5432.
As for the pg_hba.confcould you post it to the list so we can look at it.
Remove any security information that may be in the file about your system
:-)
Thanks
Darren Ferguson
> I'm having problems upgrading from 7.1 to 7.2. I'm using a Debian
> package, which says to run:
>
> su - postgres
> postgresql-dump -t db.out -dcivlp $PGDATA/../data.save
>
> When I run this, I get the following:
>
> $ postgresql-dump -t /billing/dump_database/db.out -dcivlp
> $PGDATA/../data.save
> Stopping and restarting the postmaster
> /usr/lib/postgresql/dumpall/7.1/postmaster -D /var/lib/postgres/data
> -p 5431 -o -d0
> /usr/lib/postgresql/dumpall/7.1/postmaster: PostmasterMain: initial
> environ dump:
> -----------------------------------------
> PWD=/var/lib/postgres
> PAGER=less
> HZ=100
> USER=postgres
> MAIL=/var/spool/mail/postgres
> BINDIR=/usr/lib/postgresql/dumpall/7.1
> EDITOR=vim
> LOGNAME=postgres
> SHLVL=2
> SHELL=/bin/sh
> PGLIB=/usr/lib/postgresql
> TERM=screen-w
> HOME=/var/lib/postgres
> PGDATA=/var/lib/postgres/data
> PATH=/usr/lib/postgresql/bin:/bin:/usr/bin
> PGDATESTYLE=EURO
> _=/usr/lib/postgresql/dumpall/7.1/postmaster
> -----------------------------------------
> invoking IpcMemoryCreate(size=534396928)
> FindExec: found "/usr/lib/postgresql/dumpall/7.1/postmaster" using
> argv[0] /usr/lib/postgresql/dumpall/7.1/postmaster: reaping dead
> processes... Dumping the database to /billing/dump_database/db.out
> /usr/lib/postgresql/bin/pg_dumpall
> connected to template1...
> /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop:
> handling reading 5
> /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop:
> handling reading 5
> /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop:
> handling reading 5
> /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop:
> handling reading 5
> process_hba_record: invalid syntax in pg_hba.conf file
> Missing or erroneous pg_hba.conf file, see postmaster log for details
> /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop:
> handling writing 5
> psql: Missing or erroneous pg_hba.conf file, see postmaster log for
> details Finding the default encoding
> /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop:
> handling reading 5
> /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop:
> handling reading 5
> /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop:
> handling reading 5
> /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop:
> handling reading 5
> process_hba_record: invalid syntax in pg_hba.conf file
> Missing or erroneous pg_hba.conf file, see postmaster log for details
> /usr/lib/postgresql/dumpall/7.1/postmaster: ServerLoop:
> handling writing 5
> psql: Missing or erroneous pg_hba.conf file, see postmaster log for
> details
>
> Usage: pg_encoding [options] encoding_name | encoding_number
>
> options: -b check if encoding is valid for backend
>
> Killing the postmaster
> Smart Shutdown request at Thu Mar 7 10:36:06 2002
> This is the ASCII output of the dump for you to check:
>
> -- postgresql-dump on Thu Mar 7 10:36:06 EST 2002 from version 7.1 --
> -- pg_dumpall (7.2)
> --
> \connect template1
> DELETE FROM pg_shadow WHERE usesysid <> (SELECT datdba FROM pg_database
> WHERE datname = 'template0');
>
> /usr/lib/postgresql/dumpall/7.1/postmaster: reaping dead processes...
> On the basis of this dump, is it OK to delete the old database? [y/n] n
>
>
> My pg_hba.conf file is the stock one supplied with the package. Any
> ideas on how to fix this?
>
> Andrew Clark
> 90East (Asia Pacific) Pty Ltd
> Canberra, Australia
>
>
> 02 6272 3700 (switch)
> 02 6272 3010 (facsimile)
>
>
> andrew.clark@sge.net
> www.90East.com
>
>
> **********************************************************************
> Notice: This e-mail may contain personal information as defined in the
> Privacy Act 1988, or confidential information. Please do not disclose
> personal information in this e-mail, other than that of the sender, to
> another party without the consent of the sender. If you are not the
> intended recipient, or believe that you have received this e-mail in
> error, please do not print, copy, retransmit, disseminate, or otherwise
> use the information. Also, please notify the sender that you have
> received this e-mail in error, and delete the copy you received. Thank
> you.
>
>
>
> -----BEGIN PGP PUBLIC KEY BLOCK-----
> Version: PGP 7.1
>
> mQGiBDwirksRBADcDwp1Ufx9DXVaZIIt36nOvQNl+0LhDQ/vDFIhAl6uzywXVEy/
> v5oITQcbSjwOHNzRCqdcln+1JPgAIf0uL1npk1cWiwwhTEZ7orGF+rxzAizjuwwz
> LXN81Vo/swHPe0EMHdmPJaCwgmIKzJxN5QEL7MdLKfW800NgruhfafqH9QCg/7Br
> 0CmVmnqHI77mvqMzD60M3XUD/1gUvQIjaBT35K32r8by5DaLtamiok9dvtq/rUQE
> 6yFQOiHrLWYkI1tStjiggc4ph+kEJOcuy/vLFIyrmXtaBRKLvf9G79S14nEjAoXJ
> Gbrkx5nD6V5sSzkWdWAvjs+by5WTmLx4EkKJn34Cb+zY7m/arb03EW+/X4y+jMFz
> RqxMBACFmagdfleGIQDWG8Nk7a31USDmuXyK33ex1x5MWGfx3Jl40mKMxRqEBG7Z
> Em+Tiw0t8BSk+9lJEXITAWYY/8sE9Tr12bAhDGwiCRHK4MilrRiHti87ooZ4Neaf
> 6beTTedgIaVrdEmCR7DPpNuyxYYWeVfKTSrz2R/MqgbPJx4UK7QuQW5kcmV3IEph
> bWVzIEZlbm4gQ2xhcmsgPGFuZHJldy5jbGFya0BzZ2UubmV0PokAWAQQEQIAGAUC
> PCKuSwgLAwkIBwIBCgIZAQUbAwAAAAAKCRBYTWlYuV6jywqgAKDg7t6dvJytVrtq
> Po95v/+jKqO32gCgylAJ9mW4ON+5OYoBM61uTR4GSdS5Ag0EPCKuSxAIAPZCV7cI
> fwgXcqK61qlC8wXo+VMROU+28W65Szgg2gGnVqMU6Y9AVfPQB8bLQ6mUrfdMZIZJ
> +AyDvWXpF9Sh01D49Vlf3HZSTz09jdvOmeFXklnN/biudE/F/Ha8g8VHMGHOfMlm
> /xX5u/2RXscBqtNbno2gpXI61Brwv0YAWCvl9Ij9WE5J280gtJ3kkQc2azNsOA1F
> HQ98iLMcfFstjvbzySPAQ/ClWxiNjrtVjLhdONM0/XwXV0OjHRhs3jMhLLUq/zzh
> sSlAGBGNfISnCnLWhsQDGcgHKXrKlQzZlp+r0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZ
> Jrqrol7DVekyCzsAAgIIAMADIRLh9SEV25Kvec/MwMVcFXkSKgUOO8DnSTuf0mIP
> Trl6ikx0doCauSbMh/6ASUJIBNFfy+n56j7Zw7b4r91Mk4RFbe0noGjSeb5TKUD6
> imZCcfBYCfLuotCekEUAok7Ac+XWBO05HSKSFenDqZkk2UHqwqBTz2sSyKYqtmzl
> YURrXeCgOVYlQqbPLLdnSQkdwJ4go7fLjVPKQ8aaJw3AmxTdRpaD9x29DCMiKvxK
> ZHNLjS7+f+0VxRDgZLf2HorVMMAXt3apR9PmR4pquvk+oGRSSI6q2gx50MwJfzkl
> Sytjb/enSejEHOZZMT4dYpJjIFet+BXQmSIawwJXLgeJAEwEGBECAAwFAjwirksF
> GwwAAAAACgkQWE1pWLleo8v0RgCfZ3Xt43lblTCSw3e1JeWjfrltKZEAn1sNTNaS
> LNQgT7pD11ifhyFhhpuS
> =v+xm
> -----END PGP PUBLIC KEY BLOCK-----
>
>
>
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 6: Have you searched our list
> archives?
>
> http://archives.postgresql.org
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
On Thu, 2002-03-07 at 00:18, Darren Ferguson wrote: > The first thing i notice is that the default port for postgres is wrong > unless you have changed it. > > You have it looking -p 5431 instead of 5432. That is a feature of the Debian upgrade process; it changes the port to guard against interference by normal users while the upgrade is going on. -- Oliver Elphick Oliver.Elphick@lfix.co.uk Isle of Wight http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C "Go ye therefore, and teach all nations, baptizing them in the name of the Father, and of the Son, and of the Holy Ghost; Teaching them to observe all things whatsoever I have commanded you; and, lo, I am with you alway, even unto the end of the world. Amen." Matthew 28:19,20
On Thu, 2002-03-07 at 00:32, andrew.clark@sge.net wrote: > > Don't worry, fixed it... Copied /etc/postgresql/pg_hba.conf.dpkg-old over > /etc/postgresql/pg_hba.conf and everything started working... I'm a bit > confused as to why though, seeing as they both contain the same three > lines... They must in fact have been different! The Debian release of 7.1 used 'peer' authentication, which has now been adopted into mainstream PostgreSQL as 'ident' authentication on Unix sockets. Therefore 'peer' is no longer valid in the Debian package and the new distributed pg_hba.conf has changed it to 'ident'. However, since this is a conffile, package installation will not touch it without permission. The postinst package installation script should have offered to change it for you. Is there a bug there? -- Oliver Elphick Oliver.Elphick@lfix.co.uk Isle of Wight http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C "Go ye therefore, and teach all nations, baptizing them in the name of the Father, and of the Son, and of the Holy Ghost; Teaching them to observe all things whatsoever I have commanded you; and, lo, I am with you alway, even unto the end of the world. Amen." Matthew 28:19,20
> They must in fact have been different! > They are, as you pointed out below. > The Debian release of 7.1 used 'peer' authentication, which has now been > adopted into mainstream PostgreSQL as 'ident' authentication on Unix > sockets. Therefore 'peer' is no longer valid in the Debian package and > the new distributed pg_hba.conf has changed it to 'ident'. However, > since this is a conffile, package installation will not touch it without > permission. > > The postinst package installation script should have offered to change > it for you. Is there a bug there? Only that 7.1 wants peer and 7.2 doesn't. Perhaps the postgresql-dump script show detect the change from 7.1 to 7.2 and generate a temporary pg_hba.conf file with trust set, dump the db, reimport the db and then restore the pg_hba.conf file? I did eventually get this to work, it just took a bit longer than expected (which was exaserbated by running out of space on the device I was dumping to) Thanks for you help, AJFC.