Replication Error Broken Pipe

[Richie]

I'm setting up a new server and trying to replicate the old one to the new one and i get an error message!

Mar 6 16:43:01 freenasSS autorepl.py: [tools.autorepl:334] Replication of tail/it@auto-20140306.1535-1w failed with dd: stdout: Broken pipe 2048+0 records in 0+0 records out 0 bytes transferred in 0.135869 secs (0 bytes/sec) dd: stdout: Broken pipe 4019+136 records in 1+0 records out 1048576 bytes transferred in 0.136291 secs (7693654 bytes/sec) warning: cannot send'tail/it@auto-20140306.1535-1w': Broken pipe cannot send 'tai/it': I/O error



I've made sure the public keys are correct!!! Any help would be useful!!!!!

 

[dlavigne]

You've tried the troubleshooting steps listed in http://doc.freenas.org/index.php/Replication_Tasks#Troubleshooting_Replication?

 

[Richie]

Yes, I have gone over them numerous times! And it always ends with the broken pipe error!
The only thing I am not not 100 percent is the Public key! Do i copy the whole field or just the middle?

 

[cyberjock]

You know.. normally we expect to see FreeNAS version, hardware, etc... ;)

 

[Richie]

Sorry new to this!

Build FreeNAS-9.2.1-RELEASE-x64
PlatformIntel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz
Memory2026MB is the Pull


BuildFreeNAS-9.2.1-RELEASE-x64
PlatformIntel(R) Xeon(R) CPU E5420 @ 2.50GHz
Memory12266MB is the Push

They are one the same lan and subnet! Over the weekend we could manually replicate it! But still could not get it to replicate on its own!

 

[Richie]

This is the message i have been receiving since this morning!! [tools.autorepl:125] pool/it -> ME-Storage-SS replication not enabled

 

[cyberjock]

Well, you've got 2GB of RAM on one of the systems. Upgrade to 8GB of RAM otherwise suffer the wrath of random programs randomly not performing correctly. Gee... that sounds alot like a broken pipe message. I wonder if the 2 are related... hmmm.....

 

[Richie]

Were working on the memory issue! The [tools.autorepl:125] pool/it -> ME-Storage-SS replication not enabled didn't start till this morning , but we manually made the replication Friday!


To Update: the earlier message [tools.autorepl:125] was from my partner disabling the replication task, without me knowing! So it is still just the same problem with the broken pipe message!!

 

[cyberjock]

Ok, so come back when you've upgraded your RAM. :)