Re: Postgresql service stopped automatically after restart - Mailing list pgsql-general

On 06/03/2014 10:58 PM, Kalai R wrote:
> Hi,
>
> Yesterday the psql service  stopped in our two customers's machines

See comments inline below.

>
> Windows OS  ---> Windows XP
> We re-installed the postgresql to solve the problem.

Except from what you have indicated it does not solve the problem, just
pushes it into the future again.

> We use postgresql *silent* installation method to install psql from Our
> application

You still have not indicated what exactly happens during your install
process. It would be nice to know to get a handle on the initial setup.

>
>
>
> Psql Log  for one machine
>
> 2014-06-01 18:29:48 IST LOG:  database system was interrupted; last
> known up at 2014-06-01 18:23:19 IST

The log information before this would be helpful to possibly help
determine what caused the interruption.

> 2014-06-01 18:29:49 IST LOG:  database system was not properly shut
> down; automatic recovery in progress
> 2014-06-01 18:29:49 IST LOG:  record with zero length at 0/5C44778
> 2014-06-01 18:29:49 IST LOG:  redo is not required
> 2014-06-01 18:29:50 IST LOG:  database system is ready to accept connections
> 2014-06-01 18:29:50 IST LOG:  autovacuum launcher started
> 2014-06-01 18:33:21 IST ERROR:  canceling statement due to user request
> 2014-06-01 18:33:21 IST ERROR:  canceling statement due to user request
> 2014-06-01 18:33:21 IST LOG:  received fast shutdown request

So who or what initiated the fast shutdown?

> 2014-06-01 18:33:21 IST LOG:  aborting any active transactions
> 2014-06-01 18:33:21 IST ERROR:  canceling statement due to user request
> 2014-06-01 18:33:21 IST ERROR:  canceling statement due to user request
> 2014-06-01 18:33:21 IST LOG:  autovacuum launcher shutting down
> 2014-06-01 18:33:21 IST LOG:  shutting down
> 2014-06-01 18:33:22 IST LOG:  database system is shut down
>


>
>
> psql log for another one machine
>
>
> 2014-06-02 09:50:52 IST FATAL:  the database system is starting up
> 2014-06-02 09:50:52 IST LOG:  database system was shut down at
> 2014-06-01 17:04:03 IST
> 2014-06-02 09:50:53 IST FATAL:  the database system is starting up
> 2014-06-02 09:50:53 IST FATAL:  the database system is starting up
> 2014-06-02 09:50:53 IST LOG:  database system is ready to accept connections
> 2014-06-02 09:50:53 IST LOG:  autovacuum launcher started
> 2014-06-02 10:22:56 IST LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.

This looks a firewall issue to me.

Do you know what client it is complaining about?

You might want to add information to the log entries to help with
debugging this.

See below for the options available:

http://www.postgresql.org/docs/9.3/interactive/runtime-config-logging.html

log_line_prefix (string)



>
> 2014-06-02 16:32:54 IST LOG:  could not reserve shared memory region
> (addr=029D0000) for child 000004D8: error code 1455
> 2014-06-02 16:32:54 IST LOG:  could not fork autovacuum worker process:
> A blocking operation was interrupted by a call to WSACancelBlockingCall.
>

I have seen this before, it is coming from Windows Sockets. The last
this was brought up there was no resolution.

Here is the previous thread, I would take a look at it to see if
anything looks similar. Also in the thread are links to previous reports
that might be worth looking at:

http://www.postgresql.org/message-id/2C0926ABD16BB641A8E2F11A5492004254713952D6@PHXCCRPRD01.adprod.bmc.com

> 2014-06-02 16:33:09 IST LOG:  server process (PID 5844) was terminated
> by exception 0xC000012D
> 2014-06-02 16:33:09 IST HINT:  See C include file "ntstatus.h" for a
> description of the hexadecimal value.

Well according to here:

http://msdn.microsoft.com/en-us/library/cc704588.aspx

This means:

{Out of Virtual Memory} Your system is low on virtual memory. To ensure
that Windows runs correctly, increase the size of your virtual memory
paging file. For more information, see Help.


> 2014-06-02 16:33:14 IST FATAL:  could not create shared memory segment:
> error code 1455
> 2014-06-02 16:33:14 IST DETAIL:  Failed system call was
> CreateFileMapping(size=145850368, name=Global/PostgreSQL:C:/Program
> Files/PostgreSQL/9.3/data).

Not sure about this one.
>
>
>
> Thanks in Advance
>
--
Adrian Klaver
adrian.klaver@aklaver.com