Windows install issues

Message boards : Questions and problems : Windows install issues
Message board moderation

To post messages, you must log in.

AuthorMessage
Don

Send message
Joined: 8 Sep 17
Posts: 28
United States
Message 92611 - Posted: 27 Aug 2019, 19:19:02 UTC

I installed BOINC 7.14.2 on a new install of Windows 10 Pro on an Odroid-H2. I installed as a service using an admin account and also using run as administrator. Windows is up to date with all patches and updates. I changed the password in the cfg file. I am having a few issues.

1 - the manager will not connect to the client. No error messages.
2 - there was no cc_comfig.xml file created. Do I have to create it or is it supposed to be created automatically?
3 - I get messages stating that the client has stopped x number of times in y minutes and would I like to restart.

I have BOINC running on two other Win 10 computers that I installed a few years ago and don’t remember having any install issues.

What am I missing or doing wrong?
ID: 92611 · Report as offensive
Don

Send message
Joined: 8 Sep 17
Posts: 28
United States
Message 92619 - Posted: 28 Aug 2019, 2:47:07 UTC

I think the problem is that the client keeps failing. Found this in the system application logs

Faulting application name: boinc.exe, version: 7.14.2.0, time stamp: 0x5bbe9f91
Faulting module name: LIBEAY32.dll, version: 1.0.2.7, time stamp: 0x56d5fc8e
Exception code: 0xc0000005
Fault offset: 0x00000000000e6543
Faulting process id: 0x9b4
Faulting application start time: 0x01d55d49e417c07e
Faulting application path: C:\Program Files\BOINC\boinc.exe
Faulting module path: C:\Program Files\BOINC\LIBEAY32.dll
Report Id: 476711ec-dc10-40fd-adaf-9928b0bc88e3
Faulting package full name:
Faulting package-relative application ID:
ID: 92619 · Report as offensive
Profile Gary Charpentier
Avatar

Send message
Joined: 23 Feb 08
Posts: 2463
United States
Message 92620 - Posted: 28 Aug 2019, 13:24:06 UTC - in response to Message 92619.  

I think the problem is that the client keeps failing. Found this in the system application logs

Faulting application name: boinc.exe, version: 7.14.2.0, time stamp: 0x5bbe9f91
Faulting module name: LIBEAY32.dll, version: 1.0.2.7, time stamp: 0x56d5fc8e
Exception code: 0xc0000005
Fault offset: 0x00000000000e6543
Faulting process id: 0x9b4
Faulting application start time: 0x01d55d49e417c07e
Faulting application path: C:\Program Files\BOINC\boinc.exe
Faulting module path: C:\Program Files\BOINC\LIBEAY32.dll
Report Id: 476711ec-dc10-40fd-adaf-9928b0bc88e3
Faulting package full name:
Faulting package-relative application ID:

If LIBEAY32.dll is the faulting module, it contains the open SSH encryption routines, I suggest remove - reinstall.
ID: 92620 · Report as offensive
Don

Send message
Joined: 8 Sep 17
Posts: 28
United States
Message 92623 - Posted: 28 Aug 2019, 15:19:08 UTC - in response to Message 92620.  

I tried uninstalling and reinstalling. I also tried going back one version. Same results.
ID: 92623 · Report as offensive
Profile Joseph Stateson
Volunteer tester
Avatar

Send message
Joined: 27 Jun 08
Posts: 641
United States
Message 92625 - Posted: 28 Aug 2019, 15:32:33 UTC

Is this 64 bit windows? 32 bit runtime problem?
ID: 92625 · Report as offensive
mmonnin

Send message
Joined: 1 Jul 16
Posts: 146
United States
Message 92628 - Posted: 28 Aug 2019, 19:07:39 UTC

It needs to be installed as a service?
ID: 92628 · Report as offensive
Don

Send message
Joined: 8 Sep 17
Posts: 28
United States
Message 92631 - Posted: 29 Aug 2019, 3:44:43 UTC - in response to Message 92625.  
Last modified: 29 Aug 2019, 3:45:37 UTC

Is this 64 bit windows? 32 bit runtime problem?

Yes, it is 64 bit Windows. No projects are attached/enabled yet because I cannot connect to the client.

What about the question on the cc_config.xml file?
ID: 92631 · Report as offensive
Don

Send message
Joined: 8 Sep 17
Posts: 28
United States
Message 92632 - Posted: 29 Aug 2019, 3:46:10 UTC - in response to Message 92628.  

