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

Started by neelaover 7 years ago4 messagesbugs
Jump to latest
#1neela
neelat100@gmail.com

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

#2Pavan Teja
pavan.postgresdba@gmail.com
In reply to: neela (#1)
Re: General: Unable to start the postgresql after copying postgresql.log

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@gmail.com> wrote:

Show quoted text

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

#3neela
neelat100@gmail.com
In reply to: Pavan Teja (#2)
Re: General: Unable to start the postgresql after copying postgresql.log

Dear sir/mam,
May I know why this cause. I simply doing the copying the log alone.
But why postgresql not get started.
Which causes this issue.

Regards,
Neelaveni

Show quoted text

On Wednesday 10 October 2018 07:29 PM, Pavan Teja wrote:

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@gmail.com
<mailto:neelat100@gmail.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

#4neela
neelat100@gmail.com
In reply to: neela (#3)
Fwd: Fwd: Re: General: Unable to start the postgresql after copying postgresql.log

Dear sir/mam,
Please explain whether this issue with postgresql or some other thing.

Regards,
Neelaveni

-------- Forwarded Message --------
Subject: Fwd: Re: General: Unable to start the postgresql after copying
postgresql.log
Date: Mon, 15 Oct 2018 14:16:21 +0530
From: neela <neelat100@gmail.com>
To: Pavan Teja <pavan.postgresdba@gmail.com>

Dear sir,

Kindly share why its happening.

Regards,

Neelaveni

-------- Forwarded Message --------
Subject: Re: General: Unable to start the postgresql after copying
postgresql.log
Date: Thu, 11 Oct 2018 09:28:49 +0530
From: neela <neelat100@gmail.com>
To: Pavan Teja <pavan.postgresdba@gmail.com>
CC: pgsql-bugs@postgresql.org

Dear sir/mam,
May I know why this cause. I simply doing the copying the log alone.
But why postgresql not get started.
Which causes this issue.

Regards,
Neelaveni

Show quoted text

On Wednesday 10 October 2018 07:29 PM, Pavan Teja wrote:

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@gmail.com
<mailto:neelat100@gmail.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