Jump to content

Synergy2 will not connect on any computer

rwheckman

By rwheckman
in General Discussion

Recommended Posts

rwheckman

rwheckman

Posted
Posted

Computer: heckman

log: 

[ Config ] [2017-10-25T11:32:18] INFO: log filename: /home/heckman/.config/Symless/Synergy/synergy.log

[ Config ] [2017-10-25T11:32:18] DEBUG: connecting to service

[ Config ] [2017-10-25T11:32:18] DEBUG: connected to service

[ Config ] [2017-10-25T11:32:18] DEBUG: new added screen pos: 257 161

[ Config ] [2017-10-25T11:32:19] DEBUG: current version is update to date

[ Config ] [2017-10-25T11:32:19] DEBUG: requesting profile snapshot

[ Service ] [2017-10-25T11:32:19] debug: sending last profile snapshot

[ Service ] [2017-10-25T11:32:19] debug: config ui opened, forcing connectivity test

[ Service ] [2017-10-25T11:32:19] debug: new screens detected (4), preparing connectivity test

[ Service ] [2017-10-25T11:32:19] debug: handling local profile screen set changed, mode=server

[ Service ] [2017-10-25T11:32:19] debug: starting core server process

[ Service ] [2017-10-25T11:32:19] debug: process already running, attempting to stop

[ Service ] [2017-10-25T11:32:19] debug: stopping core process

[ Config ] [2017-10-25T11:32:19] DEBUG: Profile ID: 8305 name: default

[ Config ] [2017-10-25T11:32:29] INFO: Sending log file...

[ Config ] [2017-10-25T11:32:30] INFO: Upload path: https://synergy-logs.symless.com/2017-10-25/8317-2017-10-25T11-32-30.log

 

This is typical for all computers, whether Linux or Windows.  Computer icon never goes green, as it never completes it's own connection internally.

Link to comment
Share on other sites
JDDoesIT

JDDoesIT

Posted
Posted 
[ Service ] [2017-10-16T10:19:14] debug: tcp client connect error: No route to host
[ Service ] [2017-10-16T10:19:14] debug: connectivity test failed for 9.34.214.210:24810

I am sure this is the cause. 

Link to comment
Share on other sites
rwheckman

rwheckman

Posted
  • Author
Posted

You're quoting a log not in this thread, so I have no real reference to be able to make a comparison.  I had opened up port 24800 previously, but never saw that port 24810 needed to be open in the firewall.  I have now opened that port and have experienced no change, that is to say, no success in connecting between machines.

This is the log from rwh-yoga

[ Config  ] [2018-10-26T07:15:42] INFO: log filename: /home/heckman/.config/Symless/Synergy/synergy.log
[ Config  ] [2017-10-26T07:15:42] DEBUG: connecting to service
[ Config  ] [2017-10-26T07:15:42] DEBUG: connected to service
[ Config  ] [2017-10-26T07:15:42] DEBUG: new added screen pos: 257 161
[ Config  ] [2017-10-26T07:15:43] DEBUG: current version is update to date
[ Config  ] [2017-10-26T07:15:43] DEBUG: Profile ID: 8305 name: default
[ Config  ] [2017-10-26T07:15:43] DEBUG: requesting profile snapshot
[ Service ] [2017-10-26T07:15:43] debug: sending last profile snapshot
[ Service ] [2017-10-26T07:15:43] debug: config ui opened, forcing connectivity test
[ Service ] [2017-10-26T07:15:43] debug: new screens detected (4), preparing connectivity test
[ Service ] [2017-10-26T07:15:43] debug: starting connectivity test
[ Service ] [2017-10-26T07:15:43] debug: handling local profile screen set changed, mode=client
[ Service ] [2017-10-26T07:15:46] debug: failed report: dest = 16556, ips = 192.168.20.100,192.168.122.1
[ Service ] [2017-10-26T07:15:46] debug: local profile modified, id=8305
[ Service ] [2017-10-26T07:15:46] debug: comparing profiles, id=8305 this=v19 other=v19
[ Service ] [2017-10-26T07:15:46] debug: profile screen test result changed, screenId=16556 success=``->`` failed=``->`192.168.20.100,192.168.122.1`
[ Service ] [2017-10-26T07:15:46] debug: handling new report from connectivity tester, screenId=16556 successfulIp= lastServerId=16556
[ Service ] [2017-10-26T07:15:46] debug: finished connectivity test

