On 06.02.2014 10:23, Klaas Freitag wrote:
Hi,
good news here.
As we are sitting together for a hackathon on the client this week, we
were able to have a deeper look into this problem and our friend Olivier
was actually able to nail the problem down and fix it.
It indeed was a problem with the renaming mechanism, and both the
problem and the solution are hard to understand ;-)
But: The fix will arrive with the next client release (RC2 or final).
Thanks Olivier for fixing and thanks for the report!
regards,
Klaas
On 05.02.2014 15:38, Benjamin Schieder wrote:
Am 2014-02-05 15:10, schrieb Klaas Freitag:
On 05.02.2014 14:20, Benjamin Schieder wrote:
After a reinstallation of my laptop and re-configuration of the sync
client, the client now synced the / directory of my server instead of
the /clientsync directory.
Did you have a previously configured client? Have you been asked if
you want to start over with a clean sync or keep the local files?
I had a previously configured client. For reasons I can't quite
reconstruct now, I removed the existing sync entry from the client and
added a new one. The new one didn't ask for a path and took the entire /
from the server.
Note that this sync worked like a charm!
After this initial sync I had the entire / from the server on my client
and everything where it bel
Ok, but this means that we do not deal with an update problem from one
client version to another, because it was a completely new set up client.
Well, that was fine with me, so I decided to move the directories from
/clientsync/* to / .
Where? On the server or on the client?
On the client.
Ok, so the client propagated the move to the server which we see in the
log snippet as well.
At some point, the sync client encountered a 500 Internal server error
and stopped working.
Why did that happen? Did you find something in the apache error log?
_______________________________________________
Owncloud mailing list
Owncloud@kde.org
https://mail.kde.org/mailman/listinfo/owncloud
