Thread 'BOINC 7.2.42 released to the public'

Message boards : News : BOINC 7.2.42 released to the public
Message board moderation

To post messages, you must log in.

AuthorMessage
Rom Walton
Project developer
Avatar

Send message
Joined: 26 Aug 05
Posts: 164
Message 52872 - Posted: 28 Feb 2014, 20:28:32 UTC

A new version of BOINC is ready for public use. You can download it here. See the release notes and version history for details.
ID: 52872 · Report as offensive
Profilethanar
Avatar

Send message
Joined: 13 May 07
Posts: 54
Greece
Message 53032 - Posted: 7 Mar 2014, 15:33:31 UTC - in response to Message 52872.  
Last modified: 7 Mar 2014, 15:36:43 UTC

Hello,

Upon launching the installer on my MacBook 4,1 running 10.6.8, the installer crashes with the following error in console:
Job appears to have crashed: Bus error

Any similar behavior under OS X? BOINC 7.0.65 installs just fine.

The same download runs fine on an iMac 11,1 running 10.8.5. Could be something wrong with the other host, although I never had any issues.

Downloaded 7.2.39 and it still crashes, so it's not an issue with 7.2.42.
ID: 53032 · Report as offensive
ProfileKSMarksPsych
Avatar

Send message
Joined: 30 Oct 05
Posts: 1239
United States
Message 53048 - Posted: 8 Mar 2014, 2:36:55 UTC - in response to Message 53032.  

Hello,

Upon launching the installer on my MacBook 4,1 running 10.6.8, the installer crashes with the following error in console:
Job appears to have crashed: Bus error

Any similar behavior under OS X? BOINC 7.0.65 installs just fine.

The same download runs fine on an iMac 11,1 running 10.8.5. Could be something wrong with the other host, although I never had any issues.

Downloaded 7.2.39 and it still crashes, so it's not an issue with 7.2.42.


Thanks for the report. I've forwarded it to our Mac developer.
ID: 53048 · Report as offensive
Robert Waller

Send message
Joined: 3 Apr 13
Posts: 1
United Kingdom
Message 53070 - Posted: 9 Mar 2014, 15:27:11 UTC

upgraded to this from 7.2.33 and the flashing screensaver still persists, the same as 7.2.39, I'm going back to 7.2.33 again until you get this fixed. :(
ID: 53070 · Report as offensive
ProfileJord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15560
Netherlands
Message 53072 - Posted: 9 Mar 2014, 17:23:11 UTC

For the next person who thinks 7.2.42 has a fix for the screen saver problem, or that any next version will do so and it's not mentioned in the release thread, please always read the release notes.

In the case of 7.2.42, they're strictly:
Changes in 7.2.42

• Fix problem that was causing scheduler RPCs to fail on Yoyo@home (HTTP status code 400)

ID: 53072 · Report as offensive
Brent

Send message
Joined: 30 Mar 10
Posts: 14
United States
Message 53114 - Posted: 11 Mar 2014, 16:40:03 UTC - in response to Message 53072.  

For the next person who thinks 7.2.42 has a fix for the screen saver problem, or that any next version will do so and it's not mentioned in the release thread, please always read the release notes.

In the case of 7.2.42, they're strictly:
Changes in 7.2.42

• Fix problem that was causing scheduler RPCs to fail on Yoyo@home (HTTP status code 400)


If I don't use Yoyo@home, why should I update to 7.2.42? If I don't update, how do I get rid of the nag to run the 7.2.42 update?
ID: 53114 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 53126 - Posted: 11 Mar 2014, 21:08:39 UTC - in response to Message 53114.  

If I don't use Yoyo@home, why should I update to 7.2.42? If I don't update, how do I get rid of the nag to run the 7.2.42 update?

The bug affects all projects and it affects at least scheduler request and uploads and very likely downloads as well.

There's <client_download_url> and <client_version_check_url> options available in cc_config.xml. No idea if you can abuse them to disable version check.
ID: 53126 · Report as offensive
filchef

Send message
Joined: 13 Feb 14
Posts: 5
Bulgaria
Message 53167 - Posted: 14 Mar 2014, 23:09:06 UTC - in response to Message 53070.  

upgraded to this from 7.2.33 and the flashing screensaver still persists, the same as 7.2.39, I'm going back to 7.2.33 again until you get this fixed. :(


So problem with disco screensaver is not fixed jet.
ID: 53167 · Report as offensive
Claggy

Send message
Joined: 23 Apr 07
Posts: 1112
United Kingdom
Message 53168 - Posted: 14 Mar 2014, 23:29:33 UTC - in response to Message 53167.  

upgraded to this from 7.2.33 and the flashing screensaver still persists, the same as 7.2.39, I'm going back to 7.2.33 again until you get this fixed. :(


So problem with disco screensaver is not fixed jet.

Which part of the following didn't you understand?:

For the next person who thinks 7.2.42 has a fix for the screen saver problem, or that any next version will do so and it's not mentioned in the release thread, please always read the release notes.


