|
1)
Message boards :
Number crunching :
~10x normal daily credit in a few hours!!
(Message 4176)
Posted 27 Apr 2020 by Thyme Lawn Post: Thanks Krysztof. The 7 workunits where I had a cancelled task and another task was successfully completed have granted 1000 credits to the completed task (WUs 44132225, 44132322, 44132431, 44132453, 44132693, 44132597 and 44132782), but my own successfully completed task in WU 44105196 was granted 0. The 2 differences I can see are:
|
|
2)
Message boards :
Number crunching :
~10x normal daily credit in a few hours!!
(Message 4172)
Posted 24 Apr 2020 by Thyme Lawn Post: I had 11 tasks aborted by the server 3 hours ago, with 7 of them having a successfully completed task in the workunit which now has the status "Completed, can't validate". I have one task which has suffered the same fate. Presumably the affected tasks will also be granted credit. |
|
3)
Message boards :
Number crunching :
Upload failure: file size too big
(Message 4170)
Posted 20 Apr 2020 by Thyme Lawn Post: The universe_ulx_511 and universe_ulx_512 tasks on my system have the following in client_state.xml. The <workunit> sections have the maximum disk space set to 2,384MB (2.33GB): <rsc_disk_bound>2500000000.000000</rsc_disk_bound> The <result> sections have the _1 upload file limit set to 1,621MB (1.58GB): <max_nbytes>1700000000.000000</max_nbytes> My maximum upload speed is 640Kbps so (assuming there's no other activity, which will never be the case) it would take almost 45 minutes to upload a 1.58GB file. ULX tasks average out at around 3¼ hours each on my system, so if that was the happening for all tasks running 4 of them would generate more upload data than my connection could handle. Fortunately the size range for my ULX _1 upload files has ranged from 4.4MB to 132.7MB in the past few days ... |
|
4)
Message boards :
Number crunching :
Totally false server report/status
(Message 4165)
Posted 18 Apr 2020 by Thyme Lawn Post: All workunits have a minimum quorum of 2, so a second task has to be completed with the same result before tasks can change to validated. All of your tasks are waiting for the second completion. For example, the last task in your list is from WU 43924054 and the second task still has 11 days to go until it'll be timed out (deadline 29 Apr 2020, 14:46:28 UTC). If that task fails or times out the server will issue an additional task and continue to do that until a pair of tasks are validated, 5 tasks fail or 10 tasks have been reported (any aborted tasks won't count as a failed task but will count as a reported task). 95577088 546390 15 Apr 2020, 14:46:28 UTC 29 Apr 2020, 14:46:28 UTC In progress --- --- --- Universe BHspin v2 v0.19 x86_64-pc-linux-gnu 95577089 556762 15 Apr 2020, 21:54:32 UTC 16 Apr 2020, 0:11:58 UTC Completed, waiting for validation 5,516.64 5,488.11 pending Universe BHspin v2 v0.19 x86_64-pc-linux-gnu |
|
5)
Message boards :
Number crunching :
WU Error -> WU error -> WU error
(Message 4160)
Posted 12 Apr 2020 by Thyme Lawn Post: It's definitely nothing to do with vbox. I chose not to install it and have had file size too big errors. |
|
6)
Questions and Answers :
Web site :
Universe@home not shown in BOINC Stats
(Message 4149)
Posted 9 Apr 2020 by Thyme Lawn Post: Check that Do you consent to exporting your data to BOINC statistics aggregation Web sites? is checked in your project preferences. Your stats can't be exported if it isn't. |
|
7)
Message boards :
Number crunching :
Stats problem
(Message 4148)
Posted 9 Apr 2020 by Thyme Lawn Post: Check that Do you consent to exporting your data to BOINC statistics aggregation Web sites? is checked in your project preferences. Your stats can't be exported if it isn't. |
|
8)
Message boards :
News :
New ULX's
(Message 4140)
Posted 31 Mar 2020 by Thyme Lawn Post: I've aborted 6 ULX tasks which had failed with the Disk usage limit exceeded error on other computers. One of the tasks on that list was cancelled by the server earlier today after the workunit had its 7th error task (with 4 of them being disk limit exceeded). |
|
9)
Message boards :
Number crunching :
Linux new app version
(Message 3249)
Posted 2 Feb 2019 by Thyme Lawn Post: I hope to release Windows, ARM64 and ARM32 compilations today also. The version 0.11 app has failed to start 33 tasks on my Windows 10 i7 system (which had had 468 consecutive valid tasks with the version 0.6 app). BOINC event log messages for universe_bh2_180328_253_6832283168_20000_1-999999_290400_2 were: 02-Feb-2019 16:09:49 [Universe@Home] Process creation failed: (unknown error) - error code 216 (0xd8) 02-Feb-2019 16:09:49 [Universe@Home] Process creation failed: (unknown error) - error code 216 (0xd8) 02-Feb-2019 16:09:50 [Universe@Home] Process creation failed: (unknown error) - error code 216 (0xd8) 02-Feb-2019 16:09:50 [Universe@Home] Process creation failed: (unknown error) - error code 216 (0xd8) 02-Feb-2019 16:09:51 [Universe@Home] Process creation failed: (unknown error) - error code 216 (0xd8) 02-Feb-2019 16:09:51 [Universe@Home] [task] result state=COMPUTE_ERROR for universe_bh2_180328_253_6832283168_20000_1-999999_290400_2 from CS::report_result_error 02-Feb-2019 16:09:51 [Universe@Home] [task] couldn't start app: CreateProcess() failed - (unknown error) 02-Feb-2019 16:09:51 [Universe@Home] [task] task_state=COULDNT_START for universe_bh2_180328_253_6832283168_20000_1-999999_290400_2 from start 02-Feb-2019 16:09:51 [Universe@Home] [task] task_state=COULDNT_START for universe_bh2_180328_253_6832283168_20000_1-999999_290400_2 from resume_or_start1 02-Feb-2019 16:09:51 [Universe@Home] Computation for task universe_bh2_180328_253_6832283168_20000_1-999999_290400_2 finished 02-Feb-2019 16:09:51 [Universe@Home] Output file universe_bh2_180328_253_6832283168_20000_1-999999_290400_2_r662103412_0 for task universe_bh2_180328_253_6832283168_20000_1-999999_290400_2 absent 02-Feb-2019 16:09:51 [Universe@Home] Output file universe_bh2_180328_253_6832283168_20000_1-999999_290400_2_r662103412_1 for task universe_bh2_180328_253_6832283168_20000_1-999999_290400_2 absent 02-Feb-2019 16:09:51 [Universe@Home] Output file universe_bh2_180328_253_6832283168_20000_1-999999_290400_2_r662103412_2 for task universe_bh2_180328_253_6832283168_20000_1-999999_290400_2 absent 02-Feb-2019 16:09:51 [Universe@Home] Output file universe_bh2_180328_253_6832283168_20000_1-999999_290400_2_r662103412_3 for task universe_bh2_180328_253_6832283168_20000_1-999999_290400_2 absent 02-Feb-2019 16:09:51 [Universe@Home] Output file universe_bh2_180328_253_6832283168_20000_1-999999_290400_2_r662103412_4 for task universe_bh2_180328_253_6832283168_20000_1-999999_290400_2 absent 02-Feb-2019 16:09:51 [Universe@Home] Output file universe_bh2_180328_253_6832283168_20000_1-999999_290400_2_r662103412_5 for task universe_bh2_180328_253_6832283168_20000_1-999999_290400_2 absent 02-Feb-2019 16:09:51 [Universe@Home] [task] result state=COMPUTE_ERROR for universe_bh2_180328_253_6832283168_20000_1-999999_290400_2 from CS::app_finished |
|
10)
Message boards :
News :
BHDB application
(Message 2659)
Posted 10 Mar 2018 by Thyme Lawn Post: I've had a few batch 5 tasks have failed with EXIT_DISK_LIMIT_EXCEEDED, with plenty more in progress. One has just failed at almost 99%, and BOINC Manager's event log shows the underlying problem: 10/03/2018 08:22:16 | Universe@Home | Aborting task universe_bhdb_180109_5_21874979_20000_1-999999_875200_1: exceeded disk limit: 961.11MB > 858.31MB Workunits have <rsc_disk_bound>900000000.000000</rsc_disk_bound> (858.31MB). Disk usage in that task's slot directory leading up to the failure was primarily in the data1.dat2 and data1.dat3 files, with both weighing in at over 460MB (i.e. their total disk usage was above the limit). |
|
11)
Message boards :
Number crunching :
extreme long wu's
(Message 2456)
Posted 7 Nov 2017 by Thyme Lawn Post: I have regular endless tasks to. Win 10 PC which run 7/24. Aborting the last WU after 14 hours I found the process two days later still running in Taskmanager!!! So the process wasn´t canceled but removed from Boinc. I have 80 hours wasted time. So I can´t run no more WUs because of this bad behavior. My i7-6700K Windows 10 Pro system has just had its first task which got stuck in a loop (the _2 task in WU universe_bh2_160803_202_16199984_20000_1-999999_200200, with the _1 task being successfully completed using the android_arm_pie application). The task made a single checkpoint after 0:03:27 and was aborted in BOINC Manager 5:20:29 later. It must have been in a loop because it kept running and had to be manually killed from Process Explorer (i.e. it was never executing the BOINC API code which checks for messages from the BOINC core client). It was run with no interruptions and BOINC's event log shows that the _0 task from universe_bh2_160803_202_94384906_20000_1-999999_385200 was successfully completed 1:14:40 before the problem task started: 07-Nov-2017 14:24:10 [Universe@Home] Starting task universe_bh2_160803_202_94384906_20000_1-999999_385200_0 |
(English)
(Polski)