[Linux] Unable to connect to the core client

Message boards : Questions and problems : [Linux] Unable to connect to the core client
Message board moderation

To post messages, you must log in.

AuthorMessage
Sandro kensan

Send message
Joined: 28 Apr 16
Posts: 4
Italy
Message 69239 - Posted: 28 Apr 2016, 14:36:09 UTC
Last modified: 28 Apr 2016, 14:43:58 UTC

Hi,
I have Installed Boinc via standard Mageia Repository and then I have start Boinc Manager via Start menu.
Manager shows:
Retrieving current status
and then:
Unable to connect to the core client

I have reboot and the error don't change. I have read a problem about firewall and I have put in my firewall the port:
31416/tcp

The command:
# lsof -i :31416
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
boinc_cli 1690 boinc 4u IPv4 19123 0t0 TCP localhost:31416 (LISTEN)
boincmgr 8781 sandro 6u IPv4 544741 0t0 TCP localhost:53830->localhost:31416 (CLOSE_WAIT)

$ ps aux|grep boinc
boinc 1683 0.0 0.0 12576 2528 ? SNs 15:47 0:00 /bin/bash /usr/bin/boinc --dir /var/lib/boinc
boinc 1690 0.0 0.2 90060 8760 ? SNl 15:47 0:01 /usr/bin/boinc_client --allow_multiple_clients --dir /var/lib/boinc
sandro 8781 0.1 1.0 450216 38276 ? Sl 16:25 0:00 /usr/bin/boincmgr -n localhost -d /var/lib/boinc
sandro 9246 0.0 0.0 12268 2092 pts/0 S+ 16:30 0:00 grep --color boinc

$ top|grep boinc
1690 boinc 30 10 90060 8760 7308 S 0,3 0,2 0:01.16 boinc_client
8781 sandro 20 0 450216 38424 32296 S 0,3 1,0 0:00.71 boincmgr
8781 sandro 20 0 450216 38424 32296 S 0,3 1,0 0:00.72 boincmgr
8781 sandro 20 0 450216 38424 32296 S 0,3 1,0 0:00.73 boincmgr
1690 boinc 30 10 90060 8760 7308 S 0,3 0,2 0:01.17 boinc_client
8781 sandro 20 0 450216 38424 32296 S 0,7 1,0 0:00.75 boincmgr
1690 boinc 30 10 90060 8760 7308 S 0,3 0,2 0:01.18 boinc_client
8781 sandro 20 0 450216 38424 32296 S 0,3 1,0 0:00.76 boincmgr

My Internet connection is NATed

Any solution?

Linux Mageia 5 updated, it is the last version stable. 64 bit version.
Boinc manager 7.2.42 (x64)
ID: 69239 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 69240 - Posted: 28 Apr 2016, 14:45:39 UTC - in response to Message 69239.  

Did you start the BOINC client before you started BOINC Manager? Unlike with Windows and Mac OS X, starting BOINC Manager under Linux does not start the client. It has to be started separately.
ID: 69240 · Report as offensive
Sandro kensan

Send message
Joined: 28 Apr 16
Posts: 4
Italy
Message 69245 - Posted: 28 Apr 2016, 18:21:38 UTC - in response to Message 69240.  
Last modified: 28 Apr 2016, 18:25:45 UTC

Did you start the BOINC client before you started BOINC Manager? Unlike with Windows and Mac OS X, starting BOINC Manager under Linux does not start the client. It has to be started separately.


Tanx a lot for the reply. I have noted that my service wizard shows a new service (I have sistemd) named boinc-client that is running and is started on boot. (But I have changed the default.) So boinc-client is start automatically after the boot. I have never started the client but it is running:

boinc 1709 0.0 0.0 12576 2604 ? SNs 20:09 0:00 /bin/bash /usr/bin/boinc --dir /var/lib/boinc
boinc 1715 0.3 0.2 90060 8600 ? SNl 20:09 0:01 /usr/bin/boinc_client --allow_multiple_clients --dir /var/lib/boinc
ID: 69245 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 69250 - Posted: 28 Apr 2016, 19:18:49 UTC - in response to Message 69245.  