Claggy
ID: 53168 · Report as offensive
Ron Renaud

Send message
Joined: 19 Mar 14
Posts: 1
Canada
Message 53224 - Posted: 19 Mar 2014, 13:31:47 UTC

RE: Version 7.2.42 (x86). I have tried setting "no new tasks" on a project ([email protected]) however tasks are still coming through. This was working fine up to the last version I had installed (it was before 7.2.39).
ID: 53224 · Report as offensive
ProfileJord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15560
Netherlands
Message 53230 - Posted: 19 Mar 2014, 17:39:45 UTC - in response to Message 53224.  
Last modified: 19 Mar 2014, 17:43:16 UTC

Works as advertised here:
19/03/2014 18:39:14 | LHC@home 1.0 | update requested by user
19/03/2014 18:39:18 | LHC@home 1.0 | sched RPC pending: Requested by user
19/03/2014 18:39:18 | LHC@home 1.0 | [sched_op] Starting scheduler request
19/03/2014 18:39:18 | LHC@home 1.0 | Sending scheduler request: Requested by user.
19/03/2014 18:39:18 | LHC@home 1.0 | Not requesting tasks: "no new tasks" requested via Manager
19/03/2014 18:39:18 | LHC@home 1.0 | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
19/03/2014 18:39:18 | LHC@home 1.0 | [sched_op] AMD/ATI GPU work request: 0.00 seconds; 0.00 devices
19/03/2014 18:39:20 | LHC@home 1.0 | Scheduler request completed
19/03/2014 18:39:20 | LHC@home 1.0 | [sched_op] Server version 701
19/03/2014 18:39:20 | LHC@home 1.0 | Project requested delay of 6 seconds
19/03/2014 18:39:20 | LHC@home 1.0 | [sched_op] Deferring communication for 00:00:06
19/03/2014 18:39:20 | LHC@home 1.0 | [sched_op] Reason: requested by project

Make sure the project doesn't do resend lost work, and that the work you get isn't lost work. Also make sure you set the correct project to NNT.

You can also check in client_state.xml in the BOINC data directory.
In it look for the entry of <master_url>http://lhcathomeclassic.cern.ch/sixtrack/</master_url>, then scroll down a bit and if you set NNT correctly on this project, it should say <dont_request_more_work/> just above the <rsc_backoff_time> entries.
ID: 53230 · Report as offensive
fridayjunior

Send message
Joined: 25 Mar 14
Posts: 1
Canada
Message 53280 - Posted: 25 Mar 2014, 2:22:21 UTC

I love to contribute. I had a nervous breakdown in high school, which devastated my 85-90% grade averages in academics. I've never really accepted this. Using "BOINC" gives me the chance to give back to all the health-care professionals and makes me keep trying to find answers to my educational dysfunction. Thank-you folks for the opportunity to learn and enjoy myself through self-study with the computer as my teacher.
ID: 53280 · Report as offensive
RMA

Send message
Joined: 1 Apr 14
Posts: 4
Message 53463 - Posted: 1 Apr 2014, 15:23:32 UTC

I have just installed BOINC 7.4.42. On starting it I get messages that it has crashed 3 times then 'unable to connect to the core client'. I am using Windows 7. On the windows wvent log the message is: 'event 1000 application error'
System

- Provider

[ Name] Application Error

- EventID 1000

[ Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2014-04-01T15:03:36.000000000Z

EventRecordID 4198

Channel Application

Computer Richard-PC

Security


- EventData

boinc.exe
7.2.42.0
530f97f9
MSVCR80.dll
8.0.50727.6195
4dcdd833
c0000005
000000000000b0aa
e08
01cf4dbb83790a55
C:\Program Files\BOINC\boinc.exe
C:\Program Files\BOINC\MSVCR80.dll
cc6cfa61-b9ae-11e3-ace0-94de80ea7882
ID: 53463 · Report as offensive
RMA

Send message
Joined: 1 Apr 14
Posts: 4
Message 53469 - Posted: 1 Apr 2014, 21:25:54 UTC - in response to Message 53463.  

further to my previous post. I uninstalled BOINC, re-downloaded it and re-installed it. Now working OK.

I have just installed BOINC 7.4.42. On starting it I get messages that it has crashed 3 times then 'unable to connect to the core client'. I am using Windows 7. On the windows wvent log the message is: 'event 1000 application error'
System

- Provider

[ Name] Application Error

- EventID 1000

[ Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2014-04-01T15:03:36.000000000Z

EventRecordID 4198

Channel Application

Computer Richard-PC

Security


- EventData

boinc.exe
7.2.42.0
530f97f9
MSVCR80.dll
8.0.50727.6195
4dcdd833
c0000005
000000000000b0aa
e08
01cf4dbb83790a55
C:\Program Files\BOINC\boinc.exe
C:\Program Files\BOINC\MSVCR80.dll
cc6cfa61-b9ae-11e3-ace0-94de80ea7882
ID: 53469 · Report as offensive

Message boards : News : BOINC 7.2.42 released to the public

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.