climateprediction.net home page
Work available and being requested but none downloaded

Work available and being requested but none downloaded

Message boards : Number crunching : Work available and being requested but none downloaded
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Bryn Mawr

Send message
Joined: 28 Jul 19
Posts: 147
Credit: 12,814,088
RAC: 261,385
Message 62376 - Posted: 30 Apr 2020, 18:01:53 UTC

Right, before I go the whole hog and remove / reboot / re-attach I tried reboot / reset project / update project. That produced no immediate impact but I've just gone in and set work fetch logging on.

Before I have done anything else it has logged :-

Thu 30 Apr 2020 18:44:44 BST | | choose_project(): 1588268684.165999
Thu 30 Apr 2020 18:44:44 BST | | [work_fetch] ------- start work fetch state -------
Thu 30 Apr 2020 18:44:44 BST | | [work_fetch] target work buffer: 17280.00 + 17280.00 sec
Thu 30 Apr 2020 18:44:44 BST | | [work_fetch] --- project states ---
Thu 30 Apr 2020 18:44:44 BST | climateprediction.net | [work_fetch] REC 540.959 prio -1.000 can request work
Thu 30 Apr 2020 18:44:44 BST | Rosetta@home | [work_fetch] REC 5007.826 prio -7.360 can't request work: "no new tasks" requested via Manager
Thu 30 Apr 2020 18:44:44 BST | World Community Grid | [work_fetch] REC 6263.186 prio -6.894 can't request work: "no new tasks" requested via Manager
Thu 30 Apr 2020 18:44:44 BST | | [work_fetch] --- state for CPU ---
Thu 30 Apr 2020 18:44:44 BST | | [work_fetch] shortfall 39797.07 nidle 0.00 saturated 27903.12 busy 0.00
Thu 30 Apr 2020 18:44:44 BST | climateprediction.net | [work_fetch] share 1.000
Thu 30 Apr 2020 18:44:44 BST | Rosetta@home | [work_fetch] share 0.000
Thu 30 Apr 2020 18:44:44 BST | World Community Grid | [work_fetch] share 0.000
Thu 30 Apr 2020 18:44:44 BST | | [work_fetch] ------- end work fetch state -------
Thu 30 Apr 2020 18:44:44 BST | climateprediction.net | choose_project: scanning
Thu 30 Apr 2020 18:44:44 BST | climateprediction.net | can fetch CPU
Thu 30 Apr 2020 18:44:44 BST | World Community Grid | choose_project: scanning
Thu 30 Apr 2020 18:44:44 BST | World Community Grid | skip: "no new tasks" requested via Manager
Thu 30 Apr 2020 18:44:44 BST | Rosetta@home | choose_project: scanning
Thu 30 Apr 2020 18:44:44 BST | Rosetta@home | skip: "no new tasks" requested via Manager
Thu 30 Apr 2020 18:44:44 BST | | [work_fetch] No project chosen for work fetch


Given that this says CPDN share = 1.0 and CPDN can fetch CPU I don't understand the last line, "No project chosen for work fetch".

On the assumption that this is saying that it has had no user request for a work fetch I'll suspend WCG and Rosetta and issue such a request ...

OK, as soon as I suspended the projects it took action of its own accord :-

Thu 30 Apr 2020 18:51:26 BST | Rosetta@home | project suspended by user
Thu 30 Apr 2020 18:51:26 BST | | [work_fetch] Request work fetch: project suspended
Thu 30 Apr 2020 18:51:26 BST | World Community Grid | project suspended by user
Thu 30 Apr 2020 18:51:26 BST | | [work_fetch] Request work fetch: project suspended
Thu 30 Apr 2020 18:51:30 BST | | choose_project(): 1588269090.392667
Thu 30 Apr 2020 18:51:30 BST | | [work_fetch] ------- start work fetch state -------
Thu 30 Apr 2020 18:51:30 BST | | [work_fetch] target work buffer: 17280.00 + 17280.00 sec
Thu 30 Apr 2020 18:51:30 BST | | [work_fetch] --- project states ---
Thu 30 Apr 2020 18:51:30 BST | climateprediction.net | [work_fetch] REC 539.980 prio -1.000 can request work
Thu 30 Apr 2020 18:51:30 BST | Rosetta@home | [work_fetch] REC 5007.641 prio -0.308 can't request work: suspended via Manager
Thu 30 Apr 2020 18:51:30 BST | World Community Grid | [work_fetch] REC 6264.280 prio -0.256 can't request work: suspended via Manager
Thu 30 Apr 2020 18:51:30 BST | | [work_fetch] --- state for CPU ---
Thu 30 Apr 2020 18:51:30 BST | | [work_fetch] shortfall 414720.00 nidle 12.00 saturated 0.00 busy 0.00
Thu 30 Apr 2020 18:51:30 BST | climateprediction.net | [work_fetch] share 1.000
Thu 30 Apr 2020 18:51:30 BST | Rosetta@home | [work_fetch] share 0.000
Thu 30 Apr 2020 18:51:30 BST | World Community Grid | [work_fetch] share 0.000
Thu 30 Apr 2020 18:51:30 BST | | [work_fetch] ------- end work fetch state -------
Thu 30 Apr 2020 18:51:30 BST | World Community Grid | choose_project: scanning
Thu 30 Apr 2020 18:51:30 BST | World Community Grid | skip: suspended via Manager
Thu 30 Apr 2020 18:51:30 BST | Rosetta@home | choose_project: scanning
Thu 30 Apr 2020 18:51:30 BST | Rosetta@home | skip: suspended via Manager
Thu 30 Apr 2020 18:51:30 BST | climateprediction.net | choose_project: scanning
Thu 30 Apr 2020 18:51:30 BST | climateprediction.net | can fetch CPU
Thu 30 Apr 2020 18:51:30 BST | climateprediction.net | CPU needs work - buffer low
Thu 30 Apr 2020 18:51:30 BST | climateprediction.net | checking CPU
Thu 30 Apr 2020 18:51:30 BST | climateprediction.net | [work_fetch] set_request() for CPU: ninst 12 nused_total 0.00 nidle_now 12.00 fetch share 1.00 req_inst 12.00 req_secs 414720.00
Thu 30 Apr 2020 18:51:30 BST | climateprediction.net | CPU set_request: 414720.000000
Thu 30 Apr 2020 18:51:30 BST | climateprediction.net | [work_fetch] request: CPU (414720.00 sec, 12.00 inst)
Thu 30 Apr 2020 18:51:30 BST | climateprediction.net | Sending scheduler request: To fetch work.
Thu 30 Apr 2020 18:51:30 BST | climateprediction.net | Requesting new tasks for CPU
Thu 30 Apr 2020 18:51:33 BST | climateprediction.net | Scheduler request completed: got 0 new tasks
Thu 30 Apr 2020 18:51:33 BST | climateprediction.net | No tasks sent

