Postgres won't start and doesn't generate any messages. - Mailing list pgsql-bugs

From Chris Barnes
Subject Postgres won't start and doesn't generate any messages.
Date
Msg-id AA1C2310AD924ABFBBECFD84B9DC4064@recognia89aa32
Whole thread Raw
Responses Re: Postgres won't start and doesn't generate any messages.
List pgsql-bugs
This was working, restarted to put  (custom_variable_classes = 'olap'  ) in
conf file.



Restarted but no errors in the startup.log or command line



[postgres@pgprd01 ~]$ /opt/PostgreSQL/8.3/bin/pg_ctl -w start -D
\"/data/pgsql/data/\" -l \"/data/pgsql/data//pg_log/startup.log\"



I am using continuent unicluster



I looked at the ([postgres@pgprd01 pg_log]$ tail -20
postgresql-2008-09-24_095200.log )



Doing a cluster admin stop  from  unicluster shouldn't have changed these
permissions?



Is this a bug, or continuent ism.





LOG:  database system was interrupted while in recovery at 2008-09-24
09:50:31 EDT

HINT:  This probably means that some data is corrupted and you will have to
use the last backup for recovery.

LOG:  database system was not properly shut down; automatic recovery in
progress

LOG:  redo starts at 1/2C49EE70

FATAL:  could not access status of transaction 0

DETAIL:  Could not open file "pg_clog/0001": Permission denied.

CONTEXT:  xlog redo zeropage: 32

LOG:  startup process (PID 12718) exited with exit code 1

LOG:  aborting startup due to startup process failure

[postgres@pgprd01 pg_log]$ tail -40 postgresql-2008-09-24_095200.log

LOG:  database system was interrupted while in recovery at 2008-09-24
09:50:31 EDT

HINT:  This probably means that some data is corrupted and you will have to
use the last backup for recovery.

LOG:  database system was not properly shut down; automatic recovery in
progress

LOG:  redo starts at 1/2C49EE70

FATAL:  could not access status of transaction 0

DETAIL:  Could not open file "pg_clog/0001": Permission denied.

CONTEXT:  xlog redo zeropage: 32

LOG:  startup process (PID 12718) exited with exit code 1

LOG:  aborting startup due to startup process failure





[root@pgprd01 pg_clog]# ls -l

total 25440

-rw------- 1 postgres postgres 262144 Sep 23 16:25 0000

-rw------- 1       26       26 262144 Sep  8 13:58 0001

-rw------- 1       26       26 262144 Sep 11 16:08 0002

-rw------- 1       26       26 262144 Sep 15 09:03 0003

-rw------- 1       26       26 262144 Sep 16 11:32 0004

-rw------- 1       26       26 262144 Sep 17 10:57 0005

-rw------- 1       26       26 262144 Sep 17 14:42 0006

-rw------- 1       26       26 262144 Sep 18 12:17 0007

-rw------- 1       26       26 262144 Sep 18 15:37 0008

-rw------- 1       26       26 262144 Sep 18 15:52 0009

-rw------- 1       26       26 262144 Sep 19 09:35 000A

-rw------- 1       26       26 262144 Sep 19 09:41 000B

-rw------- 1       26       26 262144 Sep 19 09:43 000C

-rw------- 1       26       26 262144 Sep 19 09:46 000D

-rw------- 1       26       26 262144 Sep 19 09:58 000E

-rw------- 1       26       26 262144 Sep 19 10:15 000F

-rw------- 1       26       26 262144 Sep 19 10:32 0010

-rw------- 1       26       26 262144 Sep 19 10:44 0011

-rw------- 1       26       26 262144 Sep 19 11:03 0012

-rw------- 1       26       26 262144 Sep 19 11:30 0013

-rw------- 1       26       26 262144 Sep 19 11:40 0014

-rw------- 1       26       26 262144 Sep 19 11:49 0015




Chris Barnes
Recognia Inc.

Operations and Database Administration..
cbarnes@recognia.com
613.789.2267 ex.260

Empowering Traders!


This email and/or any documents attached to it may contain information which
is confidential/privileged and is intended for the information of the person
named herein. Any unauthorized dissemination or copying of this email or
attachments is strictly prohibited. If you have received this email in
error, please delete it and notify the sender immediately.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #4434: Error inserting into view - unrecognized node type: 313
Next
From: "Mathieu Fenniak"
Date:
Subject: BUG #4436: (E'\\' LIKE E'\\') => f