BUG #14440: Error starting postgres

From: djlopes(at)gmail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #14440: Error starting postgres
Date: 2016-11-29 23:28:32
Message-ID: 20161129232832.6534.36459@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 14440
Logged by: david lopes
Email address: djlopes(at)gmail(dot)com
PostgreSQL version: 9.3.0
Operating system: Ubuntu 64
Description:

postgres(at)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(at)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(at)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(at)ubuntu01:/usr/lib/postgresql/9.3/bin$

postgres(at)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(at)ubuntu01:/usr/lib/postgresql/9.3/bin$

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2016-11-29 23:57:47 Re: BUG #14440: Error starting postgres
Previous Message Tom Lane 2016-11-29 23:07:45 Re: BUG #14438: Wrong row count in the join plan with unique index scan