Обсуждение: Please Help... Service fails to start
Dear Friends, I really need help for my problem, 7 days ago Postgresql service fails to start and i have no backup ! (OS: Windows XP Pro). I tried googling everywhere but didn't find any solution. I had tried to start the service manually from control panel, it started for about 5 seconds, after that stop again. This is the error log : 2009-11-02 10:13:29 LOG: database system was interrupted while in recovery at 2009-10-30 06:33:49 Malay Peninsula Standard Time 2009-11-02 10:13:29 HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery. 2009-11-02 10:13:29 LOG: checkpoint record is at 3/DA21E418 2009-11-02 10:13:29 LOG: redo record is at 3/DA21E418; undo record is at 0/0; shutdown FALSE 2009-11-02 10:13:29 LOG: next transaction ID: 0/139856773; next OID: 28846 2009-11-02 10:13:29 LOG: next MultiXactId: 4; next MultiXactOffset: 7 2009-11-02 10:13:29 LOG: database system was not properly shut down; automatic recovery in progress 2009-11-02 10:13:29 LOG: redo starts at 3/DA21E468 2009-11-02 10:13:35 FATAL: could not access status of transaction 139856778 2009-11-02 10:13:35 DETAIL: Could not read from file "pg_clog/0085" at offset 98304: Permission denied. 2009-11-02 10:13:35 CONTEXT: xlog redo commit: 2009-10-20 17:20:42 2009-11-02 10:13:38 LOG: startup process (PID 1284) exited with exit code 1 2009-11-02 10:13:38 LOG: aborting startup due to startup process failure 2009-11-02 10:13:38 LOG: logger shutting down It seems that i still have chance to redo or undo the record that caused this error. But how to do that ? How to find that file ? Postgresql data folder only contain numbered filename. Thank you for any help.
Hengky Lie <hengkyliwandouw@gmail.com> writes: > 2009-11-02 10:13:35 FATAL: could not access status of transaction > 139856778 > 2009-11-02 10:13:35 DETAIL: Could not read from file "pg_clog/0085" > at offset 98304: Permission denied. You need to fix that "Permission denied" problem. Either the file really is marked as not readable by the postgres user, or (probably more likely on Windows) you have some malfunctioning "antivirus" software installed. regards, tom lane
>> 2009-11-02 10:13:35 FATAL: could not access status of transaction 139856778
2009-11-02 10:13:35 DETAIL: Could not read from file "pg_clog/0085" at offset 98304: Permission denied.
I faced this error before a week only. Fortunately we have a valid backup and we restored the file (0085) in pg_clog directory. In our case it is the corruption issue. Kindly check with permission and also under the /usr/local/pgsql/data/pg_clog directory whether the file (0085) is there or not ? If it is not there than try to reload it from the backup. At last you can touch the file and restart the database. However, in this case you will be lose your data.
-- Thanks
Sam Jas
--- On Tue, 3/11/09, Tom Lane <tgl@sss.pgh.pa.us> wrote:
From: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: [ADMIN] Please Help... Service fails to start
To: "Hengky Lie" <hengkyliwandouw@gmail.com>
Cc: pgsql-admin@postgresql.org
Date: Tuesday, 3 November, 2009, 3:37 AMHengky Lie <hengkyliwandouw@gmail.com> writes:
> 2009-11-02 10:13:35 FATAL: could not access status of transaction
> 139856778
> 2009-11-02 10:13:35 DETAIL: Could not read from file "pg_clog/0085"
> at offset 98304: Permission denied.
You need to fix that "Permission denied" problem. Either the file
really is marked as not readable by the postgres user, or (probably
more likely on Windows) you have some malfunctioning "antivirus"
software installed.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Yahoo! India has a new look. Take a sneak peek.
>> 2009-11-02 10:13:35 FATAL: could not access status of transaction 139856778
2009-11-02 10:13:35 DETAIL: Could not read from file "pg_clog/0085" at offset 98304: Permission denied.I faced this error before a week only. Fortunately we have a valid backup and we restored the file (0085) in pg_clog directory. In our case it is the corruption issue. Kindly check with permission and also under the /usr/local/pgsql/data/pg_clog directory whether the file (0085) is there or not ? If it is not there than try to reload it from the backup. At last you can touch the file and restart the database. However, in this case you will be lose your data.
-- Thanks
Sam Jas
--- On Tue, 3/11/09, Tom Lane <tgl@sss.pgh.pa.us> wrote:
From: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: [ADMIN] Please Help... Service fails to start
To: "Hengky Lie" <hengkyliwandouw@gmail.com>
Cc: pgsql-admin@postgresql.org
Date: Tuesday, 3 November, 2009, 3:37 AMHengky Lie <hengkyliwandouw@gmail.com> writes:
> 2009-11-02 10:13:35 FATAL: could not access status of transaction
> 139856778
> 2009-11-02 10:13:35 DETAIL: Could not read from file "pg_clog/0085"
> at offset 98304: Permission denied.
You need to fix that "Permission denied" problem. Either the file
really is marked as not readable by the postgres user, or (probably
more likely on Windows) you have some malfunctioning "antivirus"
software installed.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Yahoo! India has a new look. Take a sneak peek.
What exactly file pg_clog/0085 exactly is ? Thank you for any advice. Now i'm trying to check file permission and antivirus.
pg_clog contains the commit log. Once things in pg_xlog have been committed to disk when the background writer gets around to it. They get marked committed in pg_clog.
Note that often broken antivirus programs will still cause problems if they're simply disabled. The real answer is to uninstall them (and hope they don't leave any broken system dlls behind to still cause problems).
A database server should be so far from things that can give it viruses that anti-virus software should be uneeded.
On Tue, Nov 3, 2009 at 12:41 AM, Hengky Lie <hengkyliwandouw@gmail.com> wrote:What exactly file pg_clog/0085 exactly is ? Thank you for any advice. Now i'm trying to check file permission and antivirus.
pg_clog contains the commit log. Once things in pg_xlog have been committed to disk when the background writer gets around to it. They get marked committed in pg_clog.
Note that often broken antivirus programs will still cause problems if they're simply disabled. The real answer is to uninstall them (and hope they don't leave any broken system dlls behind to still cause problems).
A database server should be so far from things that can give it viruses that anti-virus software should be uneeded.