From time to time, my insync-headless installation is crashing.
On running get_status, I get the following output:
insync-headless get_status
Traceback (most recent call last):
File “isyncd/linux/headless/cli.py”, line 108, in ipc_insync
File “socket.py”, line 228, in meth
error: [Errno 111] Connection refused
insync version 1.5.7.37371-artful
I do not have the new insync repo added, because although gnome etc. installed, I run my server headless, and I want insync running as a background task, with interaction on the command line. (based on this advice: Linux Headless reinstall - how to do safely?)
Sure. Here is the redacted output. It launches just fine, and only dies after an indetermine amount of time.
insync-headless start --no-daemon
Qt WebEngine seems to be initialized from a plugin. Please set Qt::AA_ShareOpenGLContexts using QCoreApplication::setAttribute before constructing QGuiApplication.
INFO 2019-11-27 20:47:52,175 [__main__insync__:main:105] insync version: 1.5.7.37371
INFO 2019-11-27 20:47:52,176 [__main__insync__:main:106] client created <ideskmain.client.Client object at 0x7f9812229f50>
INFO 2019-11-27 20:47:52,178 [unix_socket_server_portable:start:49] unix socket server thread start
INFO 2019-11-27 20:47:52,178 [__main__insync__:main:114] starting client
INFO 2019-11-27 20:47:52,183 [fswatch:_start:532] LinuxFSWatcher._start
INFO 2019-11-27 20:47:52,184 [fswatch:_pull_loop:267] Inotify loop enter
INFO 2019-11-27 20:47:52,202 [gdsyncer:sync_account:153] Syncing GDUser(..REDACTED..).
INFO 2019-11-27 20:48:15,428 [fswatch:watch:550] watch origin: /home/..REDACTED..
INFO 2019-11-27 20:48:26,734 [fswatch:watch:550] watch origin: /home/..REDACTED2..
INFO 2019-11-27 20:48:28,162 [fswatch:watch:550] watch origin: /home/..REDACTED3..
WARNING 2019-11-27 20:48:29,980 [fswatch:watch_tree:136] Symlink target already watched, skipping: u'/home/..REDACTED4..'
[about 10-20 similar lines, all pointing to individual files]
INFO 2019-11-27 20:48:30,011 [fswatch:watch:550] watch origin: /home/..REDACTED5..
WARNING 2019-11-27 20:48:31,248 [fswatch:add_watch:181] Inotify failed to watch: /home/..REDACTED6..
INFO 2019-11-27 20:48:31,316 [client:__on_gd_account_added:891] GDUser(..REDACTED..) (existing) is now being synced.
INFO 2019-11-27 20:49:13,317 [_updater:_run:129] No updater available.
insync has run fine for years, but this is a new system, with various changes:
it has the desktop installed (rather than being ubuntu server), although it is still run headless.
It is a new install (more recent OS, and new hardware, same file system, same config files and DBs)
I’m surprised to see the reference to Qt GUI components, as I’m explicitly running insync-headless. As I’ve said before, I run my server with no monitor or keyboard - but I do have regular ubuntu desktop installed. If there are interactions between insync-headless and the ubuntu desktop, then that would be one change that might affect things.
@Dom
You might have installed the GUI version of Insync insync package instead of the headless only insync-headless package since there are logs about Qt.
Can you send us your logs since the output above doesn’t show errors on why Insync crashes?
I’ve got a suspicion that switching to headless might be the solution… I’ve been trying to get VNC working, and that has included killing VNC sessions (and probably the desktop session at the same time). Which would probably kill insync…