Skip site navigation (1) Skip section navigation (2)

Can't connect after restart

From: Audrey Bergeron-Morin <audreybmorin2(at)yahoo(dot)com>
To: pgsql-hackers-win32(at)postgresql(dot)org
Subject: Can't connect after restart
Date: 2005-07-27 20:03:44
Message-ID: 20050727200344.77387.qmail@web32610.mail.mud.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-hackers-win32
Hi all,

I've tried posting to the General list but it's been
almost a week and I didn't get an much of an answer...

I need help trying to identify what my problem is, and
I don't know pgSQL well enough to do much
troubleshooting myself.

pgSQL 8.0.3 install on WinXP SP1. The guys on the
General list told me I didn't need SP2.

Install goes fine, DB works perfectly until we restart
the machine, then we can't connect. First time
we thought something was corrupted because we had a
power outage, we uninstalled/reinstalled and it was
fine until, again, we decided to reboot. 

Our developer thought it might be a problem with
permissions, but that seems very unlikely. I'm
wondering if it might not be a firewall issue, but
then I can't figure out why the initial install would
be fine.

One hypothesis was the pid not getting deleted
properly, but the postmaster.pid is created and
deleted properly on startup/shutdown. There is no
postgresql.pid on my machine, but that's likely to be
normal if Postgress doesn't start properly.

Here are some other symptoms:

If I shut down the service, then try to start it up
again, sometimes it simply refuses to start again (bad
user/pwd). I have to input the password again to get
it to start. Seems like it's not remembering the info.

In the EventLog, I have one application error:
2005-07-26 16:27:57 LOG:  logger shutting down

That seems to happen every time I shut down the
service. There is no error on startup.

If I try to connect with pgAdmin III:

An error has occured:
could not connect to server: Connection refused
(0x0000274D/10061)
Is the server running on host "127.0.0.1" and
accepting TCP/IP connections on port 5432?

The answer to that is, apparently, no, because I can't
telnet 127.0.0.1 5432...

Trying to connect through pgAdminIII doesn't generate
either a pg log or an event log, so I have to guess
there is really nothing happening.

pgSQL logs seem normal (to my untrained eye)

----------------------------------------------
2005-07-26 16:24:52 LOG:  database system was shut
down at 2005-07-26 16:24:47 Est
2005-07-26 16:24:52 LOG:  checkpoint record is at
0/D33F08
2005-07-26 16:24:52 LOG:  redo record is at 0/D33F08;
undo record is at 0/0; shutdown TRUE
2005-07-26 16:24:52 LOG:  next transaction ID: 3313;
next OID: 33614
2005-07-26 16:24:52 LOG:  database system is ready
2005-07-26 16:27:56 LOG:  received fast shutdown
request
2005-07-26 16:27:56 LOG:  shutting down
2005-07-26 16:27:56 LOG:  database system is shut down
2005-07-26 16:27:57 LOG:  logger shutting down
---------------------------------------------
2005-07-26 16:28:17 LOG:  database system was shut
down at 2005-07-26 16:27:56 Est
2005-07-26 16:28:17 LOG:  checkpoint record is at
0/D33F48
2005-07-26 16:28:17 LOG:  redo record is at 0/D33F48;
undo record is at 0/0; shutdown TRUE
2005-07-26 16:28:17 LOG:  next transaction ID: 3313;
next OID: 33614
2005-07-26 16:28:17 LOG:  database system is ready
-----------------------------------------------

I had also sent a bunch of logs made after
In any case, I copied the logs written since we
rebooted (around 14:05) below. 

The first log was named 
postgresql-2005-07-12_000000.log and was empty. That's
the first one written on the day of the first
reinstall. Following is every log, up to and after the
point where we rebooted at 14:05.

