Periodic crashes [Errno 111] syncing Google Drive


#1

I’m running insync 1.4.9.37127 on Debian Jessie (3.16.0).

I’m currently trying to sync two Google Drive directories (about 100GB) and I periodically (every 2 hours or so) get the following error:

:> insync show
Traceback (most recent call last):
  File "isyncd/linux/headless/cli.py", line 108, in ipc_insync
  File "socket.py", line 224, in meth
error: [Errno 111] Connection refused

I subsequently use insync-headless quit and insync-headless start to resume the process. I tried doubling the value of ‘fs.inotify.max_user_watches’ as suggested in this post, but it didn’t seem to make a difference. The process needs restarting every 2 hours or so.

Is there something I can try to make it more reliable and are there any other problems that might occur by constantly restarting the syncing process?


#2

Tagging our engineer @Kurt_Ko for assistance.


#3

Hi @AaronS!

Can you send us your logs.db and out.txt?
It’s located in ~/.config/Insync


#4

Hi Kurt,

No worries. Can you pm me an email address to send them through to (all up they’re about 2.5MB compressed)?

Cheers,
Aaron


#5

Hey Aaron,

Just send them to support@insynchq.com with the link to this post. :slight_smile: Thank you!


#6

Hi Guys,
Why do you not close these out with a solution.
This is of no use to future people.


#7

Hi @Jamie_Browning,

Good question… The short answer is because it never got sorted.

The long answer is:

I found that periodically restarting (multiple times [maybe around 50 times?] the first time an account is added. It eventually catches up) was enough to stave off the problem for a few months. Then every now and then the account seems to hit a problem that is unrecoverable… in which case I remove it and re-add it. The problem is that everything needs to be re-synchronised (150GB or so of data which takes about a week with all the restarts) every time this happens. Since the post I’ve only had to do it twice.

Our long term goal is to get decent internet and then not rely on a locally cached copy (work off the cloud version and only use the cache to ‘read’ and archive from).

Hope this kind of answers your question (probably not in the way you’d like it answered).

Good luck!
Aaron