All right, with that out of the way, try to set a password in the gui_rpc_auth.cfg file in the BOINC (data) directory. By default it's got a random 32 character hexadecimal password in it, but that may not work well.

When you do set your own password, remove the 32 char word and in its place put your password. Don't add an enter at the end though.

You can also try to start the client with boinc --gui_rpc_port 31416 to specifically tell BOINC to use that port and then start BOINC Manager with the same attribute, boincmgr --gui_rpc_port 31416

You do need to run these commands from the directory the client and manager are in. I am not sure if the name of BOINC Manager's binary is boinmgr.
And of course, if you suspect it's something about the port number, you can try to give them a different number, e.g. boinc --gui_rpc_port 62555 and boincmgr --gui_rpc_port 62555
ID: 69250 · Report as offensive
Sandro kensan

Send message
Joined: 28 Apr 16
Posts: 4
Italy
Message 69253 - Posted: 28 Apr 2016, 19:49:10 UTC - in response to Message 69250.  

All right, with that out of the way, try to set a password in the gui_rpc_auth.cfg file in the BOINC (data) directory. By default it's got a random 32 character hexadecimal password in it, but that may not work well.


In the log file(/var/log/boinc.log):

28-Apr-2016 20:09:46 [---] Data directory: /var/lib/boinc

In /var/lib/boinc there is the file gui_rpc_auth.cfg
I have inserted a random password like casetta.

When you do set your own password, remove the 32 char word and in its place put your password. Don't add an enter at the end though.

You can also try to start the client with boinc --gui_rpc_port 31416 to specifically tell BOINC to use that port and then start BOINC Manager with the same attribute, boincmgr --gui_rpc_port 31416

You do need to run these commands from the directory the client and manager are in. I am not sure if the name of BOINC Manager's binary is boinmgr.
And of course, if you suspect it's something about the port number, you can try to give them a different number, e.g. boinc --gui_rpc_port 62555 and boincmgr --gui_rpc_port 62555
ID: 69253 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 69256 - Posted: 28 Apr 2016, 20:26:23 UTC - in response to Message 69253.  

And after you done so, you have restarted the client?
ID: 69256 · Report as offensive
Sandro kensan

Send message
Joined: 28 Apr 16
Posts: 4
Italy
Message 69265 - Posted: 28 Apr 2016, 23:00:45 UTC - in response to Message 69256.  

In my opinion the problem is not the 32 hex char, I have changed the permission of the gui_rpc_auth.cfg file in the BOINC (data) directory (chmod)

-rw-r--r-- 1 boinc boinc 33 apr 28 22:37 gui_rpc_auth.cfg

and log file:

-rw-r--r-- 1 boinc boinc 0 apr 29 00:04 boincerr.log
-rw-r--r-- 1 boinc boinc 86517 apr 29 00:30 boinc.log

And now it works. But I have made a lot of change that I have reversed to the original. I'm not sure why it works now.
ID: 69265 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 69279 - Posted: 29 Apr 2016, 9:36:11 UTC - in response to Message 69265.  

LOL, the intricacies of computers. No one knows why it works when it does. But I'm glad it did. :-)
ID: 69279 · Report as offensive
Kenny

Send message
Joined: 4 May 16
Posts: 2
United States
Message 69440 - Posted: 4 May 2016, 16:46:20 UTC

I am on Windows 10 and have the same problem.
ID: 69440 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 69443 - Posted: 4 May 2016, 17:10:13 UTC - in response to Message 69440.  
Last modified: 4 May 2016, 17:13:35 UTC

Problems with not connecting to localhost are normally attributed to BOINC not being able to communicate among its parts. the client (boinc.exe) and manager/GUI (boincmgr.exe) need access through the firewall on the localhost, if specified on TCP port 31416.

When just using the Windows firewall, do know that it has to have entries for a 64bit BOINC separate from a 32bit BOINC. Again due to the path that the executables are in. C:\program files\BOINC\boinc.exe differs in path from C:\program files (x86)\BOINC\boinc.exe

