Thread: My Postgresql is inaccessible in Windows 8.1

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?

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?



>
>


--
Adrian Klaver
adrian.klaver@aklaver.com

On Wed, Aug 03, 2016 at 08:40:26AM -0300, 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
> ...
>
> What can be wrong?
>

Hi Edson,

Since it is Windows, have you checked your anti-virus engine setup.
They seem to like to insert themselves into everything by default.

Regards,
Ken

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"?

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

On 08/03/2016 08:47 AM, Melvin Davidson wrote:
>
>

>
>
>     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 <mailto:adrian.klaver@aklaver.com>
>
>
>
>     --
>     Sent via pgsql-general mailing list (pgsql-general@postgresql.org
>     <mailto: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.

Or Postgres is actually running and doing the below would not be good.

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

It is a good idea to verify before deleting.

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


--
Adrian Klaver
adrian.klaver@aklaver.com

On 08/03/2016 08:47 AM, Melvin Davidson wrote:
>
>

>
>
>     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 <mailto:adrian.klaver@aklaver.com>
>
>
>
>     --
>     Sent via pgsql-general mailing list (pgsql-general@postgresql.org
>     <mailto: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.

Or Postgres is actually running and doing the below would not be good.

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

It is a good idea to verify before deleting.

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


--
Adrian Klaver
adrian.klaver@aklaver.com

On 08/03/2016 10:15 AM, melvin6925 wrote:
> If Postgresql were running, then he would have not had the problem.
> Would he?


Except the original post was about Postgres running, but having periods
of slow down/inaccessibility. There was a later log entry showing the
pid conflict. Since I am not sure how we got from A to B and what the
current status is I would be hesitant to suggest just pulling a lock
file out from under what could be a running service. The effort to check
is negligible in relation to the benefits that accrue.

>
>
>
> Sent via the Samsung Galaxy S® 6, an AT&T 4G LTE smartphone
>
> -------- Original message --------
> From: Adrian Klaver <adrian.klaver@aklaver.com>
> Date: 8/3/16 13:01 (GMT-05:00)
> To: Melvin Davidson <melvin6925@gmail.com>
> Cc: "Edson F. Lidorio" <edson@openmailbox.org>,
> pgsql-general@postgresql.org
> Subject: Re: [GENERAL] My Postgresql is inaccessible in Windows 8.1
>
> On 08/03/2016 08:47 AM, Melvin Davidson wrote:
>>
>>
>
>>
>>
>>     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 <mailto:adrian.klaver@aklaver.com>
>>
>>
>>
>>     --
>>     Sent via pgsql-general mailing list (pgsql-general@postgresql.org
>>     <mailto: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.
>
> Or Postgres is actually running and doing the below would not be good.
>
>>
>> So just go ahead and delete /PostgreSQL/9.5/data/postmaster.pid and you
>> can then restart the PostgreSQL service.
>
> It is a good idea to verify before deleting.
>
>> *
>> --
>> *Melvin Davidson*
>> I reserve the right to fantasize.  Whether or not you
>> wish to share my fantasy is entirely up to you.
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com


--
Adrian Klaver
adrian.klaver@aklaver.com