BUG #14440: Error starting postgres
The following bug has been logged on the website:
Bug reference: 14440
Logged by: david lopes
Email address: djlopes@gmail.com
PostgreSQL version: 9.3.0
Operating system: Ubuntu 64
Description:
postgres@ubuntu01:/usr/lib/postgresql/9.3/bin$ /etc/init.d/postgresql
start
* Starting PostgreSQL 9.3 database server
* The PostgreSQL server failed to start. Please check the log
output:
2016-11-29 23:27:17 WET LOG: database system was interrupted while in
recovery at 2016-11-29 22:06:46 WET
2016-11-29 23:27:17 WET HINT: This probably means that some data is
corrupted and you will have to use the last backup for recovery.
2016-11-29 23:27:17 WET LOG: database system was not properly shut down;
automatic recovery in progress
2016-11-29 23:27:17 WET LOG: redo starts at 22/12001478
2016-11-29 23:27:17 WET LOG: record with zero length at 22/12045C88
2016-11-29 23:27:17 WET LOG: redo done at 22/12045C58
2016-11-29 23:27:17 WET LOG: last completed transaction was at log time
2016-11-27 18:28:00.398522+00
2016-11-29 23:27:17 WET FATAL: btree level 1 not found in index "77469"
2016-11-29 23:27:17 WET LOG: startup process (PID 4971) exited with exit
code 1
2016-11-29 23:27:17 WET LOG: aborting startup due to startup process
failure
postgres@ubuntu01:/usr/lib/postgresql/9.3/bin$ ./postgres -D
/var/lib/postgresql/9.3/main -P -d 1
postgres cannot access the server configuration file
"/var/lib/postgresql/9.3/main/postgresql.conf": No such file or directory
postgres@ubuntu01:/usr/lib/postgresql/9.3/bin$ ./postgres -D
/etc/postgresql/9.3/main/ -P -d 1
2016-11-29 22:06:46 WET LOG: database system was interrupted while in
recovery at 2016-11-29 21:34:02 WET
2016-11-29 22:06:46 WET HINT: This probably means that some data is
corrupted and you will have to use the last backup for recovery.
2016-11-29 22:06:46 WET DEBUG: checkpoint record is at 22/12001410
2016-11-29 22:06:46 WET DEBUG: redo record is at 22/12001410; shutdown
FALSE
2016-11-29 22:06:46 WET DEBUG: next transaction ID: 0/25540991; next OID:
2248719
2016-11-29 22:06:46 WET DEBUG: next MultiXactId: 253; next MultiXactOffset:
532
2016-11-29 22:06:46 WET DEBUG: oldest unfrozen transaction ID: 674, in
database 1
2016-11-29 22:06:46 WET DEBUG: oldest MultiXactId: 1, in database 1
2016-11-29 22:06:46 WET DEBUG: transaction ID wrap limit is 2147484321,
limited by database with OID 1
2016-11-29 22:06:46 WET DEBUG: MultiXactId wrap limit is 2147483648,
limited by database with OID 1
2016-11-29 22:06:46 WET LOG: database system was not properly shut down;
automatic recovery in progress
2016-11-29 22:06:46 WET DEBUG: resetting unlogged relations: cleanup 1 init
0
2016-11-29 22:06:46 WET LOG: redo starts at 22/12001478
2016-11-29 22:06:46 WET LOG: record with zero length at 22/12045C88
2016-11-29 22:06:46 WET LOG: redo done at 22/12045C58
2016-11-29 22:06:46 WET LOG: last completed transaction was at log time
2016-11-27 18:28:00.398522+00
2016-11-29 22:06:46 WET FATAL: btree level 1 not found in index "77469"
2016-11-29 22:06:46 WET LOG: startup process (PID 4676) exited with exit
code 1
2016-11-29 22:06:46 WET LOG: aborting startup due to startup process
failure
postgres@ubuntu01:/usr/lib/postgresql/9.3/bin$
postgres@ubuntu01:/usr/lib/postgresql/9.3/bin$ ./pg_controldata
/var/lib/postgresql/9.3/main
pg_control version number: 937
Catalog version number: 201306121
Database system identifier: 6077437424573085483
Database cluster state: in crash recovery
pg_control last modified: Tue 29 Nov 2016 10:06:46 PM WET
Latest checkpoint location: 22/12001410
Prior checkpoint location: 22/12001410
Latest checkpoint's REDO location: 22/12001410
Latest checkpoint's REDO WAL file: 000000010000002200000012
Latest checkpoint's TimeLineID: 1
Latest checkpoint's PrevTimeLineID: 1
Latest checkpoint's full_page_writes: on
Latest checkpoint's NextXID: 0/25540991
Latest checkpoint's NextOID: 2248719
Latest checkpoint's NextMultiXactId: 253
Latest checkpoint's NextMultiOffset: 532
Latest checkpoint's oldestXID: 674
Latest checkpoint's oldestXID's DB: 1
Latest checkpoint's oldestActiveXID: 0
Latest checkpoint's oldestMultiXid: 1
Latest checkpoint's oldestMulti's DB: 1
Time of latest checkpoint: Sun 27 Nov 2016 06:23:36 PM WET
Fake LSN counter for unlogged rels: 0/1
Minimum recovery ending location: 0/0
Min recovery ending loc's timeline: 0
Backup start location: 0/0
Backup end location: 0/0
End-of-backup record required: no
Current wal_level setting: minimal
Current max_connections setting: 100
Current max_prepared_xacts setting: 0
Current max_locks_per_xact setting: 64
Maximum data alignment: 8
Database block size: 8192
Blocks per segment of large relation: 131072
WAL block size: 8192
Bytes per WAL segment: 16777216
Maximum length of identifiers: 64
Maximum columns in an index: 32
Maximum size of a TOAST chunk: 1996
Date/time type storage: 64-bit integers
Float4 argument passing: by value
Float8 argument passing: by reference
Data page checksum version: 0
postgres@ubuntu01:/usr/lib/postgresql/9.3/bin$
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Tue, Nov 29, 2016 at 4:28 PM, <djlopes@gmail.com> wrote:
The following bug has been logged on the website:
Bug reference: 14440
2016-11-29 23:27:17 WET LOG: database system was interrupted while in
recovery at 2016-11-29 22:06:46 WET
2016-11-29 23:27:17 WET HINT: This probably means that some data is
corrupted and you will have to use the last backup for recovery.
Without any commentary on your part I'm going to say that this is not a
bug but rather, as the hint suggests, data corruption.
If you wish to discuss PostgreSQL administration it would be customary to
subscribe to the pgsql-general list and post some background and questions
there. The bug reporting mechanism is not a proper forum for such a
discussion.
David J.
djlopes@gmail.com writes:
PostgreSQL version: 9.3.0
9.3.0? Really? There have been numerous and serious bugs fixed in the
9.3.x branch (I'm afraid it wasn't one of our most reliable releases).
I don't know offhand if any of them would explain this particular index
corruption, but you really need to be running something much newer.
9.3.15 is the current release in that branch.
2016-11-29 23:27:17 WET FATAL: btree level 1 not found in index "77469"
2016-11-29 23:27:17 WET LOG: startup process (PID 4971) exited with exit
code 1
2016-11-29 23:27:17 WET LOG: aborting startup due to startup process
failure
Looks like severe corruption of an index. I do not think there's any
automated way to recover from this. If you don't want to revert to your
last backups (hopefully you have some) it's going to take manual forensic
analysis to see what can be extracted. There are various support
companies that specialize in Postgres data recovery ... it's unlikely
anyone will want to do it for free.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Hi,
can you help how to recover my database?
I can lose the last transaction (for me its not a problem).
Where i can find information how to solve this problem?
thansk for all your help.
Com os melhores cumprimentos,
David Lopes.
______________________________________
Director do Departamento Informático @
Conselho Geral da Ordem dos Solicitadores e dos Agentes de Execução
Rua Artilharia 1, n. 63
1250-038 Lisboa-Portugal
Phone: + 351 21 38 94 200
Fax: + 351 21 35 34 870
Mobile: + 351 96 66 19 032
E-mail: david.lopes@osae.pt
Web Site: http://www.osae.pt
Aviso de Confidencialidade
Esta mensagem é exclusivamente destinada ao seu destinatário, podendo
conter informação CONFIDENCIAL ou protegidas por sigilo profissional,
cuja divulgação está expressamente vedada nos termos da lei. Caso tenha
recepcionado indevidamente esta mensagem, solicita se que nos comunique
esse mesmo facto por esta via ou para o telefone +351 213894200
devendo apagar o seu conteúdo de imediato.
This message is intended exclusively for its addressee. It contain
CONFIDENTIAL information protected by law, protected under professional
secrecy rules. Its unauthorized use is illegal and may subject the
transgressor to the law's penalties. If this message has been received
by error, please notify us via e-mail or by telephone +351 213894200
and delete it immediately.
On Tue, Nov 29, 2016 at 11:57 PM, David G. Johnston <
david.g.johnston@gmail.com> wrote:
Show quoted text
On Tue, Nov 29, 2016 at 4:28 PM, <djlopes@gmail.com> wrote:
The following bug has been logged on the website:
Bug reference: 14440
2016-11-29 23:27:17 WET LOG: database system was interrupted while in
recovery at 2016-11-29 22:06:46 WET
2016-11-29 23:27:17 WET HINT: This probably means that some data is
corrupted and you will have to use the last backup for recovery.Without any commentary on your part I'm going to say that this is not a
bug but rather, as the hint suggests, data corruption.If you wish to discuss PostgreSQL administration it would be customary to
subscribe to the pgsql-general list and post some background and questions
there. The bug reporting mechanism is not a proper forum for such a
discussion.David J.