Christopher Browne wrote:
> 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.

That was part of it.  I forgot to turn on 'tcpip_socket = true' as well 
as permitting connectivity on my subnet.

There was still an issue of the host name.  I've resolved this issue by 
placing the IP address of the machine into the field.  For some reason 
it has a problem connecting to the database on the same machine when I 
specify the host name.

For now, that get's me past that issue.  Problem is, I get the following 
when attempt 'slon_start 2':

2007-12-13 10:04:43 EST ERROR  cannot get sl_local_node_id - ERROR: 
schema "_esc_cluster" does not exist 2007-12-13 10:04:43 EST FATAL 
main: Node is not initialized properly - sleep 10s

-- 
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin