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

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

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

neela


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

Reply | Threaded
Open this post in threaded view
|

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

pavan95
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 <[hidden email]> 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

Reply | Threaded
Open this post in threaded view
|

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

neela
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

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 <[hidden email]> 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