Thu 30 Apr 2020 18:51:33 BST | climateprediction.net | Project requested delay of 3636 seconds
Thu 30 Apr 2020 18:51:33 BST | climateprediction.net | [work_fetch] backing off CPU 733 sec


To me this puts the problem squarely at the server end - I do not see anything extra I can achieve from here.
ID: 62376 · Report as offensive     Reply Quote
Les Bayliss
Volunteer moderator

Send message
Joined: 5 Sep 04
Posts: 7629
Credit: 24,240,330
RAC: 0
Message 62377 - Posted: 30 Apr 2020, 21:44:04 UTC
Last modified: 30 Apr 2020, 21:45:14 UTC

Something seems to have happened at the project a few months ago.
I finally got 1 task to download on a new AMD machine, then nothing more.
Soon after, it worked perfectly for several hundred test models on the test site, but still nothing from the main site.
Upgrading an Intel machine to a newer OS caused it to stop working too.

I'm hoping that it's something about the BOINC version, and that someday I might get the inclination to have another try at getting an old BOINC version from the last computer, to put onto the others, but in the meantime, they're just gathering dust.
ID: 62377 · Report as offensive     Reply Quote
Harri Liljeroos
Avatar

Send message
Joined: 9 Dec 05
Posts: 110
Credit: 12,038,780
RAC: 1,393
Message 62378 - Posted: 30 Apr 2020, 22:13:06 UTC
Last modified: 30 Apr 2020, 22:15:46 UTC

There has been some changes as the server status page has a different layout now and the cakebox graphics don't understand the tables for tasks in progress for different sub-projects.
ID: 62378 · Report as offensive     Reply Quote
alanb1951

Send message
Joined: 31 Aug 04
Posts: 32
Credit: 9,526,696
RAC: 109,831
Message 62381 - Posted: 1 May 2020, 7:02:44 UTC - in response to Message 62378.  
Last modified: 1 May 2020, 7:10:49 UTC

Although it probably won't help Bryn Mawr solve the problem, I thought I'd post my observations on how fetching from CPDN has worked recently.

I have two Linux machines that request CPDN tasks on occasion. I use app_config.xml to divide the work-load as I require, and set CPDN to a lower resource share to reflect the relative workloads wanted, but whenever a necessary CPDN work fetch takes place it will try to fetch enough tasks to have one for each "CPU" BOINC has access to! From that, it would appear that the only part of the request that is of relevance to the CPDN server is the inst value!

To ensure I only get as many tasks as I want my routine is usually as follows: suspend WCG (my only other CPU task source), reduce %age of CPUs to use to match the number of CPDN tasks I want on the machine, allow CPDN to get work then update CPDN - it will fetch just enough tasks to make up the numbers - then set CPDN back to "No New Tasks" to avoid future unwanted fetches, restore the original %age of CPUs and resume WCG!

