Sign in to follow this  
Tyler Goulet

Connection issues with Synergy 1.8.1

6 posts in this topic

Hey all, I've had this problem with previous versions (1.7.6 is what I Just upgraded from) and unfortunately it seems to be even worse thus far. Synergy will be working fine and then suddenly the server will start throwing these messages: [2016-07-14T14:30:23] NOTE: disconnecting client "MLJ3AGF6T6" [2016-07-14T14:30:23] WARNING: a client with name "MLJ3AGF6T6" is already connected [2016-07-14T14:30:23] NOTE: client "MLJ3AGF6T6" has disconnected [2016-07-14T14:30:25] NOTE: accepted client connection [2016-07-14T14:30:25] INFO: accepted secure socket [2016-07-14T14:30:25] NOTE: disconnecting client "MLJ3AGF6T6" [2016-07-14T14:30:25] WARNING: a client with name "MLJ3AGF6T6" is already connected [2016-07-14T14:30:25] NOTE: client "MLJ3AGF6T6" has disconnected [2016-07-14T14:30:27] NOTE: accepted client connection [2016-07-14T14:30:27] INFO: accepted secure socket [2016-07-14T14:30:28] NOTE: disconnecting client "MLJ3AGF6T6" [2016-07-14T14:30:28] WARNING: a client with name "MLJ3AGF6T6" is already connected [2016-07-14T14:30:28] NOTE: client "MLJ3AGF6T6" has disconnected [2016-07-14T14:30:30] NOTE: accepted client connection [2016-07-14T14:30:30] INFO: accepted secure socket [2016-07-14T14:30:30] WARNING: a client with name "MLJ3AGF6T6" is already connected [2016-07-14T14:30:30] NOTE: disconnecting client "MLJ3AGF6T6" [2016-07-14T14:30:30] NOTE: client "MLJ3AGF6T6" has disconnected [2016-07-14T14:30:32] NOTE: accepted client connection [2016-07-14T14:30:32] INFO: accepted secure socket [2016-07-14T14:30:33] NOTE: disconnecting client "MLJ3AGF6T6" [2016-07-14T14:30:33] WARNING: a client with name "MLJ3AGF6T6" is already connected [2016-07-14T14:30:33] NOTE: client "MLJ3AGF6T6" has disconnected [2016-07-14T14:30:35] NOTE: accepted client connection [2016-07-14T14:30:35] INFO: accepted secure socket [2016-07-14T14:30:35] NOTE: disconnecting client "MLJ3AGF6T6" [2016-07-14T14:30:35] WARNING: a client with name "MLJ3AGF6T6" is already connected [2016-07-14T14:30:35] NOTE: client "MLJ3AGF6T6" has disconnected [2016-07-14T14:30:37] NOTE: accepted client connection [2016-07-14T14:30:37] INFO: accepted secure socket [2016-07-14T14:30:38] NOTE: disconnecting client "MLJ3AGF6T6" [2016-07-14T14:30:38] WARNING: a client with name "MLJ3AGF6T6" is already connected [2016-07-14T14:30:38] NOTE: client "MLJ3AGF6T6" has disconnected [2016-07-14T14:30:39] INFO: screen "tyler-OptiPlex-9010" grabbed clipboard 1 from "MLJ3AGF6T6" And on the client side I see: [2016-07-14T14:26: 53] WARNING: failed to connect to server: server already has a connected client with our name [2016-07-14T14:26:54] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-07-14T14:26:54] NOTE: server fingerprint: 9C:AD:AF:0B:23:F9:54:2D:C4:BB:2C:E4:F3:9E:11:60:A7:16:7C:C3 [2016-07-14T14:26:54] INFO: connected to secure socket [2016-07-14T14:26:54] INFO: server ssl certificate info: /CN=Synergy [2016 -07-14T14:26:55] ERROR: server already has a connected client with name "MLJ3AGF6T6" [2016-07-14T14:26:56] WARNING: failed to connect to server: server alread y has a connected client with our name [2016-07-14T14:26:57] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-07-14T14:26:58] NOTE: server fingerprint: 9C:AD:AF:0B:23:F9:54:2D:C4:BB:2C:E4:F3:9E:11:60:A7:16:7C:C3 [2016-07-14T14:26:58] INFO: connected to secure socket [2016-07-14T14:26:58] INFO: server ssl certificate info: /CN=Synergy [2016-07-14T14:26:58] ERROR: server already has a connected clie nt with name "MLJ3AGF6T6" [2016-07-14T14:26:59] WARNING: failed to connect to server: server already has a connected client with our name [2016-07-14T14:27:00] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-07-14T14:27:00] NOTE: server fingerprint: 9C:AD:AF:0B:23:F9:54:2D:C4:BB:2C:E4:F3:9E:11:60:A7:16:7C:C3 [2016-07-14T14:27:00] INFO: connected to secure socket [2016-07-14T14:27:00] INFO: server ssl certificate info: /CN=Synergy [2016-07-14T14:27:01] ERROR: server already has a connected client with name "MLJ3AG F6T6" [2016-07- 14T14:27:02] WARNING: failed to connect to server: server already has a connected client with our name [2016-07-14T14:27:03] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-07-14T14:27:04] NOTE: server fingerprint: 9C:AD:AF:0B:23:F9:54:2D:C4:BB:2C:E4:F3:9E:11:60:A7:16:7C:C3 [2016-07-14T14:27:04] INFO: connected to secure socket [2016-07-14T14:27:04] INFO: server ssl certificate info: /CN=Synergy [2016-07-14T14:27:04] ERROR: server already has a connected client with name "MLJ3AGF6T6" [2016-07-14T14:27:0 5] WARNING: failed to connect to server: server already has a connected client with our name [2016-07-14T14:27:06] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-07-14T14:27:06] NOTE: server fingerprint: 9C:AD:AF:0B:23:F9:54:2D:C4:BB:2C:E4:F3:9E:11:60:A7:16:7C:C3 [2016-07-14T14:27:06] INFO: connected to secure socket [2016-07-14T14:27:06] INFO: server ssl certificate info: /CN=Synergy [2016-07-14T14:27:07] ERROR: server already has a connected client with name "MLJ3AGF6T6" [2016-07-14T14:27:09] WARNING: failed to connect to server: server already has a connected client wi th our name [2016-07-14T14:27:10] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-07-14T14:27:10] NOTE: server fingerprint: 9C:AD:AF:0B:23:F9:54:2D:C4:BB:2C:E4:F3:9E:11:60:A7:16:7C:C3 [2016-07-14T14:27:10] INFO: connected to secure socket [2016-07-14T14:27:10] INFO: server ssl certificate info: /CN=Synergy [2016-07-14T14:27:10] ERROR: server already has a connected client with name "MLJ3AGF6T6" [2016-07-14T14:27:11] WARNING: failed to connect to ser ver: server already has a connected client with our name [2016-07-14T14:27:12] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-07-14T14:27:12] NOTE: server fingerprint: 9C:AD:AF:0B:23:F9:54:2D:C4:BB:2C:E4:F3:9E:11:60:A7:16:7C:C3 [2016-07-14T14:27:12] INFO: connected to secure socket [2016-07-14T14:27:12] INFO: server ssl certificate info: /CN=Synergy [2016-07-14T14:27:13] ERROR: server already has a connected client wit h name "MLJ3AGF6T6" [2016-07-14T14:27:14] WARNING: failed to connect to server: server already has a connec ted client with our name [2016-07-14T14:27:15] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-07-14T14:27:16] NOTE: server fingerprint: 9C:AD:AF:0B:23:F9:54:2D:C4:BB:2C:E4:F3:9E:11:60:A7:16:7C:C3 [2016-07-14T14:27:16] INFO: connected to secure socket [2016-07-14T14:27:16] INFO: server ssl certificate info: /CN=Synergy [2016-07-14T14:27:16] ERROR: server already has a connected client with name "MLJ3AGF6T6" [2016-07-14T14:27:17] WARNING: failed to connect to server: server already has a con nected client with our name [2016-07-14T14:27:18] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-07-14T14:27:18] NOTE: server fingerprint: 9C:AD:AF:0B:23:F9:54:2D:C4:BB:2C:E4:F3:9E:11:60:A7:16:7C:C3 [2016-07-14T14:27:19] INFO: connected to secure socket [2016-07-14T14:27:19] INFO: server ssl certificate info: /CN=Synergy [2016-07-14T14:27:19] ERROR: server already has a connected client with name "MLJ3AGF6T6" [2016-07-14T14:27:20] INFO: stopping synergy desktop process [2016-07-14T14:27:20] INFO: process exited normally [2016-07-14T14:31:50] INFO: starting client [2016-07-14T14:31:50] INFO: config file: /var/folders/d2/3j_syprd3qjgrw6ftp4r_bgsm8f5b7/T/Synergy.P42506 [2016-07-14T14:31:50] INFO: log level: INFO When I "stop" the client, the server keeps throwing the same error over and over again even though the client application is stopped which doesn't make sense to me. The only thing I can do to get the connection back is kill the server and restart but even then sometimes it will immediately say the client is already connected when that's simply not possible. Also, sometimes instead of disconnecting immediately, while it's looping through these warnings, it will allow the input to pass through between the computers but it will be spotty (work for 1 second or so) and then continue and the 'system bar' icon no longer shows the check mark to indicate the connection is established and then synergyc will shoot up to like 40% CPU usage (up from usual 2-4%). This is on a Ubuntu 16.04 LTS server and a Mac OSX 10.11.5 Client. Any ideas guys? Anymore info I can provide? Thanks, -Tyler

