On Thu, 29 Sep 2011, francescoboccacci at libero.it wrote:

> Hi, i solved the problem by installed old slony version. Now i have installed
> slony 2.0.6 and replica is working. Maybe there are some bug fixing to do on
> 2.1.0 version.
> Thanks for your answer.
>

Which version of 2.1.0 are you running, 2.1.0 rc1 ?

I would like to see your full slonik script (ie that includes the STORE 
PATH commands).  If there is a bug in 2.1.0 I'd like to figure out what it 
is so we can fix it.

Thanks


> Francesco
>
>> ----Messaggio originale----
>> Da: sjsinger at sympatico.ca
>> Data: 29/09/2011 12.01
>> A: "francescoboccacci at libero.it"<francescoboccacci at libero.it>
>> Cc: <slony1-general at lists.slony.info>
>> Ogg: Re: [Slony1-general] Slony Problem
>>
>> On Thu, 29 Sep 2011, francescoboccacci at libero.it wrote:
>>
>>> Hi,
>>> i have some problems with slony 2.1.0. I have 2 server (192.168.22.225
> Master,
>>> 192.168.22.226 Slave) .
>>> I run the following  cluster.sh  into main server:
>>
>> I don't see your STORE PATH commands anywhere did you forget those?
>>
>> What are the slon processes putting as output, any ERROR messages?
>>
>>
>>>
>>> CLUSTER=sql_cluster_test
>>> DB1=test_grade
>>> H1=192.168.22.225
>>> H2=192.168.22.226
>>> DB2=test_grade
>>> U=xxxx
>>> P=xxxx
>>> /usr/lib/postgresql/8.4/bin/slonik <<_EOF_
>>> cluster name = $CLUSTER;
>>> node 1 admin conninfo = 'dbname=$DB1  host=$H1  user=$U password=$P';
>>> node 2 admin conninfo = 'dbname=$DB2  host=$H2  user=$U password=$P';
>>>
>>> init cluster (id = 1, comment = 'Master Node');
>>> create set (id = 1, origin = 1, comment = 'contact table');
>>> ########TABLES###############################
>>> set add table (set id = 1, origin = 1, id = 1,
>>>        full qualified name = 'public.testtable',
>>>        comment = 'Table testtable');
>>> ....
>>> ...
>>>
>>> then i run:
>>>
>>> /usr/lib/postgresql/8.4/bin/slon sql_cluster_test "dbname=test_grade
>>> user=xxxx" > slon1.log &
>>>
>>> in a master server and
>>>
>>> usr/lib/postgresql/8.4/bin/slon sql_cluster_test  "dbname=test_grade
>>> user=xxxx" > slon1.log &
>>>
>>> in slave server without  errors. At the end i run the following
>>> subscribe_test.sh script:
>>>
>>>
>>> CLUSTER=sql_cluster_test
>>> DB1=test_grade
>>> H1=192.168.22.225
>>> H2=192.168.22.226
>>> DB2=test_grade
>>> U=xxxx
>>> P=xxxx
>>> /usr/lib/postgresql/8.4/bin/slonik <<_EOF_
>>>
>>> cluster name = $CLUSTER;
>>>
>>> node 1 admin conninfo = 'dbname=$DB1 host=$H1   user=$U';
>>> node 2 admin conninfo = 'dbname=$DB2 host=$H2   user=$U';
>>>
>>> subscribe set (id = 1, provider = 1, receiver = 2, forward = no);
>>>
>>> _EOF_
>>>
>>> This is the returned message :
>>>
>>> waiting for events  (2,5000000001) only at (2,0) to be confirmed on node 1
>>> waiting for events  (2,5000000001) only at (2,0) to be confirmed on node 1
>>> ...
>>> ..
>>>
>>> and the replication in slave tables aren't available and the replication
>>> systema doesn't work.
>>>
>>> Please let me know if i'm doing some mistakes.
>>>
>>> Thanks
>>>
>>> Franesco
>>>
>>>
>>>
>>> _______________________________________________
>>> Slony1-general mailing list
>>> Slony1-general at lists.slony.info
>>> http://lists.slony.info/mailman/listinfo/slony1-general
>>>
>>
>>
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>