This is today's log from heckman:

[ Config ] [2017-10-26T07:22:03] INFO: log filename: /home/heckman/.config/Symless/Synergy/synergy.log

[ Config ] [2017-10-26T07:22:03] DEBUG: connecting to service

[ Config ] [2017-10-26T07:22:03] DEBUG: connected to service

[ Config ] [2017-10-26T07:22:03] DEBUG: new added screen pos: 257 161

[ Config ] [2017-10-26T07:22:04] DEBUG: Profile ID: 8305 name: default

[ Config ] [2017-10-26T07:22:04] DEBUG: current version is update to date

[ Config ] [2017-10-26T07:22:04] DEBUG: requesting profile snapshot

[ Service ] [2017-10-26T07:22:04] debug: sending last profile snapshot

[ Service ] [2017-10-26T07:22:04] debug: config ui opened, forcing connectivity test

[ Service ] [2017-10-26T07:22:04] debug: new screens detected (4), preparing connectivity test

[ Service ] [2017-10-26T07:22:04] debug: starting connectivity test

[ Service ] [2017-10-26T07:22:04] debug: handling local profile screen set changed, mode=server

[ Service ] [2017-10-26T07:22:04] debug: starting core server process

[ Service ] [2017-10-26T07:22:04] debug: process already running, attempting to stop

[ Service ] [2017-10-26T07:22:04] debug: stopping core process

[ Service ] [2017-10-26T07:22:07] debug: failed report: dest = 16562, ips = 9.34.215.45

[ Service ] [2017-10-26T07:22:07] debug: local profile modified, id=8305

[ Service ] [2017-10-26T07:22:07] debug: comparing profiles, id=8305 this=v19 other=v19

[ Service ] [2017-10-26T07:22:07] debug: profile screen test result changed, screenId=16562 success=``->`` failed=``->`9.34.215.45`

[ Service ] [2017-10-26T07:22:07] debug: handling new report from connectivity tester, screenId=16562 successfulIp= lastServerId=16556

[ Service ] [2017-10-26T07:22:07] debug: finished connectivity test

[ Service ] [2017-10-26T07:22:07] debug: tcp client connect error: No route to host

[ Service ] [2017-10-26T07:22:07] debug: connectivity test failed for 9.34.215.45:24810

After pressing F12 on rwh-yoga, it too went to the scrolling green bar instead of green/connected.

Screenshot from 2017-10-26 07-18-57.png

Open ports on firewall.png

Link to comment
Share on other sites
rwheckman

rwheckman

Posted
  • Author
Posted

I had to further modify my firewall, opening ports 24800-24899.  I did connect once--but only once.  The synergy.service seems to start at boot up now and doesn't need to be started manually.  but the service seems to fall asleep on one machine, and the client can't connect to it even though it is running.

[ Config ] [2017-10-31T09:02:26] DEBUG: install dir: /usr/bin

[ Config ] [2017-10-31T09:02:26] INFO: log filename: /home/heckman/.config/Symless/Synergy/synergy.log

[ Config ] [2017-10-31T09:02:27] DEBUG: connecting to background service

[ Config ] [2017-10-31T09:02:27] DEBUG: new added screen pos: 257 161

[ Config ] [2017-10-31T09:02:28] DEBUG: current version is update to date

[ Config ] [2017-10-31T09:02:32] debug: rpc keep alive failed

[ Config ] [2017-10-31T09:02:37] debug: rpc keep alive failed

[ Config ] [2017-10-31T09:02:42] debug: rpc keep alive failed

[ Config ] [2017-10-31T09:02:47] debug: rpc keep alive failed

