> -----Original Message-----
> If you look at the "slon_kill" script in the altperl directory, you'll
> find that it takes much that approach.  We have a script that we use
> in production which starts with "kill -2", waits a bit, does "kill
> -3", and if the process persists, "kill -9".
> 
> If you're monitoring logs, it's probably preferable to start with
> "less intense" termination parameters so that there's a chance for the
> process to die a bit cleanly...

Noted. Less brutal :)

> > Other than create a db on the slave machine, do I need a snapshot of
> > the master? Is this stage optional?
> 
> You need the schema from the master.  I'm not quite sure what you're
> indicating by "stage"...

schema with no data?

> > Slon seems to be outputting the following and doesn't seem to be
doing
> > anything else. Whats it waiting for? I've done an insert no the
master
> > and nothing seems to be coming through and I've used the same
starting
> > point as the master.
> >
> > CONFIG main: slon version 1.0.5 starting up
> > CONFIG main: local node id = 1
> > CONFIG main: loading current cluster configuration
> > CONFIG storeNode: no_id=2 no_comment='Node 2'
> > CONFIG storePath: pa_server=2 pa_client=1
> > pa_conninfo="dbname=prod_provision host=154.8.2.51 user=pgsql"
> > pa_connretry=10
> > CONFIG storeListen: li_origin=2 li_receiver=1 li_provider=2
> > CONFIG storeSet: set_id=1 set_origin=1 set_comment=''
> > CONFIG main: configuration complete - starting threads
> > CONFIG enableNode: no_id=2
> 
> This is what both nodes are reporting???

Yes very similar, that's on the master node. Below is slave node. 

CONFIG main: slon version 1.0.5 starting up
CONFIG main: local node id = 2
CONFIG main: loading current cluster configuration
CONFIG storeNode: no_id=1 no_comment='Primary Node 1'
CONFIG storePath: pa_server=1 pa_client=2
pa_conninfo="dbname=prod_provision host=154.8.2.50 user=pgsql"
pa_connretry=10
CONFIG storeListen: li_origin=1 li_receiver=2 li_provider=1
CONFIG storeSet: set_id=1 set_origin=1 set_comment=''
WARN   remoteWorker_wakeup: node 1 - no worker thread
CONFIG main: configuration complete - starting threads
CONFIG enableNode: no_id=1

> That seems consistent with the node being devoid of configuration
> about the nodes.

I'll go through the list of things you've listed and see how it goes.

Thanks for all the help!

Jase