hi, i'm using slony 1.2.15 (from backports) on debian etch. there a 4 slon daemons (1 master, 3 slaves with ids 2,4,5) running on the host where the master database resides. replication is working fine (in my opinion).
when i started using test_slony_state-dbi.pl i got the following messages: Node: 4 Confirmations not propagating from 4 to 2 Node: 4 Confirmations not propagating from 4 to 5 since i couldn't find the reason for this error message (listen paths were ok imo) and i couldn't see any real erroneous behaviour i dropped the node using slonik_drop_node and recreated replication for this node using a different node id. again replication is working fine, messages about "confirmations not propagating" have stopped, but now i get this message (node id 4 doesnt exist any more!!): Node: 4 Events not propagating to node 4 what did i do wrong? how do i get rid of these messages? what i did notice was that when i drop nodes the corresponding slon daemon doesn't terminate itself (as it is mentioned in the docs). i usually remove dropped nodes configuration from slon_tools.conf and do a "/etc/init.d/slony1" restart. any help appreciated thx matthias -- Mit freundlichen Grüssen Matthias Leopold System & Network Administration Streams Telecommunications GmbH Universitaetsstrasse 10/7, 1090 Vienna, Austria tel: +43 1 40159113 fax: +43 1 40159300 ------------------------------------------------ _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
