Re: Can't start Postgres anymore - Mailing list pgsql-general

From Merlin Moncure
Subject Re: Can't start Postgres anymore
Date
Msg-id b42b73150802280538h5de50c50x68683db0ecdd4772@mail.gmail.com
Whole thread Raw
In response to Can't start Postgres anymore  ("George Younan" <georgesamb@hotmail.com>)
Responses Re: Can't start Postgres anymore
List pgsql-general
On Wed, Feb 27, 2008 at 4:08 PM, George Younan <georgesamb@hotmail.com> wrote:
> I have Postgres installed as a service on Windows xp pro. It has been
> working fine but suddenly i couldn't start it anymore. I looked in different
> forums for a similar problem but didn't find any solution sofar. So any help
> is very appreciated. one more thing to say is that i am a beginner with
> Postgres and don't have much administrative experience...
> As i said above, i can't start my Postgres anymore. I always get the error
> message "could not connect to server: Connection refused
> (0x0000274D/10061)Is the server running on host "???" and accepting TCP/IP
> connections on port 5432?".
> I checked if the service is running, but it wasn't running. I tried to start
> ist but i couldn't. Doing this from the console i got the following error:
> "C:\Programme\PostgreSQL\8.1\bin>pg_ctl.exe runservice -N "pgsql-8.1" -D
> "C:\Programme\PostgreSQL\8.1\data\"
> pg_ctl: could not start service "pgsql-8.1": error code 1063"
>
>  I chekced postgres.conf and the configuration is as follows:
>     # - Connection Settings -
>     listen_addresses = 'localhost'
>     port = 5432
>     max_connections = 100
>
> The last log file is:
> 2008-02-08 07:40:38 LOG:  could not connect socket for statistics collector:
> Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die
> Verbindung verweigerte.
>
>
> 2008-02-08 07:40:38 LOG:  disabling statistics collector for lack of working
> socket
> 2008-02-08 07:40:38 WARNING:  autovacuum not started because of
> misconfiguration
> 2008-02-08 07:40:38 HINT:  Enable options "stats_start_collector" and
> "stats_row_level".
> 2008-02-08 07:40:40 LOG:  database system was shut down at 2008-02-08
> 07:37:57 Westeuropäische Normalzeit
> 2008-02-08 07:40:40 LOG:  checkpoint record is at 0/45AE50
> 2008-02-08 07:40:40 LOG:  redo record is at 0/45AE50; undo record is at 0/0;
> shutdown TRUE
> 2008-02-08 07:40:40 LOG:  next transaction ID: 5100; next OID: 16515
> 2008-02-08 07:40:40 LOG:  next MultiXactId: 1; next MultiXactOffset: 0
> 2008-02-08 07:40:41 LOG:  database system is ready
> 2008-02-08 07:40:41 LOG:  transaction ID wrap limit is 2147484148, limited
> by database "postgres"

>  I'm using Zonealarm firewall but Postgres is authorized on 127.0.0.1:5432.
> It's been working fine for the last month since installtion and i didn't
> change any configuration. I stopped both zonealarm and the windows firewall
> but still success, so i guess it's not a firewall problem.

I highly doubt you have any data loss.  This line makes me suspect the
firewall:
> 2008-02-08 07:40:38 LOG:  disabling statistics collector for lack of working
> socket

Also the log suggests the database is running:
> 2008-02-08 07:40:41 LOG:  database system is ready

ISTM the problem is basically a connection issue.  Try changing
listen_addresses = 'localhost'
to
listen_addresses = '*'

(this will allow postgresql to serve connections from any interface on
the box).   Also try as Gevik suggested running pg_ctl directly.

merlin

pgsql-general by date:

Previous
From: Michael Glaesemann
Date:
Subject: Re: UUID-OSSP for windows.
Next
From: "A B"
Date:
Subject: what happens if something goes wrong in transaction?