Re: My Postgresql is inaccessible in Windows 8.1 - Mailing list pgsql-general

From Melvin Davidson
Subject Re: My Postgresql is inaccessible in Windows 8.1
Date
Msg-id CANu8FizCZqN19T93DH8WX8RKB1ZvZZFraRVLah4O1mevnjpTDg@mail.gmail.com
Whole thread Raw
In response to Re: My Postgresql is inaccessible in Windows 8.1  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: My Postgresql is inaccessible in Windows 8.1  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general


On Wed, Aug 3, 2016 at 11:23 AM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 08/03/2016 07:40 AM, Edson F. Lidorio wrote:
Em 2016-08-03 09:56, Adrian Klaver escreveu:
On 08/03/2016 04:40 AM, Edson F. Lidorio wrote:
Good Morning,

Constantly my Postgresql is inaccessible, recording the following
message in the log.
I'm using Windows 8.1 and PostgreSQL 9.5


2016-08-02 17:05:59 BRT FATAL:  the database system is starting up
2016-08-02 17:05:59 BRT LOG:  database system was not properly shut
down; automatic recovery in progress
2016-08-02 17:05:59 BRT LOG:  invalid record length at 0/42C0148
2016-08-02 17:05:59 BRT LOG:  redo is not required
2016-08-02 17:05:59 BRT LOG:  MultiXact member wraparound protections
are now enabled
2016-08-02 17:05:59 BRT LOG:  database system is ready to accept
connections
2016-08-02 17:06:00 BRT LOG:  autovacuum launcher started

2016-08-03 08:18:44 BRT WARNING:  worker took too long to start;
canceled
2016-08-03 08:19:44 BRT WARNING:  worker took too long to start;
canceled
2016-08-03 08:20:44 BRT WARNING:  worker took too long to start;
canceled
2016-08-03 08:21:44 BRT WARNING:  worker took too long to start;
canceled
2016-08-03 08:22:44 BRT WARNING:  worker took too long to start;
canceled
2016-08-03 08:23:44 BRT WARNING:  worker took too long to start;
canceled
2016-08-03 08:24:44 BRT WARNING:  worker took too long to start;
canceled
2016-08-03 08:26:44 BRT WARNING:  worker took too long to start;
canceled
2016-08-03 08:28:44 BRT WARNING:  worker took too long to start;
canceled
2016-08-03 08:30:44 BRT WARNING:  worker took too long to start;
canceled
2016-08-03 08:31:45 BRT WARNING:  worker took too long to start;
canceled


What can be wrong?

There is some sort of resource constraint preventing Postgres from
handling all its requests.

So:

Do you have any additional extensions/modules installed in Postgres?

What are the hardware specifications for the machine, memory, CPU,
storage,etc?

What is the work load on the Postgres server?

What does the system show for load during this time?

What do the system logs show?





There is some sort of resource constraint preventing Postgres from
handling all its requests.
I did not find anything strange. This problem also occurs with Windows 7 64

So: Windows 8.1 Pro

Do you have any additional extensions/modules installed in Postgres?
I have, Default Installation

What are the hardware specifications for the machine, memory, CPU,
storage,etc?
Intel Core I5 CPU 3.00 GHZ 8GB memory

What is the work load on the Postgres server?
The workload for this server is small, only a web application with few
users.

What does the system show for load during this time?
Waiting time out to start the server

What do the system logs show?
2016-08-03 08:42:39 BRT FATAL:  lock file "postmaster.pid" already exists
2016-08-03 08:42:39 BRT TIP: Another postmaster (PID 2968) is running
under the data directory "C: / Program Files / PostgreSQL / 9.5 / data"?


Well this looks like the Postgres log and it is showing that you are trying to start Postgres when there is already another instance of Postgres running.

What does the Task Manager show is running?

When I was talking about system logs I meant the OS logs, I was not clear on that point.


--
Adrian Klaver
adrian.klaver@aklaver.com



--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

> 2016-08-02 17:05:59 BRT LOG:  database system was not properly shut
> down; automatic recovery in progress

<2016-08-03 08:42:39 BRT FATAL:  lock file "postmaster.pid" already exists
>2016-08-03 08:42:39 BRT TIP: Another postmaster (PID 2968) is running under the data directory "C: / Program >Files / PostgreSQL / 9.5 / data"?

These errors point to the source of your problem. When the database is shutdown imporperly
(as in pulling the plug or manual power down), you often get left with the postmaster.pid file not beeing deleted.

So just go ahead and delete /PostgreSQL/9.5/data/postmaster.pid and you can then restart the PostgreSQL service.

--
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: My Postgresql is inaccessible in Windows 8.1
Next
From: Jeff Janes
Date:
Subject: Re: WAL directory size calculation