Hi all,

Now I have a new problem about slony-i and network failure.

I setup master node in PC1 with NIC1 = 192.168.1.226, NIC2 = 192.168.1.227

NIC1 is Microsoft Loopback Adapter and cannot access internet (no gateway)

NIC2 is Realtek RTL8169/8110 Family Gigabit Ethernet NIC, and I access
internet thought NIC2.

Then I setup slave node in PC2 with NIC1 = 192.168.1.5 (only one nic)

On PC1, I use pgAdminIII connect to 192.168.1.226 and 192.168.1.5.

Next I configure slony-i for db_master and db_slave on master node and slave
node.
Create table "staff" in two databases.
And  they work well, no problem happen.

I restart PC1 many time and no problem happen too.

Next, I disable NIC2 = 192.168.1.227 and insert some record in db_master.
And wait for minute.

Next, I enable NIC2 = 192.168.1.227, using pgAdmin on PC1 to view table
"staff" on slave node,
but slave node cannot update data from master node.

Then I wait 1 hours later, and I has the same error.

Next I restart slony service but cannot fix this error.

Next I restart computer and cannot fix this error too.

Here is pg log files:
http://www.nabble.com/file/p25676840/postgresql-2009-09-30_000000.log
postgresql-2009-09-30_000000.log 
http://www.nabble.com/file/p25676840/postgresql-2009-09-30_103703.log
postgresql-2009-09-30_103703.log 
http://www.nabble.com/file/p25676840/postgresql-2009-09-30_105055.log
postgresql-2009-09-30_105055.log 
http://www.nabble.com/file/p25676840/postgresql-2009-09-30_135154.log
postgresql-2009-09-30_135154.log 
http://www.nabble.com/file/p25676840/postgresql-2009-09-30_135449.log
postgresql-2009-09-30_135449.log 

Please help me to fix this problem

Thank you very much


Bao Luc
[email protected] 
-- 
View this message in context: 
http://www.nabble.com/Slony-I-and-network-failure.-tp25676840p25676840.html
Sent from the Slony-I -- General mailing list archive at Nabble.com.

_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general

Reply via email to