New install - Unable to connect to core client

Questions and Answers : Windows : New install - Unable to connect to core client
Message board moderation

To post messages, you must log in.

1 · 2 · Next

AuthorMessage
brownec

Send message
Joined: 21 May 99
Posts: 10
Credit: 95,510,239
RAC: 72
United States
Message 2021840 - Posted: 5 Dec 2019, 18:51:43 UTC

New machine: Microsoft Surface laptop 3 with Windows 10
did a default install of Boinc and get the error message "Unable to connect to core client". Most of the menu items are greyed out. Boinc.exe is NOT running. Starting it manually doesn't help and it kills itself after a short while.

How do I get this to run as it does on my other machines?
ID: 2021840 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13159
Credit: 1,160,866,277
RAC: 1,873
United States
Message 2021855 - Posted: 5 Dec 2019, 21:18:06 UTC - in response to Message 2021840.  

New machine: Microsoft Surface laptop 3 with Windows 10
did a default install of Boinc and get the error message "Unable to connect to core client". Most of the menu items are greyed out. Boinc.exe is NOT running. Starting it manually doesn't help and it kills itself after a short while.

How do I get this to run as it does on my other machines?

Delete the gui_rpc_auth.cfg file and start BOINC again. The password in the file is incorrect or the permissions don't allow access to the file.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 2021855 · Report as offensive
brownec

Send message
Joined: 21 May 99
Posts: 10
Credit: 95,510,239
RAC: 72
United States
Message 2022173 - Posted: 7 Dec 2019, 19:47:21 UTC - in response to Message 2021855.  

tried that. still the same error. the deleted file is re-created.

Any other ideas?
ID: 2022173 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 2022179 - Posted: 7 Dec 2019, 20:05:31 UTC - in response to Message 2021840.  

Well, that everything is greyed out in BOINC Manager is due to boinc.exe not running. Without it, there's nothing to populate as BOINC Manager only shows what BOINC runs.

What kind of messages will BOINC give on its forced exit? Can you check last lines in stdoutdae.txt and in stderrdae.txt?
Or else check in Windows Event Viewer if there is a clue as to what's happening to boinc.exe?

You did allow boinc.exe and boincmgr.exe to pass through any firewall solution? These two need to be able to communicate through TCP port 31416, boinc.exe requires internet access to TCP ports 80 and 443.
ID: 2022179 · Report as offensive
brownec

Send message
Joined: 21 May 99
Posts: 10
Credit: 95,510,239
RAC: 72
United States
Message 2022202 - Posted: 7 Dec 2019, 21:10:57 UTC - in response to Message 2022179.  

stderrdae.txt is empty
the tail of stdoutdae.txt is:
07-Dec-2019 12:30:32 [---] Setting up project and slot directories
07-Dec-2019 12:30:32 [---] Checking active tasks
07-Dec-2019 12:30:32 [---] Setting up GUI RPC socket
07-Dec-2019 12:30:32 [---] Checking presence of 0 project files
07-Dec-2019 12:30:32 [---] This computer is not attached to any projects
07-Dec-2019 12:30:32 Initialization completed

Also the choose a project dialog that comes up automatically has no projects listed even though all_projects_list.xml has lots of stuff in it
ID: 2022202 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 2022272 - Posted: 8 Dec 2019, 1:06:48 UTC - in response to Message 2022202.  

The choose project wizard is part of the BOINC client (boinc.exe) and again if that's not running or dumped out, it won't show anything.
can you open BOINC Manager->View->Advanced view->Options->Other options... and check that "Run the client?" is checked? And if it isn't, check it?
Go back to just Options (exit Other options), then open the Event Log options... and check gui_rpc_debug, and benchmark_debug then save.
File->Exit

Restart BOINC Manager.
Does the client still kick out?
What does it now say for the last 20-30 lines of stdoutdae.txt?
ID: 2022272 · Report as offensive
brownec

Send message
Joined: 21 May 99
Posts: 10
Credit: 95,510,239
RAC: 72
United States
Message 2022433 - Posted: 9 Dec 2019, 1:17:51 UTC - in response to Message 2022272.  

Well, I must apologize. Things are somewhat further along now I re-installed using "run as administrator" on the installer.

Now the boinc client is running and things aren't grayed out.