Share this post


Link to post
Share on other sites
For what it's worth - it's much better today (no issues thus far) so I'll give it some more time and update this ticket as needed. Maybe some initial upgrade quirks? -Tyler

Share this post


Link to post
Share on other sites
Hey all, I've updated to Synergy 1.8.2 today and I'm still seeing 'client already connected' disconnect / reconnect errors: [2016-08-08T11:58:02] INFO: OpenSSL 1.0.2 22 Jan 2015 [2016-08-08T11:58:02] NOTE: server fingerprint: 18:3D:2F:A4:34:67:12:77:47:7F:0A:D4:B5:E2:40:59:54:14:7E:D6 [2016-08-08T11:58:02] INFO: connected to secure socket [2016-08-08T11:58:02] INFO: server ssl certificate info: /CN=Synergy [2016-08-08T11:58:02] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2016-08-08T11:58:03] ERROR: server already has a connected client with name "MLJ3AGF6T6" [2016-08-08T11:58:04] WARNING: failed to connect to serv [2016-08-08T11:58:04] DEBUG: retry in 1 seconds er: server already has a connected client with our name [2016-08-08T11:58:05] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-08-08T11:58:05] INFO: OpenSSL 1.0.2 22 Jan 2015 [2016-08-08T11:58:05] NOTE: server fingerprint: 18:3D:2F:A4:34:67:12:77:47:7F:0A:D4:B5:E2:40:59:54:14:7E:D6 [2016-08-08T11:58:05] INFO: connected to secure socket [2016-08-08T11:58:05] INFO: server ssl certificate info: /CN=Synergy [2016-08-08T11:58:05] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2016-08-08T11:58:05] ERROR: server already has a connected client with name "MLJ3AGF6T6" [2016-08-08T11:58:06] WARNING: failed to connect to server: server already has a connected client with our name [2016-08-08T11:58:06] DEBUG: retry in 1 seconds [2016-08-08T11:58:07] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-08-08T11:58:07] INFO: OpenSSL 1.0.2 22 Jan 2015 [2016-08-08T11:58:07] NOTE: server fingerprint: 18:3D:2F:A4:34:67:12:77:47:7F:0A:D4:B5:E2:40:59:54:14:7E:D6 [2016-08-08T11:58:07] INFO: connected to secure socket [2016-08-08T11:58:07] INFO: server ssl certificate info: /CN=Synergy [2016-08-08T11:58:07] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2016-08-08T11:58:08] ERROR: server already has a connected client with name "MLJ3AGF6T6" [ [2016-08-08T11:58:09] DEBUG: retry in 1 seconds 2016-08-08T11:58:09] WARNING: failed to connect to server: server already has a connected client with our name [2016-08-08T11:58:10] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-08-08T11:58:10] INFO: OpenSSL 1.0.2 22 Jan 2015 [2016-08-08T11:58:10] NOTE: server fingerprint: 18:3D:2F:A4:34:67:12:77:47:7F:0A:D4:B5:E2:40:59:54:14:7E:D6 [2016-08-08T11:58:10] INFO: connected to secure socket [2016-08-08T11:58:10] INFO: server ssl certificate info: /CN=Synergy [2016-08-08T11:58:10] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2016-08-08T11:58:10] ERROR: serv er already has a connected client with name "MLJ3AGF6T6" [2016-08-08T11:58:11] WARNING: failed to connect to server: server already has a connected client with our name [2016-08-08T11:58:11] DEBUG: retry in 1 seconds [2016-08-08T11:58:12] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-08-08T11:58:12] INFO: OpenSSL 1.0.2 22 Jan 2015 [2016-08-08T11:58:12] NOTE: server fingerprint: 18:3D:2F:A4:34:67:12:77:47:7F:0A:D4:B5:E2:40:59:54:14:7E:D6 [2016-08-08T11:58:12] INFO: connected to secure socket [2016-08-08T11:58:12] INFO: server ssl certificate info: /CN=Synergy [2016-08-08T11:58:12] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2016-08-08T11:58:13] ERROR: server already has a connected client with name "MLJ3AGF6T6" [2016-08-08T11:58:14] WARNING: failed to connect to server: server already ha [2016-08-08T11:58:14] DEBUG: retry in 1 seconds s a connected client with our name [2016-08-08T11:58:15] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-08-08T11:58:15] INFO: OpenSSL 1.0.2 22 Jan 2015 [2016-08-08T11:58:15] NOTE: server fingerprint: 18:3D:2F:A4:34:67:12:77:47:7F:0A:D4:B5:E2:40:59:54:14:7E:D6 [2016-08-08T11:58:15] INFO: connected to secure socket [2016-08-08T11:58:15] INFO: server ssl certificate info: /CN=Synergy [2016-08-08T11:58:15] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2016-08-08T11:58:15] ERROR: server already has a connected client with name "MLJ3AGF6T6" [2016-08-08T11:58:16] WARNING: failed to connect to server: server already has a connect ed client with our name [2016-08-08T11:58:16] DEBUG: retry in 1 seconds [2016-08-08T11:58:17] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-08-08T11:58:17] INFO: OpenSSL 1.0.2 22 Jan 2015 [2016-08-08T11:58:17] NOTE: server fingerprint: 18:3D:2F:A4:34:67:12:77:47:7F:0A:D4:B5:E2:40:59:54:14:7E:D6 [2016-08-08T11:58:17] INFO: connected to secure socket [2016-08-08T11:58:17] INFO: server ssl certificate info: /CN=Synergy [2016-08-08T11:58:17] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2016-08-08T11:58:18] ERROR: server already has a connected c lient with name "MLJ3AGF6T6" [2016-08-08T11:58:19] WARNING: failed to connect to server: server already has a connected client [2016-08-08T11:58:19] DEBUG: retry in 1 seconds with our name [2016-08-08T11:58:20] NOTE: connecting to '10.66.58.170': 10.66.58.170:24800 [2016-08-08T11:58:20] INFO: OpenSSL 1.0.2 22 Jan 2015 [2016-08-08T11:58:20] NOTE: server fingerprint: 18:3D:2F:A4:34:67:12:77:47:7F:0A:D4:B5:E2:40:59:54:14:7E:D6 [2016-08-08T11:58:20] INFO: connected to secure socket [2016-08-08T11:58:20] INFO: server ssl certificate info: /CN=Synergy [2016-08-08T11:58:20] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2016-0 8-08T11:58:20] ERROR: server already has a connected client with name "MLJ3AGF6T6" [2016-08-08T 11:58:21] WARNING: failed to connect to server: server already has a connected client with our name [2016-08-08T11:58:21] DEBUG: retry in 1 seconds Is there any way I can force it to punt the existing client and take control of the connection? I end up in this weird split state where I have to restart the server and client to reestaslish the connection. The odd part is that when it's in the split brain kind of state, synergy on the client thinks the connection has dropped but it's actually in/out (intermittent) - basically adds like a 500 ms delay to the input so it still works but it's frustrating to use and doesn't work as normal. Thanks, -Tyler

Share this post


Link to post
Share on other sites
I'm seeing the same issue on 1.8.2. Windows 10 1511 Server Mac OS 10.11.6 Client If I close the lid of my MacBook Air, it shows a screen resize then Synergy will say that there is already the host that is connected.

Share this post


Link to post
Share on other sites
I was also getting exactly the same [code]ERROR: server already has a connected client with name "The-MacBook-Pro.local"[/code] message. Running 1.8.2 on MacOS 10.11.6 on both server and client. I then realised that in the preferences, the screen name was set the same for both instances. Silly mistake, but it's now working fine.

Share this post


Link to post
Share on other sites
I was also getting exactly the same
ERROR: server already has a connected client with name "The-MacBook-Pro.local"

message. Running 1.8.2 on MacOS 10.11.6 on both server and client.

 

I then realised that in the preferences, the screen name was set the same for both instances. Silly mistake, but it's now working fine.

 

My screen names have never been the same so unfortunately, this is not the problem. I am happy to report, however, that the issue is happening much,much less frequently!

 

I can now at least go multiple days without having to restart either the client or server which is good. Feel like Synergy is back to being called a Productive app again!

 

-Tyler

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this