|
1)
Questions and Answers :
Preferences :
How do I prevent getting partial CPU tasks
(Message 41921)
Posted 16 Mar 2020 by jelle Post: Thank you. I did search for mention of this, but did not find it. I will explore the solution with an app_config. |
|
2)
Questions and Answers :
Preferences :
How do I prevent getting partial CPU tasks
(Message 41907)
Posted 15 Mar 2020 by jelle Post: I often get tasks for 0.2, or 0.4 or 0.8 CPUs. This is annoying because this causes many of them to try loading themselves. Often they then run out of memory, or they ignore CPU limits and all try to run simultaneously. How can I prevent myself from getting these partial CPU tasks? |
|
3)
Message boards :
ATLAS application :
Uploading stuck
(Message 41001)
Posted 18 Dec 2019 by jelle Post: For good measure I just did a reboot as well. Event log from restarting BOINC afterwards (with some irrelevant lines removed) is as follows. Wed 18 Dec 2019 23:02:53 NZDT | | Starting BOINC client version 7.9.3 for x86_64-pc-linux-gnu Wed 18 Dec 2019 23:02:53 NZDT | | log flags: file_xfer, sched_ops, task Wed 18 Dec 2019 23:02:53 NZDT | | Libraries: libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3 Wed 18 Dec 2019 23:02:53 NZDT | | Data directory: /var/lib/boinc-client Wed 18 Dec 2019 23:02:53 NZDT | | CUDA: NVIDIA GPU 0: GeForce GTX 1050 (driver version 390.11, CUDA version 9.1, compute capability 6.1, 1999MB, 1744MB available, 1960 GFLOPS peak) Wed 18 Dec 2019 23:02:53 NZDT | | OpenCL: NVIDIA GPU 0: GeForce GTX 1050 (driver version 390.116, device version OpenCL 1.2 CUDA, 1999MB, 1744MB available, 1960 GFLOPS peak) Wed 18 Dec 2019 23:02:53 NZDT | | [libc detection] gathered: 2.27, Ubuntu GLIBC 2.27-3ubuntu1 Wed 18 Dec 2019 23:02:53 NZDT | | Host name: ZARX1804 Wed 18 Dec 2019 23:02:53 NZDT | | Processor: 4 GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz [Family 6 Model 58 Stepping 9] Wed 18 Dec 2019 23:02:53 NZDT | | OS: Linux Ubuntu: Ubuntu 18.04.3 LTS [5.0.0-37-generic|libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1)] Wed 18 Dec 2019 23:02:53 NZDT | | Memory: 15.55 GB physical, 0 bytes virtual Wed 18 Dec 2019 23:02:53 NZDT | | Disk: 38.20 GB total, 9.35 GB free Wed 18 Dec 2019 23:02:53 NZDT | | Local time is UTC +13 hours Wed 18 Dec 2019 23:02:53 NZDT | | VirtualBox version: 6.0.8r130520 Wed 18 Dec 2019 23:02:53 NZDT | | Config: GUI RPCs allowed from: Wed 18 Dec 2019 23:02:53 NZDT | | Last benchmark was 34 days 03:00:57 ago Wed 18 Dec 2019 23:02:53 NZDT | Asteroids@home | URL http://asteroidsathome.net/boinc/; Computer ID 532806; resource share 25 Wed 18 Dec 2019 23:02:53 NZDT | Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID 12751963; resource share 100 Wed 18 Dec 2019 23:02:53 NZDT | LHC@home | URL https://lhcathome.cern.ch/lhcathome/; Computer ID 10543635; resource share 300 Wed 18 Dec 2019 23:02:53 NZDT | Rosetta@home | URL http://boinc.bakerlab.org/rosetta/; Computer ID 3394589; resource share 100 Wed 18 Dec 2019 23:02:53 NZDT | Universe@Home | URL https://universeathome.pl/universe/; Computer ID 489260; resource share 100 Wed 18 Dec 2019 23:02:53 NZDT | | Running CPU benchmarks Wed 18 Dec 2019 23:02:53 NZDT | | Suspending computation - CPU benchmarks in progress Wed 18 Dec 2019 23:03:24 NZDT | | Benchmark results: Wed 18 Dec 2019 23:03:24 NZDT | | Number of CPUs: 2 Wed 18 Dec 2019 23:03:24 NZDT | | 4343 floating point MIPS (Whetstone) per CPU Wed 18 Dec 2019 23:03:24 NZDT | | 126625 integer MIPS (Dhrystone) per CPU Wed 18 Dec 2019 23:03:25 NZDT | | Suspending GPU computation - computer is in use Wed 18 Dec 2019 23:03:40 NZDT | LHC@home | Started upload of gCxMDmN9izvn9Rq4apoT9bVoABFKDmABFKDmt4SaDmABFKDmY4ACQo_0_r369045851_ATLAS_hits Wed 18 Dec 2019 23:03:59 NZDT | Rosetta@home | project resumed by user Wed 18 Dec 2019 23:04:12 NZDT | Universe@Home | project resumed by user Wed 18 Dec 2019 23:04:17 NZDT | Universe@Home | work fetch resumed by user Wed 18 Dec 2019 23:04:17 NZDT | Rosetta@home | work fetch resumed by user Wed 18 Dec 2019 23:04:44 NZDT | LHC@home | Backing off 04:49:32 on upload of gCxMDmN9izvn9Rq4apoT9bVoABFKDmABFKDmt4SaDmABFKDmY4ACQo_0_r369045851_ATLAS_hits Wed 18 Dec 2019 23:05:24 NZDT | LHC@home | Started upload of kspKDmb7wzvnsSi4apGgGQJmABFKDmABFKDmvDwVDmABFKDmzd6Ztn_0_r115146122_ATLAS_hits Wed 18 Dec 2019 23:06:26 NZDT | LHC@home | Backing off 03:30:16 on upload of kspKDmb7wzvnsSi4apGgGQJmABFKDmABFKDmvDwVDmABFKDmzd6Ztn_0_r115146122_ATLAS_hits So the ATLAS files are still receiving a project backoff when they try to upload, while everything else uploads fine. |
|
4)
Message boards :
ATLAS application :
Uploading stuck
(Message 41000)
Posted 18 Dec 2019 by jelle Post: Just to be sure your basic network connection works. Thank you for suggestion. I tried that command. Got your expected output, so no problem there. I can also note that the SixTrack I got on my last update successfully completed, uploaded and reported, so it's only the ATLAS tasks that are stuck. |
|
5)
Message boards :
ATLAS application :
Uploading stuck
(Message 40998)
Posted 18 Dec 2019 by jelle Post: Thank you for those suggestions. I have done another Update request. In the Boinc manager GUI, because using terminals seemed overkill. This is recent output from the event logl Wed 18 Dec 2019 20:44:57 NZDT | LHC@home | Started upload of gCxMDmN9izvn9Rq4apoT9bVoABFKDmABFKDmt4SaDmABFKDmY4ACQo_0_r369045851_ATLAS_hits Wed 18 Dec 2019 20:44:57 NZDT | LHC@home | Started upload of kspKDmb7wzvnsSi4apGgGQJmABFKDmABFKDmvDwVDmABFKDmzd6Ztn_0_r115146122_ATLAS_hits Wed 18 Dec 2019 20:46:01 NZDT | LHC@home | Backing off 03:14:20 on upload of gCxMDmN9izvn9Rq4apoT9bVoABFKDmABFKDmt4SaDmABFKDmY4ACQo_0_r369045851_ATLAS_hits Wed 18 Dec 2019 20:46:01 NZDT | LHC@home | Backing off 04:27:48 on upload of kspKDmb7wzvnsSi4apGgGQJmABFKDmABFKDmvDwVDmABFKDmzd6Ztn_0_r115146122_ATLAS_hits Wed 18 Dec 2019 21:20:59 NZDT | Universe@Home | Sending scheduler request: Requested by project. Wed 18 Dec 2019 21:20:59 NZDT | Universe@Home | Requesting new tasks for CPU Wed 18 Dec 2019 21:21:02 NZDT | Universe@Home | Scheduler request completed: got 1 new tasks Wed 18 Dec 2019 21:21:04 NZDT | Universe@Home | Started download of universe_bh2_190723_292_448744552_20000_1-999999_745100 Wed 18 Dec 2019 21:21:08 NZDT | Universe@Home | Finished download of universe_bh2_190723_292_448744552_20000_1-999999_745100 Wed 18 Dec 2019 21:24:43 NZDT | | Suspending GPU computation - computer is in use Wed 18 Dec 2019 21:35:26 NZDT | LHC@home | project resumed by user Wed 18 Dec 2019 21:35:29 NZDT | LHC@home | Sending scheduler request: Requested by project. Wed 18 Dec 2019 21:35:29 NZDT | LHC@home | Requesting new tasks for CPU Wed 18 Dec 2019 21:35:33 NZDT | LHC@home | update requested by user Wed 18 Dec 2019 21:35:33 NZDT | LHC@home | Scheduler request completed: got 1 new tasks Wed 18 Dec 2019 21:35:35 NZDT | LHC@home | Started download of workspace1_hl14_OnErrors_OnOct_NoBB_col_B1_radial_dp_0.00003__1__s__62.31_60.32__13_13.1__6__84_1_sixvf_boinc11654.zip Wed 18 Dec 2019 21:35:38 NZDT | LHC@home | Finished download of workspace1_hl14_OnErrors_OnOct_NoBB_col_B1_radial_dp_0.00003__1__s__62.31_60.32__13_13.1__6__84_1_sixvf_boinc11654.zip The top lines represent the failing upload attempt. As you can see, I have no trouble connecting. I even downloaded a new SixTrack task for my effort. However, those two completed ATLAS tasks are just endlessly retrying their upload. Identical problem on another laptop, so it is not machine dependent. I will let it run that SixTrack task and see if that can upload. |
|
6)
Message boards :
ATLAS application :
Uploading stuck
(Message 40994)
Posted 18 Dec 2019 by jelle Post: For the last few days I have upload transfers stuck. Two ATLAS tasks have been trying to upload for at least two days now. The upload file size is only 221 bytes. I have the exact same problem on another computer, so it's probably not just a solution of turning it off and on again. Not having the problem uploading and reporting to other Boinc projects, so it's unique to LHC@home. Any suggestions? |
|
7)
Message boards :
News :
No RESULTS accepted from Linux Kernel 4.8.*
(Message 31545)
Posted 21 Jul 2017 by jelle Post: My apologies for late reply. I only now saw your message. I do have hyper-threading enabled. However, my CPUs are older Intel models that are not affected by the hyper-threading bug that is affecting Intel's Skylake and Kaby Lake CPUs. P.S. I would expect that Intel bug in the microcode to be affecting other Linux kernels and other operating systems too for the relevant CPUs. |
|
8)
Message boards :
News :
No RESULTS accepted from Linux Kernel 4.8.*
(Message 31392)
Posted 14 Jul 2017 by jelle Post: I'm not sure how you arrived at that conclusion? I represent a sample size of 1, but my SixTrack tasks seem to be running OK and are being (slowly) validated. I run Xubuntu Linux 64-bit with kernel 4.8.0-58. P.S. Maybe my sample size is 2. I have 2 machines running SixTrack without problems under Xubuntu Linux with the 64-bit kernel 4.8. You can check the details of my CPUs. |
|
9)
Message boards :
News :
VM applications
(Message 27925)
Posted 23 Nov 2016 by jelle Post: Thank you. That is helpful. My work machine with 4GB often needs to run a virtual machine with a Windows XP guest, so in practice that means I typically have only 2 GB available as free memory (prior to any BOINC tasks). |
|
10)
Message boards :
News :
VM applications
(Message 27913)
Posted 23 Nov 2016 by jelle Post: Is there any overview to indicate what the recommended requirements for each application are? At work I am using an older machine with only 4GB of memory, so I know that Atlas is practically out. My apologies if there is a response for this already. |
|
11)
Message boards :
Number crunching :
Available work?
(Message 27254)
Posted 1 Apr 2015 by jelle Post: Will it last over the Easter weekend? I have a work machine that is now crunching away on SixTrack only, with all other Boinc projects suspended. It would be a shame if that machine sits idle over the weekend because the Sixtrack tasks run out. |
|
12)
Message boards :
Number crunching :
Host messing up tons of results
(Message 26965)
Posted 8 Nov 2014 by jelle Post: I do expect the tasks to eventually be validated with another wingman, so I'm not worried about that. The strange thing is that the owner of the malfunctioning computer has 3 other machines that seem to be crunching away properly and getting good results. His total credit for LHC@home is 2,354,637; which is more than double what I have and entirely respectable. It's only 10137504 that throws off all the errors. |
|
13)
Message boards :
Number crunching :
Host messing up tons of results
(Message 26958)
Posted 8 Nov 2014 by jelle Post: Looks like same host is at it again and causing problems again. I have 2 tasks with validation inconclusive where this host is my wingman. One task in which the other host spent no CPU time at all, and another task that it "completed" in less than 1 second while I spent 1937 seconds on my Intel i7-3770. As of now, he has 2 valid results, 1337 pending, and 4249 inconclusive. I suspect that he will have errors in all those inconclusive results. Can somebody please block this guy from messing up results or block him from getting any new tasks. 10137504 currently has 13152 inconclusive results and 16 valid ones. |
|
14)
Message boards :
Number crunching :
Orphaned WU?
(Message 26920)
Posted 22 Oct 2014 by jelle Post: I have two work units that have been waiting for validation for more than 2 weeks. My original wingman timed out. Since that time the task for a new wingman is still waiting with status "Unsent". I'm curious if I should remain patient or if these work units have now become orphans. The work units in question are: http://lhcathomeclassic.cern.ch/sixtrack/workunit.php?wuid=21485769 and http://lhcathomeclassic.cern.ch/sixtrack/workunit.php?wuid=21484890 |
|
15)
Message boards :
Number crunching :
Invalid tasks
(Message 26350)
Posted 15 Apr 2014 by jelle Post: I suspect it's more of a trend or tendency, than a fixed pattern or rule. I didn't analyze all my results, and we can't go back enough far in time anyway. Like you, I suspect I may have long jobs with Windows wingmen that were validated correctly. However, I do notice that all my recent invalidated results seem to be long jobs with Windows wingmen. That's why it's only an impression or hunch that I wanted to share for now. P.S. Hat's off for keeping your Pentium III crunching. |
|
16)
Message boards :
Number crunching :
Invalid tasks
(Message 26348)
Posted 15 Apr 2014 by jelle Post: I don't have statistics to back this up, but my impression is that it is longer-running tasks on Linux that fail to validate against Windows. I have the impression that short runs may be OK, but any tasks that take more than a few hours on my i7-3770 seem to end up as invalidated if they go up against wingmen running Windows. They validate OK if my wingman is also running Linux. I am particularly bummed out because I have an Intel Atom powered netbook that was crunching away for more than 2 days on a task. And the wingman ran Windows so it invalidated. Would be good if this good be rectified. |
|
17)
Message boards :
Number crunching :
Abandoned tasks?
(Message 26333)
Posted 8 Apr 2014 by jelle Post: Hooray for the many new tasks I'm crunching. In the last hour, however, I'm suddenly getting tasks that complete, but are subsequently reported as being in error. The error status is "abandoned", which I've never seen before. I haven't abandoned anything, so I'm feeling very sorry for them. What's up with that? |
|
18)
Message boards :
Number crunching :
News, Status and Plans, 19th November, 2013
(Message 26077)
Posted 20 Nov 2013 by jelle Post:
There may indeed be diverse opinions on the merits of million-turn tasks and 200MB downloads and uploads. Personally I think it's great, but probably not suitable for all my machines. I would be delighted to crunch such tasks on my Intel i7-3770 powered desktop. I also do not expect to be constrained by bandwidth. However, I would probably not want to try the same thing on my Intel Atom powered netbook; particularly if I have to use a lousy wireless connection. I suggest a solution is to split those tasks into a different application type that people can select on the Sixtrack preferences page. Similar to how Einstein@Home has different applications for BRP, Gravitational Wave, and Gamma-ray pulsar searches. Perhaps the default for the large tasks should be turned off. People willing and with the bandwidth to deal with those tasks too can then select them explicitly. |
|
19)
Message boards :
Number crunching :
Big problem: work units running with negative time.
(Message 25847)
Posted 19 Sep 2013 by jelle Post: Sample size of 3 now. 3 completed of which 2 have already been validated. One on work PC with Xubuntu 12.04 and other on home PC with Xubuntu 12.10. Looks to me like the problem really has been solved. Congratulations and thanks. |
|
20)
Message boards :
Number crunching :
Big problem: work units running with negative time.
(Message 25845)
Posted 18 Sep 2013 by jelle Post: Sample size of 1 so far. Task 20475555 just completed on my work machine, running Xubuntu 12.04 64 bit. Took about 44 minutes. Is now waiting for validation. Second work unit has now started, and also seems to be running without trouble. Assuming it will stay that way, I am very grateful for the fix. |
Next 20
©2024 CERN