[09/08/16 09:12:57] file-cache-mgr.c(1004): Read cache file C:/Users/7134956/seadrive/data\file-cache/676aa500-2e2f-4492-a9ed-cd0cd36e9a73/doc/Система команд.docx timeout.
[09/08/16 09:12:57] utils.c(236): Failed to set file time for C:/Users/7134956/seadrive/data\file-cache\676aa500-2e2f-4492-a9ed-cd0cd36e9a73\doc/Система команд.docx: 87.
[09/08/16 09:12:57] file-cache-mgr.c(282): Failed to set mtime for C:/Users/7134956/seadrive/data\file-cache\676aa500-2e2f-4492-a9ed-cd0cd36e9a73\doc/Система команд.docx.
[09/08/16 09:12:58] file-cache-mgr.c(1004): Read cache file C:/Users/7134956/seadrive/data\file-cache/676aa500-2e2f-4492-a9ed-cd0cd36e9a73/doc/БЭП макет.pdf timeout.
[09/08/16 09:12:59] utils.c(236): Failed to set file time for C:/Users/7134956/seadrive/data\file-cache\676aa500-2e2f-4492-a9ed-cd0cd36e9a73\doc/БЭП макет.pdf: 87.
[09/08/16 09:12:59] file-cache-mgr.c(282): Failed to set mtime for C:/Users/7134956/seadrive/data\file-cache\676aa500-2e2f-4492-a9ed-cd0cd36e9a73\doc/БЭП макет.pdf.
[09/08/16 09:13:00] file-cache-mgr.c(1004): Read cache file C:/Users/7134956/seadrive/data\file-cache/676aa500-2e2f-4492-a9ed-cd0cd36e9a73/doc/БЭП с РШ макет.pdf timeout.
Hi,
I have Seafile server (6.0.3) behind Apache https (self-signed certificate), I’ve unchecked “Advanced->Do not verify server cert…” but still got error:
http-tx-mgr.c(578): libcurl failed to GET https://[hidden]/api2/repos/: Peer certificate cannot be authenticated with given CA certificates.
Is this temporary or permanent? Could you check whether the file ‘C:/Users/7134956/seadrive/data\file-cache/676aa500-2e2f-4492-a9ed-cd0cd36e9a73/doc/Система команд.docx’ exist or not?
I’m sorry you are right I’ve installed Seafile Drive, have seen nothing on drive S, unchecked that option, restart Seafile Drive, and still have seen nothing, and wrote my not entirely thought out message on forum. But conslusion is that I see the same message (Peer certificate cannot be authenticated with given CA certificates) regardless of which option is selected.
Windows7 system. The file is loaded into the cache is loaded again and again ad infinitum. On the S: drive file does not open. This library has a strange behavior. Removing the C:\Users\user\seadrive not solve the problem.
On windows 10 is no such problem.
After removal of the C:\Users\user\seadrive on windows 10 had this same problem.
The reason is revealed. The files do not have the last update time on the server. We need to carry around this problem.
It should work. The writes are completely local. So it should have similar performance as a local disk. But one pitfall I could think of is that, there may be many “indexing” operations if the downloaded file is not updated frequently enough. If you use the sync client, it should demonstrate a similar behavior. The client starts indexing the file if there is no update activity for 2 seconds.
The problem may be that is my administrator did some changes in infrastucture so my seafile server is deploy now at other subdomain and he didn’t change certificate so I have mismatch between site in certificate and site which my seafile is deploy on. I have checked option “Do not verify…” and still got error message “…/seafhttp/protocol-version: Peer certificate cannot be authenticated with given CA certificates”
The two problems are linked :
> [09/14/16 09:48:24] seadrive.c(429): Starting SeaDrive client 0.1.0
> [09/14/16 09:48:24] seadrive.c(453): rpc server started.
> [09/14/16 09:48:24] seadrive.c(481): Can’t assign a drive letter
maybe it would be a good idea to test before if the drive letter is free and get a clear message error if already in use.
Having issue with the client. Installs fine. but doesnt seem to do anyting. Most of the time when i open i get Seadrive drive failed to initialize. When it does actually open, it doesnt create the drive letter or anything.
The video thumbnail generator may read part of a video file to generate thumbnail. Then Drive client starts to cache the file on local disk. But as soon as the thumbnail generator closes the file, the caching will be stopped. So the entire file shouldn’t be cached, unless somehow the entire file is read or the Drive client has a bug.
Is the total size of the video folder about 3GB? Could you check the cached files under C:\users\username\seadrive\data\file-cached<library-id>?