So if an earlier installation only allowed C:\program files (x86)\BOINC\boinc.exe and C:\program files (x86)\BOINC\boincmgr.exe through the firewall under the names boinc.exe and boincmgr.exe, a next start of C:\program files\boinc.exe and C:\program files\boincmgr.exe will result in neither being able to communicate with each other, because these aren't allowed through the Windows firewall.

Windows firewall does not check if the paths are still correct, as far as I know. It only checks if programs of a certain name are allowed to pass.

So if an earlier installation only allowed C:\program files (x86)\BOINC\boinc.exe and C:\program files (x86)\BOINC\boincmgr.exe through the firewall under the names boinc.exe and boincmgr.exe, a next start of C:\program files\boinc.exe and C:\program files\boincmgr.exe will result in neither being able to communicate with each other, because these aren't allowed through the Windows firewall.

Manually adding a new BOINC and BOINCMGR with the correct paths is necessary here.

Start->type Windows firewall in Search, hit Enter.
Click Inbound Rules.
Click New Rule.
Program->Next.
This program path->path to correct 32bit or 64bit boinc.exe->Next.
Allow the connection->Next.
Check Public and Private->Next.
Name: what you want, e.g. BOINC.exe
Finish.

Do the same for boincmgr.exe, but here check the Private rule only. BOINC Manager only needs access to the localhost, private network. It does not need an internet connection.

When done, no need to reboot, you should be able to start BOINC Manager now and have it connect to the client. If you use a different firewall package, you'll have to add these through there.

If you can set ports, boinc.exe needs an internet connection on TCP ports 80 and 443.
boinc.exe and boincmgr.exe need a connection on localhost on TCP port 31416.

If that still doesn't work, exit BOINC completely, navigate to its data directory (default a hidden directory at C:\Programdata\BOINC\, when you fill in the path in Windows Explorer and hit Enter you'll get there) and delete the gui_rpc_auth.cfg file.
Then restart BOINC Manager and try again.
ID: 69443 · Report as offensive
Kenny

Send message
Joined: 4 May 16
Posts: 2
United States
Message 69483 - Posted: 6 May 2016, 1:45:13 UTC - in response to Message 69443.  

I have tried everything you suggested. I cannot find the gui_rpc_auth.cfg file. No matter what I do, it still doesn't connect.
ID: 69483 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 69489 - Posted: 6 May 2016, 13:46:13 UTC - in response to Message 69483.  

Well, let's start with some basic information then, as asked here:
- BOINC version?
- Installed as a service or as a user?
- 32bit, 64bit?
- Windows 10, 32bit or 64bit?
- When checking in Windows Task Manager, is the BOINC client (boinc.exe) running when or after you started BOINC Manager?
- Which firewall do you use? (you never answered)
- What have you tried to do to get it to connect?
- Did you install BOINC and the data directory in the default directories?
- Did you update BOINC from a previous version?
- Was that previous version the same kind (32bit/64bit) as the new one is?
- What kind of anti virus do you have?
- Have you added the BOINC program directory and the data directory as exceptions in this program?
- Have you had a GPU of some brand in that computer, but have you since removed it or changed it for another GPU? In that case, you may need to remove the previous drivers. Use a program such as Display Driver Uninstaller if unsure.
- It's possible that another program is taking up the default port (TCP 31416) that BOINC uses to communicate between its parts. You can check what ports are in use by:
* Click Start->Search, type cmd.exe and wait for it to show in the column, then right-click it and choose "Run as administrator". If need be, acknowledge.
* In the black window that opens type netstat -b -n >> C:\tmp\stats.txt (with spaces) and hit Enter, then wait for the blinking cursor to be visiable again. (Leave the window open)
* Open Windows Explorer and navigate to C:\tmp\, then open stats.txt with Notepad.
* Copy its contents and paste those here for all to see.
* Next go back to the command line window, then type netstat -a -n >> C:\tmp\stats2.txt (including the spaces) and hit Enter.
* Wait for the blinking cursor to be visiable again. (Leave the window open)
* Open Windows Explorer and navigate to C:\tmp\, then open stats2.txt with Notepad.
* Copy its contents and paste those here for all to see.
You can close the command line window now, and close/delete the files.
ID: 69489 · Report as offensive

Message boards : Questions and problems : [Linux] Unable to connect to the core client

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.