Re: Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: "Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush
Date: 2010-02-02 23:17:07
Message-ID: dcc563d11002021517g50824974r21bb271845c8682a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Feb 2, 2010 at 3:29 PM, Wang, Mary Y <mary(dot)y(dot)wang(at)boeing(dot)com> wrote:
> Thanks Tom.
>
> After talking to my co-worker, we decided to go to the last backup (we used the pg_dumpall -c command).
> However, when I did enter "psql -f /usr/pgsql/backups/31.bak template1" to restore the database, I got "
> psql: connectDBStart() -- connect() failed: No such file or directory
>        Is the postmaster running locally
>        and accepting connections on Unix socket '/tmp/.s.PGSQL.5432'?
> ".
> I can't start my postmaster.  So how would I restore my last good backup?

The normal way is to drop the old cluster and create a new one. I'm
not entirely sure how to do that on something as old as RHEL 2.1. The
normal way would be to mv or rm -rf the /var/lib/pgsql/data dir and
run initdb again. something like:

sudo /etc/init.d/pgsql stop
sudo rm -rf /var/lib/pgsql/data/*
sudo -u postgres initdb -D /var/lib/pgsql/data
sudo /etc/init.d/pgsql start

or something like that.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Kiswono Prayogo 2010-02-02 23:34:07 Re: How to increase postgresql performance
Previous Message Jan-Peter Seifert 2010-02-02 23:07:48 Re: encoding error in new Postgres version