[ Config ] [2017-10-31T09:02:52] debug: rpc keep alive failed

[ Config ] [2017-10-31T09:02:57] debug: rpc keep alive failed

[ Config ] [2017-10-31T09:03:02] debug: rpc keep alive failed

[ Config ] [2017-10-31T09:03:07] debug: rpc keep alive failed

[ Config ] [2017-10-31T09:03:12] debug: rpc keep alive failed

 

synergy.service seems to be hung and will not restart.  Once I stopped the service (systemctl stop synergy.service) the other machine that was available for connection also lost it's connection to the background service.  This is the log from that machine:

 

[ Router  ] [2017-10-31T09:06:26] debug: Adding 192.168.122.1:24802
[ Router  ] [2017-10-31T09:06:26] debug: Connecting to 192.168.122.1:24802 (attempt 1/10)
[ Router  ] [2017-10-31T09:06:26] debug: Adding 9.34.214.88:24802
[ Router  ] [2017-10-31T09:06:26] debug: Connecting to 9.34.214.88:24802 (attempt 1/10)
[ Router  ] [2017-10-31T09:06:26] debug: Adding 192.168.1.13:24802
[ Router  ] [2017-10-31T09:06:26] debug: Connecting to 192.168.1.13:24802 (attempt 1/10)
[ Router  ] [2017-10-31T09:06:26] debug: Adding 192.168.124.1:24802
[ Router  ] [2017-10-31T09:06:26] debug: Connecting to 192.168.124.1:24802 (attempt 1/10)
[ Router  ] [2017-10-31T09:06:26] debug: Adding 9.34.215.90:24802
[ Router  ] [2017-10-31T09:06:26] debug: Connecting to 9.34.215.90:24802 (attempt 1/10)
[ Service ] [2017-10-31T09:06:26] debug: setting core uid from rpc: 1000
[ Router  ] [2017-10-31T09:06:26] debug: Connection 3 created
[ Router  ] [2017-10-31T09:06:26] debug: Accepted connection from router 9.34.214.88:36170
[ Router  ] [2017-10-31T09:06:26] debug: Connection 4 created
[ Router  ] [2017-10-31T09:06:26] debug: Successfully connected to 9.34.214.88:24802
[ Router  ] [2017-10-31T09:06:26] debug: Successfully connected to 9.34.214.88:24802
[ Router  ] [2017-10-31T09:06:26] debug: Connection to 9.34.215.90:24802 refused
[ Router  ] [2017-10-31T09:06:26] debug: Received route advertisement from router 16562
[ Router  ] [2017-10-31T09:06:26] debug:  Received own route advertisement. This indicates a loop. Ignoring
[ Router  ] [2017-10-31T09:06:26] debug: Received route advertisement from router 16562
[ Router  ] [2017-10-31T09:06:26] debug:  Received own route advertisement. This indicates a loop. Ignoring
[ Service ] [2017-10-31T09:06:26] debug: sending last profile snapshot
[ Config  ] [2017-10-31T09:06:26] DEBUG: service cloud connection recovered
[ Config  ] [2017-10-31T09:06:27] DEBUG: current version is update to date
[ Router  ] [2017-10-31T09:06:27] debug: Received own hello message. Closing connection 3
[ Router  ] [2017-10-31T09:06:27] debug:  Disabling connection 3
[ Router  ] [2017-10-31T09:06:27] debug: Removing 0 route(s) broken by removal of connection 3
[ Router  ] [2017-10-31T09:06:27] debug: Route table is empty
[ Router  ] [2017-10-31T09:06:27] debug: Connection 3 is not enabled
[ Router  ] [2017-10-31T09:06:27] debug: Connection 3 terminated receive loop
[ Router  ] [2017-10-31T09:06:27] debug: Received own hello message. Closing connection 4
[ Router  ] [2017-10-31T09:06:27] debug:  Disabling connection 4
[ Router  ] [2017-10-31T09:06:27] debug: Removing 0 route(s) broken by removal of connection 4
[ Router  ] [2017-10-31T09:06:27] debug: Route table is empty
[ Router  ] [2017-10-31T09:06:27] debug: Connection 4 is not enabled
[ Router  ] [2017-10-31T09:06:27] debug: Connection 4 terminated receive loop
[ Router  ] [2017-10-31T09:06:27] debug: Connecting to 9.34.215.90:24802 (attempt 2/10)
[ Router  ] [2017-10-31T09:06:27] debug: Connection to 9.34.215.90:24802 refused
[ Router  ] [2017-10-31T09:06:28] debug: Connecting to 9.34.215.90:24802 (attempt 3/10)
[ Router  ] [2017-10-31T09:06:28] debug: Connection to 9.34.215.90:24802 refused
[ Router  ] [2017-10-31T09:06:28] debug: Connection to 9.34.214.159:24802 refused
[ Router  ] [2017-10-31T09:06:29] debug: Connection 4 destroyed
[ Router  ] [2017-10-31T09:06:29] debug: Connection 3 destroyed
[ Router  ] [2017-10-31T09:06:29] debug: Connecting to 9.34.215.90:24802 (attempt 4/10)
[ Router  ] [2017-10-31T09:06:29] debug: Connection to 9.34.215.90:24802 refused
[ Router  ] [2017-10-31T09:06:29] debug: Connecting to 9.34.214.159:24802 (attempt 2/10)
[ Router  ] [2017-10-31T09:06:30] debug: Connecting to 9.34.215.90:24802 (attempt 5/10)
[ Router  ] [2017-10-31T09:06:30] debug: Connection to 9.34.215.90:24802 refused
[ Core    ] [2017-10-31T09:06:31] NOTE: server is dead
[ Router  ] [2017-10-31T09:06:31] debug: Error reading from core client: End of file
[ Router  ] [2017-10-31T09:06:31] debug: Terminating core client read loop
[ Core    ] [2017-10-31T09:06:31] WARNING: failed to connect to server: server is not responding
[ Core    ] [2017-10-31T09:06:31] DEBUG: retry in 1 seconds
[ Router  ] [2017-10-31T09:06:31] debug: Connection to 192.168.20.100:24802 timed out
[ Router  ] [2017-10-31T09:06:31] debug: Connection to 192.168.122.1:24802 timed out
[ Router  ] [2017-10-31T09:06:31] debug: Connection to 192.168.1.13:24802 timed out
[ Router  ] [2017-10-31T09:06:31] debug: Connection to 192.168.124.1:24802 timed out
[ Router  ] [2017-10-31T09:06:31] debug: Connecting to 9.34.215.90:24802 (attempt 6/10)
[ Router  ] [2017-10-31T09:06:31] debug: Connection to 9.34.215.90:24802 refused
[ Core    ] [2017-10-31T09:06:32] NOTE: connecting to '127.0.0.1': 127.0.0.1:24801
[ Router  ] [2017-10-31T09:06:32] debug: Saying Hello to core client
[ Router  ] [2017-10-31T09:06:32] debug: Connecting to 192.168.20.100:24802 (attempt 2/10)
[ Router  ] [2017-10-31T09:06:32] debug: Connecting to 192.168.122.1:24802 (attempt 2/10)
[ Router  ] [2017-10-31T09:06:32] debug: Connecting to 192.168.1.13:24802 (attempt 2/10)
[ Router  ] [2017-10-31T09:06:32] debug: Connecting to 192.168.124.1:24802 (attempt 2/10)
[ Router  ] [2017-10-31T09:06:32] debug: Connecting to 9.34.215.90:24802 (attempt 7/10)
[ Router  ] [2017-10-31T09:06:32] debug: Connection to 9.34.215.90:24802 refused
[ Service ] [2017-10-31T09:06:32] debug: comparing profiles, id=8305 this=v19 other=v19
[ Service ] [2017-10-31T09:06:32] debug: profile has not changed, no action needed
[ Config  ] [2017-10-31T09:06:32] DEBUG: service cloud connection recovered
[ Router  ] [2017-10-31T09:06:33] debug: Connecting to 9.34.215.90:24802 (attempt 8/10)
[ Router  ] [2017-10-31T09:06:33] debug: Connection to 9.34.215.90:24802 refused
[ Router  ] [2017-10-31T09:06:33] debug: Connection to 9.34.214.159:24802 refused
[ Router  ] [2017-10-31T09:06:34] debug: Connecting to 9.34.215.90:24802 (attempt 9/10)
[ Router  ] [2017-10-31T09:06:34] debug: Connection to 9.34.215.90:24802 refused
[ Router  ] [2017-10-31T09:06:34] debug: Connecting to 9.34.214.159:24802 (attempt 3/10)
[ Router  ] [2017-10-31T09:06:35] debug: Connecting to 9.34.215.90:24802 (attempt 10/10)
[ Router  ] [2017-10-31T09:06:35] debug: Connection to 9.34.215.90:24802 refused
[ Router  ] [2017-10-31T09:06:36] debug: Gave up trying to connect to 9.34.215.90:24802
[ Router  ] [2017-10-31T09:06:37] debug: Connection to 192.168.20.100:24802 timed out
[ Router  ] [2017-10-31T09:06:37] debug: Connection to 192.168.122.1:24802 timed out
[ Router  ] [2017-10-31T09:06:37] debug: Connection to 192.168.1.13:24802 timed out
[ Router  ] [2017-10-31T09:06:37] debug: Connection to 192.168.124.1:24802 timed out
[ Router  ] [2017-10-31T09:06:38] debug: Connecting to 192.168.20.100:24802 (attempt 3/10)
[ Router  ] [2017-10-31T09:06:38] debug: Connecting to 192.168.122.1:24802 (attempt 3/10)
[ Router  ] [2017-10-31T09:06:38] debug: Connecting to 192.168.1.13:24802 (attempt 3/10)
[ Router  ] [2017-10-31T09:06:38] debug: Connecting to 192.168.124.1:24802 (attempt 3/10)
[ Router  ] [2017-10-31T09:06:39] debug: Connection to 9.34.214.159:24802 refused
[ Router  ] [2017-10-31T09:06:40] debug: Connecting to 9.34.214.159:24802 (attempt 4/10)
[ Core    ] [2017-10-31T09:06:41] NOTE: server is dead
[ Router  ] [2017-10-31T09:06:41] debug: Error reading from core client: End of file
[ Router  ] [2017-10-31T09:06:41] debug: Terminating core client read loop
[ Core    ] [2017-10-31T09:06:41] WARNING: failed to connect to server: server is not responding
[ Core    ] [2017-10-31T09:06:41] DEBUG: retry in 1 seconds
[ Router  ] [2017-10-31T09:06:41] debug: Connection to 9.34.214.159:24802 refused
[ Core    ] [2017-10-31T09:06:42] NOTE: connecting to '127.0.0.1': 127.0.0.1:24801
[ Router  ] [2017-10-31T09:06:42] debug: Saying Hello to core client
[ Router  ] [2017-10-31T09:06:42] debug: Connecting to 9.34.214.159:24802 (attempt 5/10)
[ Service ] [2017-10-31T09:06:42] debug: comparing profiles, id=8305 this=v19 other=v19
[ Service ] [2017-10-31T09:06:42] debug: profile has not changed, no action needed
[ Config  ] [2017-10-31T09:06:42] DEBUG: service cloud connection recovered

 

