Обсуждение: PANIC: read of clog file 3165, offset 0 failed: Success

Поиск
Список
Период
Сортировка

PANIC: read of clog file 3165, offset 0 failed: Success

От
Khangelani Gama
Дата:

Please assist, I am getting the following error when trying to vacuum analyze the database(database name db0532). It’s PostgreSQL_7.3.4 running on CentOS5

 

 

 

db0532=# vacuum analyze;

PANIC:  read of clog file 3165, offset 0 failed: Success

server closed the connection unexpectedly

        This probably means the server terminated abnormally

        before or while processing the request.

The connection to the server was lost. Attempting reset: Failed.

 

 

 

 

 

 

 

 

 

 

Confidentiality Notice:http://ucs.co.za/conf.html

 

 



The contents of and attachments to this e-mail are intended for the addressee only, and may contain the confidential information of UCS Group and/or its subsidiaries. Any review, use or dissemination thereof by anyone other than the intended addressee is prohibited. If you are not the intended addressee please notify the writer immediately and destroy the e-mail. UCS Group Limited and its subsidiaries distance themselves from and accept no liability for unauthorised use of their e-mail facilities or e-mails sent other than strictly for business purposes.

Re: PANIC: read of clog file 3165, offset 0 failed: Success

От
Lewis Kapell
Дата:
I am not a member of the Postgres team and so I don't have any special
knowledge, but I can tell you two things for sure:

1) Version 7.3.4 is not supported any more, see:
http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy

You should arrange to upgrade to a supported version as soon as
possible.  Preferably to 8.4, but you would need to study the release
notes of each of the major releases in-between and see what
compatibility issues you would need to face.  In particular, there was a
change in 8.3 regarding type-casting behavior that might require a
significant re-write of your applications.

2) The Postgres experts will need more information about your situation
in order to give you advice.  For one thing, they will want to see the
contents of your $PGDATA/pg_clog directory.  Issue the command "ls -l"
in that directory and capture the output.

Also, is it possible you are running out of disk space?  Have there been
any other errors recently?  Check your operating system logs.

Thank you,

Lewis Kapell
Computer Operations
Seton Home Study School



On 4/19/2010 3:17 AM, Khangelani Gama wrote:
> Please assist, I am getting the following error when trying to vacuum
> analyze the database(database name db0532). It’s PostgreSQL_7.3.4
> running on CentOS5
>
> db0532=# vacuum analyze;
>
> *PANIC: read of clog file 3165, offset 0 failed: Success*
>
> server closed the connection unexpectedly
>
> This probably means the server terminated abnormally
>
> before or while processing the request.
>
> The connection to the server was lost. Attempting reset: Failed.
>
> * *
>
> Confidentiality Notice:http://ucs.co.za/conf.html
>
>
> ------------------------------------------------------------------------
> The contents of and attachments to this e-mail are intended for the
> addressee only, and may contain the confidential information of UCS
> Group and/or its subsidiaries. Any review, use or dissemination thereof
> by anyone other than the intended addressee is prohibited. If you are
> not the intended addressee please notify the writer immediately and
> destroy the e-mail. UCS Group Limited and its subsidiaries distance
> themselves from and accept no liability for unauthorised use of their
> e-mail facilities or e-mails sent other than strictly for business purposes.


Re: PANIC: read of clog file 3165, offset 0 failed: Success

От
Alvaro Herrera
Дата:
Lewis Kapell wrote:
> I am not a member of the Postgres team and so I don't have any
> special knowledge, but I can tell you two things for sure:
>
> 1) Version 7.3.4 is not supported any more, see:
> http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy
>
> You should arrange to upgrade to a supported version as soon as
> possible.

Yeah, at least update to 7.3.21 which is not supported but has quite a
few bugs fixed -- and I think this misleading error message was fixed in
one of them.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support