I'm not getting credits. My computer is on all the time. I routinely ask for updates, but I am showing no action on the statistics graph since 15 May. Don't know what's happening.
Check through the BOINC Manager and see if you have everything straight there, if you haven't already:
1. Click on your "Activity" button (very top row) and make sure nothing is suspended.
2. On your "Project" tab, see in the status section that it is not set on "Won't get new tasks" and/or "Suspended by user".
3. Through your "Message" tab, copy the messages and post them here as that may supply additional information to what the problem may be if 1 and 2 above are a washout.
Your one host hasn't contacted the servers since early July.
Can you copy/paste some recent lines from the message tab/window of BOINC?
I think I have the same problem. It is affecting both projects that I am part of, Einstein and Rosetta.
Here is a post of my message tab statements. At one point I tried to reset the account.
Wed Aug 8 20:19:27 2007||Starting BOINC client version 5.10.7 for powerpc-apple-darwin
Wed Aug 8 20:19:27 2007||log flags: task, file_xfer, sched_ops
Wed Aug 8 20:19:27 2007||Libraries: libcurl/7.16.1 OpenSSL/0.9.7l zlib/1.2.3
Wed Aug 8 20:19:27 2007||Data directory: /Library/Application Support/BOINC Data
Wed Aug 8 20:19:27 2007||Processor: 1 Power Macintosh Power Macintosh [Power Macintosh Model PowerMac9,1] [AltiVec]
Wed Aug 8 20:19:27 2007||Processor features:
Wed Aug 8 20:19:27 2007||Memory: 1.25 GB physical, 18.65 GB virtual
Wed Aug 8 20:19:27 2007||Disk: 70.20 GB total, 18.41 GB free
Wed Aug 8 20:19:27 2007||Version change (5.8.17 -> 5.10.7)
Wed Aug 8 20:19:27 2007|rosetta@home|URL: http://boinc.bakerlab.org/rosetta/; Computer ID: 273773; location: (none); project prefs: default
Wed Aug 8 20:19:27 2007|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 693306; location: home; project prefs: default
Wed Aug 8 20:19:27 2007||General prefs: from http://setiathome.berkeley.edu/ (last modified 2005-03-17 22:27:46)
Wed Aug 8 20:19:27 2007||Host location: none
Wed Aug 8 20:19:27 2007||General prefs: using your defaults
Wed Aug 8 20:19:27 2007||Preferences limit memory usage when active to 640.00MB
Wed Aug 8 20:19:27 2007||Preferences limit memory usage when idle to 1152.00MB
Wed Aug 8 20:19:27 2007||Preferences limit disk usage to 18.31GB
Wed Aug 8 20:19:27 2007||Running CPU benchmarks
Wed Aug 8 20:19:59 2007||Benchmark results:
Wed Aug 8 20:19:59 2007|| Number of CPUs: 1
Wed Aug 8 20:19:59 2007|| 944 floating point MIPS (Whetstone) per CPU
Wed Aug 8 20:19:59 2007|| 3143 integer MIPS (Dhrystone) per CPU
Wed Aug 8 20:20:03 2007|Einstein@Home|Sending scheduler request: Requested by user
Wed Aug 8 20:20:03 2007|Einstein@Home|Requesting 30240 seconds of new work, and reporting 1 completed tasks
Wed Aug 8 20:20:08 2007|Einstein@Home|Scheduler RPC succeeded [server version 509]
Wed Aug 8 20:20:08 2007|Einstein@Home|Deferring communication for 1 min 0 sec
Wed Aug 8 20:20:08 2007|Einstein@Home|Reason: requested by project
Wed Aug 8 20:20:10 2007|Einstein@Home|Starting h1_0485.85_S5R2__135_S5R2c_0
Wed Aug 8 20:20:13 2007|Einstein@Home|Deferring communication for 1 min 0 sec
Wed Aug 8 20:20:13 2007|Einstein@Home|Reason: Unrecoverable error for result h1_0485.85_S5R2__135_S5R2c_0 (Can't create shared memory: system shmget)
Wed Aug 8 20:20:13 2007|Einstein@Home|Computation for task h1_0485.85_S5R2__135_S5R2c_0 finished
Wed Aug 8 20:20:13 2007|Einstein@Home|Output file h1_0485.85_S5R2__135_S5R2c_0_0 for task h1_0485.85_S5R2__135_S5R2c_0 absent
Wed Aug 8 20:21:14 2007|Einstein@Home|Sending scheduler request: To fetch work
Wed Aug 8 20:21:14 2007|Einstein@Home|Requesting 30240 seconds of new work, and reporting 1 completed tasks
Wed Aug 8 20:21:19 2007|Einstein@Home|Scheduler RPC succeeded [server version 509]
Wed Aug 8 20:21:19 2007|Einstein@Home|Message from server: No work sent
Wed Aug 8 20:21:19 2007|Einstein@Home|Message from server: (reached daily quota of 4 results)
Wed Aug 8 20:21:19 2007|Einstein@Home|Deferring communication for 23 hr 51 min 14 sec
Wed Aug 8 20:21:19 2007|Einstein@Home|Reason: requested by project
Wed Aug 8 20:21:56 2007||General prefs: from http://setiathome.berkeley.edu/ (last modified 2005-03-17 22:27:46)
Wed Aug 8 20:21:56 2007||Host location: none
Wed Aug 8 20:21:56 2007||General prefs: using your defaults
Wed Aug 8 20:21:56 2007||Reading preferences override file
Wed Aug 8 20:21:56 2007||Preferences limit memory usage when active to 640.00MB
Wed Aug 8 20:21:56 2007||Preferences limit memory usage when idle to 1152.00MB
Wed Aug 8 20:21:56 2007||Preferences limit disk usage to 9.31GB
Shared memory is a known BOINC problem in your version of BOINC for Intel Mac - see this BOINC thread. There's a workround (which involves changing the Mac configuration - follow the link), and it's supposed to have been fixed in later (test) versions of BOINC. Not sure about PowerPC, though.
I inform you that I have the same problem: since April 2007 my computer works and works but ineffective for "Einstein" project, since nothing is credited, although apparently there are no communication problems with "Einstein at Home" and work-pieces thereof may be regularly downloaded and put under calculations by my system.
I just set out here tha actual information, written by my system, if this can help:
11.08.2007 11:09:21||Starting BOINC client version 5.10.7 for windows_intelx86
11.08.2007 11:09:21||log flags: task, file_xfer, sched_ops
11.08.2007 11:09:21||Libraries: libcurl/7.16.1 OpenSSL/0.9.8e zlib/1.2.3
11.08.2007 11:09:21||Data directory: C:\\Programme\\BOINC
11.08.2007 11:09:23||Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 CPU 3.20GHz [x86 Family 15 Model 3 Stepping 3]
11.08.2007 11:09:23||Processor features: fpu tsc sse sse2 mmx
11.08.2007 11:09:23||Memory: 2.00 GB physical, 3.85 GB virtual
11.08.2007 11:09:23||Disk: 60.00 GB total, 26.26 GB free
11.08.2007 11:09:23|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 968114; location: home; project prefs: default
11.08.2007 11:09:24||General prefs: from Einstein@Home (last modified 2005-12-08 18:28:19)
11.08.2007 11:09:24||Host location: home
11.08.2007 11:09:24||General prefs: using separate prefs for home
11.08.2007 11:09:24||Reading preferences override file
11.08.2007 11:09:24||Preferences limit memory usage when active to 1023.74MB
11.08.2007 11:09:24||Preferences limit memory usage when idle to 1842.74MB
11.08.2007 11:09:24||Preferences limit disk usage to 9.31GB
11.08.2007 11:09:48|Einstein@Home|Restarting task h1_0508.25_S5R2__264_S5R2c_0 using einstein_S5R2 version 430
11.08.2007 11:18:57|Einstein@Home|Deferring communication for 1 min 0 sec
11.08.2007 11:18:57|Einstein@Home|Reason: Unrecoverable error for result h1_0508.25_S5R2__264_S5R2c_0 ( - exit code 99 (0x63))
11.08.2007 11:18:57|Einstein@Home|Computation for task h1_0508.25_S5R2__264_S5R2c_0 finished
11.08.2007 11:18:57|Einstein@Home|Output file h1_0508.25_S5R2__264_S5R2c_0_0 for task h1_0508.25_S5R2__264_S5R2c_0 absent
11.08.2007 11:19:59|Einstein@Home|Sending scheduler request: To fetch work
11.08.2007 11:19:59|Einstein@Home|Requesting 64800 seconds of new work, and reporting 1 completed tasks
11.08.2007 11:20:04|Einstein@Home|Scheduler RPC succeeded [server version 509]
11.08.2007 11:20:04|Einstein@Home|Deferring communication for 1 min 0 sec
11.08.2007 11:20:04|Einstein@Home|Reason: requested by project
11.08.2007 11:20:07|Einstein@Home|Starting h1_0508.25_S5R2__332_S5R2c_3
11.08.2007 11:20:07|Einstein@Home|Starting task h1_0508.25_S5R2__332_S5R2c_3 using einstein_S5R2 version 430
I would therefore also appreciate as well as other participants with the same problem detailed steps/indication of a solution.
Thank you.
11.08.2007 11:09:21||Starting BOINC client version 5.10.7 for windows_intelx86
....
11.08.2007 11:09:48|Einstein@Home|Restarting task h1_0508.25_S5R2__264_S5R2c_0 using einstein_S5R2 version 430
...
11.08.2007 11:18:57|Einstein@Home|Reason: Unrecoverable error for result h1_0508.25_S5R2__264_S5R2c_0 ( - exit code 99 (0x63))
Your full list of results has 41 results listed, of which 40 have terminated with a compute error. Whilst most of these are indeed the "exit code 99" type as listed above, there are also "exit code 10's" as well as some with "exit code -1073741819".
These latter ones are due to access violations (ie an attempt to access an illegal part of memory) and they trigger the automatic loading of PDB symbols resulting in a stack dump which may be of use to the Developers in trying to track down the bug(s) causing the crash. I have drawn your full results list to the attention of the Developers and hopefully they may be able to determine the cause of the problem.
In the meantime, there is something very useful that you could do to assist. From the messages I've listed above, you are running a version of BOINC (5.10.7) which was an alpha test version and therefore likely to have bugs. You should upgrade to 5.10.13 which is the recommended version. The science app you are using is the current version (4.30) but there is a later version available (4.33) through the beta test page. As your machine is having lots of problems, it should be a good candidate for switching to the beta test app to see if that solves any of your problems.
After you have upgraded your version of BOINC, this is exactly what you need to do to run the beta app. Use these instructions and do not abort any current work in your cache:-
*Download the 4.33 zip archive
*Extract the app_info.xml and the 4.33 executable from the archive
*Copy and paste both into the BOINC\\projects\\einstein.phys.uwm.edu\\ folder
*Do not touch any other file in that folder
*Completely stop BOINC
*Restart BOINC
The messages tab of Boinc Manager will say that the result in progress is being restarted with 430 but in actual fact 4.33 really is being used. You can confirm this with Task Manager if you wish.
If your machine has further compute errors you should report them in the sticky thread for the 4.33 beta test.
Your one host hasn't contacted the servers since early July.
Can you copy/paste some recent lines from the message tab/window of BOINC?
8/5/2007 8:13:01 AM||Starting BOINC client version 5.4.9 for windows_intelx86
8/5/2007 8:13:01 AM||libcurl/7.15.3 OpenSSL/0.9.8a zlib/1.2.3
8/5/2007 8:13:01 AM||Data directory: C:\\Program Files\\BOINC
8/5/2007 8:13:03 AM||Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 CPU 1.60GHz
8/5/2007 8:13:03 AM||Memory: 255.30 MB physical, 618.14 MB virtual
8/5/2007 8:13:03 AM||Disk: 37.24 GB total, 29.22 GB free
8/5/2007 8:13:04 AM|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 702345; location: ; project prefs: default
8/5/2007 8:13:04 AM||General prefs: from Einstein@Home (last modified 2006-07-28 15:10:58)
8/5/2007 8:13:04 AM||General prefs: using your defaults
8/5/2007 8:13:05 AM||Local control only allowed
8/5/2007 8:13:05 AM||Listening on port 31416
8/5/2007 8:13:05 AM|Einstein@Home|Resuming task h1_0482.70_S5R2__213_S5R2c_0 using einstein_S5R2 version 424
8/5/2007 8:13:07 AM||Using earliest-deadline-first scheduling because computer is overcommitted.
8/5/2007 8:13:07 AM||Suspending work fetch because computer is overcommitted.
8/6/2007 6:26:04 PM||Suspending computation - running CPU benchmarks
8/6/2007 6:26:04 PM|Einstein@Home|Pausing task h1_0482.70_S5R2__213_S5R2c_0 (removed from memory)
8/6/2007 6:26:04 PM||Suspending network activity - running CPU benchmarks
8/6/2007 6:26:06 PM||Running CPU benchmarks
8/6/2007 6:27:05 PM||Benchmark results:
8/6/2007 6:27:05 PM|| Number of CPUs: 1
8/6/2007 6:27:05 PM|| 791 floating point MIPS (Whetstone) per CPU
8/6/2007 6:27:05 PM|| 1523 integer MIPS (Dhrystone) per CPU
8/6/2007 6:27:05 PM||Finished CPU benchmarks
8/6/2007 6:27:07 PM||Resuming computation
8/6/2007 6:27:07 PM||Rescheduling CPU: Resuming computation
8/6/2007 6:27:07 PM||Resuming network activity
8/6/2007 6:27:07 PM|Einstein@Home|Restarting task h1_0482.70_S5R2__213_S5R2c_0 using einstein_S5R2 version 424
8/6/2007 6:27:08 PM|Einstein@Home|einstein_S5R2 not responding to screensaver, exiting
8/6/2007 6:27:10 PM|Einstein@Home|Task h1_0482.70_S5R2__213_S5R2c_0 exited with zero status but no 'finished' file
8/6/2007 6:27:10 PM|Einstein@Home|If this happens repeatedly you may need to reset the project.
8/6/2007 6:27:10 PM||Rescheduling CPU: application exited
8/6/2007 6:27:10 PM|Einstein@Home|Restarting task h1_0482.70_S5R2__213_S5R2c_0 using einstein_S5R2 version 424
8/7/2007 10:46:27 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:46:27 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:46:27 AM|Einstein@Home|Requesting 16 seconds of new work
8/7/2007 10:46:32 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:46:33 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:46:33 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.8% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:46:33 AM|Einstein@Home|No work from project
8/7/2007 10:47:33 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:47:33 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:47:33 AM|Einstein@Home|Requesting 53 seconds of new work
8/7/2007 10:47:38 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:47:38 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:47:38 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.8% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:47:38 AM|Einstein@Home|No work from project
8/7/2007 10:48:38 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:48:38 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:48:38 AM|Einstein@Home|Requesting 90 seconds of new work
8/7/2007 10:48:43 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:48:43 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:48:43 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.8% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:48:43 AM|Einstein@Home|No work from project
8/7/2007 10:49:43 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:49:43 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:49:43 AM|Einstein@Home|Requesting 164 seconds of new work
8/7/2007 10:49:48 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:49:48 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:49:48 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.8% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:49:48 AM|Einstein@Home|No work from project
8/7/2007 10:50:49 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:50:49 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:50:49 AM|Einstein@Home|Requesting 201 seconds of new work
8/7/2007 10:50:54 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:50:54 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:50:54 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.8% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:50:54 AM|Einstein@Home|No work from project
8/7/2007 10:50:54 AM|Einstein@Home|Deferring scheduler requests for 1 minutes and 2 seconds
8/7/2007 10:51:59 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:51:59 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:51:59 AM|Einstein@Home|Requesting 275 seconds of new work
8/7/2007 10:52:04 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:52:04 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:52:04 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.8% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:52:04 AM|Einstein@Home|No work from project
8/7/2007 10:52:04 AM|Einstein@Home|Deferring scheduler requests for 3 minutes and 37 seconds
8/7/2007 10:55:44 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:55:44 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:55:44 AM|Einstein@Home|Requesting 423 seconds of new work
8/7/2007 10:55:49 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:55:49 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:55:49 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.9% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:55:49 AM|Einstein@Home|No work from project
8/7/2007 10:55:49 AM|Einstein@Home|Deferring scheduler requests for 3 minutes and 27 seconds
8/7/2007 10:59:19 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:59:19 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:59:19 AM|Einstein@Home|Requesting 571 seconds of new work
8/7/2007 10:59:24 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:59:24 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:59:24 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.9% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:59:24 AM|Einstein@Home|No work from project
8/7/2007 10:59:24 AM|Einstein@Home|Deferring scheduler requests for 36 minutes and 52 seconds
8/7/2007 11:36:22 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 11:36:22 AM|Einstein@Home|Reason: To fetch work
8/7/2007 11:36:22 AM|Einstein@Home|Requesting 2499 seconds of new work
8/7/2007 11:36:27 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 11:36:27 AM|Einstein@Home|Message from server: No work sent
8/7/2007 11:36:27 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.9% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 11:36:27 AM|Einstein@Home|No work from project
8/7/2007 11:36:27 AM|Einstein@Home|Deferring scheduler requests for 2 hours, 9 minutes and 3 seconds
8/7/2007 1:30:55 PM||Rescheduling CPU: application exited
8/7/2007 1:30:55 PM|Einstein@Home|Computation for task h1_0482.70_S5R2__213_S5R2c_0 finished
8/7/2007 1:30:55 PM||Resuming round-robin CPU scheduling.
8/7/2007 1:30:58 PM|Einstein@Home|Started upload of file h1_0482.70_S5R2__213_S5R2c_0_0
8/7/2007 1:31:08 PM|Einstein@Home|Finished upload of file h1_0482.70_S5R2__213_S5R2c_0_0
8/7/2007 1:31:08 PM|Einstein@Home|Throughput 15414 bytes/sec
8/7/2007 1:45:34 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 1:45:34 PM|Einstein@Home|Reason: To report completed tasks
8/7/2007 1:45:34 PM|Einstein@Home|Requesting 8640 seconds of new work, and reporting 1 completed tasks
8/7/2007 1:45:44 PM|Einstein@Home|Scheduler request succeeded
8/7/2007 1:45:46 PM|Einstein@Home|Started download of file einstein_S5R2_4.30_windows_intelx86.exe
8/7/2007 1:45:49 PM||Allowing work fetch again.
8/7/2007 1:46:20 PM|Einstein@Home|Finished download of file einstein_S5R2_4.30_windows_intelx86.exe
8/7/2007 1:46:20 PM|Einstein@Home|Throughput 92142 bytes/sec
8/7/2007 1:46:21 PM||Rescheduling CPU: files downloaded
8/7/2007 1:46:21 PM||Using earliest-deadline-first scheduling because computer is overcommitted.
8/7/2007 1:46:21 PM|Einstein@Home|Starting task h1_0482.70_S5R2__73_S5R2c_0 using einstein_S5R2 version 430
8/7/2007 1:46:25 PM||Suspending work fetch because computer is overcommitted.
8/10/2007 6:58:13 PM||Allowing work fetch again.
8/10/2007 7:47:01 PM||Resuming round-robin CPU scheduling.
8/11/2007 6:27:06 PM||Suspending computation - running CPU benchmarks
8/11/2007 6:27:06 PM|Einstein@Home|Pausing task h1_0482.70_S5R2__73_S5R2c_0 (removed from memory)
8/11/2007 6:27:06 PM||Suspending network activity - running CPU benchmarks
8/11/2007 6:27:09 PM||Running CPU benchmarks
8/11/2007 6:28:08 PM||Benchmark results:
8/11/2007 6:28:08 PM|| Number of CPUs: 1
8/11/2007 6:28:08 PM|| 783 floating point MIPS (Whetstone) per CPU
8/11/2007 6:28:08 PM|| 1505 integer MIPS (Dhrystone) per CPU
8/11/2007 6:28:08 PM||Finished CPU benchmarks
8/11/2007 6:28:09 PM||Resuming computation
8/11/2007 6:28:09 PM||Rescheduling CPU: Resuming computation
8/11/2007 6:28:09 PM||Resuming network activity
8/11/2007 6:28:09 PM|Einstein@Home|Restarting task h1_0482.70_S5R2__73_S5R2c_0 using einstein_S5R2 version 430
8/11/2007 10:10:37 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/11/2007 10:10:37 PM|Einstein@Home|Reason: Requested by user
8/11/2007 10:10:37 PM|Einstein@Home|(not requesting new work or reporting completed tasks)
8/11/2007 10:10:42 PM|Einstein@Home|Scheduler request succeeded
8/11/2007 10:19:34 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/11/2007 10:19:34 PM|Einstein@Home|Reason: Requested by user
8/11/2007 10:19:34 PM|Einstein@Home|(not requesting new work or reporting completed tasks)
8/11/2007 10:19:39 PM|Einstein@Home|Scheduler request succeeded
Please be a little more selective of the messages you post and please don't post the whole lot twice. Here is an example of the number of lines that would have been much more friendly for the person trying to analyse your problem:-
Quote:
Quote:
Can you copy/paste some recent lines from the message tab/window of BOINC?
8/5/2007 8:13:01 AM||Starting BOINC client version 5.4.9 for windows_intelx86
8/5/2007 8:13:01 AM||libcurl/7.15.3 OpenSSL/0.9.8a zlib/1.2.3
8/5/2007 8:13:01 AM||Data directory: C:\\Program Files\\BOINC
8/5/2007 8:13:03 AM||Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 CPU 1.60GHz
8/5/2007 8:13:03 AM||Memory: 255.30 MB physical, 618.14 MB virtual
8/5/2007 8:13:03 AM||Disk: 37.24 GB total, 29.22 GB free
8/5/2007 8:13:04 AM|Einstein@Home|URL: http://einstein.phys.uwm.edu/;Computer ID: 702345; location: ; project prefs: default
8/5/2007 8:13:04 AM||General prefs: from Einstein@Home (last modified 2006-07-28 15:10:58)
8/5/2007 8:13:04 AM||General prefs: using your defaults
8/5/2007 8:13:05 AM||Local control only allowed
8/5/2007 8:13:05 AM||Listening on port 31416
8/5/2007 8:13:05 AM|Einstein@Home|Resuming task h1_0482.70_S5R2__213_S5R2c_0 using einstein_S5R2 version 424
8/5/2007 8:13:07 AM||Using earliest-deadline-first scheduling because computer is overcommitted.
8/5/2007 8:13:07 AM||Suspending work fetch because computer is overcommitted.
There are a couple of interesting things (highlighted in red) that immediately come to light.
You (the user Mike - ID 200943) don't own this computer. The above computer ID is clearly shown as 702345 and it's owned by a user called Michael - ID 205761. The computer that Mike owns is ID 674671. This computer last contacted the project back in early July and it's this that confused both Kathryn and myself when we read your initial message and Kathryn asked you to post some messages. All we did was check your computers as we didn't know about Michael :).
Now Mike and Michael may well be the same person but it does create confusion if one ID posts about a computer belonging to the other ID. The computers are different too. Michael's is a P4 1.6GHz whilst Mike's is a P4 2.8GHz.
Both your UserIDs were created over a year ago and both have credit although Michael is a long way ahead of Mike in that regard. Unless you have some particular reason for the dual identity, you should choose which ID you want to be and make sure that both you and your computer(s) (and all your posts for that matter) belong to the chosen account. You can't delete an account but you can let it fade away by not using it.
Now that we know the computer whose log you posted, the next item of interest comes from examining its results list. It's quite astounding to see that it took over 18 days of CPU time to do a result. That's not an estimate nor is it wall clock time, it's the actual elapsed cpu time to crunch the result. It's little wonder that BOINC decided to suspend work fetch.
That result should have taken about one fifth of that time on that sort of hardware so there is something wrong somewhere. Have you changed your computers time/date setting at all? Did the result crunch nearly to the end and then somehow get reset so that it started crunching from the beginning without resetting the CPU time? That sort of thing has been know to happen in the past but is usually associated with older versions of Windows, eg Win98. To rack up 18 days, this would have to happen several times.
Do you monitor the progress of your machine using Boinc Manager? Do you watch the behaviour of both CPU time and %Progress on the Tasks tab to see if everything looks normal? How about writing down the two values and checking them again a couple of hours later to see what is happening? That would be a useful thing to do.
When that extra long running result finally finished, you got these messages:-
Quote:
8/7/2007 1:30:55 PM|Einstein@Home|Computation for task h1_0482.70_S5R2__213_S5R2c_0 finished
8/7/2007 1:30:55 PM||Resuming round-robin CPU scheduling.
8/7/2007 1:30:58 PM|Einstein@Home|Started upload of file h1_0482.70_S5R2__213_S5R2c_0_0
8/7/2007 1:31:08 PM|Einstein@Home|Finished upload of file h1_0482.70_S5R2__213_S5R2c_0_0
8/7/2007 1:31:08 PM|Einstein@Home|Throughput 15414 bytes/sec
8/7/2007 1:45:34 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 1:45:34 PM|Einstein@Home|Reason: To report completed tasks
8/7/2007 1:45:34 PM|Einstein@Home|Requesting 8640 seconds of new work, and reporting 1 completed tasks
8/7/2007 1:45:44 PM|Einstein@Home|Scheduler request succeeded
8/7/2007 1:45:46 PM|Einstein@Home|Started download of file einstein_S5R2_4.30_windows_intelx86.exe
8/7/2007 1:45:49 PM||Allowing work fetch again.
8/7/2007 1:46:20 PM|Einstein@Home|Finished download of file einstein_S5R2_4.30_windows_intelx86.exe
8/7/2007 1:46:20 PM|Einstein@Home|Throughput 92142 bytes/sec
8/7/2007 1:46:21 PM||Rescheduling CPU: files downloaded 8/7/2007 1:46:21 PM||Using earliest-deadline-first scheduling because computer is overcommitted.
8/7/2007 1:46:21 PM|Einstein@Home|Starting task h1_0482.70_S5R2__73_S5R2c_0 using einstein_S5R2 version 430
8/7/2007 1:46:25 PM||Suspending work fetch because computer is overcommitted. 8/10/2007 6:58:13 PM||Allowing work fetch again.
8/10/2007 7:47:01 PM||Resuming round-robin CPU scheduling.
What happened here is quite revealing. The long running result finished at 1:30:55 on August 7 and BOINC immediately resumed round-robin scheduling. The result was uploaded and eventually reported and new work was downloaded. Also a new executable was downloaded because there had been a version change in the app. As soon as the new work was commenced, BOINC went back into EDF (Earliest Deadline First) mode because the estimate of how long the result would take had been poisoned by the previous long running result. BOINC will correct this itself over (a very long) time, but if it were my machine, I'd correct it manually once I was sure that the new result was processing more normally. You can see that the new result is probably going OK because on August 10 the estimate of remaining crunch time must have dropped considerably, allowing BOINC to get out of EDF and back to the normal round-robin scheduling.
It would be helpful if you could let us know the CPU time, %Progress and the estimate of remaining crunch time for the current result. Also have a look in your client_state.xml file and see what is the current value for the variable called "duration_correction_factor" (DCF). I suspect it will have a value greater than 3.0 when it probably should be less than 1.0.
Once this information is known, it should be possible to tell if things are getting back to normal.
Computer is Computing, but Not Communicate w/ Einstein
)
Check through the BOINC Manager and see if you have everything straight there, if you haven't already:
1. Click on your "Activity" button (very top row) and make sure nothing is suspended.
2. On your "Project" tab, see in the status section that it is not set on "Won't get new tasks" and/or "Suspended by user".
3. Through your "Message" tab, copy the messages and post them here as that may supply additional information to what the problem may be if 1 and 2 above are a washout.
Your one host hasn't
)
Your one host hasn't contacted the servers since early July.
Can you copy/paste some recent lines from the message tab/window of BOINC?
Kathryn :o)
Einstein@Home Moderator
RE: Your one host hasn't
)
I think I have the same problem. It is affecting both projects that I am part of, Einstein and Rosetta.
Here is a post of my message tab statements. At one point I tried to reset the account.
Wed Aug 8 20:19:27 2007||Starting BOINC client version 5.10.7 for powerpc-apple-darwin
Wed Aug 8 20:19:27 2007||log flags: task, file_xfer, sched_ops
Wed Aug 8 20:19:27 2007||Libraries: libcurl/7.16.1 OpenSSL/0.9.7l zlib/1.2.3
Wed Aug 8 20:19:27 2007||Data directory: /Library/Application Support/BOINC Data
Wed Aug 8 20:19:27 2007||Processor: 1 Power Macintosh Power Macintosh [Power Macintosh Model PowerMac9,1] [AltiVec]
Wed Aug 8 20:19:27 2007||Processor features:
Wed Aug 8 20:19:27 2007||Memory: 1.25 GB physical, 18.65 GB virtual
Wed Aug 8 20:19:27 2007||Disk: 70.20 GB total, 18.41 GB free
Wed Aug 8 20:19:27 2007||Version change (5.8.17 -> 5.10.7)
Wed Aug 8 20:19:27 2007|rosetta@home|URL: http://boinc.bakerlab.org/rosetta/; Computer ID: 273773; location: (none); project prefs: default
Wed Aug 8 20:19:27 2007|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 693306; location: home; project prefs: default
Wed Aug 8 20:19:27 2007||General prefs: from http://setiathome.berkeley.edu/ (last modified 2005-03-17 22:27:46)
Wed Aug 8 20:19:27 2007||Host location: none
Wed Aug 8 20:19:27 2007||General prefs: using your defaults
Wed Aug 8 20:19:27 2007||Preferences limit memory usage when active to 640.00MB
Wed Aug 8 20:19:27 2007||Preferences limit memory usage when idle to 1152.00MB
Wed Aug 8 20:19:27 2007||Preferences limit disk usage to 18.31GB
Wed Aug 8 20:19:27 2007||Running CPU benchmarks
Wed Aug 8 20:19:59 2007||Benchmark results:
Wed Aug 8 20:19:59 2007|| Number of CPUs: 1
Wed Aug 8 20:19:59 2007|| 944 floating point MIPS (Whetstone) per CPU
Wed Aug 8 20:19:59 2007|| 3143 integer MIPS (Dhrystone) per CPU
Wed Aug 8 20:20:03 2007|Einstein@Home|Sending scheduler request: Requested by user
Wed Aug 8 20:20:03 2007|Einstein@Home|Requesting 30240 seconds of new work, and reporting 1 completed tasks
Wed Aug 8 20:20:08 2007|Einstein@Home|Scheduler RPC succeeded [server version 509]
Wed Aug 8 20:20:08 2007|Einstein@Home|Deferring communication for 1 min 0 sec
Wed Aug 8 20:20:08 2007|Einstein@Home|Reason: requested by project
Wed Aug 8 20:20:10 2007|Einstein@Home|Starting h1_0485.85_S5R2__135_S5R2c_0
Wed Aug 8 20:20:13 2007|Einstein@Home|Deferring communication for 1 min 0 sec
Wed Aug 8 20:20:13 2007|Einstein@Home|Reason: Unrecoverable error for result h1_0485.85_S5R2__135_S5R2c_0 (Can't create shared memory: system shmget)
Wed Aug 8 20:20:13 2007|Einstein@Home|Computation for task h1_0485.85_S5R2__135_S5R2c_0 finished
Wed Aug 8 20:20:13 2007|Einstein@Home|Output file h1_0485.85_S5R2__135_S5R2c_0_0 for task h1_0485.85_S5R2__135_S5R2c_0 absent
Wed Aug 8 20:21:14 2007|Einstein@Home|Sending scheduler request: To fetch work
Wed Aug 8 20:21:14 2007|Einstein@Home|Requesting 30240 seconds of new work, and reporting 1 completed tasks
Wed Aug 8 20:21:19 2007|Einstein@Home|Scheduler RPC succeeded [server version 509]
Wed Aug 8 20:21:19 2007|Einstein@Home|Message from server: No work sent
Wed Aug 8 20:21:19 2007|Einstein@Home|Message from server: (reached daily quota of 4 results)
Wed Aug 8 20:21:19 2007|Einstein@Home|Deferring communication for 23 hr 51 min 14 sec
Wed Aug 8 20:21:19 2007|Einstein@Home|Reason: requested by project
Wed Aug 8 20:21:56 2007||General prefs: from http://setiathome.berkeley.edu/ (last modified 2005-03-17 22:27:46)
Wed Aug 8 20:21:56 2007||Host location: none
Wed Aug 8 20:21:56 2007||General prefs: using your defaults
Wed Aug 8 20:21:56 2007||Reading preferences override file
Wed Aug 8 20:21:56 2007||Preferences limit memory usage when active to 640.00MB
Wed Aug 8 20:21:56 2007||Preferences limit memory usage when idle to 1152.00MB
Wed Aug 8 20:21:56 2007||Preferences limit disk usage to 9.31GB
RE: RE: Your one host
)
Since it is the shared memory error, I sent the question to the BOINC developer for the Mac versions.
Shared memory is a known
)
Shared memory is a known BOINC problem in your version of BOINC for Intel Mac - see this BOINC thread. There's a workround (which involves changing the Mac configuration - follow the link), and it's supposed to have been fixed in later (test) versions of BOINC. Not sure about PowerPC, though.
I inform you that I have the
)
I inform you that I have the same problem: since April 2007 my computer works and works but ineffective for "Einstein" project, since nothing is credited, although apparently there are no communication problems with "Einstein at Home" and work-pieces thereof may be regularly downloaded and put under calculations by my system.
I just set out here tha actual information, written by my system, if this can help:
11.08.2007 11:09:21||Starting BOINC client version 5.10.7 for windows_intelx86
11.08.2007 11:09:21||log flags: task, file_xfer, sched_ops
11.08.2007 11:09:21||Libraries: libcurl/7.16.1 OpenSSL/0.9.8e zlib/1.2.3
11.08.2007 11:09:21||Data directory: C:\\Programme\\BOINC
11.08.2007 11:09:23||Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 CPU 3.20GHz [x86 Family 15 Model 3 Stepping 3]
11.08.2007 11:09:23||Processor features: fpu tsc sse sse2 mmx
11.08.2007 11:09:23||Memory: 2.00 GB physical, 3.85 GB virtual
11.08.2007 11:09:23||Disk: 60.00 GB total, 26.26 GB free
11.08.2007 11:09:23|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 968114; location: home; project prefs: default
11.08.2007 11:09:24||General prefs: from Einstein@Home (last modified 2005-12-08 18:28:19)
11.08.2007 11:09:24||Host location: home
11.08.2007 11:09:24||General prefs: using separate prefs for home
11.08.2007 11:09:24||Reading preferences override file
11.08.2007 11:09:24||Preferences limit memory usage when active to 1023.74MB
11.08.2007 11:09:24||Preferences limit memory usage when idle to 1842.74MB
11.08.2007 11:09:24||Preferences limit disk usage to 9.31GB
11.08.2007 11:09:48|Einstein@Home|Restarting task h1_0508.25_S5R2__264_S5R2c_0 using einstein_S5R2 version 430
11.08.2007 11:18:57|Einstein@Home|Deferring communication for 1 min 0 sec
11.08.2007 11:18:57|Einstein@Home|Reason: Unrecoverable error for result h1_0508.25_S5R2__264_S5R2c_0 ( - exit code 99 (0x63))
11.08.2007 11:18:57|Einstein@Home|Computation for task h1_0508.25_S5R2__264_S5R2c_0 finished
11.08.2007 11:18:57|Einstein@Home|Output file h1_0508.25_S5R2__264_S5R2c_0_0 for task h1_0508.25_S5R2__264_S5R2c_0 absent
11.08.2007 11:19:59|Einstein@Home|Sending scheduler request: To fetch work
11.08.2007 11:19:59|Einstein@Home|Requesting 64800 seconds of new work, and reporting 1 completed tasks
11.08.2007 11:20:04|Einstein@Home|Scheduler RPC succeeded [server version 509]
11.08.2007 11:20:04|Einstein@Home|Deferring communication for 1 min 0 sec
11.08.2007 11:20:04|Einstein@Home|Reason: requested by project
11.08.2007 11:20:07|Einstein@Home|Starting h1_0508.25_S5R2__332_S5R2c_3
11.08.2007 11:20:07|Einstein@Home|Starting task h1_0508.25_S5R2__332_S5R2c_3 using einstein_S5R2 version 430
I would therefore also appreciate as well as other participants with the same problem detailed steps/indication of a solution.
Thank you.
RE: 11.08.2007
)
See this thread.
RE: 11.08.2007
)
Your full list of results has 41 results listed, of which 40 have terminated with a compute error. Whilst most of these are indeed the "exit code 99" type as listed above, there are also "exit code 10's" as well as some with "exit code -1073741819".
These latter ones are due to access violations (ie an attempt to access an illegal part of memory) and they trigger the automatic loading of PDB symbols resulting in a stack dump which may be of use to the Developers in trying to track down the bug(s) causing the crash. I have drawn your full results list to the attention of the Developers and hopefully they may be able to determine the cause of the problem.
In the meantime, there is something very useful that you could do to assist. From the messages I've listed above, you are running a version of BOINC (5.10.7) which was an alpha test version and therefore likely to have bugs. You should upgrade to 5.10.13 which is the recommended version. The science app you are using is the current version (4.30) but there is a later version available (4.33) through the beta test page. As your machine is having lots of problems, it should be a good candidate for switching to the beta test app to see if that solves any of your problems.
After you have upgraded your version of BOINC, this is exactly what you need to do to run the beta app. Use these instructions and do not abort any current work in your cache:-
*Extract the app_info.xml and the 4.33 executable from the archive
*Copy and paste both into the BOINC\\projects\\einstein.phys.uwm.edu\\ folder
*Do not touch any other file in that folder
*Completely stop BOINC
*Restart BOINC
The messages tab of Boinc Manager will say that the result in progress is being restarted with 430 but in actual fact 4.33 really is being used. You can confirm this with Task Manager if you wish.
If your machine has further compute errors you should report them in the sticky thread for the 4.33 beta test.
Thanks for your help.
Cheers,
Gary.
RE: Your one host hasn't
)
8/5/2007 8:13:01 AM||Starting BOINC client version 5.4.9 for windows_intelx86
8/5/2007 8:13:01 AM||libcurl/7.15.3 OpenSSL/0.9.8a zlib/1.2.3
8/5/2007 8:13:01 AM||Data directory: C:\\Program Files\\BOINC
8/5/2007 8:13:03 AM||Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 CPU 1.60GHz
8/5/2007 8:13:03 AM||Memory: 255.30 MB physical, 618.14 MB virtual
8/5/2007 8:13:03 AM||Disk: 37.24 GB total, 29.22 GB free
8/5/2007 8:13:04 AM|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 702345; location: ; project prefs: default
8/5/2007 8:13:04 AM||General prefs: from Einstein@Home (last modified 2006-07-28 15:10:58)
8/5/2007 8:13:04 AM||General prefs: using your defaults
8/5/2007 8:13:05 AM||Local control only allowed
8/5/2007 8:13:05 AM||Listening on port 31416
8/5/2007 8:13:05 AM|Einstein@Home|Resuming task h1_0482.70_S5R2__213_S5R2c_0 using einstein_S5R2 version 424
8/5/2007 8:13:07 AM||Using earliest-deadline-first scheduling because computer is overcommitted.
8/5/2007 8:13:07 AM||Suspending work fetch because computer is overcommitted.
8/6/2007 6:26:04 PM||Suspending computation - running CPU benchmarks
8/6/2007 6:26:04 PM|Einstein@Home|Pausing task h1_0482.70_S5R2__213_S5R2c_0 (removed from memory)
8/6/2007 6:26:04 PM||Suspending network activity - running CPU benchmarks
8/6/2007 6:26:06 PM||Running CPU benchmarks
8/6/2007 6:27:05 PM||Benchmark results:
8/6/2007 6:27:05 PM|| Number of CPUs: 1
8/6/2007 6:27:05 PM|| 791 floating point MIPS (Whetstone) per CPU
8/6/2007 6:27:05 PM|| 1523 integer MIPS (Dhrystone) per CPU
8/6/2007 6:27:05 PM||Finished CPU benchmarks
8/6/2007 6:27:07 PM||Resuming computation
8/6/2007 6:27:07 PM||Rescheduling CPU: Resuming computation
8/6/2007 6:27:07 PM||Resuming network activity
8/6/2007 6:27:07 PM|Einstein@Home|Restarting task h1_0482.70_S5R2__213_S5R2c_0 using einstein_S5R2 version 424
8/6/2007 6:27:08 PM|Einstein@Home|einstein_S5R2 not responding to screensaver, exiting
8/6/2007 6:27:10 PM|Einstein@Home|Task h1_0482.70_S5R2__213_S5R2c_0 exited with zero status but no 'finished' file
8/6/2007 6:27:10 PM|Einstein@Home|If this happens repeatedly you may need to reset the project.
8/6/2007 6:27:10 PM||Rescheduling CPU: application exited
8/6/2007 6:27:10 PM|Einstein@Home|Restarting task h1_0482.70_S5R2__213_S5R2c_0 using einstein_S5R2 version 424
8/7/2007 10:46:27 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:46:27 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:46:27 AM|Einstein@Home|Requesting 16 seconds of new work
8/7/2007 10:46:32 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:46:33 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:46:33 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.8% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:46:33 AM|Einstein@Home|No work from project
8/7/2007 10:47:33 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:47:33 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:47:33 AM|Einstein@Home|Requesting 53 seconds of new work
8/7/2007 10:47:38 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:47:38 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:47:38 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.8% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:47:38 AM|Einstein@Home|No work from project
8/7/2007 10:48:38 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:48:38 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:48:38 AM|Einstein@Home|Requesting 90 seconds of new work
8/7/2007 10:48:43 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:48:43 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:48:43 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.8% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:48:43 AM|Einstein@Home|No work from project
8/7/2007 10:49:43 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:49:43 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:49:43 AM|Einstein@Home|Requesting 164 seconds of new work
8/7/2007 10:49:48 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:49:48 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:49:48 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.8% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:49:48 AM|Einstein@Home|No work from project
8/7/2007 10:50:49 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:50:49 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:50:49 AM|Einstein@Home|Requesting 201 seconds of new work
8/7/2007 10:50:54 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:50:54 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:50:54 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.8% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:50:54 AM|Einstein@Home|No work from project
8/7/2007 10:50:54 AM|Einstein@Home|Deferring scheduler requests for 1 minutes and 2 seconds
8/7/2007 10:51:59 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:51:59 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:51:59 AM|Einstein@Home|Requesting 275 seconds of new work
8/7/2007 10:52:04 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:52:04 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:52:04 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.8% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:52:04 AM|Einstein@Home|No work from project
8/7/2007 10:52:04 AM|Einstein@Home|Deferring scheduler requests for 3 minutes and 37 seconds
8/7/2007 10:55:44 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:55:44 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:55:44 AM|Einstein@Home|Requesting 423 seconds of new work
8/7/2007 10:55:49 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:55:49 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:55:49 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.9% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:55:49 AM|Einstein@Home|No work from project
8/7/2007 10:55:49 AM|Einstein@Home|Deferring scheduler requests for 3 minutes and 27 seconds
8/7/2007 10:59:19 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 10:59:19 AM|Einstein@Home|Reason: To fetch work
8/7/2007 10:59:19 AM|Einstein@Home|Requesting 571 seconds of new work
8/7/2007 10:59:24 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 10:59:24 AM|Einstein@Home|Message from server: No work sent
8/7/2007 10:59:24 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.9% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 10:59:24 AM|Einstein@Home|No work from project
8/7/2007 10:59:24 AM|Einstein@Home|Deferring scheduler requests for 36 minutes and 52 seconds
8/7/2007 11:36:22 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 11:36:22 AM|Einstein@Home|Reason: To fetch work
8/7/2007 11:36:22 AM|Einstein@Home|Requesting 2499 seconds of new work
8/7/2007 11:36:27 AM|Einstein@Home|Scheduler request succeeded
8/7/2007 11:36:27 AM|Einstein@Home|Message from server: No work sent
8/7/2007 11:36:27 AM|Einstein@Home|Message from server: (won't finish in time) Computer on 76.9% of time, BOINC on 99.7% of that, this project gets 100.0% of that
8/7/2007 11:36:27 AM|Einstein@Home|No work from project
8/7/2007 11:36:27 AM|Einstein@Home|Deferring scheduler requests for 2 hours, 9 minutes and 3 seconds
8/7/2007 1:30:55 PM||Rescheduling CPU: application exited
8/7/2007 1:30:55 PM|Einstein@Home|Computation for task h1_0482.70_S5R2__213_S5R2c_0 finished
8/7/2007 1:30:55 PM||Resuming round-robin CPU scheduling.
8/7/2007 1:30:58 PM|Einstein@Home|Started upload of file h1_0482.70_S5R2__213_S5R2c_0_0
8/7/2007 1:31:08 PM|Einstein@Home|Finished upload of file h1_0482.70_S5R2__213_S5R2c_0_0
8/7/2007 1:31:08 PM|Einstein@Home|Throughput 15414 bytes/sec
8/7/2007 1:45:34 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/7/2007 1:45:34 PM|Einstein@Home|Reason: To report completed tasks
8/7/2007 1:45:34 PM|Einstein@Home|Requesting 8640 seconds of new work, and reporting 1 completed tasks
8/7/2007 1:45:44 PM|Einstein@Home|Scheduler request succeeded
8/7/2007 1:45:46 PM|Einstein@Home|Started download of file einstein_S5R2_4.30_windows_intelx86.exe
8/7/2007 1:45:49 PM||Allowing work fetch again.
8/7/2007 1:46:20 PM|Einstein@Home|Finished download of file einstein_S5R2_4.30_windows_intelx86.exe
8/7/2007 1:46:20 PM|Einstein@Home|Throughput 92142 bytes/sec
8/7/2007 1:46:21 PM||Rescheduling CPU: files downloaded
8/7/2007 1:46:21 PM||Using earliest-deadline-first scheduling because computer is overcommitted.
8/7/2007 1:46:21 PM|Einstein@Home|Starting task h1_0482.70_S5R2__73_S5R2c_0 using einstein_S5R2 version 430
8/7/2007 1:46:25 PM||Suspending work fetch because computer is overcommitted.
8/10/2007 6:58:13 PM||Allowing work fetch again.
8/10/2007 7:47:01 PM||Resuming round-robin CPU scheduling.
8/11/2007 6:27:06 PM||Suspending computation - running CPU benchmarks
8/11/2007 6:27:06 PM|Einstein@Home|Pausing task h1_0482.70_S5R2__73_S5R2c_0 (removed from memory)
8/11/2007 6:27:06 PM||Suspending network activity - running CPU benchmarks
8/11/2007 6:27:09 PM||Running CPU benchmarks
8/11/2007 6:28:08 PM||Benchmark results:
8/11/2007 6:28:08 PM|| Number of CPUs: 1
8/11/2007 6:28:08 PM|| 783 floating point MIPS (Whetstone) per CPU
8/11/2007 6:28:08 PM|| 1505 integer MIPS (Dhrystone) per CPU
8/11/2007 6:28:08 PM||Finished CPU benchmarks
8/11/2007 6:28:09 PM||Resuming computation
8/11/2007 6:28:09 PM||Rescheduling CPU: Resuming computation
8/11/2007 6:28:09 PM||Resuming network activity
8/11/2007 6:28:09 PM|Einstein@Home|Restarting task h1_0482.70_S5R2__73_S5R2c_0 using einstein_S5R2 version 430
8/11/2007 10:10:37 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/11/2007 10:10:37 PM|Einstein@Home|Reason: Requested by user
8/11/2007 10:10:37 PM|Einstein@Home|(not requesting new work or reporting completed tasks)
8/11/2007 10:10:42 PM|Einstein@Home|Scheduler request succeeded
8/11/2007 10:19:34 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
8/11/2007 10:19:34 PM|Einstein@Home|Reason: Requested by user
8/11/2007 10:19:34 PM|Einstein@Home|(not requesting new work or reporting completed tasks)
8/11/2007 10:19:39 PM|Einstein@Home|Scheduler request succeeded
Please be a little more
)
Please be a little more selective of the messages you post and please don't post the whole lot twice. Here is an example of the number of lines that would have been much more friendly for the person trying to analyse your problem:-
There are a couple of interesting things (highlighted in red) that immediately come to light.
You (the user Mike - ID 200943) don't own this computer. The above computer ID is clearly shown as 702345 and it's owned by a user called Michael - ID 205761. The computer that Mike owns is ID 674671. This computer last contacted the project back in early July and it's this that confused both Kathryn and myself when we read your initial message and Kathryn asked you to post some messages. All we did was check your computers as we didn't know about Michael :).
Now Mike and Michael may well be the same person but it does create confusion if one ID posts about a computer belonging to the other ID. The computers are different too. Michael's is a P4 1.6GHz whilst Mike's is a P4 2.8GHz.
Both your UserIDs were created over a year ago and both have credit although Michael is a long way ahead of Mike in that regard. Unless you have some particular reason for the dual identity, you should choose which ID you want to be and make sure that both you and your computer(s) (and all your posts for that matter) belong to the chosen account. You can't delete an account but you can let it fade away by not using it.
Now that we know the computer whose log you posted, the next item of interest comes from examining its results list. It's quite astounding to see that it took over 18 days of CPU time to do a result. That's not an estimate nor is it wall clock time, it's the actual elapsed cpu time to crunch the result. It's little wonder that BOINC decided to suspend work fetch.
That result should have taken about one fifth of that time on that sort of hardware so there is something wrong somewhere. Have you changed your computers time/date setting at all? Did the result crunch nearly to the end and then somehow get reset so that it started crunching from the beginning without resetting the CPU time? That sort of thing has been know to happen in the past but is usually associated with older versions of Windows, eg Win98. To rack up 18 days, this would have to happen several times.
Do you monitor the progress of your machine using Boinc Manager? Do you watch the behaviour of both CPU time and %Progress on the Tasks tab to see if everything looks normal? How about writing down the two values and checking them again a couple of hours later to see what is happening? That would be a useful thing to do.
When that extra long running result finally finished, you got these messages:-
What happened here is quite revealing. The long running result finished at 1:30:55 on August 7 and BOINC immediately resumed round-robin scheduling. The result was uploaded and eventually reported and new work was downloaded. Also a new executable was downloaded because there had been a version change in the app. As soon as the new work was commenced, BOINC went back into EDF (Earliest Deadline First) mode because the estimate of how long the result would take had been poisoned by the previous long running result. BOINC will correct this itself over (a very long) time, but if it were my machine, I'd correct it manually once I was sure that the new result was processing more normally. You can see that the new result is probably going OK because on August 10 the estimate of remaining crunch time must have dropped considerably, allowing BOINC to get out of EDF and back to the normal round-robin scheduling.
It would be helpful if you could let us know the CPU time, %Progress and the estimate of remaining crunch time for the current result. Also have a look in your client_state.xml file and see what is the current value for the variable called "duration_correction_factor" (DCF). I suspect it will have a value greater than 3.0 when it probably should be less than 1.0.
Once this information is known, it should be possible to tell if things are getting back to normal.
Cheers,
Gary.