Bugreport: 1.7.0 master-slave direct replication

10 views

Skip to first unread message

googlew...@resellerdesktop.de

unread,

Feb 27, 2014, 11:33:39 AM2/27/14

to les...@googlegroups.com

A "masterslave" setup, which replicates directly via ports and not via batch, produces this messages:

On the slave:

Feb 27 17:29:02 s113 lessfs[8213]: replication_worker : nakcount > 3, disconnect
Feb 27 17:29:06 s113 lessfs[8213]: replication_worker : nakcount > 3, disconnect
Feb 27 17:29:10 s113 lessfs[8213]: replication_worker : nakcount > 3, disconnect
Feb 27 17:29:14 s113 lessfs[8213]: replication_worker : nakcount > 3, disconnect
Feb 27 17:29:18 s113 lessfs[8213]: replication_worker : nakcount > 3, disconnect
Feb 27 17:29:22 s113 lessfs[8213]: replication_worker : nakcount > 3, disconnect
Feb 27 17:29:26 s113 lessfs[8213]: replication_worker : nakcount > 3, disconnect
Feb 27 17:29:30 s113 lessfs[8213]: replication_worker : nakcount > 3, disconnect
Feb 27 17:29:34 s113 lessfs[8213]: replication_worker : nakcount > 3, disconnect
Feb 27 17:29:38 s113 lessfs[8213]: replication_worker : nakcount > 3, disconnect

in fact, the replication works fine. Whatever this message wants to tell, seems to be a small flow.
Unfortunatly, it fills up the logfiles.

best regards.

Reply all

Reply to author

Forward

0 new messages