Not getting WU
3 Jun 2006 1:23:10 UTC
Topic 191306
(moderation:
This is what I'm getting. My other PC works fine.
6/1/2006 9:28:46 PM||Starting BOINC client version 4.45 for windows_intelx86
6/1/2006 9:28:46 PM||Data directory: C:\\Program Files\\BOINC
6/1/2006 9:28:47 PM|Einstein@Home|Computer ID: 401280; location: home; project prefs: default
6/1/2006 9:28:47 PM||General prefs: from unknown project http://setiathome.berkeley.edu/ (last modified 2005-07-05 11:23:52)
6/1/2006 9:28:47 PM||General prefs: no separate prefs for home; using your defaults
6/1/2006 9:28:47 PM||Remote control not allowed; using loopback address
6/1/2006 9:28:47 PM|Einstein@Home|Deferring communication with project for 2 days, 2 hours, 30 minutes, and 47 seconds
6/1/2006 9:28:47 PM||Insufficient work; requesting more
6/1/2006 9:51:32 PM||request_reschedule_cpus: project op
6/1/2006 9:51:35 PM||request_reschedule_cpus: project op
6/1/2006 10:28:48 PM|Einstein@Home|Deferring communication with project for 2 days, 1 hours, 30 minutes, and 46 seconds
6/1/2006 10:28:48 PM||Insufficient work; requesting more
6/1/2006 11:28:48 PM|Einstein@Home|Deferring communication with project for 2 days, 0 hours, 30 minutes, and 46 seconds
6/1/2006 11:28:48 PM||Insufficient work; requesting more
6/2/2006 12:28:48 AM|Einstein@Home|Deferring communication with project for 1 days, 23 hours, 30 minutes, and 45 seconds
6/2/2006 12:28:48 AM||Insufficient work; requesting more
6/2/2006 1:28:49 AM|Einstein@Home|Deferring communication with project for 1 days, 22 hours, 30 minutes, and 45 seconds
6/2/2006 1:28:49 AM||Insufficient work; requesting more
6/2/2006 2:28:49 AM|Einstein@Home|Deferring communication with project for 1 days, 21 hours, 30 minutes, and 44 seconds
6/2/2006 2:28:49 AM||Insufficient work; requesting more
6/2/2006 3:28:50 AM|Einstein@Home|Deferring communication with project for 1 days, 20 hours, 30 minutes, and 44 seconds
6/2/2006 3:28:50 AM||Insufficient work; requesting more
6/2/2006 4:28:50 AM|Einstein@Home|Deferring communication with project for 1 days, 19 hours, 30 minutes, and 44 seconds
6/2/2006 4:28:50 AM||Insufficient work; requesting more
6/2/2006 5:28:50 AM|Einstein@Home|Deferring communication with project for 1 days, 18 hours, 30 minutes, and 44 seconds
6/2/2006 5:28:50 AM||Insufficient work; requesting more
6/2/2006 6:28:50 AM|Einstein@Home|Deferring communication with project for 1 days, 17 hours, 30 minutes, and 43 seconds
6/2/2006 6:28:50 AM||Insufficient work; requesting more
6/2/2006 7:28:51 AM|Einstein@Home|Deferring communication with project for 1 days, 16 hours, 30 minutes, and 43 seconds
6/2/2006 7:28:51 AM||Insufficient work; requesting more
6/2/2006 8:28:52 AM|Einstein@Home|Deferring communication with project for 1 days, 15 hours, 30 minutes, and 42 seconds
6/2/2006 8:28:52 AM||Insufficient work; requesting more
6/2/2006 9:28:53 AM|Einstein@Home|Deferring communication with project for 1 days, 14 hours, 30 minutes, and 41 seconds
6/2/2006 9:28:53 AM||Insufficient work; requesting more
6/2/2006 10:28:54 AM|Einstein@Home|Deferring communication with project for 1 days, 13 hours, 30 minutes, and 40 seconds
6/2/2006 10:28:54 AM||Insufficient work; requesting more
6/2/2006 11:28:54 AM|Einstein@Home|Deferring communication with project for 1 days, 12 hours, 30 minutes, and 40 seconds
6/2/2006 11:28:54 AM||Insufficient work; requesting more
6/2/2006 12:28:54 PM|Einstein@Home|Deferring communication with project for 1 days, 11 hours, 30 minutes, and 40 seconds
6/2/2006 12:28:54 PM||Insufficient work; requesting more
6/2/2006 1:28:55 PM|Einstein@Home|Deferring communication with project for 1 days, 10 hours, 30 minutes, and 39 seconds
6/2/2006 1:28:55 PM||Insufficient work; requesting more
6/2/2006 2:28:55 PM|Einstein@Home|Deferring communication with project for 1 days, 9 hours, 30 minutes, and 38 seconds
6/2/2006 2:28:55 PM||Insufficient work; requesting more
6/2/2006 3:28:56 PM|Einstein@Home|Deferring communication with project for 1 days, 8 hours, 30 minutes, and 38 seconds
6/2/2006 3:28:56 PM||Insufficient work; requesting more
6/2/2006 4:00:37 PM||Suspending computation and network activity - running CPU benchmarks
6/2/2006 4:00:39 PM||Running CPU benchmarks
6/2/2006 4:01:36 PM||Benchmark results:
6/2/2006 4:01:36 PM|| Number of CPUs: 1
6/2/2006 4:01:36 PM|| 752 double precision MIPS (Whetstone) per CPU
6/2/2006 4:01:36 PM|| 1507 integer MIPS (Dhrystone) per CPU
6/2/2006 4:01:36 PM||Finished CPU benchmarks
6/2/2006 4:01:36 PM||Resuming computation and network activity
6/2/2006 4:01:36 PM||request_reschedule_cpus: Resuming activities
6/2/2006 4:28:57 PM|Einstein@Home|Deferring communication with project for 1 days, 7 hours, 30 minutes, and 37 seconds
6/2/2006 4:28:57 PM||Insufficient work; requesting more
6/2/2006 5:28:57 PM|Einstein@Home|Deferring communication with project for 1 days, 6 hours, 30 minutes, and 36 seconds
6/2/2006 5:28:57 PM||Insufficient work; requesting more
6/2/2006 6:28:58 PM|Einstein@Home|Deferring communication with project for 1 days, 5 hours, 30 minutes, and 35 seconds
6/2/2006 6:28:58 PM||Insufficient work; requesting more
6/2/2006 7:28:59 PM|Einstein@Home|Deferring communication with project for 1 days, 4 hours, 30 minutes, and 35 seconds
6/2/2006 7:28:59 PM||Insufficient work; requesting more
6/2/2006 8:28:59 PM|Einstein@Home|Deferring communication with project for 1 days, 3 hours, 30 minutes, and 34 seconds
6/2/2006 8:28:59 PM||Insufficient work; requesting more
6/2/2006 9:19:04 PM||Suspending computation and network activity - running CPU benchmarks
6/2/2006 9:19:06 PM||Running CPU benchmarks
Not getting WU
)
Try Updating to BOINC 5.4.9 from here.
Then if i still refuses to download naything give the messages from the Messages tab again.
I'm having the same problem
)
I'm having the same problem since the EAH system recovered from the May 28 problem. But my machine usually has 3 EAH jobs running so I don't know why it's requesting more work since the 3 jobs in progress when EAH went down are still reported as unfinished. Here's the report for one of them:
Name r1_1318.0__102_S4R2a_0
Workunit 8953027
Created 28 May 2006 3:00:34 UTC
Sent 28 May 2006 3:44:16 UTC
Received ---
Server state In Progress
Outcome Unknown
Client state New
Exit status 0 (0x0)
Computer ID 392906
Report deadline 11 Jun 2006 3:44:16 UTC
CPU time 0
stderr out
Validate state Initial
Claimed credit 0
Granted credit 0
application version ---
------------------------------------------------------------------------
They would normally be done by now.
--thelma
RE: I'm having the same
)
What’s the status of those WUs as shown in your BOINC manager? After the outage I noticed my systems had several completed ones sitting around, uploaded but not yet reported. Although one of my hosts still hasn’t made contact since before the outage, the others all did eventually. While I’m not sure what’s going on, it’s my impression that repeated failures to contact the scheduler can produce a long ‘back-off’ interval, so that even though up- and downloads have resumed, BOINC will wait quite some time—maybe until it’s got another completed result—before trying to report again. If my last system hasn’t checked in by Monday I’ll start to worry, but for now I’m assuming it’s just waiting for the right planetary alignment. ;)
RE: RE: I'm having the
)
I posted the status of one of those jobs: it claims to be unfinished--outcome = unknown, validate state = initial..
It seems to me that it's lost track of those jobs and hasn't really worked on them since coming up again.
--thelma
RE: I posted the status of
)
From the wording, that must come from the website, which only knows what’s been reported—it can’t tell whether a host has actually started or finished processing a particular task, only that it was assigned and downloaded. I was asking what they look like locally, on your system.
RE: RE: I posted the
)
Thanks. You must have been right that it would have shown differently locally, since it all had cleared the next time I looked. It's running smoothly again now.
--tthelma
RE: You must have been
)
Good to hear. They probably would have shown locally as “Sent� or “Ready to report�, so they’d been uploaded to the server but not yet reported for entry into the database—until just before you looked again.
I believe the reason it works this way is that I/O to the large & complex database tends to be a performance bottleneck (up- and downloading uses more bandwidth but can be handled by a rather ‘dumb’ server) so BOINC is set up to interact with it as little as possible. The result is that completed work can pile up for a while, until a ‘batch’ is reported all at once.