Closed rahno closed 8 years ago
We've fixed a similar crash recently. But the fix is not yet released. Could you try this test package: https://app.seafile.de/f/2ccc2e94ae/?raw=1 We also added some more debug messages into the package. So the seafile.log would be interesting for us, no matter the bug is fixed or not.
thank you killing,
with the 5.0.4 package from you the client syncs without crashing - althoug the syncing results in hundrets of conflicts!
can you tell me how i can revert the library back to the snapshot before syncing (19.02.2016 @ 11:51)? because i dont know if this library with the conflicts is really the the latest version.
i read that this is possible with the webinterface... however is there another way like shell command to export a complete library snapshot by parameter?
the seafile.log is pretty big now, if you tell me your email i will send it. < Edit >: i sent it by mail.< /Edit > keep in mind: that i manually copied the folder from another pc before i updated to the client package you send me. so i don't think that you will find the original error that leaded to the client crash.
summary:
I dont want to check each file which is the correct one, so i want to rolle back to the snapshot before (6.) 19.02.2016 @ 11:51
hope you understand this report, ask me if something is unclear. thanks!
Hi, To restore the entire library back to a certain snapshot, assuming you use the latest server,
Hey,
my Windows Client ver. 5.0.3 keep crashing while syncing.
It looks like the Client only crashes if he trys to sync the library: "Unity Projects (Unity Groupe)" because if i turn of syncing this library in the client there is no crash.
I tryed the suggested serverside library checking:
but no abnormity was found. (see seaf-fsck log)
my seafile log
my seafile log after manual syncing the "Unity Projects (Unity Group)" library. (copied it while client was shutdown)
client still crashes!