haiwen / seafile

High performance file syncing and sharing, with also Markdown WYSIWYG editing, Wiki, file label and other knowledge management features.
http://seafile.com/
Other
12.25k stars 1.54k forks source link

Seafile client losses library synced status on force shutdown #956

Closed shuhaowu closed 8 years ago

shuhaowu commented 9 years ago

I had a couple of hard system crashes and after that Seafile lost the state for which a library is synced.

The only way to fix this to delete/move the library and resync it. However, this doesn't work as seafile kinda gets stuck, uses 100% CPU and doesn't download anything.

Logs:

[12/05/14 22:58:27] ccnet-daemon.c(193): starting ccnet client 3.1.11
[12/05/14 22:58:27] ccnet-daemon.c(195): ccnet source code version 13630d608da7528cbda151ddcc9e65b0984439e4
[12/05/14 22:58:27] ../common/session.c(432): socket file exists, delete it anyway
[12/05/14 22:58:27] ../common/session.c(461): Listen on /home/shuhao/.ccnet/ccnet.sock for local clients
[12/05/14 22:58:27] ../common/session.c(267): Update pubinfo file
[12/05/14 22:58:28] ../common/session.c(375): Accepted a local client
[12/05/14 22:58:28] ../common/session.c(375): Accepted a local client
[12/05/14 22:58:28] ../common/session.c(375): Accepted a local client
[12/05/14 22:58:28] ../common/session.c(375): Accepted a local client
[12/05/14 22:58:28] ../common/session.c(375): Accepted a local client
[12/05/14 22:58:28] ../common/session.c(375): Accepted a local client
[12/05/14 22:58:28] ../common/processors/rcvcmd-proc.c(492): Add server 3ab12b1b seafile.thekks.net:10001
[12/05/14 22:58:28] ../common/connect-mgr.c(364): [Conn] Start outgoing connect to (null)(3ab12b1b2b) 192.168.2.15:10001
[12/05/14 22:58:28] ../common/connect-mgr.c(289): [Conn] Peer (null) (3ab12b1b2b) connected
[12/05/14 22:58:35] ../common/peer.c(766): Delayed update from local-2(cb418fec), id is 1011, 500 Shutdown
[12/05/14 22:58:28] seaf-daemon.c(490): starting seafile client 3.1.11
[12/05/14 22:58:28] seaf-daemon.c(492): seafile source code version e2ec7141503a7035868cf7b9ab72627c906e00bc
[12/05/14 22:58:28] ../common/mq-mgr.c(60): [mq client] mq cilent is started
[12/05/14 22:58:28] ../common/mq-mgr.c(106): [mq mgr] publish to hearbeat mq: seafile.heartbeat
[12/05/14 22:58:28] clone-mgr.c(628): Transition clone state for a7bbc6ed from [init] to [connect].
[12/05/14 22:58:30] sync-mgr.c(375): Repo 'Public' sync state transition from 'synchronized' to 'committing'.
[12/05/14 22:58:30] repo-mgr.c(951): All events are processed for repo a540c5c6-eed0-4dfc-bd07-6ab903714235.
[12/05/14 22:58:30] sync-mgr.c(375): Repo 'Public' sync state transition from 'committing' to 'initializing'.
[12/05/14 22:58:31] sync-mgr.c(375): Repo 'nsg' sync state transition from 'synchronized' to 'committing'.
[12/05/14 22:58:31] repo-mgr.c(951): All events are processed for repo 8815f552-4cda-47bd-8ce1-366bb5d59fb7.
[12/05/14 22:58:31] sync-mgr.c(375): Repo 'nsg' sync state transition from 'committing' to 'initializing'.
[12/05/14 22:58:33] clone-mgr.c(628): Transition clone state for a7bbc6ed from [connect] to [connect].
[12/05/14 22:58:33] clone-mgr.c(628): Transition clone state for a7bbc6ed from [connect] to [fetch].
[12/05/14 22:58:34] transfer-mgr.c(309): Transfer repo 'a7bbc6ed': ('normal', 'init') --> ('normal', 'check')
[12/05/14 22:58:34] processors/check-tx-v3-proc.c(313): repo version is 1, protocol version is 7.
[12/05/14 22:58:34] transfer-mgr.c(309): Transfer repo 'a7bbc6ed': ('normal', 'check') --> ('normal', 'commit')
[12/05/14 22:58:34] transfer-mgr.c(309): Transfer repo 'a7bbc6ed': ('normal', 'commit') --> ('normal', 'fs')
[12/05/14 22:58:35] transfer-mgr.c(309): Transfer repo 'a7bbc6ed': ('normal', 'fs') --> ('normal', 'get-chunk-server')
[12/05/14 22:58:35] transfer-mgr.c(309): Transfer repo 'a7bbc6ed': ('normal', 'get-chunk-server') --> ('normal', 'data')
[12/05/14 22:59:05] block-tx-client.c(757): Data connection is closed by the server.
killing commented 9 years ago

Did you have a crash on the client or on the server? What's in the server's log?

shuhaowu commented 9 years ago

There's no crash by the seafile client/server. My computer had a crash and I had to force shut it down.

Those logs are for after the computer restarts.

killing commented 9 years ago

Can you post the complete seafile.log from the client?