won't finish in time
30 Jun 2009 17:59:43 UTC
Topic 194426
(moderation:
Sirs, sence I upgraded to ver. 6.6.36 I have had the following problem getting updates for Einstein:
6/30/2009 12:54:34 Starting BOINC client version 6.6.36 for windows_intelx86
6/30/2009 12:54:34 log flags: task, file_xfer, sched_ops
6/30/2009 12:54:34 Libraries: libcurl/7.19.4 OpenSSL/0.9.8j zlib/1.2.3
6/30/2009 12:54:34 Data directory: C:\ProgramData\BOINC
6/30/2009 12:54:34 Running under account Ron
6/30/2009 12:54:34 Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 CPU 2.80GHz [x86 Family 15 Model 4 Stepping 1]
6/30/2009 12:54:34 Processor features: fpu tsc pae nx sse sse2 pni mmx
6/30/2009 12:54:34 OS: Microsoft Windows Vista: Ultimate x86 Edition, Service Pack 1, (06.00.6001.00)
6/30/2009 12:54:34 Memory: 2.00 GB physical, 4.23 GB virtual
6/30/2009 12:54:34 Disk: 74.53 GB total, 13.38 GB free
6/30/2009 12:54:34 Local time is UTC -5 hours
6/30/2009 12:54:34 No CUDA devices found
6/30/2009 12:54:34 No coprocessors
6/30/2009 12:54:34 Not using a proxy
6/30/2009 12:54:34 climateprediction.net URL: http://climateprediction.net/; Computer ID: 812789; location: (none); project prefs: default
6/30/2009 12:54:34 Einstein@Home URL: http://einstein.phys.uwm.edu/; Computer ID: 714599; location: (none); project prefs: default
6/30/2009 12:54:34 SETI@home URL: http://setiathome.berkeley.edu/; Computer ID: 1932570; location: home; project prefs: default
6/30/2009 12:54:34 SETI@home General prefs: from SETI@home (last modified 22-Oct-2008 22:42:42)
6/30/2009 12:54:34 SETI@home Computer location: home
6/30/2009 12:54:34 SETI@home General prefs: no separate prefs for home; using your defaults
6/30/2009 12:54:34 Reading preferences override file
6/30/2009 12:54:34 Preferences limit memory usage when active to 1022.71MB
6/30/2009 12:54:34 Preferences limit memory usage when idle to 1840.87MB
6/30/2009 12:54:34 Preferences limit disk usage to 14.44GB
6/30/2009 12:54:34 SETI@home Restarting task 13dc08ac.10841.6616.4.8.216_0 using setiathome_enhanced version 603
6/30/2009 12:54:39 Einstein@Home Sending scheduler request: To fetch work.
6/30/2009 12:54:39 Einstein@Home Requesting new tasks
6/30/2009 12:54:44 Einstein@Home Scheduler request completed: got 0 new tasks
6/30/2009 12:54:44 Einstein@Home Message from server: No work sent
6/30/2009 12:54:44 Einstein@Home Message from server: (won't finish in time) BOINC runs 93.0% of time, computation enabled 100.0% of that
I have tried updating, reset project and even reinstalling. Can you help?
won't finish in time
)
According to the logs you got a new task. The reset must've done that.
RE: According to the logs
)
If it did, it isn't processing it. It keeps on trying to fetch work but is unable to, giving the same error.
6/30/2009 14:00:24 Einstein@Home Sending scheduler request: To fetch work.
6/30/2009 14:00:24 Einstein@Home Requesting new tasks
6/30/2009 14:00:29 Einstein@Home Scheduler request completed: got 0 new tasks
6/30/2009 14:00:29 Einstein@Home Message from server: No work sent
6/30/2009 14:00:29 Einstein@Home Message from server: (won't finish in time) BOINC runs 93.0% of time, computation enabled 100.0% of that
If you have no tasks in BOINC
)
If you have no tasks in BOINC manager's task list, then detach and reattach instead of resetting, because you have a ghost work unit, which only by a detach can be set free.
There have been several threads on the BOINC dev boards (see this one) to the effect that a downgrading could help, because it's a scheduling problem introduced with 6.6.36.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: because it's a
)
It happens on earlier versions as well, Gundolf, even on 5.10s. It's not a client problem, but a server problem. I'll be trying to get a correct log from malaria on this when they have work next week. Nicolas has already set the correct flag for that in the server config file, I'll let him know when to grab the log of my computer. (Hoping it still does it, of course. ;-))
Apropos, Einstein uses the resent lost task option, so a next reset of BOINC should just send the same file again. If that active_frac isn't in the way. And according to what the server gets in, it's only 99.9910% (active_frac 0.999910)