lilHermit Posted September 23, 2017 Share Posted September 23, 2017 I'm running Ubuntu 17.4 with Gnome desktop (non wayland) and the service start fails and running synergyd show incorrect commands. Firstly service (I've done the changes to ExecStart) scott@nero:~$ sudo systemctl daemon-reload scott@nero:~$ sudo systemctl start synergy scott@nero:~$ sudo systemctl enable synergy scott@nero:~$ sudo systemctl status synergy ● synergy.service - Synergy Service Loaded: loaded (/lib/systemd/system/synergy.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Sat 2017-09-23 14:18:47 BST; 8s ago Main PID: 6288 (code=dumped, signal=ABRT) CPU: 3ms Sep 23 14:18:47 nero systemd[1]: synergy.service: Failed with result 'core-dump'. Sep 23 14:18:47 nero systemd[1]: synergy.service: Service has no hold-off time, scheduling restart. Sep 23 14:18:47 nero systemd[1]: Stopped Synergy Service. Sep 23 14:18:47 nero systemd[1]: synergy.service: Start request repeated too quickly. Sep 23 14:18:47 nero systemd[1]: Failed to start Synergy Service. Sep 23 14:18:47 nero systemd[1]: synergy.service: Unit entered failed state. Sep 23 14:18:47 nero systemd[1]: synergy.service: Failed with result 'core-dump'. on launching synergyd directly I notice the synergys command is invalid [2017-09-23T14:21:05] debug: service log path: /var/log/synergy-service.log [2017-09-23T14:21:05] info: starting service... [2017-09-23T14:21:05] debug: connecting websocket [2017-09-23T14:21:05] debug: connectivity test server started [rawsocket_server_impl.cpp:94][start] starting rawsocket server RawSocket handshake reply received connect successful: valid handshake RX preparing to receive message .. TX message (126 octets) ... TX message: hello ["default", {"authid":"", "authmethods":[], "roles":{"subscriber":{}, "callee":{"features":{"call_timeout":true}}, "publisher":{}, "caller":{"features":{"call_timeout":true}}}}] [wamp_message_processor.cpp:47][process_message] processing message: hello [wamp_router_impl.cpp:108][attach_session] attaching session: session [7090515283965860,default,none] [wamp_dealer.cpp:65][attach_session] attach session: session [7090515283965860,default,none] [wamp_broker.cpp:51][attach_session] attach session: session [7090515283965860,default,none] [wamp_router_impl.cpp:164][process_hello_message] session [7090515283965860,default,none], hello [default, {"authid":"", "authmethods":[], "roles":{"subscriber":{}, "callee":{"features":{"call_timeout":true}}, "publisher":{}, "caller":{"features":{"call_timeout":true}}}}] [wamp_router_impl.cpp:192][process_hello_message] session [7090515283965860,default,open], welcome [7090515283965860, {"roles":{"dealer":{"features":{"call_timeout":true, "progressive_call_results":true}}, "broker":{}}}] [rawsocket_transport.cpp:39][send_message] sending message: welcome RX message (85 octets) ... RX message received. RX message: welcome [7090515283965860, {"roles":{"dealer":{"features":{"call_timeout":true, "progressive_call_results":true}}, "broker":{}}}] [2017-09-23T14:21:05] debug: creating rpc endpoints [2017-09-23T14:21:05] debug: rpc endpoints created [2017-09-23T14:21:05] info: service started successfully RX preparing to receive message .. TX message (79 octets) ... TX message: publish [1, {}, "synergy.service.log", ["[2017-09-23T14:21:05] debug: creating rpc endpoints\n"]] TX message (23 octets) ... TX message: register [2, {}, "synergy.core.start"] TX message (28 octets) ... TX message: register [3, {}, "synergy.profile.request"] TX message (24 octets) ... TX message: register [4, {}, "synergy.auth.update"] TX message (78 octets) ... TX message: publish [5, {}, "synergy.service.log", ["[2017-09-23T14:21:05] debug: rpc endpoints created\n"]] TX message (84 octets) ... TX message: publish [6, {}, "synergy.service.log", ["[2017-09-23T14:21:05] info: service started successfully\n"]] [wamp_message_processor.cpp:47][process_message] processing message: publish [wamp_broker.cpp:111][process_publish_message] session [7090515283965860,default,open], publish [1, {}, synergy.service.log, ["[2017-09-23T14:21:05] debug: creating rpc endpoints\n"], null] [wamp_message_processor.cpp:47][process_message] processing message: register [wamp_dealer.cpp:304][process_register_message] session [7090515283965860,default,open], register [2, {}, synergy.core.start] [wamp_dealer.cpp:345][process_register_message] session [7090515283965860,default,open], registered [2, 1] [rawsocket_transport.cpp:39][send_message] sending message: registered RX message (4 octets) ... [wamp_message_processor.cpp:47][process_message] processing message: register [wamp_dealer.cpp:304][process_register_message] session [7090515283965860,default,open], register [3, {}, synergy.profile.request] [wamp_dealer.cpp:345][process_register_message] session [7090515283965860,default,open], registered [3, 2] [rawsocket_transport.cpp:39][send_message] sending message: registered RX message received. RX message: registered [2, 1] RX preparing to receive message .. RX message (4 octets) ... [wamp_message_processor.cpp:47][process_message] processing message: register [wamp_dealer.cpp:304][process_register_message] session [7090515283965860,default,open], register [4, {}, synergy.auth.update] [wamp_dealer.cpp:345][process_register_message] session [7090515283965860,default,open], registered [4, 3] [rawsocket_transport.cpp:39][send_message] sending message: registered RX message received. RX message: registered [3, 2] RX preparing to receive message .. RX message (4 octets) ... [wamp_message_processor.cpp:47][process_message] processing message: publish [wamp_broker.cpp:111][process_publish_message] session [7090515283965860,default,open], publish [5, {}, synergy.service.log, ["[2017-09-23T14:21:05] debug: rpc endpoints created\n"], null] RX message received. RX message: registered [4, 3] RX preparing to receive message .. [wamp_message_processor.cpp:47][process_message] processing message: publish [wamp_broker.cpp:111][process_publish_message] session [7090515283965860,default,open], publish [6, {}, synergy.service.log, ["[2017-09-23T14:21:05] info: service started successfully\n"], null] [2017-09-23T14:21:06] debug: websocket connected TX message (76 octets) ... TX message: publish [7, {}, "synergy.service.log", ["[2017-09-23T14:21:06] debug: websocket connected\n"]] [2017-09-23T14:21:06] debug: comparing profiles, id=-1 this=v-1 other=v9 [2017-09-23T14:21:06] debug: profile id changed, -1->1793 [2017-09-23T14:21:06] debug: profile name changed, ->default [2017-09-23T14:21:06] debug: profile server changed, -1->3613 [2017-09-23T14:21:06] debug: profile screen set changed, added=2 removed=0 [2017-09-23T14:21:06] debug: new screens detected (2), preparing connectivity test [2017-09-23T14:21:06] debug: profile changed, storing local copy TX message (100 octets) ... TX message: publish [8, {}, "synergy.service.log", ["[2017-09-23T14:21:06] debug: comparing profiles, id=-1 this=v-1 other=v9\n"]] TX message (85 octets) ... TX message: publish [9, {}, "synergy.service.log", ["[2017-09-23T14:21:06] debug: profile id changed, -1->1793\n"]] TX message (88 octets) ... TX message: publish [10, {}, "synergy.service.log", ["[2017-09-23T14:21:06] debug: profile name changed, ->default\n"]] TX message (89 octets) ... TX message: publish [11, {}, "synergy.service.log", ["[2017-09-23T14:21:06] debug: profile server changed, -1->3613\n"]] [2017-09-23T14:21:06] debug: handling local profile server changed, mode=unknown thisId=3613 serverId=3613 lastServerId=-1 [2017-09-23T14:21:06] debug: starting core server process [2017-09-23T14:21:06] debug: starting core process with command: /home/scott/synergys -f --no-tray --debug DEBUG --name nero --enable-drag-drop --profile-dir /home/scott/.config/synergy --log synergy.log -c /home/scott/.config/synergy/synergy.conf --address :24800 [2017-09-23T14:21:06] error: failed to start server core process: execve failed: No such file or directory TX message (102 octets) ... TX message: publish [12, {}, "synergy.service.log", ["[2017-09-23T14:21:06] debug: profile screen set changed, added=2 removed=0\n"]] TX message (110 octets) ... TX message: publish [13, {}, "synergy.service.log", ["[2017-09-23T14:21:06] debug: new screens detected (2), preparing connectivity test\n"]] [2017-09-23T14:21:06] debug: handling local profile screen set changed, mode=server [2017-09-23T14:21:06] debug: starting core server process [2017-09-23T14:21:06] debug: process already running, attempting to stop [2017-09-23T14:21:06] debug: stopping core process Notice "/home/scott/synergys" starting core process with command: /home/scott/synergys -f --no-tray --debug DEBUG --name nero --enable-drag-drop --profile-dir /home/scott/.config/synergy --log synergy.log -c /home/scott/.config/synergy/synergy.conf --address :24800 This is all on the "server" I haven't got as far getting the client to connect however I did notice the client was try the docker IP. Is there any config directive on the client where I can set the IP or atleast the interface to connect via? Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted September 23, 2017 Synergy Team Share Posted September 23, 2017 These issues will be fixed in beta5, which is due in about 4-5 weeks. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.