Geoffrey <lists at serioustechnology.com> writes:
> Sorry for the shotgun blasts of messages.
>
> I'm checking the logs for my node2 and I see the following:
>
> 2007-12-12 20:44:32 EST FATAL  main: Cannot connect to local database
> -
> could not connect to server: D\uffff\uffff\uffffPVW
>         Is the server running on host "earth" and accepting
>         TCP/IP connections on port 5443?
>
> Now I'm all too familiar with this error from working with
> Postgres. What I think is going on is that when it tries to connect to
> the database running on the local machine, it's passing the host
> parameter and failing to connect.  I can duplicate this issue with
> psql command line.
>
> Problem is, I've tried setting the value to localhost, 127.0.0.1 and
> to a null string, but none of this works.
>
> What should the host value be in the conf file for starting a slon
> process on the local machine?

I'd be inclined to use a host name that isn't supposed to change.
Definitely NOT localhost or anything that assumes locality.

I expect there is some sort of pg_hba.conf problem here; not quite
sure.

> I guess I could simply start that slon process on the other node, but
> that doesn't make a lot of sense.

No, "solving" the issue that way will leave you with the problem that
when the slon wants to talk to the 'other' node, it will encounter
this problem again, breaking replication.

So you need to solve this right.
-- 
output = ("cbbrowne" "@" "linuxdatabases.info")
http://linuxdatabases.info/info/rdbms.html
We  all live in  a yellow  subroutine, a  yellow subroutine,  a yellow
subroutine...