It needs to be installed as a service?

Yes if you want it to start when the computer starts. Otherwise you have to log in for it to start.
ID: 92632 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5080
United Kingdom
Message 92633 - Posted: 29 Aug 2019, 8:01:55 UTC - in response to Message 92631.  

What about the question on the cc_config.xml file?
cc_config.xml is completely optional, and not created by default. Make one if you feel the need to run something non-standard, once you get the client working.
ID: 92633 · Report as offensive
Profile Joseph Stateson
Volunteer tester
Avatar

Send message
Joined: 27 Jun 08
Posts: 641
United States
Message 92634 - Posted: 29 Aug 2019, 11:44:55 UTC - in response to Message 92619.  
Last modified: 29 Aug 2019, 11:49:54 UTC

On more than one occasion I have accidently installed 32bit BOINC on a 64 bit windows. I remember seeing errors with libraries. Just a guess. However, I was looking at the following


Faulting module name: LIBEAY32.dll, version: 1.0.2.7, time stamp: 0x56d5fc8e


Using https://www.freeformatter.com/epoch-timestamp-to-date-converter.html

Your LIBEALY32.dll is dated 3/1/2016, 2:33:18 PM

I just checked two of my 7.14.2 win10x64 systems and they show 12/18/2016 4:46 PM for the same version 1.0.2.7

Not sure of the significance. If your version includes VM possible the dll package is older.

I have not used service installs of BOINC since I got rid of my XP systems so I cannot advise other to say netplwiz can be used to log in automatically.
ID: 92634 · Report as offensive
Don

Send message
Joined: 8 Sep 17
Posts: 28
United States
Message 92652 - Posted: 1 Sep 2019, 6:07:20 UTC

I am still unable to get this to run. I have uninstalled/installed many times. I have even installed it not as a service. I have disabled Windows firewall and UAC while troubleshooting. Still no joy. Still getting the following in the application event log

Faulting application name: boinc.exe, version: 7.14.2.0, time stamp: 0x5bbe9f91
Faulting module name: LIBEAY32.dll, version: 1.0.2.7, time stamp: 0x56d5fc8e
Exception code: 0xc0000005
Fault offset: 0x00000000000e6543
Faulting process id: 0xfb8
Faulting application start time: 0x01d5608826577129
Faulting application path: C:\Program Files\BOINC\boinc.exe
Faulting module path: C:\Program Files\BOINC\LIBEAY32.dll
Report Id: 2480f8f7-d9f6-4e84-950a-d55c5db7b6d9
Faulting package full name:
Faulting package-relative application ID:

Any BOINC developers out there that can shed some light on this?
ID: 92652 · Report as offensive
rebirther
Avatar

Send message
Joined: 21 Jun 06
Posts: 156
Germany
Message 92653 - Posted: 1 Sep 2019, 7:22:00 UTC - in response to Message 92652.  
Last modified: 1 Sep 2019, 7:27:11 UTC

https://github.com/BOINC/boinc/issues/2470

You can try this. It looks like it was an older issue.

Do you have also tried an older version of BOINC?
ID: 92653 · Report as offensive
Don

Send message
Joined: 8 Sep 17
Posts: 28
United States
Message 92663 - Posted: 1 Sep 2019, 21:41:35 UTC - in response to Message 92653.  

https://github.com/BOINC/boinc/issues/2470

You can try this. It looks like it was an older issue.

Do you have also tried an older version of BOINC?

I tried adding <no_info_fetch>1</no_info_fetch> and still won't work. My cpu is Processor: 4 GenuineIntel Intel(R) Celeron(R) J4105 CPU @ 1.50GHz [Family 6 Model 122 Stepping 1]. I'll try installing the 32 bit version.

There are a few other threads on this issue.

https://boinc.berkeley.edu/dev/forum_thread.php?id=11870#81545
https://setiathome.berkeley.edu/forum_thread.php?id=82881#1933142
https://boinc.berkeley.edu/forum_thread.php?id=12383#85590

All talk about it being addressed in a future release but that never happened. Any idea when it will be fixed?

Just an FYI. I purchased three Odroid-H2's to just run BOINC. It is a SBC containing an Intel Quad-core processor J4105 (14nm) with 4MiB Cache, up to 2.5Ghz(Single Thread) or 2.3Ghz(Multi Thread). A very nice piece of kit --> https://www.hardkernel.com/shop/odroid-h2/.

