Re: General: Unable to start the postgresql after copying postgresql.log

From: Pavan Teja <pavan(dot)postgresdba(at)gmail(dot)com>
To: neela <neelat100(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: General: Unable to start the postgresql after copying postgresql.log
Date: 2018-10-10 13:59:57
Message-ID: CACh9nsac+07g6jvv4-24Kcv-XHHwqAFKW0eWkAA7seDcrSumRA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi neela,

In this case, you can delete the postmaster.pid file and try to restart the
Postgresql database.

I hope it might start. Kindly acknowledge for further queries if any.

Regards,
Pavan,
9841380956

On Wed, Oct 10, 2018, 7:26 PM neela <neelat100(at)gmail(dot)com> wrote:

>
> Dear sir/mam,
> I'm using postgresql 9.4.6 version.
> I've copied the postgresql.log as postgresql.log_bk.
> While copying the postgresql.log, I've restarted the postgresql
> process.
> Then the process got failed and I've got the following error,
>
> psql: could not connect to server: Connection refused
> Is the server running locally and accepting
> connections on Unix domain socket "*/tmp/*.s.PGSQL.5432"?
>
> And then I've check with log, it gives the result as follow,
> FATAL: pre-existing shared memory block is still in use
> HINT: If you're sure there are no old server processes still running,
> remove the shared memory block or just delete the file
> "postmaster.pid".
>
> After that unable to restart the postgresql, it always fails.
> After rebooting it gets succeed and truncating postmaster.pid gets
> succeed.
> Kindly help me how to fix this.
>
> --
> with regards,
> Neelaveni
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-10-10 16:17:23 BUG #15425: DETACH/ATTACH PARTITION bug
Previous Message neela 2018-10-10 10:18:06 General: Unable to start the postgresql after copying postgresql.log