Overall:  Yes beta 5 is different than beta 4, and not as boring.  Beta4 always failed the same way.  beta5 seems to find different ways to fail each time, while giving the hope that it might work....then something new goes wrong.  odd.

Screenshot from 2017-10-31 09-02-01.png

Link to comment
Share on other sites
rwheckman

rwheckman

Posted
  • Author
Posted

I am perplexed by the logs.  The 2 machines I am attempting to connect have ip's on the same subnet, one ending with 159 and the other with 88.  However the logs show attempts to connect to a log of other ip's that have nothing to do with either of these machines:

[ Service ] [2017-10-31T09:37:58] debug: comparing profiles, id=8305 this=v19 other=v19
[ Service ] [2017-10-31T09:37:58] debug: profile has not changed, no action needed
[ Config  ] [2017-10-31T09:37:58] DEBUG: service cloud connection recovered
[ Router  ] [2017-10-31T09:37:58] debug: Connecting to 9.34.215.90:24802 (attempt 6/10)
[ Router  ] [2017-10-31T09:37:58] debug: Connection to 9.34.215.90:24802 refused
[ Router  ] [2017-10-31T09:37:59] debug: Connection to 192.168.1.13:24802 timed out
[ Router  ] [2017-10-31T09:37:59] debug: Connection to 192.168.124.1:24802 timed out
[ Router  ] [2017-10-31T09:37:59] debug: Connecting to 9.34.215.90:24802 (attempt 7/10)
[ Router  ] [2017-10-31T09:37:59] debug: Connection to 9.34.215.90:24802 refused
[ Router  ] [2017-10-31T09:38:00] debug: Connecting to 192.168.1.13:24802 (attempt 3/10)
[ Router  ] [2017-10-31T09:38:00] debug: Connecting to 192.168.124.1:24802 (attempt 3/10)
[ Router  ] [2017-10-31T09:38:00] debug: Connecting to 9.34.215.90:24802 (attempt 8/10)
[ Router  ] [2017-10-31T09:38:00] debug: Connection to 9.34.215.90:24802 refused
[ Router  ] [2017-10-31T09:38:01] debug: Connecting to 9.34.215.90:24802 (attempt 9/10)
[ Router  ] [2017-10-31T09:38:01] debug: Connection to 9.34.215.90:24802 refused
[ Router  ] [2017-10-31T09:38:02] debug: Connecting to 9.34.215.90:24802 (attempt 10/10)
[ Router  ] [2017-10-31T09:38:02] debug: Connection to 9.34.215.90:24802 refused
[ Router  ] [2017-10-31T09:38:03] debug: Gave up trying to connect to 9.34.215.90:24802
[ Router  ] [2017-10-31T09:38:05] debug: Connection to 192.168.1.13:24802 timed out
[ Router  ] [2017-10-31T09:38:05] debug: Connection to 192.168.124.1:24802 timed out
[ Router  ] [2017-10-31T09:38:06] debug: Connecting to 192.168.1.13:24802 (attempt 4/10)
[ Router  ] [2017-10-31T09:38:06] debug: Connecting to 192.168.124.1:24802 (attempt 4/10)
[ Router  ] [2017-10-31T09:38:11] debug: Connection to 192.168.1.13:24802 timed out
[ Router  ] [2017-10-31T09:38:11] debug: Connection to 192.168.124.1:24802 timed out
[ Router  ] [2017-10-31T09:38:12] debug: Connecting to 192.168.1.13:24802 (attempt 5/10)
[ Router  ] [2017-10-31T09:38:12] debug: Connecting to 192.168.124.1:24802 (attempt 5/10)
[ Router  ] [2017-10-31T09:38:17] debug: Connection to 192.168.1.13:24802 timed out
[ Router  ] [2017-10-31T09:38:17] debug: Connection to 192.168.124.1:24802 timed out


where is the .90 coming from?  192.168.1.13? 192.168.124.1? what's that about?  This seems to be a pretty severe security violation, and needs to be rectified as soon as possible.  My machines should only connect to each other and not to other random machines used by other synergy users.  By the same token, are other synergy users also connecting or failing to connect from their machine to mine?  This is not acceptable.

Link to comment
Share on other sites
  • Synergy Team
Nick Bolton

Nick Bolton

Posted
  • Synergy Team
Posted

Don't worry, it's not connecting to other users. It's not a security risk, and it's pretty harmless. These are simply IP addresses on your other machines (probably virtual machines, etc).

It's probably not a connection issue, but more likely that the background service is crashing for some reason. Have you tried restarting the services on both machines? Check out this post...

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

Go to topic listing
×
×
  • Create New...