Users Mac Book Pro stops syncing constantly


#1

have a MBP (latest OS + seafile client installed)

This particular mac is having issues where a library will just stop syncing and network trasnfer rates drop to 0/0 in the client window

Logs as follows:

[9/26/18 14:38:53] http-tx-mgr.c(806): libcurl failed to GET https://seafile.domain.com/seafhttp/repo/fa6b7e8d-14f6-4bda-a5ee-1613e885b5de/block/29d384ad41d2b40c203b0364169478facc83xxxx: Timeout was reached.
[09/26/18 14:38:53] http-tx-mgr.c(806): libcurl failed to GET https://seafile.domain.com/seafhttp/repo/fa6b7e8d-14f6-4bda-a5ee-1613e885b5de/block/695f96ee5b5fd8713561c63792c6f73363a6xxxx: Timeout was reached.
[09/26/18 14:38:53] http-tx-mgr.c(1177): Transfer repo 'fa6b7e8d': ('canceled', 'data') --> ('canceled', 'finished')
[09/26/18 14:38:53] clone-mgr.c(713): Transition clone state for fa6b7e8d from [canceling] to [canceled].
[09/26/18 14:41:36] clone-mgr.c(713): Transition clone state for fa6b7e8d from [init] to [check server].
[09/26/18 14:41:36] [09/26/18 14:41:36] http-tx-mgr.c(1177): Transfer repo 'fa6b7e8d': ('normal', 'init') --> ('normal', 'check')
clone-mgr.c(713): Transition clone state for fa6b7e8d from [check server] to [fetch].
[09/26/18 14:41:37] http-tx-mgr.c(1177): Transfer repo 'fa6b7e8d': ('normal', 'check') --> ('normal', 'commit')
[09/26/18 14:41:37] http-tx-mgr.c(1177): Transfer repo 'fa6b7e8d': ('normal', 'commit') --> ('normal', 'fs')
[09/26/18 14:41:38] http-tx-mgr.c(1177): Transfer repo 'fa6b7e8d': ('normal', 'fs') --> ('normal', 'data')
[09/26/18 14:49:11] seaf-daemon.c(491): starting seafile client 6.2.5
[09/26/18 14:49:11] seaf-daemon.c(493): seafile source code version 9d53c0f14887c1b1c4ef1b548308b922242fxxxx
[09/26/18 14:49:11] seafile-session.c(382): client id = 4cdbfe40296f162c5c16cd28a80b16d60442xxxx, client_name = xxxx-MacBook-Pro.local
[09/26/18 14:49:11] seaf-daemon.c(518): rpc server started.
[09/26/18 14:49:11] clone-mgr.c(713): Transition clone state for fa6b7e8d from [init] to [check server].
[09/26/18 14:49:11] clone-mgr.c(713): Transition clone state for fa6b7e8d from [check server] to [fetch].
[09/26/18 14:49:11] http-tx-mgr.c(1177): Transfer repo 'fa6b7e8d': ('normal', 'init') --> ('normal', 'check')
[09/26/18 14:49:11] http-tx-mgr.c(1177): Transfer repo 'fa6b7e8d': ('normal', 'check') --> ('normal', 'commit')
[09/26/18 14:49:11] http-tx-mgr.c(1177): Transfer repo 'fa6b7e8d': ('normal', 'commit') --> ('normal', 'fs')
[09/26/18 14:49:12] sync-mgr.c(1309): File syncing protocol version on server https://seafile.domain.com is 1. Client file syncing protocol version is 2. Use version 1.
[09/26/18 14:49:12] http-tx-mgr.c(1177): Transfer repo 'fa6b7e8d': ('normal', 'fs') --> ('normal', 'data')
[09/26/18 14:49:13] sync-mgr.c(545): Repo 'Comms & Marketing - New' sync state transition from 'synchronized' to 'committing'.

I believe its something to do with the syncing protocol, but ive not had this message appear on any other client on site so not sure why its happening with this particular device.

What can I do about this? we been trying to get it synced for a week or so now


#2

nobody has any advice?


#3

Which version of macOS are you running? I haven’t tried or seen any reports on Mojave (10.14) yet but it is officially out now.

Have you tried removing the client software and re-installing? Also, you might try removing the invisible support directories too in case it’s really troubled. That would put you back to a clean installation of the client software.


#4

I did mention that its running the lastest (at the time) MacOS (High Sierra). but we have many machines running on that version.

Dont the logs help the devs identify what could be causing the problem?

