search

haiwen / seafile-client

Seafile desktop client.
http://seafile.com
Apache License 2.0
476 stars 279 forks source link

At start, the libraries don’t sync even when the network becomes active #838

Closed papoteur-mga closed 6 years ago

papoteur-mga commented 8 years ago

Description of the problem: I use seafile-client 5.1.3 on Linux to connect app.seafile.de When I start my machine, and when the network is not on, I get a message that the libraries can't be accessed. But when the network becomes up, I get a grey cloud in regard with each library "wait for synchronisation". If I ask for synchronisation now, nothing changes. But if I close the client and reopen it, all comes fine. It seems that the client goes in a bad state and can't out by itself. What I found as error in .ccnet/seafile.log is this line, repeated more and more (every ten seconds) [11/02/16 08:32:55] http-tx-mgr.c(707): libcurl failed to GET https://app.seafile.de/seafhttp/protocol-version: Couldn't resolve host name.

shoeper commented 8 years ago

https://github.com/haiwen/seafile-client/issues/759

papoteur-mga commented 8 years ago

Thanks Shoeper, What I report is different. The error message I get is : couldn't resolve host name And I checked with web access that local files created in directories put in library are not synced. Thus, I consider that this bug is not the same. My Qt version is 5.4.2. I don't think it can be updated on Mageia 5 because of release policy.

shoeper commented 8 years ago

couldn't resolve host name is also a common error for suspend. But as I see it hasn't been mentioned in the other ticket.

urbie-mk2 commented 8 years ago

@papoteur-mga The error is not related to Qt since libcurl fails to resolve for the Seafile client daemon and not the GUI applet.

This looks like a race condition happening in your linux distribution. Without further assumptions please check the following:
1) By which mechanism is the Seaflie client automatically getting started? Will manually starting Seafile client after the machine and network is brought up solve the problem ? 2) Network: Which network manager is being used? 3) Mobile machine ? Is this happening in only one and the same network or regardless of the local network, i.e. does it happen in other networks as well ? 4a) DNS: Do you use any kind of DNS caching or other customizations for name resolution (e.g. cryptdns, special name resolution services etc) ? 4b) DNS: Which resolver method do you use (i.e. resolvconf or systemd resolver or resolv.conf directly) ? 5) libcurl: Version ?

Also try asking the seafile.de for support in this regard if you have a paid subscription.

urbie-mk2 commented 8 years ago

Just FYI: There is a similar symptom: If the tray icon indicates a connection problem right after startup then this apparent connection problem might resolve shortly after few seconds later.

papoteur-mga commented 8 years ago

1) the seafile applet start automatically through KDE mechanism, in autostart. 2) mageia-applet 3) Yes, mobile machine. This happens on 2 network accesses I use currently, one as Ethernet, the other over wifi. 4a) Nothing non standard, for what I know. DNS address are the one provided by my Internet provider. 4b) I don't know how to check that. I think that the file /etc/resolv.conf is written by the network manager. 5) rpm -qa |grep curl lib64curl4-7.40.0-3.5.mga5 curl-7.40.0-3.5.mga5 ...

Thanks

freeplant commented 6 years ago

The problem should have been fixed in the latest version.

papoteur-mga commented 6 years ago

Hello, Yes, I confirm, with mageia 6. seafile-6.0.7-1.mga6 It's OK