"Trinath Somanchi" <trinaths at intoto.com> writes:
> I have installed 1.2.11 version of slony-1 with perl scripts enabled .
>
> I have initialized the database . and modified the slony_tools.conf to =
>
> fit my specifications ,
>
> Then I executed  ./perltools/slonik_init_cluster   and
> /perltools/slonik_store_node --config =
>
> /home/mss_user/masterdb/etc/slon_tools.conf  node1  =
>
>
> and after these two executions , I executed ./perltools/slon_start 1
>
> But Slony did not start .
>
> I get the following error :
>
> 2007-09-21 16:28:53 IST CONFIG main: slon version 1.2.11 starting up
> 2007-09-21 16:28:53 IST DEBUG2 slon: watchdog process started
> 2007-09-21 16:28:53 IST DEBUG2 slon: watchdog ready - pid =3D 25083
> 2007-09-21 16:28:53 IST DEBUG2 slon: worker process created - pid =3D 25122
> 2007-09-21 16:28:53 IST ERROR  cannot get sl_local_node_id - ERROR:  =
>
> schema "_public" does not exist
> 2007-09-21 16:28:53 IST FATAL  main: Node is not initialized properly - =
>
> sleep 10s
>
>
> How can I troubleshoot this error . I have searched google for the same =
>
> ,, in some of the forms they said to execute "slonik_init_cluster " and =
>
> "slonik_store_node" and then start the slon ..
>
> I have done the same as described in the google search , but =
>
> , I get the same error .

Well, it appears that that one or the other of the nodes did not get
initialized.  And as long as that is the case, none of the things that
depend on the node being properly initialized will work.

Usually, it's a useful sort of thing to simplify things until you can
identify exactly which step didn't work.

The simplest thing would be to run minimal slonik scripts to perform
the actions, step by step, and see when one of those scripts fails,
which presumably some step did.  At that point, the error messages
ought to give some clue as to what failure caused your problem, and
perhaps clues as to how to fix it...
-- 
let name="cbbrowne" and tld="cbbrowne.com" in name ^ "@" ^ tld;;
http://cbbrowne.com/info/linuxxian.html
If you add a couple of i's to Microsoft's stock ticker symbol, you get
'misfit'.  This is, of course, not a coincidence.