Re: [GENERAL] could not bind IPv4 socket

2009-05-04 Thread Grzegorz Buś
could not bind IPv4 socket Importance: High On Monday 04 May 2009 4:29:27 am Grzegorz Buś wrote: > When I run separately start/stop commands I still get "could not bind > socket" message: > > # service postgresql stop > Stopping postgresql service:

Re: [GENERAL] could not bind IPv4 socket

2009-05-04 Thread Adrian Klaver
On Monday 04 May 2009 4:29:27 am Grzegorz Buś wrote: > When I run separately start/stop commands I still get "could not bind > socket" message: > > # service postgresql stop > Stopping postgresql service: [ OK ] > # netstat -plunt | grep 5432 > # ps -A | grep postmas

Re: [GENERAL] could not bind IPv4 socket

2009-05-04 Thread Grzegorz Buś
not, wait a few seconds and retry. -- Kind Regards, Grzegorz Bus -Original Message- From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Vladimir N. Indik Sent: Monday, May 04, 2009 10:15 AM To: pgsql-general@postgresql.org Subject: Re: [GENERAL]

Re: [GENERAL] could not bind IPv4 socket

2009-05-04 Thread Grzegorz Buś
> > # cat /var/lib/pgsql/data/pgstartup.log > > LOG: could not bind IPv4 socket: Address already in use > > HINT: Is another postmaster already running on port 5432? If not, > wait a > > few seconds and retry. > > Did you heed the HINT and see if there is another instance of Postgres > running?

Re: [GENERAL] could not bind IPv4 socket

2009-05-04 Thread Vladimir N. Indik
Try this command separately. # service postgresql stop and then # service postgresql start On Воскресенье 03 мая 2009 23:01:24 Grzegorz Buś wrote: > postgresql restart > Stopping postgresql service: [ OK ] > Starting postgresql service:

Re: [GENERAL] could not bind IPv4 socket

2009-05-03 Thread Adrian Klaver
On Sunday 03 May 2009 12:01:24 pm Grzegorz Buś wrote: > > listen_addresses gets set to the IP address of the server itself, the > > IP address it is "listening" for input on. Since you're giving it a > > remote address, that's why it can't create a socket to listen there. > > > > There is a second

Re: [GENERAL] could not bind IPv4 socket

2009-05-03 Thread Grzegorz Buś
> listen_addresses gets set to the IP address of the server itself, the > IP address it is "listening" for input on. Since you're giving it a > remote address, that's why it can't create a socket to listen there. > There is a second file here, pg_hba.conf, that filters down who can > connect t

Re: [GENERAL] could not bind IPv4 socket

2009-05-01 Thread Craig Ringer
Greg Smith wrote: > Normal practice here is to set: > > listen_address='*' > > So that the server is remotely accessible from all of its interfaces, > and then you can do all filtering of who can connect just via > pg_hba.conf instead. Just to expand on that: listen_addresses is usually used i

Re: [GENERAL] could not bind IPv4 socket

2009-04-30 Thread Greg Smith
On Thu, 30 Apr 2009, Grzegorz Bu? wrote: listen_addresses = 'localhost,XXX.XXX.XXX.XXX' where XXX.XXX.XXX.XXX is IP address of remote client that I want to be able to use PostgreSQL server. Port is default. listen_addresses gets set to the IP address of the server itself, the IP address it i

[GENERAL] could not bind IPv4 socket

2009-04-30 Thread Grzegorz Buś
Hi, I'm using Centos 4.7 and after upgrading PostgreSQL to version 8.3.7 (from ver. 7.4) via yum I cannot connect to my postgres server from remote hosts. I know that for PostgreSQL servers starting with version 8.0 remote connections can only be set in postgresql.conf allowing them in "l

[GENERAL] could not bind IPv4 socket: Address already in use

2004-06-07 Thread Eric . Hillmuth
I'm just getting started with postgresql and things are going pretty well. However, I seem to be having trouble connecting to my database via TCP/IP. I'm assuming that my problems are related to the message I get at startup (using "postmaster -D data - i"). The postmaster starts but produces th