Geoffrey <lists at serioustechnology.com> writes:
> Christopher Browne wrote:
>> Geoffrey <lists at serioustechnology.com> writes:
>>> 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
>> Well, apparently the "store node" for node #2 didn't get done...
>
> Is this possibly an environment issue?  Configuration problem?  I'm
> not sure what you mean by the 'store node.'

Configuration, of a sort.

Setting up replication involves, at the slonik level, the following steps:

- Initializing the first node in the cluster (e.g. - INIT CLUSTER)
- Initializing other nodes (e.g. - STORE NODE), which is where things evidently broke down
- Setting up communications between nodes (STORE PATH)
- Setting up a replication set
  - CREATE SET (to begin setup)
  - SET ADD TABLE (to add tables in)
  - SET ADD SEQUENCE (to add in sequences)
- Then subscribing nodes to that set - SUBSCRIBE SET

If you see the message "Node is not initialized properly", that means
that either an INIT CLUSTER or a STORE NODE did not take place.
-- 
let name="cbbrowne" and tld="linuxdatabases.info" in String.concat "@" [name;tld];;
http://linuxdatabases.info/info/x.html
If one synchronized swimmer drowns, do the rest have to drown too?