Sartorum Posted July 26, 2017 Share Posted July 26, 2017 [Core] [2017-07-26T10:47:59] DEBUG: event queue is ready [Core] [2017-07-26T10:47:59] DEBUG: signalling carbon loop ready [Core] [2017-07-26T10:47:59] DEBUG: add pending events to buffer [Core] [2017-07-26T10:47:59] DEBUG: starting carbon loop [Core] [2017-07-26T10:47:59] DEBUG: carbon loop ready [Core] [2017-07-26T10:47:59] DEBUG: add pending events to buffer [Core] [2017-07-26T10:47:59] DEBUG: screen "Fabios-iMac.local" shape changed [Core] [2017-07-26T10:47:59] DEBUG: screen "Fabios-iMac.local" shape changed [ UI ] [2017-07-26T10:47:59] ERROR: 2017-07-26 10:47:59.495 synergys[7686:4525306] starting cocoa loop [Core] [2017-07-26T10:47:59] NOTE: accepted client connection [Core] [2017-07-26T10:47:59] DEBUG: received client "odin" info shape=0,0 1920x1080 at 960,540 [Core] [2017-07-26T10:47:59] NOTE: client "odin" has connected [ UI ] [2017-07-26T10:47:59] DEBUG: claim to be server [Core] [2017-07-26T10:48:00] NOTE: accepted client connection [Core] [2017-07-26T10:48:00] DEBUG: received client "fsartorato-nb" info shape=0,0 1366x768 at 16795,32762 [Core] [2017-07-26T10:48:00] NOTE: client "fsartorato-nb" has connected [Core] [2017-07-26T10:48:48] INFO: switch from "Fabios-iMac.local" to "odin" at 1919,36 [Core] [2017-07-26T10:48:48] INFO: leaving screen [Core] [2017-07-26T10:48:48] DEBUG: hiding cursor [ UI ] [2017-07-26T10:48:48] ERROR: [2017-07-26T10:48:48] WARNING: cursor may not be visible [Core] [2017-07-26T10:48:48] DEBUG: opening clipboard [Core] [2017-07-26T10:48:48] DEBUG: closing clipboard [Core] [2017-07-26T10:48:48] INFO: screen "Fabios-iMac.local" updated clipboard 0 [Core] [2017-07-26T10:48:48] DEBUG: opening clipboard [Core] [2017-07-26T10:48:48] DEBUG: closing clipboard [Core] [2017-07-26T10:48:48] INFO: screen "Fabios-iMac.local" updated clipboard 1 [Core] [2017-07-26T10:48:48] DEBUG: sending clipboard 0 to "odin" [Core] [2017-07-26T10:48:48] DEBUG: sent clipboard size=23 [Core] [2017-07-26T10:48:48] DEBUG: sending clipboard 1 to "odin" [Core] [2017-07-26T10:48:48] DEBUG: sent clipboard size=23 [Core] [2017-07-26T10:48:48] DEBUG: dropped bogus motion -1280,-669 [Core] [2017-07-26T10:48:48] INFO: switch from "odin" to "fsartorato-nb" at 20,29 [Core] [2017-07-26T10:48:48] DEBUG: sending clipboard 0 to "fsartorato-nb" [Core] [2017-07-26T10:48:48] DEBUG: sent clipboard size=23 [Core] [2017-07-26T10:48:48] DEBUG: sending clipboard 1 to "fsartorato-nb" [Core] [2017-07-26T10:48:48] DEBUG: sent clipboard size=23 [Core] [2017-07-26T10:48:51] INFO: switch from "fsartorato-nb" to "odin" at 1887,637 [Core] [2017-07-26T10:48:52] INFO: switch from "odin" to "fsartorato-nb" at 82,455 [Core] [2017-07-26T10:48:55] NOTE: client "odin" has disconnected [ UI ] [2017-07-26T10:48:55] ERROR: [2017-07-26T10:48:55] WARNING: error writing to client "fsartorato-nb" [Core] [2017-07-26T10:48:55] INFO: jump from "fsartorato-nb" to "Fabios-iMac.local" at 1280,720 [Core] [2017-07-26T10:48:55] INFO: entering screen [Core] [2017-07-26T10:48:55] DEBUG: showing cursor [ UI ] [2017-07-26T10:48:56] INFO: write configuration file complete [ UI ] [2017-07-26T10:48:56] DEBUG: connecting to server: 105.103.135.226 [ UI ] [2017-07-26T10:48:56] ERROR: process exited with error code: 9 [Core] [2017-07-26T10:48:56] DEBUG: screen shape: center=0,0 size=2560x1440 on 1 display [Core] [2017-07-26T10:48:56] DEBUG: starting watchSystemPowerThread [Core] [2017-07-26T10:48:56] DEBUG: adopting new buffer [Core] [2017-07-26T10:48:56] DEBUG: opened display [Core] [2017-07-26T10:48:56] NOTE: started client [Core] [2017-07-26T10:48:56] NOTE: connecting to '105.103.135.226': 105.103.135.226:24800 [Core] [2017-07-26T10:48:56] DEBUG: started watchSystemPowerThread [Core] [2017-07-26T10:48:56] DEBUG: waiting for event loop [Core] [2017-07-26T10:48:56] DEBUG: waiting for carbon loop [Core] [2017-07-26T10:48:56] DEBUG: event queue is ready [Core] [2017-07-26T10:48:56] DEBUG: signalling carbon loop ready [Core] [2017-07-26T10:48:56] DEBUG: add pending events to buffer [Core] [2017-07-26T10:48:56] DEBUG: starting carbon loop [Core] [2017-07-26T10:48:56] DEBUG: carbon loop ready [ UI ] [2017-07-26T10:48:56] ERROR: [2017-07-26T10:48:56] WARNING: failed to connect to server: Connection refused 2017-07-26 10:48:56.229 synergyc[7689:4526112] starting cocoa loop [Core] [2017-07-26T10:48:56] DEBUG: retry in 1 seconds [Core] [2017-07-26T10:48:57] NOTE: connecting to '105.103.135.226': 105.103.135.226:24800 [Core] [2017-07-26T10:48:57] DEBUG: hiding cursor [ UI ] [2017-07-26T10:48:57] ERROR: [2017-07-26T10:48:57] WARNING: cursor may not be visible [Core] [2017-07-26T10:48:57] NOTE: connected to server [Core] [2017-07-26T10:48:57] INFO: local input detected [Core] [2017-07-26T10:48:57] INFO: local input detected [Core] [2017-07-26T10:48:57] INFO: local input detected [ UI ] [2017-07-26T10:48:58] INFO: write configuration file complete [ UI ] [2017-07-26T10:48:58] ERROR: process exited with error code: 9 [Core] [2017-07-26T10:48:58] DEBUG: opening configuration "/Users/f.sartorato/Library/Preferences/Symless/Synergy/synergy.conf" [Core] [2017-07-26T10:48:58] DEBUG: configuration read successfully [Core] [2017-07-26T10:48:58] DEBUG: screen shape: center=0,0 size=2560x1440 on 1 display [Core] [2017-07-26T10:48:58] DEBUG: starting watchSystemPowerThread [Core] [2017-07-26T10:48:58] DEBUG: adopting new buffer [Core] [2017-07-26T10:48:58] DEBUG: opened display [Core] [2017-07-26T10:48:58] DEBUG: started watchSystemPowerThread [Core] [2017-07-26T10:48:58] DEBUG: waiting for event loop [Core] [2017-07-26T10:48:58] DEBUG: could not map hotkey id=ef14 mask=0000 [Core] [2017-07-26T10:48:58] NOTE: started server, waiting for clients [ UI ] [2017-07-26T10:48:58] ERROR: 2017-07-26 10:48:58.253 synergys[7690:4526189] starting cocoa loop [Core] [2017-07-26T10:48:58] DEBUG: waiting for carbon loop [Core] [2017-07-26T10:48:58] DEBUG: event queue is ready [Core] [2017-07-26T10:48:58] DEBUG: add pending events to buffer [Core] [2017-07-26T10:48:58] DEBUG: add pending events to buffer [Core] [2017-07-26T10:48:58] DEBUG: signalling carbon loop ready [Core] [2017-07-26T10:48:58] DEBUG: starting carbon loop [Core] [2017-07-26T10:48:58] DEBUG: carbon loop ready [Core] [2017-07-26T10:48:58] DEBUG: screen "Fabios-iMac.local" shape changed [Core] [2017-07-26T10:48:58] DEBUG: screen "Fabios-iMac.local" shape changed [Core] [2017-07-26T10:48:58] NOTE: accepted client connection [Core] [2017-07-26T10:48:58] DEBUG: received client "odin" info shape=0,0 1920x1080 at 960,540 [Core] [2017-07-26T10:48:58] NOTE: client "odin" has connected [ UI ] [2017-07-26T10:48:58] DEBUG: claim to be server [Core] [2017-07-26T10:48:59] NOTE: accepted client connection [Core] [2017-07-26T10:48:59] DEBUG: received client "fsartorato-nb" info shape=0,0 1366x768 at 16795,32762 [Core] [2017-07-26T10:48:59] NOTE: client "fsartorato-nb" has connected [ UI ] [2017-07-26T10:49:56] INFO: Sending log file... [ UI ] [2017-07-26T10:49:59] INFO: Upload path: https://synergy-logs.symless.com/2017-07-26/593-2017-07-26T10-49-57.log So, in my current configuration I have 3 different screens, one Ubuntu (odin) one MacOS (Fabios-iMac.local) and one windows (fsartorato-nb). My macos is my main. If I use then in pairs I have no connections problems, but when turning on the 3 (ubuntu on left, macos on center and windows on right) the cursor is initially on macos, if I switch to any of the other two, then I can't get back to macos and they only switch between each other. Thanks o/ Link to comment Share on other sites More sharing options...
Paul Suarez Posted July 26, 2017 Share Posted July 26, 2017 Hi @Sartorum! Please try omitting ".local" from your Mac's screen name then try connecting them again. Link to comment Share on other sites More sharing options...
Sartorum Posted July 28, 2017 Author Share Posted July 28, 2017 @Paul Suarez, Hi! It kind of worked. Now, I have some connections issues. Thanks for the reply o/ Link to comment Share on other sites More sharing options...
Paul Suarez Posted July 28, 2017 Share Posted July 28, 2017 Connection issues with what and why @Sartorum? Link to comment Share on other sites More sharing options...
Sartorum Posted August 2, 2017 Author Share Posted August 2, 2017 @Paul Suarez, Hello, Sorry for the late response, I was away in this time. The issue disappeared when I downloaded the new release, but now the first problem returned. the ".local" of my mac is already omitted. Link to comment Share on other sites More sharing options...
Paul Suarez Posted August 2, 2017 Share Posted August 2, 2017 Do you mean you can't connect both machines? If so, please post a screenshot of both machine's Synergy interface and the Server Configuration interface on your server machine. Link to comment Share on other sites More sharing options...
redlotusaustin Posted August 2, 2017 Share Posted August 2, 2017 @Paul Suarez, I think I'm having the same problem as @Sartorum: the Synergy server is in the middle with a client on either side but, after everything is connected, if I move the mouse to either client, when I try to move it back to the center, it skips that screen entirely and moves to the opposite client. In other words, instead of being able to go 2,1,2,3,2,1,2,3, etc., all I can do is: 2,1,3,1,3,1,3, etc. My log is here https://synergy-logs.symless.com/2017-08-02/999-2017-08-02T10-50-26.log You can see the switch from the server to a client on line 48, then on lines 61-70 it goes from client to client, skipping the server "ender". The server and one client are Windows 10 Pro 64 bit and the other client is Ubuntu 17.04 64 bit. Link to comment Share on other sites More sharing options...
Sartorum Posted August 2, 2017 Author Share Posted August 2, 2017 1 hour ago, redlotusaustin said: @Paul Suarez, I think I'm having the same problem as @Sartorum: the Synergy server is in the middle with a client on either side but, after everything is connected, if I move the mouse to either client, when I try to move it back to the center, it skips that screen entirely and moves to the opposite client. In other words, instead of being able to go 2,1,2,3,2,1,2,3, etc., all I can do is: 2,1,3,1,3,1,3, etc. My log is here https://synergy-logs.symless.com/2017-08-02/999-2017-08-02T10-50-26.log You can see the switch from the server to a client on line 48, then on lines 61-70 it goes from client to client, skipping the server "ender". The server and one client are Windows 10 Pro 64 bit and the other client is Ubuntu 17.04 64 bit. That's exactly my problem. For some hours when I omitted the ".local" from the Mac machine the error disappeared, but now it came back. Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 4, 2017 Synergy Team Share Posted August 4, 2017 Hey, sorry about that. We're having some scalability issues with our new cloud config server. We're frantically working to fix this now, so please sit tight! Link to comment Share on other sites More sharing options...
Sartorum Posted August 11, 2017 Author Share Posted August 11, 2017 Hey @Nick Bolton. Any updates on this issue? Thanks Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 12, 2017 Synergy Team Share Posted August 12, 2017 15 hours ago, Sartorum said: Hey @Nick Bolton. Any updates on this issue? Thanks Could you try now? The cloud server is back online. Link to comment Share on other sites More sharing options...
Sartorum Posted August 15, 2017 Author Share Posted August 15, 2017 On 8/12/2017 at 4:36 AM, Nick Bolton said: Could you try now? The cloud server is back online. Nope. Still the same problem =[ Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 16, 2017 Synergy Team Share Posted August 16, 2017 Could you send me the link to your latest logs for both computers? Link to comment Share on other sites More sharing options...
Sartorum Posted August 16, 2017 Author Share Posted August 16, 2017 3 hours ago, Nick Bolton said: Could you send me the link to your latest logs for both computers? Sure thing: Linux:https://synergy-logs.symless.com/2017-08-16/593-2017-08-16T07-54-32.log Windows:https://synergy-logs.symless.com/2017-08-16/593-2017-08-16T07-56-21.log Mac: https://synergy-logs.symless.com/2017-08-16/593-2017-08-16T07-52-19.log Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 17, 2017 Synergy Team Share Posted August 17, 2017 Ah, that's annoying. Yeah, I'm still seeing 502 codes. [ UI ] [2017-08-16T07:52:14] ERROR: Reply status code: 502 [ UI ] [2017-08-16T07:52:15] ERROR: Reply status code: 502 We're working on a major fix for this in beta4, which will be ready in 2 weeks. Can you hang on until then? Meanwhile you could downgrade back to Synergy 1. Link to comment Share on other sites More sharing options...
redlotusaustin Posted August 17, 2017 Share Posted August 17, 2017 @Nick Bolton: Does this mean that the new version of Synergy is going to require an internet connection for more than just activation? Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 17, 2017 Synergy Team Share Posted August 17, 2017 2 hours ago, redlotusaustin said: @Nick Bolton: Does this mean that the new version of Synergy is going to require an internet connection for more than just activation? Yes, absolutely! But don't worry, we're currently making it more scalable and stable. The code you're using right now is purely experimental. Link to comment Share on other sites More sharing options...
redlotusaustin Posted August 17, 2017 Share Posted August 17, 2017 @Nick Bolton That actually does worry me quite a bit. What happens when your servers are DDOS'd? Or when my internet cuts out for hours at a time because they're doing construction down the road? Will Synergy simply not work? I would much rather have to manually configure the connections than have what amounts to always-on DRM. Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 17, 2017 Synergy Team Share Posted August 17, 2017 Just now, redlotusaustin said: @Nick Bolton That actually does worry me quite a bit. What happens when your servers are DDOS'd? Or when my internet cuts out for hours at a time because they're doing construction down the road? Will Synergy simply not work? I would much rather have to manually configure the connections than have what amounts to always-on DRM. Don't worry, our goal is for Synergy to still work even while offline (in terms of keyboard and mouse sharing). Right now it might not work offline since we haven't finished. The finished product will be available in November. Please let me know if you want a refund. Link to comment Share on other sites More sharing options...
redlotusaustin Posted August 17, 2017 Share Posted August 17, 2017 55 minutes ago, Nick Bolton said: Please let me know if you want a refund Now now, don't run off and cancel my account or anything... I've gotten a lot of use out of Synergy and know that the new version is still being worked on so I'm comfortable waiting and helping to find bugs, I just wanted to point out that not everyone would have a connection 100% of the time so that you could hopefully keep that in mind in the future. Thanks for coming up with something that I use probably more than any other single piece of software! Link to comment Share on other sites More sharing options...
Albert C Posted August 18, 2017 Share Posted August 18, 2017 I've just installed Synergy 2.0 beta3, and had something similar happen. I'm using (atm) two Windows 10 laptops and a Macbook. The Macbook's screen name does have .local on it. For me, all 3 devices were seen by Synergy. But if the macbook was in the middle, I couldn't reach it with the mouse and keyboard. I shifted the macbook to the left position, and it's working to move between all 3 screens as I expected I'm sharing this in case it helps narrow down what's happening. I can try to capture the appropriate logs if they'll be helpful. Thanks! Link to comment Share on other sites More sharing options...
redlotusaustin Posted September 14, 2017 Share Posted September 14, 2017 @Nick Bolton: I'm getting slightly better results with Synergy 2.0 beta4 but I'm still unable to connect the 3rd computer (Ubuntu). The log for that computer is here: https://synergy-logs.symless.com/2017-09-14/283-2017-09-14T13-02-16.log The first 2 computers seem to work ok and, after manually starting the synergyd service, I'm able to see them from the 3rd, but they never show it in their windows, even though it shows up in the log for the server: https://synergy-logs.symless.com/2017-09-14/283-2017-09-14T13-06-16.log I've completely disabled the firewall on both the server and the computer with issues (what ports are needed, so I can open them in the Linux firewall?) but I think the problem may be that the one of the computers has 2 network interfaces and only one works for this network (192.168.1.3). Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted September 15, 2017 Synergy Team Share Posted September 15, 2017 Hey, this looks to be the issue... [ Service ] [2017-09-14T12:59:46] debug: failed report: dest = 513, ips = 192.168.1.3,192.168.56.1 This is an intermittent bug that we're fixing now. The workaround is to restart the service on all of your computers. https://symless.com/synergy-2-beta4-troubleshooting Link to comment Share on other sites More sharing options...
redlotusaustin Posted October 4, 2017 Share Posted October 4, 2017 @Nick Bolton I'm still having the same issue and no amount of restarting services or even restarting all of the computers will help. Link to comment Share on other sites More sharing options...
redlotusaustin Posted October 4, 2017 Share Posted October 4, 2017 @Nick Bolton Scratch that: now the 2 windows computers (left & middle, middle is server) are working but the Linux computer is still trying to connect to the wrong network interface of one of the other machine: https://synergy-logs.symless.com/2017-10-04/283-2017-10-04T12-39-41.log Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.