I'll provide a separate write up once I get it working.
ID: 92663 · Report as offensive
Profile Byron Leigh Hatch @ team Carl ...
Avatar

Send message
Joined: 30 Aug 05
Posts: 505
Canada
Message 92664 - Posted: 1 Sep 2019, 23:06:15 UTC - in response to Message 92632.  

It needs to be installed as a service?

Yes if you want it to start when the computer starts. Otherwise, you have to log in for it to start.

BOINC 7.14.2 (x64) not installed as a Service
i hope i can help
hi Don, when I start up my computer BOINC 7.14.2 Client starts automatically.

Editon --------- Windows 10 Pro for Workstations
Version -------- 1903
installed on --- 2019-08-27
OS Build ------- 18362.295


My experience is the following:
When for whatever reason I have to close BOINC or reboot my machine,

1) Open BOINC Manager, for me, 7.14.2 (x64) not installed as a Service
2) you will see tabs for - - - File, View, Activity, Options, Tools, Help



3) Click on the Options tap,
4) you will see a drop-down list,
5) Scroll down to other options,
6) Click on other Options and you will see the following,

7) Under the general tap. you should see Enable Manager exit dialog?
8) Make sure you tick that Box
9) then click OK
10) Now when you Exit BOINC, this popup Box should appear:



(11) Make sure the little box is tick: stop running tasks when exiting BOINC
(12) then click OK

I hope I got it right did I miss anything with the problem you're having?.
is this of any help to you?[/quote]

also, I'm running these 28 BOINC Projects.

ID: 92664 · Report as offensive
Don

Send message
Joined: 8 Sep 17
Posts: 28
United States
Message 92672 - Posted: 2 Sep 2019, 15:39:33 UTC - in response to Message 92664.  

@byron,

The issue is not about BOINC starting. It is about it crashing. The 64bit version crashes in LIBEAY32.dll. This SSL library is not current and needs to be updated to support certain CPUs. The library is version: 1.0.2.7 and the current one is 1.1.1. It was discussed over a year ago about updating the SSL library in BOINC but it looks like it never happened.

From OpenSSL.org: The latest stable version is the 1.1.1 series. This is also our Long Term Support (LTS) version, supported until 11th September 2023. Our previous LTS version (1.0.2 series) will continue to be supported until 31st December 2019 (security fixes only during the last year of support). The 1.1.0 series is currently only receiving security fixes and will go out of support on 11th September 2019. All users of 1.0.2 and 1.1.0 are encouraged to upgrade to 1.1.1 as soon as possible. The 0.9.8, 1.0.0 and 1.0.1 versions are now out of support and should not be used.

I have installed the 32bit version of BOINC and it is running but I'd rather be running the 64bit version as 64bit should run a little faster as long as it is optimized for 64bit.

I hope the developers issue an update soon that includes the latest SSL library.
ID: 92672 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15480
Netherlands
Message 92673 - Posted: 2 Sep 2019, 15:50:52 UTC - in response to Message 92672.  

I have installed the 32bit version of BOINC and it is running but I'd rather be running the 64bit version as 64bit should run a little faster as long as it is optimized for 64bit.
The 32bit version of BOINC can still run 64bit science applications and it's these latter that speed up calculations or not, not the bitness of the BOINC version you have.
ID: 92673 · Report as offensive
Don

Send message
Joined: 8 Sep 17
Posts: 28
United States
Message 92676 - Posted: 2 Sep 2019, 18:24:23 UTC - in response to Message 92673.  

I have installed the 32bit version of BOINC and it is running but I'd rather be running the 64bit version as 64bit should run a little faster as long as it is optimized for 64bit.
The 32bit version of BOINC can still run 64bit science applications and it's these latter that speed up calculations or not, not the bitness of the BOINC version you have.

I didn't realize that. Good to know!

Thanks
ID: 92676 · Report as offensive
wolfman1360

Send message
Joined: 5 Sep 17
Posts: 10
Canada
Message 92704 - Posted: 4 Sep 2019, 20:44:43 UTC

Hello
I was having these exact same issues not 3 weeks ago.
I'm glad to see I'm not the only one. This was on a Topjoy Falcon running a Pentium Silver J5005.
I ended up installing the WCG client, which worked, and I believe is also 32 bit.
ID: 92704 · Report as offensive

Message boards : Questions and problems : Windows install issues

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.