Jan 17 19:20:46 linux systemd: **rvice: Failed with result 'exit-code'.**Īs I said, I updated all boinc unconditionally via yast. Jan 17 19:20:46 linux systemd: **rvice: Main process exited, code=exited, status=108/n/a** Jan 17 19:20:46 linux boinc: 1 19:20:46 Another instance of BOINC is running. Jan 17 19:20:36 linux boinc: 1 19:20:36 -] cc_config.xml not found - using defaults Jan 17 19:20:34 linux systemd: Started Berkeley Open Infrastructure Network Computing Client. Loaded: loaded (/usr/lib/systemd/system/rvice enabled vendor preset: disabled)Īctive: **failed** (Result: exit-code) since Fri 19:20:46 EST 17h ago rvice - Berkeley Open Infrastructure Network Computing Client I did not try to zypper in boinc but I did run the other command. I’m running Tumbleweed and my reference was to the failure to get the boinc gui to run after the last zypper dup, earlier this week. I+ | boinc-manager | package | 7.8.3-lp151.2.7 | x86_64 | Main RepositoryĪll works fine here running as my user qemu machine, GNOME DE… S | Name | Type | Version | Arch | Repository Alternatively instead of localhost2, use the actual IP (same as Windows). This is Leap 15.1, zypper dup? Or did you mean zypper up… Add a computer with IP localhost2 and port 31414 with a blank password. UDP port 1043 would not have guaranteed communication as TCP. Guaranteed communication over TCP port 1043 is the main difference between TCP and UDP. I updated boinc unconditionally through yast but that did nothing. TCP guarantees delivery of data packets on port 1043 in the same order in which they were sent. Today’s zypper dup apparently has caused the problem. I can launch the gui from the menu but cannot launch it from the root command line which has always been the only way I could connect to localhost previous to today. I ran the command and the boinc manager launches but fails to connect to localhost. └─6193 /usr/bin/boinc -dir /var/lib/boinc Process: 6184 ExecStopPost=/bin/rm -f $BOINC_BOINC_DIR/lockfile (code=exited, status=0/SUCCESS) I normally just run the boinc-gui command…Īctive: active (running) since Mon 19:43:19 CST 1s ago How can I solve this issue? Any one has any ideas what to do next?Īll working fine here in a KVM machine with Nvidia GPU… Nc: connect to localhost port 31416 (tcp) failed: Connection refused I tried also the command line and received the following: └─20914 /bin/sh /usr/bin/VBoxManage -version Process: 20698 ExecStop=/usr/bin/boinccmd -quit (code=exited, status=1/FAILURE)ĬGroup: /background.slice/rvice Process: 20713 ExecStopPost=/bin/rm -f $BOINC_BOINC_DIR/lockfile (code=exited, status=0/SUCCESS) Loaded: loaded (/usr/lib/systemd/system/rvice disabled vendor preset: disabled)Īctive: active (running) since Mon 08:33:55 MST 34min ago
rvice - Berkeley Open Infrastructure Network Computing Client.I installed boinc-client and boing manager and the manager is not connection to boinc.
0 kommentar(er)
