Server/Client Disconnect

[Adam McKee 0]

I've enabled DEBUG2 while running the server and remote client from a command line, and was able to witness the issue: server: [code][2016-01-01T19:01:43] DEBUG2: send mouse move to "laptop" 12,433 [2016-01-01T19:01:43] DEBUG2: writef(DMMV%2i%2i) [2016-01-01T19:01:43] DEBUG2: wrote 8 bytes [2016-01-01T19:01:43] DEBUG2: event: MotionNotify 1744,450 [2016-01-01T19:01:43] DEBUG2: msg from "laptop": CNOP [2016-01-01T19:01:43] DEBUG2: no-op from [2016-01-01T19:01:43] DEBUG2: event: MotionNotify 1707,450 [2016-01-01T19:01:43] DEBUG2: warped to 1744,450 [2016-01-01T19:01:43] DEBUG2: event: MotionNotify 1707,450 [2016-01-01T19:01:43] DEBUG2: warped to 1744,450 [2016-01-01T19:01:43] DEBUG2: event: MotionNotify 1744,450 [2016-01-01T19:01:43] DEBUG2: onMouseMoveSecondary -37,+0 [2016-01-01T19:01:43] DEBUG2: find neighbor on left of "laptop" [2016-01-01T19:01:43] DEBUG2: "curly" is on left of "laptop" at 0.564453 [2016-01-01T19:01:43] DEBUG1: try to leave "laptop" on left [2016-01-01T19:01:43] DEBUG2: mapping state: 16 [2016-01-01T19:01:43] DEBUG2: |= modifier: 4 [2016-01-01T19:01:43] INFO: switch from "laptop" to "curly" at 2439,508 [2016-01-01T19:01:43] DEBUG1: send leave to "laptop" [2016-01-01T19:01:43] DEBUG2: writef(COUT) [2016-01-01T19:01:43] DEBUG2: wrote 4 bytes [2016-01-01T19:01:43] DEBUG2: mapping state: 16 [2016-01-01T19:01:43] DEBUG2: |= modifier: 4 [2016-01-01T19:01:43] DEBUG2: warped to 2439,508 [2016-01-01T19:01:43] INFO: entering screen [2016-01-01T19:01:43] DEBUG1: ignoring X error: 8 [2016-01-01T19:01:43] DEBUG: send xscreensaver command: 491 0 0 [2016-01-01T19:01:43] DEBUG1: flagging X error: 3 [/code] client: [code][2016-01-01T18:39:34] INFO: leaving screen [2016-01-01T18:39:34] INFO: entering screen [2016-01-01T18:52:53] INFO: leaving screen [2016-01-01T18:53:05] INFO: entering screen [2016-01-01T18:54:17] INFO: leaving screen [2016-01-01T18:54:46] INFO: entering screen [2016-01-01T18:54:46] INFO: leaving screen [2016-01-01T18:54:46] INFO: entering screen [2016-01-01T18:57:04] INFO: leaving screen [2016-01-01T18:57:18] INFO: entering screen [2016-01-01T18:57:25] INFO: leaving screen [2016-01-01T18:57:26] INFO: entering screen [2016-01-01T18:57:26] INFO: leaving screen [2016-01-01T18:57:32] INFO: entering screen [2016-01-01T18:57:34] INFO: leaving screen [2016-01-01T18:58:22] INFO: entering screen [2016-01-01T18:58:22] INFO: clipboard was updated [2016-01-01T19:01:22] INFO: leaving screen [2016-01-01T19:01:57] NOTE: server is dead [2016-01-01T19:01:57] WARNING: failed to connect to server: server is not responding [2016-01-01T19:01:58] NOTE: connecting to '192.168.1.118': 192.168.1.118:24800 [2016-01-01T19:02:13] WARNING: failed to connect to server: Timed out [/code] Client continues to retry the connection, always failing. The server is not able to be stopped with a Ctrl+C, and a kill -9 is required instead. Upon restarting the server, connection with the client is reestablished. I cannot say for sure if this is related to other reports suspecting copy-paste, though I've also stopped attempting to as part of testing. What may still be occurring, however, is Xorg's built-in 'highlight, middle click' as a secondary copy buffer. In an attempt to narrow down the issue, I've disabled encryption, SSL, and firewalls. Running mtr between boxes does show a spike in ping times during a screen change, sometimes resulting in a lost packet. As a band aid fix I've hacked together a keyboard shortcut to kill everything and restart everything. Server side details: [list]Linux curly 4.1.0-1-686-pae #1 SMP Debian 4.1.3-1 (2015-08-03) i686 GNU/Linux synergys 1.7.5, protocol version 1.6[/list:u] Client side details: [list]Linux larry 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:22 UTC 2015 i686 i686 i686 GNU/Linux synergyc 1.7.5, protocol version 1.6[/list:u] I figure I'll keep troubleshooting and add details here as I go. Perhaps someone sees something I don't.

[Adam McKee 0]

New observations: This message (almost?) always appears in the logs for synergys just before breakage: [code][2016-02-02T19:23:35] DEBUG1: ignoring X error: 8[/code] Restoring connections to both clients is quick and easy by restarting the server. Interestingly, 'synergys' is not easily killable, and requires a SIGKILL to have an affect. This suggest the server binary is locking up, most likely due to ignoring whatever that X error is. Since my first post, I've put all devices in question on a wired network, and the laggyness along with rate of lockups have decreased quite a bit. I wonder if there's an issue with the flood of UDP packets the server sends for mouse positional updates. Could the flood be saturating the connection enough, and is there handling in the code for delayed/lost packets?

[Adam McKee 0]

I've installed the new version, 1.7.6 on all of my systems, and haven't found issues since. No crashing on client or server, and copy/paste working in all directions without issue. Nice! Something did strike me as odd, which is that I installed all three updates within a 10m timespan, and the process runtimes on each are very different: Server: 1h 30m Client 1: 23m Client 2: 1h 6m Meh. It works seamlessly again from an end user perspective.