When I try to select SETI@home project, I get response of "Project temporarily unavailable". Pretty sure that's not true.
I've checked my firewall rules and both Manager and client have access to all ports.

Last line of stdoutdae.txt is
Fetching configuration file from http://setiathome.berkeley.edu/get_project_config.php.

I can reach that file with my web browser...
ID: 2022433 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13159
Credit: 1,160,866,277
RAC: 1,873
United States
Message 2022441 - Posted: 9 Dec 2019, 1:51:56 UTC - in response to Message 2022433.  

Use Jord's suggestion of the Event Log flags for the gui_rpc_debug, and benchmark_debug and post the log results after trying to join the project.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 2022441 · Report as offensive
brownec

Send message
Joined: 21 May 99
Posts: 10
Credit: 95,510,239
RAC: 72
United States
Message 2022547 - Posted: 9 Dec 2019, 23:21:05 UTC - in response to Message 2022441.  

Ok, so here's the tail of stdoutdae.txt. the first line seems to be the issue

09-Dec-2019 15:18:09 [---] [gui_rpc] handler returned -102, closing socket
09-Dec-2019 15:18:09 [---] [gui_rpc] GUI RPC Command = '<boinc_gui_rpc_request>
<get_project_status/>
</boinc_gui_rpc_request>
'
09-Dec-2019 15:18:09 [---] [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply>
<projects>
</projects>
</boinc_gui_rpc_reply>
'
09-Dec-2019 15:18:09 [---] [gui_rpc] GUI RPC Command = '<boinc_gui_rpc_request>
<get_all_projects_list/>
</boinc_gui_rpc_request>
'
09-Dec-2019 15:18:09 [---] [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply>
<projects>
<project>
<name>DENIS@Home</name>
<id>4</id>
<url>http://denis.usj.'
ID: 2022547 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13159
Credit: 1,160,866,277
RAC: 1,873
United States
Message 2022595 - Posted: 10 Dec 2019, 5:32:45 UTC

You have a permissions issue. The OS does not have permission to read or write to the client directory. Your gui_rpc_auth.cfg file does not have the correct password or the user does not have permissions to access the client or the directory it resides.
https://boinc.mundayweb.com/wiki/index.php?title=Error_code_-100_to_-110_explained
https://boinc.mundayweb.com/wiki/index.php?title=BOINC_Client_Errors_and_Error_Codes
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 2022595 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 2022621 - Posted: 10 Dec 2019, 12:46:16 UTC - in response to Message 2022433.  

Things are somewhat further along now I re-installed using "run as administrator" on the installer.
Yeah, don't do that. The Super User Administrator account in Windows is a different beast than the normal administrator account. You now have a severe permissions problem. Best uninstall and reinstall with just your normal administrator account. Don't forget to check "Allow all users on this computer to control BOINC" in the (third screen in the installer click Advanced) installer.

I don't mind you testing things, but it's difficult for us who try to help as we don't know what you do. And it gets more difficult if we try to give help and you completely ignore that.
BOINC by default doesn't need super user accounts or any hoop hustling to be installed. Just an administrator account to install, "Allow all users on this computer to control BOINC" checked and anyone logging in can use it, from normal users to power users to administrators.
ID: 2022621 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 2022628 - Posted: 10 Dec 2019, 14:00:08 UTC
Last modified: 10 Dec 2019, 14:03:43 UTC

And here too, you can always try to uninstall BOINC, then download and install https://boinc.berkeley.edu/dl/boinc_7.14.2_windows_intelx86.exe
Mind to point out the BOINC Programs directory correctly, in the third screen of the installer click Advanced, then change the C:\Program Files\BOINC\ path to C:\Program Files (x86)\BOINC\ and continue the installation.

This is a 32bit version of BOINC. The 64bit version of BOINC can't run on all 64bit versions of Windows for some reason, but the 32bit version always can. It too can run 64bit applications on a 64bit CPU.
ID: 2022628 · Report as offensive
brownec

Send message
Joined: 21 May 99
Posts: 10
Credit: 95,510,239
RAC: 72
United States
Message 2022652 - Posted: 10 Dec 2019, 16:32:59 UTC - in response to Message 2022595.  

I've checked all the permissions and the C:\ProgramData\BOINC has full permissions for "Everyone".

Don't know about the password. I've deleted the file and let it re-create itself, but still no luck.

OS is Windows 10 Home, 1903

PS: Why is a default install so difficult?
ID: 2022652 · Report as offensive
brownec

Send message
Joined: 21 May 99
Posts: 10
Credit: 95,510,239
RAC: 72
United States
Message 2022664 - Posted: 10 Dec 2019, 23:04:35 UTC - in response to Message 2022652.  

Deleted 64bit version and deleted the data folder.
Downloaded and instgalled the 32bit version. NO ISSUES!
Only a message about virtual box not detected. I assume that is not an issue.
Since its Tuesday, I can't get any tasks ATM...I'll let you know if that works out
ID: 2022664 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 2022677 - Posted: 11 Dec 2019, 0:12:58 UTC - in response to Message 2022664.  
Last modified: 11 Dec 2019, 0:14:54 UTC

Seti doesn't use VirtualBox so no, for this project it isn't an issue. You don't seem to run any other projects, one of which may require VB, but if it's needed it's always best to download the latest version from their website anyway, as the one included in BOINC is now old - by standards.

But since your BOINC now starts up, and your new system is in your list of computers, I suspect your troubles are over. Glad to have been of help.
ID: 2022677 · Report as offensive
brownec

Send message
Joined: 21 May 99
Posts: 10
Credit: 95,510,239
RAC: 72
United States
Message 2022689 - Posted: 11 Dec 2019, 1:33:23 UTC - in response to Message 2022677.  

Tasks are now running. Thank you immensely...

Curious as to why 64bit won't work on this machine/OS. Also there is no indication for this on the boinc main page.
I would never have found the 32bit version without your help
ID: 2022689 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 2022737 - Posted: 11 Dec 2019, 7:43:01 UTC - in response to Message 2022689.  

Something about an incompatibility between the OS and one of the library files BOINC makes use of, usually the libeay32.dll used by the OpenSSL encryption algorithm. Why it won't run on some Windows versions we don't know. That makes it so hard to figure out.
ID: 2022737 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13414
Credit: 208,696,464
RAC: 304
Australia
Message 2022739 - Posted: 11 Dec 2019, 7:45:23 UTC - in response to Message 2022689.  
Last modified: 11 Dec 2019, 7:49:32 UTC

Curious as to why 64bit won't work on this machine/OS.
It claims to be
Microsoft Windows 10
Core x64
indicating it's meant to be 64bt (but it is the most basic of all Windows editions).


Edit- ignore below, your system is showing 16GB of RAM, so it is 64bit.

You can check whether it is 32bit or 64bit-
1. Select the Start button (the window thingy in the bottom left corner), then select Settings, then System, then About.
2. At the right, under Device specifications, see System type.
Grant
Darwin NT
ID: 2022739 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14542
Credit: 200,643,578
RAC: 874
United Kingdom
Message 2022742 - Posted: 11 Dec 2019, 9:26:37 UTC - in response to Message 2022737.  

Something about an incompatibility between the OS and one of the library files BOINC makes use of, usually the libeay32.dll used by the OpenSSL encryption algorithm. Why it won't run on some Windows versions we don't know. That makes it so hard to figure out.
I think we know that it happens on certain CPU types, like the low-power Intel N4x00 range.
ID: 2022742 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 2022752 - Posted: 11 Dec 2019, 11:56:15 UTC

I see that I wrote in ticket #2470 that there's another work around for the 64bit client, it's to make a cc_config.xml with the following lines:
<cc_config>
<log_flags>
</log_flags>
<options>
<no_info_fetch>1</no_info_fetch>
</options>
</cc_config>
Or adapt this into an existing cc_config.xml file.
This file, when it exists, lives in the BOINC Data directory. It doesn't come standard with BOINC, one has to make it by hand, or use the Event Log options menu once to make it automatically. When making it by hand, use Notepad, and save the file in ANSI format as an All Files (*.*) file format. Or make sure that when you save it that it doesn't get the .txt extension as then it won't work.

Afterwards restart BOINC.
ID: 2022752 · Report as offensive
1 · 2 · Next

Questions and Answers : Windows : New install - Unable to connect to core client


 
©2023 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.