I had last observed this on 25th April when I forgot to follow my usual CPDN fetch routine on my i7-7700K (BOINC is allowed 5 "CPUs" for CPU work [there's a GPU too...] and I only run 1 CPDN task at a time, so I try for two tasks at any one time...) and when it ran out of tasks it fetched 5 new ones because I hadn't put No New Tasks on previously!

However, as there seems to be a suggestion that this might be a recent change, I have just allowed my other machine (a Ryzen 3700X, with 13 of the 16 "CPUs" allowed to BOINC (and CPDN restricted to two)) to get more work; it had 2 running and 4 waiting [already more than I really wanted, but never mind...], so I paused WCG, set CPUs to 50% and allowed CPDN to fetch - it got two tasks as I expected (and the request was as shown below...)

Fri 01 May 2020 06:43:36 BST | climateprediction.net | [work_fetch] set_request() for CPU: ninst 8 nused_total 6.00 nidle_now 2.00 fetch share 1.00 req_inst 2.00 req_secs 86400.00
Fri 01 May 2020 06:43:36 BST | climateprediction.net | [work_fetch] request: CPU (86400.00 sec, 2.00 inst) NVIDIA GPU (0.00 sec, 0.00 inst)

Fri 01 May 2020 06:43:36 BST | climateprediction.net | Sending scheduler request: To fetch work.
Fri 01 May 2020 06:43:36 BST | climateprediction.net | Requesting new tasks for CPU
Fri 01 May 2020 06:43:42 BST | climateprediction.net | Scheduler request completed: got 2 new tasks

Note that I have my cache control set to 0.45 + 0.05 days so it asked for 1 day of work, (The Ryzen usually takes just over 7 days to do one of these, so if it were paying any attention to that it wouldn't send anything!) Note also there's a GPU, but I doubt that's making any difference to the actual request.

Pursuant to Les's comment about older clients, and other things that might come into play, my Ryzen is on XUbuntu 18.04.04 with a 5.3 kernel and uses BOINC client 7.9.3 (I didn't want the version available from Gianfranco's repository when I set it up), and the Intel box is on an earlier 18.04 with client 7.14.2.

So, as I said, probably not helpful for Bryn Mawr but it is a "data point"... (and perhaps a marker to try a different client?)

Good luck - Al.

[Edited to add some (obvious?) steps I'd forgotten to list...]
ID: 62381 · Report as offensive     Reply Quote
Bryn Mawr

Send message
Joined: 28 Jul 19
Posts: 147
Credit: 12,814,088
RAC: 261,385
Message 62382 - Posted: 1 May 2020, 11:23:45 UTC

Thanks for that Alan, another data point is always useful.

A separate symptom that might, at a stretch, be related? Normally I can find the results of the weekly credit run on Thursday morning and it hits BAM on Friday morning. So far this week I still cannot see these results - is there a problem?
ID: 62382 · Report as offensive     Reply Quote
Profile Dave Jackson
Volunteer moderator

Send message
Joined: 15 May 09
Posts: 4314
Credit: 16,378,503
RAC: 3,632
Message 62383 - Posted: 1 May 2020, 11:39:27 UTC

Pursuant to Les's comment about older clients, and other things that might come into play, my Ryzen is on XUbuntu 18.04.04 with a 5.3 kernel and uses BOINC client 7.9.3 (I didn't want the version available from Gianfranco's repository when I set it up), and the Intel box is on an earlier 18.04 with client 7.14.2.


I haven't used Gianferanco's repository recently but have 7.16.3 (home compiled) on one machine and 7.17.0 also compiled from source downloaded from Git-hub without issues. I really don't know what is going on and have run out of ideas but suspect it isn't as simple as something to do with the BOINC version. If it were, I suspect I would have seen more posts about similar problems over at the BOINC forums.
ID: 62383 · Report as offensive     Reply Quote
Bryn Mawr

Send message
Joined: 28 Jul 19
Posts: 147
Credit: 12,814,088
RAC: 261,385
Message 62384 - Posted: 1 May 2020, 11:58:15 UTC - in response to Message 62383.  

Pursuant to Les's comment about older clients, and other things that might come into play, my Ryzen is on XUbuntu 18.04.04 with a 5.3 kernel and uses BOINC client 7.9.3 (I didn't want the version available from Gianfranco's repository when I set it up), and the Intel box is on an earlier 18.04 with client 7.14.2.


I haven't used Gianferanco's repository recently but have 7.16.3 (home compiled) on one machine and 7.17.0 also compiled from source downloaded from Git-hub without issues. I really don't know what is going on and have run out of ideas but suspect it isn't as simple as something to do with the BOINC version. If it were, I suspect I would have seen more posts about similar problems over at the BOINC forums.


My system is using Gianfranco’s version (I’m convinced that it was showing 7.17.0 at one point but it’s 7.16.6 now) but I’ve convinced myself it has to be server side rather than the client - but then, I’m Jon Snow and I know nothing :-)
ID: 62384 · Report as offensive     Reply Quote
Jim1348

Send message
Joined: 15 Jan 06
Posts: 637
Credit: 26,751,529
RAC: 653
Message 62385 - Posted: 1 May 2020, 12:10:34 UTC - in response to Message 62384.  

My system is using Gianfranco’s version (I’m convinced that it was showing 7.17.0 at one point but it’s 7.16.6 now) but I’ve convinced myself it has to be server side rather than the client - but then, I’m Jon Snow and I know nothing :-)

Same for me. All my machines are now up to 7.16.6 and working fine.
I think your idea about the server is right. It seems to me that I have had problems in the past getting the work going.
Just leave it attached and it will show up one of these days.
ID: 62385 · Report as offensive     Reply Quote
Profile geophi
Volunteer moderator

Send message
Joined: 7 Aug 04
Posts: 2167
Credit: 64,403,322
RAC: 5,085
Message 62387 - Posted: 1 May 2020, 19:24:37 UTC - in response to Message 62382.  

A separate symptom that might, at a stretch, be related? Normally I can find the results of the weekly credit run on Thursday morning and it hits BAM on Friday morning. So far this week I still cannot see these results - is there a problem?

Sometimes a script crashes, or doesn't get restarted after a server reboot. I e-mailed Andy about the credit thing.
ID: 62387 · Report as offensive     Reply Quote
Profile Dave Jackson
Volunteer moderator

Send message
Joined: 15 May 09
Posts: 4314
Credit: 16,378,503
RAC: 3,632
Message 62388 - Posted: 1 May 2020, 20:00:33 UTC - in response to Message 62384.  
Last modified: 1 May 2020, 20:59:59 UTC

My system is using Gianfranco’s version (I’m convinced that it was showing 7.17.0 at one point but it’s 7.16.6 now) but I’ve convinced myself it has to be server side rather than the client - but then, I’m Jon Snow and I know nothing :-)


I can confirm that Gianfranco's version was using 7.17.0 at one point, I think before a decent 7.16.x was released. There was some discussion about it over on the BOINC forums.

Edit 7.17 is the testing branch indicated by the 17 being an odd number Gianfranco will use the testing branch if he thinks it is has few enough bugs to be worth using over the current official release. This means that 7.17.0 that I am using from the code latest version of the master branch will almost certainly have different bugs in it compared to the one Gianfranco was using. (I haven't found any yet but haven't done any checking other than continuing to crunch, download work and upload some zips and would be a little surprised if I could find bugs without stressing and investigating a little more deeply.)
ID: 62388 · Report as offensive     Reply Quote
Profile geophi
Volunteer moderator

Send message
Joined: 7 Aug 04
Posts: 2167
Credit: 64,403,322
RAC: 5,085
Message 62391 - Posted: 3 May 2020, 19:08:58 UTC - in response to Message 62387.  

A separate symptom that might, at a stretch, be related? Normally I can find the results of the weekly credit run on Thursday morning and it hits BAM on Friday morning. So far this week I still cannot see these results - is there a problem?

Sometimes a script crashes, or doesn't get restarted after a server reboot. I e-mailed Andy about the credit thing.

Looks like the credit script ran in the last day. Stats should be updated on cpdn now. Not sure when the credit sites pick up that stats from cpdn.
ID: 62391 · Report as offensive     Reply Quote
Bryn Mawr

Send message
Joined: 28 Jul 19
Posts: 147
Credit: 12,814,088
RAC: 261,385
Message 62392 - Posted: 3 May 2020, 20:49:49 UTC - in response to Message 62391.  

A separate symptom that might, at a stretch, be related? Normally I can find the results of the weekly credit run on Thursday morning and it hits BAM on Friday morning. So far this week I still cannot see these results - is there a problem?

Sometimes a script crashes, or doesn't get restarted after a server reboot. I e-mailed Andy about the credit thing.

Looks like the credit script ran in the last day. Stats should be updated on cpdn now. Not sure when the credit sites pick up that stats from cpdn.


Normally cpdn updates on Thursday morning and bam gets the data on Friday afternoon so it could be tomorrow or Tuesday depending on cut-offs.

Many thanks for sorting it.
ID: 62392 · Report as offensive     Reply Quote
Bryn Mawr

Send message
Joined: 28 Jul 19
Posts: 147
Credit: 12,814,088
RAC: 261,385
Message 62490 - Posted: 24 May 2020, 18:26:47 UTC

OK, can I come back to this problem?
Having done everything I can think of including disconnecting from the project, rebooting and then reconnecting I had a last try this evening with different results that could point to a client side problem.

Firstly I suspended all projects, changed by buffers to 10+10 and turned on work fetch logging. At this point I noticed that climate prediction was subject to a resource backoff of 5159.17 seconds (this did not show up under the projects page in the resource manager) so I did a project reset. This zeroed the resource backoff so I proceeded to resume climate prediction to allow it to request work. It decided that it could request work and requested 5184000 seconds but the number of instances requested was 0, despite the number of idle cores being 12. Unsurprisingly it got what it asked for, 0 instances :-

Sun 24 May 2020 19:01:48 BST | Rosetta@home | project suspended by user
Sun 24 May 2020 19:01:48 BST | World Community Grid | project suspended by user
Sun 24 May 2020 19:01:48 BST | climateprediction.net | project suspended by user
Sun 24 May 2020 19:02:11 BST | World Community Grid | General prefs: from World Community Grid (last modified 30-Apr-2020 19:22:12)
Sun 24 May 2020 19:02:11 BST | World Community Grid | Computer location: school
Sun 24 May 2020 19:02:11 BST | | General prefs: using separate prefs for school
Sun 24 May 2020 19:02:11 BST | | Reading preferences override file
Sun 24 May 2020 19:02:11 BST | | Preferences:
Sun 24 May 2020 19:02:11 BST | | max memory usage when active: 14445.46 MB
Sun 24 May 2020 19:02:11 BST | | max memory usage when idle: 15247.99 MB
Sun 24 May 2020 19:02:11 BST | | max disk usage: 82.36 GB
Sun 24 May 2020 19:02:11 BST | | suspend work if non-BOINC CPU load exceeds 75%
Sun 24 May 2020 19:02:11 BST | | (to change preferences, visit a project web site or select Preferences in the Manager)
Sun 24 May 2020 19:02:24 BST | | Re-reading cc_config.xml
Sun 24 May 2020 19:02:24 BST | | Config: GUI RPC allowed from any host
Sun 24 May 2020 19:02:24 BST | | Config: GUI RPCs allowed from:
Sun 24 May 2020 19:02:24 BST | | log flags: file_xfer, sched_ops, task, work_fetch_debug
Sun 24 May 2020 19:02:24 BST | climateprediction.net | Found app_config.xml
Sun 24 May 2020 19:02:24 BST | | [work_fetch] Request work fetch: Core client configuration
Sun 24 May 2020 19:02:29 BST | | choose_project(): 1590343349.519837
Sun 24 May 2020 19:02:29 BST | | [work_fetch] ------- start work fetch state -------
Sun 24 May 2020 19:02:29 BST | | [work_fetch] target work buffer: 864000.00 + 864000.00 sec
Sun 24 May 2020 19:02:29 BST | | [work_fetch] --- project states ---
Sun 24 May 2020 19:02:29 BST | climateprediction.net | [work_fetch] REC 0.000 prio 0.000 can't request work: suspended via Manager
Sun 24 May 2020 19:02:29 BST | Rosetta@home | [work_fetch] REC 5242.605 prio -0.005 can't request work: suspended via Manager
Sun 24 May 2020 19:02:29 BST | World Community Grid | [work_fetch] REC 6547.688 prio -0.003 can't request work: suspended via Manager
Sun 24 May 2020 19:02:29 BST | | [work_fetch] --- state for CPU ---
Sun 24 May 2020 19:02:29 BST | | [work_fetch] shortfall 20736000.00 nidle 12.00 saturated 0.00 busy 0.00
Sun 24 May 2020 19:02:29 BST | climateprediction.net | [work_fetch] share 0.000 project is backed off (resource backoff: 5159.17, inc 9600.00)
Sun 24 May 2020 19:02:29 BST | Rosetta@home | [work_fetch] share 0.000
Sun 24 May 2020 19:02:29 BST | World Community Grid | [work_fetch] share 0.000
Sun 24 May 2020 19:02:29 BST | | [work_fetch] ------- end work fetch state -------
Sun 24 May 2020 19:02:29 BST | climateprediction.net | choose_project: scanning
Sun 24 May 2020 19:02:29 BST | climateprediction.net | skip: suspended via Manager
Sun 24 May 2020 19:02:29 BST | World Community Grid | choose_project: scanning
Sun 24 May 2020 19:02:29 BST | World Community Grid | skip: suspended via Manager
Sun 24 May 2020 19:02:29 BST | Rosetta@home | choose_project: scanning
Sun 24 May 2020 19:02:29 BST | Rosetta@home | skip: suspended via Manager
Sun 24 May 2020 19:02:29 BST | | [work_fetch] No project chosen for work fetch
Sun 24 May 2020 19:03:07 BST | | [work_fetch] Request work fetch: project reset by user
Sun 24 May 2020 19:03:07 BST | climateprediction.net | Resetting project
Sun 24 May 2020 19:03:09 BST | | choose_project(): 1590343389.792348
Sun 24 May 2020 19:03:09 BST | | [work_fetch] ------- start work fetch state -------
Sun 24 May 2020 19:03:09 BST | | [work_fetch] target work buffer: 864000.00 + 864000.00 sec
Sun 24 May 2020 19:03:09 BST | | [work_fetch] --- project states ---
Sun 24 May 2020 19:03:09 BST | climateprediction.net | [work_fetch] REC 0.000 prio 0.000 can't request work: suspended via Manager
Sun 24 May 2020 19:03:09 BST | Rosetta@home | [work_fetch] REC 5240.785 prio -0.005 can't request work: suspended via Manager
Sun 24 May 2020 19:03:09 BST | World Community Grid | [work_fetch] REC 6545.416 prio -0.003 can't request work: suspended via Manager
Sun 24 May 2020 19:03:09 BST | | [work_fetch] --- state for CPU ---
Sun 24 May 2020 19:03:09 BST | | [work_fetch] shortfall 20736000.00 nidle 12.00 saturated 0.00 busy 0.00
Sun 24 May 2020 19:03:09 BST | climateprediction.net | [work_fetch] share 0.000
Sun 24 May 2020 19:03:09 BST | Rosetta@home | [work_fetch] share 0.000
Sun 24 May 2020 19:03:09 BST | World Community Grid | [work_fetch] share 0.000
Sun 24 May 2020 19:03:09 BST | | [work_fetch] ------- end work fetch state -------
Sun 24 May 2020 19:03:09 BST | climateprediction.net | choose_project: scanning
Sun 24 May 2020 19:03:09 BST | climateprediction.net | skip: suspended via Manager
Sun 24 May 2020 19:03:09 BST | World Community Grid | choose_project: scanning
Sun 24 May 2020 19:03:09 BST | World Community Grid | skip: suspended via Manager
Sun 24 May 2020 19:03:09 BST | Rosetta@home | choose_project: scanning
Sun 24 May 2020 19:03:09 BST | Rosetta@home | skip: suspended via Manager
Sun 24 May 2020 19:03:09 BST | | [work_fetch] No project chosen for work fetch
Sun 24 May 2020 19:03:34 BST | | [work_fetch] Request work fetch: project reset by user
Sun 24 May 2020 19:03:34 BST | climateprediction.net | Resetting project
Sun 24 May 2020 19:03:34 BST | | choose_project(): 1590343414.953606
Sun 24 May 2020 19:03:34 BST | | [work_fetch] ------- start work fetch state -------
Sun 24 May 2020 19:03:34 BST | | [work_fetch] target work buffer: 864000.00 + 864000.00 sec
Sun 24 May 2020 19:03:34 BST | | [work_fetch] --- project states ---
Sun 24 May 2020 19:03:34 BST | climateprediction.net | [work_fetch] REC 0.000 prio 0.000 can't request work: suspended via Manager
Sun 24 May 2020 19:03:34 BST | Rosetta@home | [work_fetch] REC 5239.685 prio -0.005 can't request work: suspended via Manager
Sun 24 May 2020 19:03:34 BST | World Community Grid | [work_fetch] REC 6544.041 prio -0.003 can't request work: suspended via Manager
Sun 24 May 2020 19:03:34 BST | | [work_fetch] --- state for CPU ---
Sun 24 May 2020 19:03:34 BST | | [work_fetch] shortfall 20736000.00 nidle 12.00 saturated 0.00 busy 0.00
Sun 24 May 2020 19:03:34 BST | climateprediction.net | [work_fetch] share 0.000
Sun 24 May 2020 19:03:34 BST | Rosetta@home | [work_fetch] share 0.000
Sun 24 May 2020 19:03:34 BST | World Community Grid | [work_fetch] share 0.000
Sun 24 May 2020 19:03:34 BST | | [work_fetch] ------- end work fetch state -------
Sun 24 May 2020 19:03:34 BST | climateprediction.net | choose_project: scanning
Sun 24 May 2020 19:03:34 BST | climateprediction.net | skip: suspended via Manager
Sun 24 May 2020 19:03:34 BST | World Community Grid | choose_project: scanning
Sun 24 May 2020 19:03:34 BST | World Community Grid | skip: suspended via Manager
Sun 24 May 2020 19:03:34 BST | Rosetta@home | choose_project: scanning
Sun 24 May 2020 19:03:34 BST | Rosetta@home | skip: suspended via Manager
Sun 24 May 2020 19:03:34 BST | | [work_fetch] No project chosen for work fetch
Sun 24 May 2020 19:03:56 BST | climateprediction.net | project resumed by user
Sun 24 May 2020 19:03:56 BST | | [work_fetch] Request work fetch: project resumed
Sun 24 May 2020 19:04:00 BST | | choose_project(): 1590343440.066158
Sun 24 May 2020 19:04:00 BST | | [work_fetch] ------- start work fetch state -------
Sun 24 May 2020 19:04:00 BST | | [work_fetch] target work buffer: 864000.00 + 864000.00 sec
Sun 24 May 2020 19:04:00 BST | | [work_fetch] --- project states ---
Sun 24 May 2020 19:04:00 BST | climateprediction.net | [work_fetch] REC 0.000 prio -0.000 can request work
Sun 24 May 2020 19:04:00 BST | Rosetta@home | [work_fetch] REC 5238.756 prio -0.005 can't request work: suspended via Manager
Sun 24 May 2020 19:04:00 BST | World Community Grid | [work_fetch] REC 6542.881 prio -0.003 can't request work: suspended via Manager
Sun 24 May 2020 19:04:00 BST | | [work_fetch] --- state for CPU ---
Sun 24 May 2020 19:04:00 BST | | [work_fetch] shortfall 20736000.00 nidle 12.00 saturated 0.00 busy 0.00
Sun 24 May 2020 19:04:00 BST | climateprediction.net | [work_fetch] share 1.000
Sun 24 May 2020 19:04:00 BST | Rosetta@home | [work_fetch] share 0.000
Sun 24 May 2020 19:04:00 BST | World Community Grid | [work_fetch] share 0.000
Sun 24 May 2020 19:04:00 BST | | [work_fetch] ------- end work fetch state -------
Sun 24 May 2020 19:04:00 BST | climateprediction.net | choose_project: scanning
Sun 24 May 2020 19:04:00 BST | climateprediction.net | can fetch CPU
Sun 24 May 2020 19:04:00 BST | climateprediction.net | CPU needs work - buffer low
Sun 24 May 2020 19:04:00 BST | climateprediction.net | checking CPU
Sun 24 May 2020 19:04:00 BST | climateprediction.net | [work_fetch] using MC shortfall 5184000.000000 instead of shortfall 20736000.000000
Sun 24 May 2020 19:04:00 BST | climateprediction.net | [work_fetch] set_request() for CPU: ninst 12 nused_total 0.00 nidle_now 12.00 fetch share 1.00 req_inst 0.00 req_secs 5184000.00
Sun 24 May 2020 19:04:00 BST | climateprediction.net | CPU set_request: 5184000.000000
Sun 24 May 2020 19:04:04 BST | climateprediction.net | Master file download succeeded
Sun 24 May 2020 19:04:04 BST | | [work_fetch] Request work fetch: Master fetch complete
Sun 24 May 2020 19:04:09 BST | | choose_project(): 1590343449.109191
Sun 24 May 2020 19:04:09 BST | | [work_fetch] ------- start work fetch state -------
Sun 24 May 2020 19:04:09 BST | | [work_fetch] target work buffer: 864000.00 + 864000.00 sec
Sun 24 May 2020 19:04:09 BST | | [work_fetch] --- project states ---
Sun 24 May 2020 19:04:09 BST | climateprediction.net | [work_fetch] REC 0.000 prio -0.000 can request work
Sun 24 May 2020 19:04:09 BST | Rosetta@home | [work_fetch] REC 5238.756 prio -0.005 can't request work: suspended via Manager
Sun 24 May 2020 19:04:09 BST | World Community Grid | [work_fetch] REC 6542.881 prio -0.003 can't request work: suspended via Manager
Sun 24 May 2020 19:04:09 BST | | [work_fetch] --- state for CPU ---
Sun 24 May 2020 19:04:09 BST | | [work_fetch] shortfall 20736000.00 nidle 12.00 saturated 0.00 busy 0.00
Sun 24 May 2020 19:04:09 BST | climateprediction.net | [work_fetch] share 1.000
Sun 24 May 2020 19:04:09 BST | Rosetta@home | [work_fetch] share 0.000
Sun 24 May 2020 19:04:09 BST | World Community Grid | [work_fetch] share 0.000
Sun 24 May 2020 19:04:09 BST | | [work_fetch] ------- end work fetch state -------
Sun 24 May 2020 19:04:09 BST | climateprediction.net | choose_project: scanning
Sun 24 May 2020 19:04:09 BST | climateprediction.net | can fetch CPU
Sun 24 May 2020 19:04:09 BST | climateprediction.net | CPU needs work - buffer low
Sun 24 May 2020 19:04:09 BST | climateprediction.net | checking CPU
Sun 24 May 2020 19:04:09 BST | climateprediction.net | [work_fetch] using MC shortfall 5184000.000000 instead of shortfall 20736000.000000
Sun 24 May 2020 19:04:09 BST | climateprediction.net | [work_fetch] set_request() for CPU: ninst 12 nused_total 0.00 nidle_now 12.00 fetch share 1.00 req_inst 0.00 req_secs 5184000.00
Sun 24 May 2020 19:04:09 BST | climateprediction.net | CPU set_request: 5184000.000000
Sun 24 May 2020 19:04:09 BST | climateprediction.net | [work_fetch] request: CPU (5184000.00 sec, 0.00 inst)
Sun 24 May 2020 19:04:09 BST | climateprediction.net | Sending scheduler request: To fetch work.
Sun 24 May 2020 19:04:09 BST | climateprediction.net | Requesting new tasks for CPU
Sun 24 May 2020 19:04:13 BST | climateprediction.net | Scheduler request completed: got 0 new tasks
Sun 24 May 2020 19:04:13 BST | climateprediction.net | No tasks sent
Sun 24 May 2020 19:04:13 BST | climateprediction.net | Project requested delay of 3636 seconds
Sun 24 May 2020 19:04:13 BST | climateprediction.net | [work_fetch] backing off CPU 722 sec
Sun 24 May 2020 19:04:13 BST | | [work_fetch] Request work fetch: RPC complete
Sun 24 May 2020 19:04:18 BST | | choose_project(): 1590343458.184406
Sun 24 May 2020 19:04:18 BST | | [work_fetch] ------- start work fetch state -------
Sun 24 May 2020 19:04:18 BST | | [work_fetch] target work buffer: 864000.00 + 864000.00 sec
Sun 24 May 2020 19:04:18 BST | | [work_fetch] --- project states ---
Sun 24 May 2020 19:04:18 BST | climateprediction.net | [work_fetch] REC 0.000 prio 0.000 can't request work: scheduler RPC backoff (3630.98 sec)
Sun 24 May 2020 19:04:18 BST | Rosetta@home | [work_fetch] REC 5238.756 prio -0.005 can't request work: suspended via Manager
Sun 24 May 2020 19:04:18 BST | World Community Grid | [work_fetch] REC 6542.881 prio -0.003 can't request work: suspended via Manager
Sun 24 May 2020 19:04:18 BST | | [work_fetch] --- state for CPU ---
Sun 24 May 2020 19:04:18 BST | | [work_fetch] shortfall 20736000.00 nidle 12.00 saturated 0.00 busy 0.00
Sun 24 May 2020 19:04:18 BST | climateprediction.net | [work_fetch] share 0.000 project is backed off (resource backoff: 717.33, inc 600.00)
Sun 24 May 2020 19:04:18 BST | Rosetta@home | [work_fetch] share 0.000
Sun 24 May 2020 19:04:18 BST | World Community Grid | [work_fetch] share 0.000
Sun 24 May 2020 19:04:18 BST | | [work_fetch] ------- end work fetch state -------
Sun 24 May 2020 19:04:18 BST | climateprediction.net | choose_project: scanning
Sun 24 May 2020 19:04:18 BST | climateprediction.net | skip: scheduler RPC backoff
Sun 24 May 2020 19:04:18 BST | World Community Grid | choose_project: scanning
Sun 24 May 2020 19:04:18 BST | World Community Grid | skip: suspended via Manager
Sun 24 May 2020 19:04:18 BST | Rosetta@home | choose_project: scanning
Sun 24 May 2020 19:04:18 BST | Rosetta@home | skip: suspended via Manager
Sun 24 May 2020 19:04:18 BST | | [work_fetch] No project chosen for work fetch
Sun 24 May 2020 19:05:18 BST | | choose_project(): 1590343518.442208
Sun 24 May 2020 19:05:18 BST | | [work_fetch] ------- start work fetch state -------
Sun 24 May 2020 19:05:18 BST | | [work_fetch] target work buffer: 864000.00 + 864000.00 sec
Sun 24 May 2020 19:05:18 BST | | [work_fetch] --- project states ---
Sun 24 May 2020 19:05:18 BST | climateprediction.net | [work_fetch] REC 0.000 prio 0.000 can't request work: scheduler RPC backoff (3570.72 sec)
Sun 24 May 2020 19:05:18 BST | Rosetta@home | [work_fetch] REC 5236.223 prio -0.005 can't request work: suspended via Manager
Sun 24 May 2020 19:05:18 BST | World Community Grid | [work_fetch] REC 6539.717 prio -0.003 can't request work: suspended via Manager
Sun 24 May 2020 19:05:18 BST | | [work_fetch] --- state for CPU ---
Sun 24 May 2020 19:05:18 BST | | [work_fetch] shortfall 20736000.00 nidle 12.00 saturated 0.00 busy 0.00
Sun 24 May 2020 19:05:18 BST | climateprediction.net | [work_fetch] share 0.000 project is backed off (resource backoff: 657.08, inc 600.00)
Sun 24 May 2020 19:05:18 BST | Rosetta@home | [work_fetch] share 0.000
Sun 24 May 2020 19:05:18 BST | World Community Grid | [work_fetch] share 0.000
Sun 24 May 2020 19:05:18 BST | | [work_fetch] ------- end work fetch state -------
Sun 24 May 2020 19:05:18 BST | climateprediction.net | choose_project: scanning
Sun 24 May 2020 19:05:18 BST | climateprediction.net | skip: scheduler RPC backoff
Sun 24 May 2020 19:05:18 BST | World Community Grid | choose_project: scanning
Sun 24 May 2020 19:05:18 BST | World Community Grid | skip: suspended via Manager
Sun 24 May 2020 19:05:18 BST | Rosetta@home | choose_project: scanning
Sun 24 May 2020 19:05:18 BST | Rosetta@home | skip: suspended via Manager
Sun 24 May 2020 19:05:18 BST | | [work_fetch] No project chosen for work fetch
Sun 24 May 2020 19:05:30 BST | | Re-reading cc_config.xml
Sun 24 May 2020 19:05:30 BST | | Config: GUI RPC allowed from any host
Sun 24 May 2020 19:05:30 BST | | Config: GUI RPCs allowed from:
Sun 24 May 2020 19:05:30 BST | | log flags: file_xfer, sched_ops, task
Sun 24 May 2020 19:05:30 BST | climateprediction.net | Found app_config.xml
Sun 24 May 2020 19:05:50 BST | World Community Grid | General prefs: from World Community Grid (last modified 30-Apr-2020 19:22:12)
Sun 24 May 2020 19:05:50 BST | World Community Grid | Computer location: school
Sun 24 May 2020 19:05:50 BST | | General prefs: using separate prefs for school
Sun 24 May 2020 19:05:50 BST | | Reading preferences override file
Sun 24 May 2020 19:05:50 BST | | Preferences:
Sun 24 May 2020 19:05:50 BST | | max memory usage when active: 14445.46 MB
Sun 24 May 2020 19:05:50 BST | | max memory usage when idle: 15247.99 MB
Sun 24 May 2020 19:05:50 BST | | max disk usage: 82.37 GB
Sun 24 May 2020 19:05:50 BST | | suspend work if non-BOINC CPU load exceeds 75%
Sun 24 May 2020 19:05:50 BST | | (to change preferences, visit a project web site or select Preferences in the Manager)
Sun 24 May 2020 19:06:22 BST | Rosetta@home | project resumed by user
Sun 24 May 2020 19:06:22 BST | World Community Grid | project resumed by user


Once again, any suggestions would be greatly appreciated.
ID: 62490 · Report as offensive     Reply Quote
Profile Dave Jackson
Volunteer moderator

Send message
Joined: 15 May 09
Posts: 4314
Credit: 16,378,503
RAC: 3,632
Message 62494 - Posted: 25 May 2020, 5:10:37 UTC

Still not spotting what the problem is. Next time you post from the event log it may be worth first clicking on one of the Climateprediction.net messages and then at the bottom right of the event log click on "Show only this Project."

It may not help us to spot the problem but I have certainly found it easier on my ageing eyes looking for stuff without the other projects' messages there to filter out with my brain.
ID: 62494 · Report as offensive     Reply Quote
Bryn Mawr

Send message
Joined: 28 Jul 19
Posts: 147
Credit: 12,814,088
RAC: 261,385
Message 62495 - Posted: 25 May 2020, 6:14:42 UTC - in response to Message 62494.  

Still not spotting what the problem is. Next time you post from the event log it may be worth first clicking on one of the Climateprediction.net messages and then at the bottom right of the event log click on "Show only this Project."

It may not help us to spot the problem but I have certainly found it easier on my ageing eyes looking for stuff without the other projects' messages there to filter out with my brain.


My sincere apologies, as the only thing that happened during that period was the work fetch I thought it might be relevant to show what was happening to the other projects as well but I’ll certainly make sure I do so in future.
ID: 62495 · Report as offensive     Reply Quote
Previous · 1 · 2

Message boards : Number crunching : Work available and being requested but none downloaded

©2024 climateprediction.net