Suddenly Problems with Data Replication via VPN

Since at least a year now, I am doing nightly data replication via VPN offsite to another DSS. Since some weeks the replication process does run forever. And because it is still running, the next night the process is not starting again. I have to stop replication manually and start it again. When I look in my gateway monitor (looking for the total traffic at my VPN gateway), I see that replication starts (huge traffic for some minutes) and after some minutes (this time is different for any try), the traffic goes done, but the replication task in DSS does not stop.

In the last manual tries, I received one time also the error "Error 12 : Error in rsync protocol data stream protocol"

Could I get some more logs about this process?
What could be the problem here?

Both dss have the same version: 6.0UP90.8101.5845 64BIT
I also had a ping running to monitor VPN connection. Everything looked fine with VPN.

Any idea?

http://kb.open-e.com/What-does-Error...ation_982.html

Thanks for this link!

I checked all of the solutions of error 12, but none of them were true (at least to what I found out, of course). Indeed, when I read "Disk is full" I thought that this could maybe be the case, but it's not. Anyway this error 12 only happened once now, most of the time rsync simply keeps running with no traffic and no error message at all.

Can you update both of to the latest version w/ build 6335, we have latest drivers for the NICs, I would also check in the tests.log in the ifconfig -a section to see if there are any dropped packets, look for RX and TX.

I just downloaded log files and had a look at tests.log: There are no dropped packets at all!

Code:

---

eth2      Link encap:Ethernet  HWaddr 00:1B:21:04:9B:8E 
          inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:26516354 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44536409 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:11838663423 (11.0 GiB)  TX bytes:54379820600 (50.6 GiB)
          Interrupt:16 Memory:ea220000-ea240000

---

I just updated destination dss to latest version, the other one will follow some days later.
Is it not possible to see the log of rsync itself?

I would also look at the rsync.log as well and look the date that it happened in the log to see if there was another error that happened just before the error 12.

Strange, the last entry in rsync.log is from 2011/02/09. Why that? Where can I get actual log data?

Is the date set ok in DSS?
Events will be logged in rsync.log on destination, is it the one you are checking?

Yes, the dates are set ok on both DSS servers, I just confirmed this. But of course I was looking on the source DSS for rsync.log!
On the destination there is a log, but it is not really helpful:

Code:

---

2012/08/02 21:52:07 [1663] name lookup failed for 192.168.1.4: Name or service not known
2012/08/02 21:52:07 [1663] connect from UNKNOWN (192.168.1.4)
2012/08/02 21:52:07 [1663] module-list request from UNKNOWN (192.168.1.4)
2012/08/02 21:52:07 [1664] name lookup failed for 192.168.1.4: Name or service not known
2012/08/02 21:52:07 [1664] connect from UNKNOWN (192.168.1.4)
2012/08/02 21:52:07 [1664] module-list request from UNKNOWN (192.168.1.4)
2012/08/02 21:52:19 [1754] name lookup failed for 192.168.1.4: Name or service not known
2012/08/02 21:52:19 [1754] connect from UNKNOWN (192.168.1.4)
2012/08/02 21:52:19 [1754] rsync to kunden_bup/ from root@unknown (192.168.1.4)
2012/08/02 19:52:19 [1754] receiving file list

---

Does the 2-hour-time jump means anything? I started this rsync manually at 21:52, now it's around 30 minutes later and rsync is still running on the source machine. But in fact, it looks like nothing is happening anymore... please look at the attached screenshot of my traffic monitor. After around 10 minutes, rsync stops producing traffic... :-(
https://www.hidrive.strato.com/lnk/LmINgmDk