I have the same problem since a few weeks with the windows desktop
client. It only happens sporadically and I didn't find a way to
reproduce it yet. I only see "unkonwn error" after a while. No more
information in the client or the log files of the server.
What I can say is, that the process seems to stop after a file was
mainly already transfered to the server. The .part file already exists
and than the process stops. For me restarting the client usually helps,
that at least a few more files are transferred. But if I have e.g. 20
new files then it is likely that I have to restart the client several times.
Is there a way to investigate the behavior of the windows desktop client
more deeply when the issue happens the next time?
Am 01.11.2013 17:25, schrieb Daniel Wunderlich:
As I wrote, I already submitted this error to mirall's bug tracker. The
question is: Is this a sync client or an server bug and how to detect this?
Please follow the instructions here to get this problem triaged and
corrected:
http://owncloud.org/submit-bug-reports/
Thanks!
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
---
Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz
ist aktiv.
http://www.avast.com
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
