Syncdocs did not retry after an error

(2 posts) (2 voices)

Tags:

begood
Member

Hi,

I logged in to my remote machine, and found that syncdocs has not been synching for few hours. It did not retry when an error condition occurred although the status dialog did mention that it will "retry soon".

The error condition is shown below. The issue was simply resolved by manually resuming sync (but I lost few hours of upload time).

Is there any config parameter to let syncdocs to work in completely unattended mode, were if there is an error it simply retries on it's own? Or is that the intended behavior and there is a bug?

3/28/2012 7:20:39 AM(ver. 2.23) Powered down at 3/28/2012 7:20:39 AM
3/28/2012 1:24:55 PM(ver. 2.23) Power resumed at 3/28/2012 1:24:55 PM
3/28/2012 1:25:06 PM(ver. 2.23) Resuming sync after power up at 3/28/2012 1:25:06 PM
3/28/2012 1:25:11 PM(ver. 2.23) Error getting initial doc list
User Pause System.Exception : sd criticality=6
Inner:
Source: mscorlib : sd criticality=6

Posted 1 year ago #
Phil
Syncdocs

The error is probably caused by the network not being available just after power wakeup.

Whatever the cause of that error ("Error getting initial doc list") Syncdocs should probably not go into paused mode after it, but retry, so we'll look into it and fix it in the next release.

Posted 1 year ago #

Reply

You must log in to post.