[09/26/18 14:49:12] sync-mgr.c(1309): File syncing protocol version on server https://seafile.domain.com is 1. Client file syncing protocol version is 2. Use version 1.

I would have thought it was this


#5

The user of the Mac Book Pro are stopping to syncing constantly where the client serveer will worked to support the installation preocess which is vwery mush iessentail while working nad need teh most of it so contact microsoft for teh all the information where it required for the machine which runs it.


#6

Sorry I didnt understand that. Not sure why youre asking me to contact Microsoft when im talking about a Mac


#7

So no devs around to help…?


#8

Im on 10.13, and this is fresh account I created and setup Seafile on so there should be no conflict. There was an old account on this machine that also had seafile and had access to the same libraries. I have deleted that account from the machine now, though.


#9

How soon after you start syncing does the Mac stop? Once it stops does it resume syncing or try to sync later? I have seen strange cases where syncing will trip on certain (damaged) files and stop. I have also seen cases where bad blocks on the server can stop a sync. Have you run fsck on the server? That would help pinpoint a bad library.

Have you tried clearing all files and starting over adding files a few at a time to see if you can sync? When it does trip up is it always with a protocol version error?

By the way what kind of server are you running? Is this the current CE on Linux? What is your SSL setup like? Maybe we can get some clarification on the error type from @daniel.pan or @Jonathan when they pass by.


#11

it will stop randomly. sometimes ive noticed it stops downloading if the machine off left alone for a while and the monitor turns off, however, I have set power settings to not shut down the hard drive when the screen goes off.

The only way to start the sync again is to completely close the Seafile client and launch it again.

I have deleted seafile and reinstalled, deleted the library and tried to re-download it. we recently did a file check on the server and it showed no errors. nobody else has had a similar issue.

Were running the server on Linux.

There was a log entry on the machine that said that seafile couldnt not resolve the file path:

[10/01/18 17:37:47] http-tx-mgr.c(806): libcurl failed to GET https://seafile.domain.com/seafhttp/repo/fa6b7e8d-14f6-4bda-a5ee-1613e885b5de/commit/HEAD: Couldn't resolve host name.
[10/01/18 17:37:47] sync-mgr.c(607): Repo 'Image Bank - New' sync state transition from initializing to 'error': 'Failed to get sync info from server.'.
[10/02/18 05:44:18] http-tx-mgr.c(806): libcurl failed to GET https://seafile.domain.com/seafhttp/repo/fa6b7e8d-14f6-4bda-a5ee-1613e885b5de/commit/HEAD: Couldn't resolve host name.
[10/02/18 05:44:18] http-tx-mgr.c(806): libcurl failed to GET https://seafile.domain.com/seafhttp/repo/3485d27c-780b-48b7-b107-41c912577f57/commit/HEAD: Couldn't resolve host name.
[10/02/18 05:44:18] sync-mgr.c(607): Repo 'Image Bank - New' sync state transition from initializing to 'error': 'Failed to get sync info from server.'.
[10/02/18 05:44:18] sync-mgr.c(607): Repo 'Comms & Marketing - New' sync state transition from initializing to 'error': 'Failed to get sync info from server.'.

could these help point to what the issue is?


#12

Couldn’t resolve host name

Do you use your own or different dns server?
If it does not work sometimes it might be related to a resolver issue.


#13

That “error” usually happens when the computer has no internet connection.


#14

Do you see the version 1/ version 2 syncing protocol error at the same time the client shows ‘Couldn’t resolve the host name’?

When the client stops syncing do you see the red ‘!’ disconnected icon in the Seafile menu bar and/or a disconnect message in the client GUI?

Echoing DerDanilo, can you locate/lookup/ping the Seafile Server using Network Utility when a disconnect/sync-fail is detected?

Is this client falling off its network connection?


#15

our server is hosted on-site and was setup by myself and a colleague. has worked without a problem for 3+ years. this is so far an isolated problem regarding these specific symptoms


#16

There is an interenet connection at all times during the transfer. Shutting down seafile and launching it again resumes the download for a time before cutting out again


#17

I dont think so. Before we were seeing ‘Timeout was reached’ then it became ‘could not resolve hostname’. It works for a few minutes at launch, but stops randomly throughout the download.

No. The Tx Rx indicator at the bottom of the screen goes to 0up 0 down while the library shows ‘Downloading’
nothing happens after that, though.

Nope.


#18

What’s the your seafile server version? Fro the above message it seems it is a pretty old version.