Thread

Postgredb issue

Thusitha Maheepala <thusitha@onsys.com.au> — 2020-05-09T02:33:47Z

Hi Team,
     I need big support in my postgresql server suddenly shutdown.But again
didn't start I attached here with log can you give solution i search
community also i didn't find solution.I attached here with log.can you give
solution for me.Fix this issue.I really appericate,

-- 
Thusitha Mahipala
M.Sc-IT,B.Sc,OCP,OCS,OCE,MCP
Country Manager/Head of Database Services
Onsys Technologies
M: +94716326751
E: thusitha@onsys.com.au
W: www.onsys.com.au
No 30, Deanston Place
Colombo 03, Sri Lanka

Re: Postgredb issue

David G. Johnston <david.g.johnston@gmail.com> — 2020-05-09T14:38:00Z

On Sat, May 9, 2020 at 6:18 AM Thusitha Maheepala <thusitha@onsys.com.au>
wrote:

> Hi Team,
>      I need big support in my postgresql server suddenly shutdown.But
> again didn't start I attached here with log can you give solution i search
> community also i didn't find solution.I attached here with log.can you give
> solution for me.Fix this issue.I really appericate,
>
>
Just out of curosity - what if the answer you get is basically that your
live database is hosed you should just setup a new machine and restore your
last backup to it?

David J.

Re: Postgredb issue

Rod Taylor <rbt@rbt.ca> — 2020-05-09T15:05:58Z

On Sat, 9 May 2020 at 09:18, Thusitha Maheepala <thusitha@onsys.com.au>
wrote:

> Hi Team,
>      I need big support in my postgresql server suddenly shutdown.But
> again didn't start I attached here with log can you give solution i search
> community also i didn't find solution.I attached here with log.can you give
> solution for me.Fix this issue.I really appericate,
>
>
It appears all errors are related to the c_acctprocessorlog_pkey index? Run
the below to ditch the current index and rebuild with data from the table
files.

REINDEX INDEX c_acctprocessorlog_pkey;

It could be a bug in Pg but it's most likely a filesystem corruption or a
hardware issue (bad memory, bad disk controller, bad disk itself). You
might find some additional useful messages in the kernel logs.

Since you don't mention a version, upgrade to the most recent minor version
of Pg very soon.

regards,

Rod

Re: Postgredb issue

Rod Taylor <rbt@rbt.ca> — 2020-05-09T15:09:10Z

On Sat, 9 May 2020 at 11:05, Rod Taylor <rbt@rbt.ca> wrote:

> On Sat, 9 May 2020 at 09:18, Thusitha Maheepala <thusitha@onsys.com.au>
> wrote:
>
>> Hi Team,
>>      I need big support in my postgresql server suddenly shutdown.But
>> again didn't start I attached here with log can you give solution i search
>> community also i didn't find solution.I attached here with log.can you give
>> solution for me.Fix this issue.I really appericate,
>>
>>
> It appears all errors are related to the c_acctprocessorlog_pkey index?
> Run the below to ditch the current index and rebuild with data from the
> table files.
>

Sorry, ignore my response. I just realized you said it won't start at all.
Check for hardware issues and restore from backup.

-- 
Rod Taylor

Re: Postgredb issue

Thusitha Maheepala <thusitha@onsys.com.au> — 2020-05-09T15:38:59Z

Hi Team,
      Problem is database service also not started.how to start and index
this situation

On Sat, May 9, 2020 at 8:36 PM Rod Taylor <rbt@rbt.ca> wrote:

> On Sat, 9 May 2020 at 09:18, Thusitha Maheepala <thusitha@onsys.com.au>
> wrote:
>
>> Hi Team,
>>      I need big support in my postgresql server suddenly shutdown.But
>> again didn't start I attached here with log can you give solution i search
>> community also i didn't find solution.I attached here with log.can you give
>> solution for me.Fix this issue.I really appericate,
>>
>>
> It appears all errors are related to the c_acctprocessorlog_pkey index?
> Run the below to ditch the current index and rebuild with data from the
> table files.
>
> REINDEX INDEX c_acctprocessorlog_pkey;
>
>
> It could be a bug in Pg but it's most likely a filesystem corruption or a
> hardware issue (bad memory, bad disk controller, bad disk itself). You
> might find some additional useful messages in the kernel logs.
>
> Since you don't mention a version, upgrade to the most recent minor
> version of Pg very soon.
>
> regards,
>
> Rod
>


-- 
Thusitha Mahipala
M.Sc-IT,B.Sc,OCP,OCS,OCE,MCP
Country Manager/Head of Database Services
Onsys Technologies
M: +94716326751
E: thusitha@onsys.com.au
W: www.onsys.com.au
No 30, Deanston Place
Colombo 03, Sri Lanka

Re: Postgredb issue

Tom Lane <tgl@sss.pgh.pa.us> — 2020-05-09T15:49:29Z

Rod Taylor <rbt@rbt.ca> writes:
> It appears all errors are related to the c_acctprocessorlog_pkey index? Run
> the below to ditch the current index and rebuild with data from the table
> files.
> REINDEX INDEX c_acctprocessorlog_pkey;

That appears to have been the original problem, but at the end of the
log we see that the database is refusing to start, which suggests some
other filesystem corruption has manifested.  I'm suspecting some
combination of unreliable storage, ancient/buggy Postgres version etc.

It's troubling that the "last completed transaction" log messages suggest
that no checkpoint has completed since last July ... has the OP somehow
turned off checkpoints?  Ordinarily the only thing that could prevent
checkpoint completion is I/O errors, but there's no trace of such in the
log.  I wonder how much WAL has accumulated in the pg_wal/pg_xlog area.

It's possible that a professional data recovery service could help you
get something out of this mess.  If the data is worth money to you,
see [1] for some places to try.  Otherwise, chalk it up to experience
and start over.

			regards, tom lane

[1] https://www.postgresql.org/support/professional_support/