Message boards : Questions and problems : project list doesn't populate & URL entry does not work for addition of 1st project new machine
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
Send message Joined: 28 Nov 19 Posts: 9 ![]() |
No local host connection = no boinc.exe running (at least as far as I can tell).Yup, that's a good takeaway. Conversely, boinc.exe has to be running in order for connection to be made. |
Send message Joined: 5 Oct 06 Posts: 5149 ![]() |
Thanks goodness the Alzheimer's hasn't kicked in yet. Have a look at message 85887. |
![]() Send message Joined: 28 Jun 10 Posts: 2842 ![]() |
@other helpers - didn't we have a problem with one of those low-power Intel chips failing to run 64-bit SSL routines? Might be worth a try with a 32-bit BOINC while we look up 'Celeron(R) N4000 CPU'. I did wonder about SSE instructions but at least according to the Intel specs that CPU has SSE instruction set built in up to 4. Doesn't stop there being a problem with it I suppose. I know at some point two or three years ago CPDN stopped working with CPUs which didn't have SSE2 minimum support. It may even be longer my memory on the time scale of these things is not very reliable. I would certainly try the 32 bit BOINC to see if that works. |
![]() Send message Joined: 29 Aug 05 Posts: 15632 ![]() |
Quote fest. Anyway, I'll go with Richard: Uninstall your present BOINC, then download and install this version: https://boinc.berkeley.edu/dl/boinc_7.14.2_windows_intelx86.exe This is a 32bit version of BOINC. Don't worry, it'll run all the 64bit applications on your 64bit CPU as well. Edit: 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. Edit: lol, thanks for the proof read Richard |
Send message Joined: 5 Oct 06 Posts: 5149 ![]() |
|
Send message Joined: 28 Nov 19 Posts: 9 ![]() |
Thanks to all helping out here! Downloading & installing the 32bit version solves the problem, but... it sure would be nice to know why the 64bit machine can't run the 64bit version of Boinc. I'll check back to see if anyone has solved why this Asus PN40 Mini PC fan-less w a dual core 64bit Celeron Intel processor won't run the 64bit Boinc, but for now it's running and I've got electronics to design if I'm going to be able to retire before I turn 70 (10 years from now). Again, Thanks to All'Y'All!!! JSDeBruyn Dutchman Electronics Team founder |
![]() Send message Joined: 28 Jun 10 Posts: 2842 ![]() |
I wonder if this is at all related to why the 64bit Windows version of BOINC doesn't work with WINE under Linux? |
![]() Send message Joined: 29 Aug 05 Posts: 15632 ![]() |
it sure would be nice to know why the 64bit machine can't run the 64bit version of Boinc.As far as we can deduct it's to do with your CPU. The problem happens when the BOINC client contacts the BOINC server for the first time to check for an update. This contact happens via SSL, and something in the OpenSSL libraries balks at making this contact on a low powered CPU. 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. |
Send message Joined: 5 Oct 06 Posts: 5149 ![]() |
What happens when a 64-bit client with <no_info_fetch> tries to contact a project over SSL? That fix might just push the problem a bit further down the road. |
![]() Send message Joined: 29 Aug 05 Posts: 15632 ![]() |
The problem never seemed to be with contacting a project or the client didn't get that far, it was the contact with the BOINC server that crashed the client. |
Send message Joined: 5 Oct 06 Posts: 5149 ![]() |
Your report was on Apr 16, 2018, nearly 20 months ago - I think more projects might have switched to SSL since then. Else, what is strange about The BOINC server? The BOINC SSL certificate? The 'get info' process/code? that makes that fail, but allows everything else? |
![]() Send message Joined: 29 Aug 05 Posts: 15632 ![]() |
IMHO, the question is why it fails on low powered CPUs? Or is it Windows Core that it can't work with? But I don't think we're going to get an easy fix, unless we manage to get a developer one of these systems it fails on, so he can test what makes it go boom. |
Send message Joined: 5 Oct 06 Posts: 5149 ![]() |
Well, maybe I could get a nano-computer next Black Friday. But at the moment I'm a bit busy with the Android tablet I bought this time. |
Copyright © 2025 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.