AND Are you sure this is the right pg_hba.conf? It's a common mistake for
people to install postgresql from .tar.gz file on a machine with an RPM
install of postgresql already in place and have these kinds of issues.
On 3 Oct 2003, Dave Cramer wrote:
> and you HUPPED postmaster after changing this?
>
> --dc--
> On Fri, 2003-10-03 at 10:32, Gordon Ross wrote:
> > OK, error from server.log:
> >
> > FATAL: No pg_hba.conf entry for host 192.168.24.108, user postgres, database switchboards
> >
> > entries in pg_hba.conf:
> >
> > # TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
> >
> > local all all trust
> > host all all 127.0.0.1 255.255.255.255 trust
> > host all all 192.168.24.108 255.255.255.255 trust
> >
> > 192.168.24.108 is my PCs IP address.
> >
> > Thanks,
> >
> > GTG
> >
> > >>> Tom Lane <tgl@sss.pgh.pa.us> 03/10/2003 15:24:47 >>>
> > Paul Thomas <paul@tmsl.demon.co.uk> writes:
> > > On 03/10/2003 11:35 Gordon Ross wrote:
> > >> OK. I increased it from the default of 32 to 128 and did a pg_ctl
> > >> reload. Still get the same problem. With server running (but doing
> > >> nothing), cannot connect from PC, I get the error message: "No
> > >> pg_hba.conf entry for host 192.168.24.108" - yet shutting down the
> > >> server process allows the PC to connect.
> >
> > > Wierd. It sounds like your server program is grabbing every possible
> > > tcp/ip connection to the db.
> >
> > I don't think that's the issue at all --- if it were an
> > out-of-connections situation, that error message would not be what comes
> > up. But I cannot think how the presence of one connection would affect
> > the ability of another to match a pg_hba.conf entry. What do you have
> > in pg_hba.conf, anyway?? Does the complaint message actually match your
> > PC's address? (And let's see the entire error message, please, not an
> > edited subset. Looking in the postmaster log to see if more is reported
> > there would be helpful too.)
> >
> > regards, tom lane
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 5: Have you checked our extensive FAQ?
> >
> > http://www.postgresql.org/docs/faqs/FAQ.html
> >
>