I’m not sure why, but I’ve got a fair number of files stuck in UNKNOWN in a folder that’s otherwise successfully syncing. I’m tried using force_sync (I’m running headless) to no avail, and I’ve already updated to latest and rebooted.
Any further suggestions or do I just need to send logs at this point?
Can you explain what UNKNOWN means and what normal diagnostics would be for files stuck in this state?
BTW, looking in out.txt, I see a whole lot of these (it’s exactly u2026):
The stack trace is:
Exception happened during processing of request from
Traceback (most recent call last):
File “SocketServer.py”, line 596, in process_request_thread
File “SocketServer.py”, line 331, in finish_request
File “isyncd/linux/portable/unix_socket_server_portable.py”, line 112, in __handler
File “posixpath.py”, line 375, in realpath
File “posixpath.py”, line 400, in _joinrealpath
File “posixpath.py”, line 135, in islink
UnicodeEncodeError: ‘ascii’ codec can’t encode character u’\u2026’ in position 93: ordinal not in range(128)
I’ve checked, and force_sync isn’t doing anything because the file for some reason doesn’t exist in GDrive, resulting in a lot of event_log entries like this:
… ‘root in _do_for_cm’,‘ideskmain/clientmenuitems.py’,215,NULL,NULL,’{“message”: “Received CM action %r for %r but there’'s no GDocsFile.”, “params”: [“refresh_local”, …
Restart seems to have fixed this. You really need to up your reliability game.
Hi @Bayard_Bell,
Thank you for updating us. 
I’ve forwarded this to our engineer so we can also check on our end.