Обсуждение: BUG #6118: Server doesn't listen
The following bug has been logged online:
Bug reference: 6118
Logged by: Shahnawaz Shaikh
Email address: Shahnawaz.shaikh@accenture.com
PostgreSQL version: 8.4
Operating system: Windows server 2003
Description: Server doesn't listen
Details:
When i try to start the PostgreSQL 8.4 server, below issue is encountered,
System error 1069 has occurred.
The service did not start due to a logon failure.
The start command returned an error <2>
Press <return> to continue....
While, when i try to connect the PostgreSQL 8.4 from pgAdmin III i get the
below error on entering password
Server doesn't listen
The server doesn't accept connections: the connection library reports
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?
If you encounter this message, please check if the server you're trying to
contact is actually running PostgreSQL on the given port. Test if you have
network connectivity from your client to the server host using ping or
equivalent tools. Is your network / VPN / SSH tunnel / firewall configured
correctly?
For security reasons, PostgreSQL does not listen on all available IP
addresses on the server machine initially. In order to access the server
over the network, you need to enable listening on the address first.
For PostgreSQL servers starting with version 8.0, this is controlled using
the "listen_addresses" parameter in the postgresql.conf file. Here, you can
enter a list of IP addresses the server should listen on, or simply use '*'
to listen on all available IP addresses. For earlier servers (Version 7.3 or
7.4), you'll need to set the "tcpip_socket" parameter to 'true'.
You can use the postgresql.conf editor that is built into pgAdmin III to
edit the postgresql.conf configuration file. After changing this file, you
need to restart the server process to make the setting effective.
If you double-checked your configuration but still get this error message,
it's still unlikely that you encounter a fatal PostgreSQL misbehaviour. You
probably have some low level network connectivity problems (e.g. firewall
configuration). Please check this thoroughly before reporting a bug to the
PostgreSQL community.
My Postgresql.conf has the below settings:
# - Connection Settings -
listen_addresses = '*' # what IP address(es) to listen on;
# comma-separated list of addresses;
# defaults to 'localhost', '*' = all
# (change requires restart)
port = 5432 # (change requires restart)
max_connections = 100 # (change requires restart)
My pg_hba.conf has below configuration:
# TYPE DATABASE USER CIDR-ADDRESS METHOD
# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
#host all all ::1/128 md5
Kindly do the needful.
On 07/13/11 10:38 PM, Shahnawaz Shaikh wrote: > The following bug has been logged online: > > Bug reference: 6118 > Logged by: Shahnawaz Shaikh > Email address: Shahnawaz.shaikh@accenture.com > PostgreSQL version: 8.4 > Operating system: Windows server 2003 > Description: Server doesn't listen > Details: > > When i try to start the PostgreSQL 8.4 server, below issue is encountered, > > System error 1069 has occurred. > The service did not start due to a logon failure. > The start command returned an error<2> > Press<return> to continue.... > > While, when i try to connect the PostgreSQL 8.4 from pgAdmin III i get the > below error on entering password > > Server doesn't listen this is not a bug, it appears to be a configuration error, the logon credentials given in the Windows Service do not match the appropriate account, so the service isn't starting, since the servce isn't running, the client can't connect. This sort of issue would best be handled on the pgsql-general email list.... you need to properly configure the postgresql service in the Windows Service manager, I believe I would go into Administration Tools -> User Manager, find the postgres account, set a new reasonably complex password, then go into the Windows Service manager, find the postgresql service, and in its properties, on the Log On tab, set the user and password to match what you set in User Manager. This should have been done automatically by the windows installer. After you do this, you should be able to START the service. note this password you set in User Manager has nothing to do with the password (if any) for the postgres role you use to log onto the database server for administration. -- john r pierce N 37, W 122 santa cruz ca mid-left coast
SGkgSm9obiwNCg0KVGh4IGZvciB5b3VyIGhlbHAuDQoNClRoYW5rcyAmIFJl Z2FyZHMsDQpTaGFobmF3YXogU2hhaWtoDQpBY2NlbnR1cmUgU2VydmljZXMg UHZ0IEx0ZC4NCklEQyBSUFNJDQpNb2I6ICs5MSA5ODE5IDEzMyA5MjYNCk9m ZjogICArMjIgNDIwIDIxMDE5DQpFbWFpbDogc2hhaG5hd2F6LnNoYWlraEBh Y2NlbnR1cmUuY29tDQpBSU06IHNoYWhuYXdhejFzaGFpa2ggfCBNU046IHNo YWhuYXdhei5zdW4NCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K RnJvbTogSm9obiBSIFBpZXJjZSBbbWFpbHRvOnBpZXJjZUBob2dyYW5jaC5j b21dDQpTZW50OiBUaHVyc2RheSwgSnVseSAxNCwgMjAxMSAxOjA5IFBNDQpU bzogU2hhaWtoLCBTaGFobmF3YXoNCkNjOiBwZ3NxbC1idWdzQHBvc3RncmVz cWwub3JnDQpTdWJqZWN0OiBSZTogW0JVR1NdIEJVRyAjNjExODogU2VydmVy IGRvZXNuJ3QgbGlzdGVuDQoNCk9uIDA3LzEzLzExIDEwOjM4IFBNLCBTaGFo bmF3YXogU2hhaWtoIHdyb3RlOg0KPiBUaGUgZm9sbG93aW5nIGJ1ZyBoYXMg YmVlbiBsb2dnZWQgb25saW5lOg0KPg0KPiBCdWcgcmVmZXJlbmNlOiAgICAg IDYxMTgNCj4gTG9nZ2VkIGJ5OiAgICAgICAgICBTaGFobmF3YXogU2hhaWto DQo+IEVtYWlsIGFkZHJlc3M6ICAgICAgU2hhaG5hd2F6LnNoYWlraEBhY2Nl bnR1cmUuY29tDQo+IFBvc3RncmVTUUwgdmVyc2lvbjogOC40DQo+IE9wZXJh dGluZyBzeXN0ZW06ICAgV2luZG93cyBzZXJ2ZXIgMjAwMw0KPiBEZXNjcmlw dGlvbjogICAgICAgIFNlcnZlciBkb2Vzbid0IGxpc3Rlbg0KPiBEZXRhaWxz Og0KPg0KPiBXaGVuIGkgdHJ5IHRvIHN0YXJ0IHRoZSBQb3N0Z3JlU1FMIDgu NCBzZXJ2ZXIsIGJlbG93IGlzc3VlIGlzIGVuY291bnRlcmVkLA0KPg0KPiBT eXN0ZW0gZXJyb3IgMTA2OSBoYXMgb2NjdXJyZWQuDQo+IFRoZSBzZXJ2aWNl IGRpZCBub3Qgc3RhcnQgZHVlIHRvIGEgbG9nb24gZmFpbHVyZS4NCj4gVGhl IHN0YXJ0IGNvbW1hbmQgcmV0dXJuZWQgYW4gZXJyb3I8Mj4NCj4gUHJlc3M8 cmV0dXJuPiAgdG8gY29udGludWUuLi4uDQo+DQo+IFdoaWxlLCB3aGVuIGkg dHJ5IHRvIGNvbm5lY3QgdGhlIFBvc3RncmVTUUwgOC40IGZyb20gcGdBZG1p biBJSUkgaSBnZXQgdGhlDQo+IGJlbG93IGVycm9yIG9uIGVudGVyaW5nIHBh c3N3b3JkDQo+DQo+IFNlcnZlciBkb2Vzbid0IGxpc3Rlbg0KDQp0aGlzIGlz IG5vdCBhIGJ1ZywgaXQgYXBwZWFycyB0byBiZSBhIGNvbmZpZ3VyYXRpb24g ZXJyb3IsIHRoZSBsb2dvbg0KY3JlZGVudGlhbHMgZ2l2ZW4gaW4gdGhlIFdp bmRvd3MgU2VydmljZSBkbyBub3QgbWF0Y2ggdGhlIGFwcHJvcHJpYXRlDQph Y2NvdW50LCBzbyB0aGUgc2VydmljZSBpc24ndCBzdGFydGluZywgc2luY2Ug dGhlIHNlcnZjZSBpc24ndCBydW5uaW5nLA0KdGhlIGNsaWVudCBjYW4ndCBj b25uZWN0LiAgICBUaGlzIHNvcnQgb2YgaXNzdWUgd291bGQgYmVzdCBiZSBo YW5kbGVkIG9uDQp0aGUgcGdzcWwtZ2VuZXJhbCBlbWFpbCBsaXN0Li4uLg0K DQoNCnlvdSBuZWVkIHRvIHByb3Blcmx5IGNvbmZpZ3VyZSB0aGUgcG9zdGdy ZXNxbCBzZXJ2aWNlIGluIHRoZSBXaW5kb3dzDQpTZXJ2aWNlIG1hbmFnZXIs IEkgYmVsaWV2ZSBJIHdvdWxkIGdvIGludG8gQWRtaW5pc3RyYXRpb24gVG9v bHMgLT4gVXNlcg0KTWFuYWdlciwgZmluZCB0aGUgcG9zdGdyZXMgYWNjb3Vu dCwgc2V0IGEgbmV3IHJlYXNvbmFibHkgY29tcGxleA0KcGFzc3dvcmQsIHRo ZW4gZ28gaW50byB0aGUgV2luZG93cyBTZXJ2aWNlIG1hbmFnZXIsIGZpbmQg dGhlIHBvc3RncmVzcWwNCnNlcnZpY2UsIGFuZCBpbiBpdHMgcHJvcGVydGll cywgb24gdGhlIExvZyBPbiB0YWIsIHNldCB0aGUgdXNlciBhbmQNCnBhc3N3 b3JkIHRvIG1hdGNoIHdoYXQgeW91IHNldCBpbiBVc2VyIE1hbmFnZXIuICAg ICBUaGlzIHNob3VsZCBoYXZlDQpiZWVuIGRvbmUgYXV0b21hdGljYWxseSBi eSB0aGUgd2luZG93cyBpbnN0YWxsZXIuICBBZnRlciB5b3UgZG8gdGhpcywN CnlvdSBzaG91bGQgYmUgYWJsZSB0byBTVEFSVCB0aGUgc2VydmljZS4NCg0K bm90ZSB0aGlzIHBhc3N3b3JkIHlvdSBzZXQgaW4gVXNlciBNYW5hZ2VyIGhh cyBub3RoaW5nIHRvIGRvIHdpdGggdGhlDQpwYXNzd29yZCAoaWYgYW55KSBm b3IgdGhlIHBvc3RncmVzIHJvbGUgeW91IHVzZSB0byBsb2cgb250byB0aGUg ZGF0YWJhc2UNCnNlcnZlciBmb3IgYWRtaW5pc3RyYXRpb24uDQoNCg0KDQoN Ci0tDQpqb2huIHIgcGllcmNlICAgICAgICAgICAgICAgICAgICAgICAgICAg IE4gMzcsIFcgMTIyDQpzYW50YSBjcnV6IGNhICAgICAgICAgICAgICAgICAg ICAgICAgIG1pZC1sZWZ0IGNvYXN0DQoNCg0KDQpUaGlzIG1lc3NhZ2UgaXMg Zm9yIHRoZSBkZXNpZ25hdGVkIHJlY2lwaWVudCBvbmx5IGFuZCBtYXkgY29u dGFpbiBwcml2aWxlZ2VkLCBwcm9wcmlldGFyeSwgb3Igb3RoZXJ3aXNlIHBy aXZhdGUgaW5mb3JtYXRpb24uICBJZiB5b3UgaGF2ZSByZWNlaXZlZCBpdCBp biBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGltbWVkaWF0ZWx5 IGFuZCBkZWxldGUgdGhlIG9yaWdpbmFsLiAgQW55IG90aGVyIHVzZSBvZiB0 aGUgZW1haWwgYnkgeW91IGlzIHByb2hpYml0ZWQuDQo=