Jump to content

Beta Application Fails with Reinstall


SoleRunNHide

Recommended Posts

SoleRunNHide

Currently the beta application will fall into an endless connecting loop if a PC already included in the sync has its OS installed and then is reconnected via a new installation of the Synergy 2.0 (latest version).  The system will then show 3 devices, but not allow for actual 2 to connect (assuming 2 devices).  Can I get staff to remove the saved computers in my synergy account so that it will auto configure, as I know manually removing systems is not yet available in this version.

Link to comment
Share on other sites

SoleRunNHide

Device which had the reinstall 

[Core] [2017-08-20T12:53:29] DEBUG: retry in 1 seconds
[Core] [2017-08-20T12:53:30] NOTE: connecting to '192.168.1.74': 192.168.1.74:24800
[ UI ] [2017-08-20T12:53:31] ERROR: [2017-08-20T12:53:31] WARNING: failed to connect to server: Connection was refused
[Core] [2017-08-20T12:53:31] DEBUG: retry in 1 seconds
[Core] [2017-08-20T12:53:32] NOTE: connecting to '192.168.1.74': 192.168.1.74:24800
[ UI ] [2017-08-20T12:53:33] ERROR: [2017-08-20T12:53:33] WARNING: failed to connect to server: Connection was refused

Device without reinstall

[Core] [2017-08-20T15:58:33] NOTE: connecting to '192.168.1.74': 192.168.1.74:24800
[Core] [2017-08-20T15:58:33] DEBUG: event queue is ready
[ UI ] [2017-08-20T15:58:48] ERROR: [2017-08-20T15:58:48] WARNING: failed to connect to server: Timed out
[Core] [2017-08-20T15:58:48] DEBUG: retry in 1 seconds
[Core] [2017-08-20T15:58:49] NOTE: connecting to '192.168.1.74': 192.168.1.74:24800

It appears to me as if the application has used the no longer existing device as the server which the two existing devices are trying to connect to indefinitely.

Link to comment
Share on other sites

SoleRunNHide

As an additional update, forcing the recently reinstalled device to a new fixed internal IP will not solve the issue.  Each of the devices will still attempt to connect to the old device (prior to reinstall) at the now vacant local IP.  Moreover, moving a device to the vacant IP which the devices are trying to connect results in connection refused status.

The logged errors after switching reinstalled device to a new fixed local IP is a connectivity error.  Firewalls are disabled for this troubleshooting as well:

[ UI ] [2017-08-20T16:24:44] DEBUG: retry in 3 seconds
[ UI ] [2017-08-20T16:24:47] DEBUG: can not find any successful connectivity result for the server screen: 3068
[ UI ] [2017-08-20T16:24:47] DEBUG: retry in 3 seconds
[ UI ] [2017-08-20T16:24:50] DEBUG: can not find any successful connectivity result for the server screen: 3068
[ UI ] [2017-08-20T16:24:50] DEBUG: retry in 3 seconds
[ UI ] [2017-08-20T16:24:53] DEBUG: can not find any successful connectivity result for the server screen: 3068
[ UI ] [2017-08-20T16:24:53] DEBUG: retry in 3 seconds
[ UI ] [2017-08-20T16:24:56] DEBUG: can not find any successful connectivity result for the server screen: 3068

 

Link to comment
Share on other sites

SoleRunNHide

Thanks for the update Nick and sounds like a plan.  Just wanted to make sure I reported the bug in case it was something other than the auto switching on the server, as I did not see it reported elsewhere. 

Thanks for the great work you guys are doing.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...