---------------------------------------------------
2005-07-21 11:01:25 LOG:  database system was
interrupted at 2005-07-11 14:24:13 Est
2005-07-21 11:01:25 LOG:  checkpoint record is at
0/D33C48
2005-07-21 11:01:25 LOG:  redo record is at 0/D33C48;
undo record is at 0/0; shutdown FALSE
2005-07-21 11:01:25 LOG:  next transaction ID: 3313;
next OID: 33614
2005-07-21 11:01:25 LOG:  database system was not
properly shut down; automatic recovery in progress
2005-07-21 11:01:25 LOG:  record with zero length at
0/D33C88
2005-07-21 11:01:25 LOG:  redo is not required
2005-07-21 11:01:25 LOG:  database system is ready
2005-07-21 11:02:04 FATAL:  password authentication
failed for user "jbondc"
2005-07-21 11:02:05 FATAL:  password authentication
failed for user "jbondc"
2005-07-21 11:02:06 FATAL:  password authentication
failed for user "jbondc"
2005-07-21 11:02:07 FATAL:  password authentication
failed for user "jbondc"
2005-07-21 11:02:38 FATAL:  password authentication
failed for user "jbondc"
2005-07-21 11:02:38 FATAL:  password authentication
failed for user "jbondc"
2005-07-21 11:02:39 FATAL:  password authentication
failed for user "jbondc"
2005-07-21 11:02:40 FATAL:  password authentication
failed for user "jbondc"
2005-07-21 11:03:18 FATAL:  password authentication
failed for user "jbondc"
2005-07-21 14:04:53 LOG:  received fast shutdown
request
2005-07-21 14:04:54 LOG:  shutting down
2005-07-21 14:04:54 LOG:  database system is shut down
2005-07-21 14:04:58 LOG:  logger shutting down
********************************
2005-07-21 11:02:36 LOG:  database system was
interrupted at 2005-07-21 11:01:25 Est
2005-07-21 11:02:36 LOG:  checkpoint record is at
0/D33C88
2005-07-21 11:02:36 LOG:  redo record is at 0/D33C88;
undo record is at 0/0; shutdown TRUE
2005-07-21 11:02:36 LOG:  next transaction ID: 3313;
next OID: 33614
2005-07-21 11:02:36 LOG:  database system was not
properly shut down; automatic recovery in progress
2005-07-21 11:02:36 LOG:  record with zero length at
0/D33CC8
2005-07-21 11:02:36 LOG:  redo is not required
2005-07-21 11:02:36 LOG:  database system is ready
2005-07-21 14:04:53 LOG:  received fast shutdown
request
2005-07-21 14:04:54 LOG:  shutting down
2005-07-21 14:04:55 LOG:  database system is shut down
2005-07-21 14:04:58 LOG:  logger shutting down
*********************************
2005-07-21 14:06:10 LOG:  database system was shut
down at 2005-07-21 14:04:54 Est
2005-07-21 14:06:10 LOG:  checkpoint record is at
0/D33D48
2005-07-21 14:06:10 LOG:  redo record is at 0/D33D48;
undo record is at 0/0; shutdown TRUE
2005-07-21 14:06:10 LOG:  next transaction ID: 3313;
next OID: 33614
2005-07-21 14:06:11 LOG:  database system is ready
2005-07-21 14:28:28 LOG:  received fast shutdown
request
2005-07-21 14:28:28 LOG:  shutting down
2005-07-21 14:28:28 LOG:  database system is shut down
2005-07-21 14:28:28 LOG:  logger shutting down
***********************************
2005-07-21 14:29:10 LOG:  database system was shut
down at 2005-07-21 14:28:28 Est
2005-07-21 14:29:10 LOG:  checkpoint record is at
0/D33D88
2005-07-21 14:29:10 LOG:  redo record is at 0/D33D88;
undo record is at 0/0; shutdown TRUE
2005-07-21 14:29:10 LOG:  next transaction ID: 3313;
next OID: 33614
2005-07-21 14:29:10 LOG:  database system is ready
2005-07-21 14:29:54 LOG:  received fast shutdown
request
2005-07-21 14:29:54 LOG:  shutting down
2005-07-21 14:29:54 LOG:  database system is shut down
2005-07-21 14:29:55 LOG:  logger shutting down
****************************************
2005-07-21 14:29:56 LOG:  database system was shut
down at 2005-07-21 14:29:54 Est
2005-07-21 14:29:56 LOG:  checkpoint record is at
0/D33DC8
2005-07-21 14:29:56 LOG:  redo record is at 0/D33DC8;
undo record is at 0/0; shutdown TRUE
2005-07-21 14:29:56 LOG:  next transaction ID: 3313;
next OID: 33614
2005-07-21 14:29:56 LOG:  database system is ready
2005-07-21 15:04:50 LOG:  received fast shutdown
request
2005-07-21 15:04:50 LOG:  shutting down
2005-07-21 15:04:50 LOG:  database system is shut down
2005-07-21 15:04:52 LOG:  logger shutting down
*************************************
2005-07-21 15:06:03 LOG:  database system was shut
down at 2005-07-21 15:04:50 Est
2005-07-21 15:06:03 LOG:  checkpoint record is at
0/D33E48
2005-07-21 15:06:03 LOG:  redo record is at 0/D33E48;
undo record is at 0/0; shutdown TRUE
2005-07-21 15:06:03 LOG:  next transaction ID: 3313;
next OID: 33614
2005-07-21 15:06:03 LOG:  database system is ready
---------------------------------------------------

Thanks for any help you can provide.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

pgsql-hackers-win32 by date

Next:From: Magnus HaganderDate: 2005-07-27 20:38:26
Subject: Re: Can't connect after restart
Previous:From: Magnus HaganderDate: 2005-07-27 20:02:54
Subject: Re: Query on support for trigger functions defined in a Shared library in Windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group