I am wondering as to why (I am or Have not been recieving any new work?
Just a guess - were you running the Beta application? If so, you need to delete the app_info.xml file from your Einstein folder (and restart BOINC). But, if you weren't using the Beta app, we will need a little more info from you before we can help - like the messages from under your BOINC Manager "Messages" tab (also after a BOINC restart).
It's been days since i've received workunits.
What's going on?
09-01-06 23:59:34||request_reschedule_cpus: project op
09-01-06 23:59:36||request_reschedule_cpus: project op
09-01-06 23:59:37||request_reschedule_cpus: project op
09-01-06 23:59:38||request_reschedule_cpus: project op
09-01-06 23:59:39|rosetta@home|Sending scheduler request to http://boinc.bakerlab.org/rosetta_cgi/cgi
09-01-06 23:59:39|rosetta@home|Reason: Requested by user
09-01-06 23:59:39|rosetta@home|Note: not requesting new work or reporting results
09-01-06 23:59:39||request_reschedule_cpus: project op
09-01-06 23:59:44|rosetta@home|Scheduler request to http://boinc.bakerlab.org/rosetta_cgi/cgi succeeded
09-01-06 23:59:50|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
09-01-06 23:59:50|climateprediction.net|Reason: Requested by user
09-01-06 23:59:50|climateprediction.net|Note: not requesting new work or reporting results
09-01-06 23:59:55|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
10-01-06 00:00:00|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
10-01-06 00:00:00|LHC@home|Reason: Requested by user
10-01-06 00:00:00|LHC@home|Note: not requesting new work or reporting results
10-01-06 00:00:05|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
10-01-06 00:00:10|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
10-01-06 00:00:10|SETI@home|Reason: Requested by user
10-01-06 00:00:10|SETI@home|Note: not requesting new work or reporting results
10-01-06 00:00:15|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
10-01-06 00:00:20|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
10-01-06 00:00:20|Einstein@Home|Reason: Requested by user
10-01-06 00:00:20|Einstein@Home|Note: not requesting new work or reporting results
10-01-06 00:00:25|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
It's been days since i've received workunits.
What's going on?
Exit BOINC completely. Relaunch. Wait two minutes. Look in "messages" tab for "overcommitted" or "earliest deadline first" messages. Your cache is probably set too large for the number of projects you have attached, _or_ you have just built up a huge debt for one project, and it's trying to work that out.
If you paste all the messages here, and tell us what your projects are, what their resource shares are, what your cache setting is, and how many WUs from each project you have and their shortest deadlines, plus what is running at present, we can narrow down exactly what the problem is. 100 to 1 though that it's too large a cache; with five projects (at least) the maximum you should have is 3 days, and even that would be tight.
10-01-06 00:12:04||Starting BOINC client version 5.2.6 for windows_intelx86
10-01-06 00:12:04||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
10-01-06 00:12:04||Data directory: C:\\Program Files\\BOINC
10-01-06 00:12:04||Invalid account filename: account_.xml
10-01-06 00:12:05||Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 CPU 2.66GHz
10-01-06 00:12:05||Memory: 255.48 MB physical, 718.00 MB virtual
10-01-06 00:12:05||Disk: 70.51 GB total, 10.33 GB free
10-01-06 00:12:05|rosetta@home|Computer ID: 102019; location: ; project prefs: default
10-01-06 00:12:05|climateprediction.net|Computer ID: 161076; location: work; project prefs: default
10-01-06 00:12:05|Einstein@Home|Computer ID: 510664; location: home; project prefs: default
10-01-06 00:12:05|LHC@home|Computer ID: 55578; location: 0; project prefs: default
10-01-06 00:12:05|SETI@home|Computer ID: 462722; location: work; project prefs: default
10-01-06 00:12:05||General prefs: from LHC@home (last modified 2006-01-09 23:56:20)
10-01-06 00:12:05||General prefs: no separate prefs for 0; using your defaults
10-01-06 00:12:05||Remote control not allowed; using loopback address
10-01-06 00:12:05|climateprediction.net|Resuming computation for result sulphur_ga6k_000759692_0 using sulphur_cycle version 422
10-01-06 00:12:05||Suspending work fetch because computer is overcommitted.
10-01-06 00:12:05||Using earliest-deadline-first scheduling because computer is overcommitted.
10-01-06 00:12:13|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
10-01-06 00:12:13|climateprediction.net|Reason: To send trickle-up message
10-01-06 00:12:13|climateprediction.net|Note: not requesting new work or reporting results
10-01-06 00:12:16|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
My preferences:
Processor usage
Do work while computer is running on batteries?
(matters only for portable computers) no
Do work while computer is in use? no
Do work only after computer is idle for 2 minutes
Do work only between the hours of (no restriction)
Leave applications in memory while preempted?
(suspended applications will consume swap space if 'yes') yes
Switch between applications every
(recommended: 60 minutes) 60 minutes
On multiprocessors, use at most 2 processors
Disk and memory usage
Use no more than 1.5 GB disk space
Leave at least 2 GB disk space free
Use no more than 50% of total disk space
Write to disk at most every 60 seconds
Use no more than 50% of total virtual memory
Network usage
Connect to network about every
(determines size of work cache; maximum 10 days) 0.1 days
Confirm before connecting to Internet?
(matters only if you have a modem, ISDN or VPN connection) no
Disconnect when done?
(matters only if you have a modem, ISDN or VPN connection) no
Maximum download rate: no limit
Maximum upload rate: no limit
Use network only between the hours of
Enforced by versions 4.46 and greater (no restriction)
Skip image file verification?
Check this ONLY if your Internet provider modifies image files (UMTS does this, for example).
Skipping verification reduces the security of BOINC. no
10-01-06 00:12:05|climateprediction.net|Resuming computation for result sulphur_ga6k_000759692_0 using sulphur_cycle version 422
10-01-06 00:12:05||Suspending work fetch because computer is overcommitted.
10-01-06 00:12:05||Using earliest-deadline-first scheduling because computer is overcommitted.
Well, I lose my bet that it's because of too large a cache... :-( And it's not just a debt situation.
You show overcommitted, and working entirely on CPDN; but this is a "sulphur" WU, which I don't think _can_ be more than a month or two old, and should have at least 10 months left to deadline. This makes me think there is some reason BOINC thinks that even in 10 months, it's not going to have enough time to finish the CPDN result. The only setting I see that _could_ lead to this is the "Do work only after computer is idle for 2 minutes" part. If for some reason your computer was not able to give BOINC any reasonable amount of time, for a day or so, the "active frac" could be very low. Here is the bottom part of the page for one of my hosts, from SETI:
% of time BOINC client is running 86.8507 %
While BOINC running, % of time work is allowed 99.9806 %
Average CPU efficiency 0.969016
Result duration correction factor 0.181145
If that "While BOINC running, % of time work is allowed" figure is very small, you may need to manually correct it. (It will correct itself, but that could take days, during which time you'll run only CPDN.) If that number is something like 0.5%, then you can completely exit BOINC, open the client_state.xml file in the BOINC folder using Notepad (or equivalent text editor; NOT a word processor) and about 30 lines down you'll see "active_frac". Change that to a "1", save and close, then restart BOINC.
If the numbers for your computer are close to the numbers for mine, then I'm totally lost - hopefully someone else will have some ideas. It will help if you tell us what the resource shares are for the projects and how many WUs from each project you have in your cache (probably none) for anything other than CPDN.
not recieving any new work what's up
)
Just a guess - were you running the Beta application? If so, you need to delete the app_info.xml file from your Einstein folder (and restart BOINC). But, if you weren't using the Beta app, we will need a little more info from you before we can help - like the messages from under your BOINC Manager "Messages" tab (also after a BOINC restart).
It's been days since i've
)
It's been days since i've received workunits.
What's going on?
09-01-06 23:59:34||request_reschedule_cpus: project op
09-01-06 23:59:36||request_reschedule_cpus: project op
09-01-06 23:59:37||request_reschedule_cpus: project op
09-01-06 23:59:38||request_reschedule_cpus: project op
09-01-06 23:59:39|rosetta@home|Sending scheduler request to http://boinc.bakerlab.org/rosetta_cgi/cgi
09-01-06 23:59:39|rosetta@home|Reason: Requested by user
09-01-06 23:59:39|rosetta@home|Note: not requesting new work or reporting results
09-01-06 23:59:39||request_reschedule_cpus: project op
09-01-06 23:59:44|rosetta@home|Scheduler request to http://boinc.bakerlab.org/rosetta_cgi/cgi succeeded
09-01-06 23:59:50|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
09-01-06 23:59:50|climateprediction.net|Reason: Requested by user
09-01-06 23:59:50|climateprediction.net|Note: not requesting new work or reporting results
09-01-06 23:59:55|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
10-01-06 00:00:00|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
10-01-06 00:00:00|LHC@home|Reason: Requested by user
10-01-06 00:00:00|LHC@home|Note: not requesting new work or reporting results
10-01-06 00:00:05|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
10-01-06 00:00:10|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
10-01-06 00:00:10|SETI@home|Reason: Requested by user
10-01-06 00:00:10|SETI@home|Note: not requesting new work or reporting results
10-01-06 00:00:15|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
10-01-06 00:00:20|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
10-01-06 00:00:20|Einstein@Home|Reason: Requested by user
10-01-06 00:00:20|Einstein@Home|Note: not requesting new work or reporting results
10-01-06 00:00:25|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
RE: It's been days since
)
Exit BOINC completely. Relaunch. Wait two minutes. Look in "messages" tab for "overcommitted" or "earliest deadline first" messages. Your cache is probably set too large for the number of projects you have attached, _or_ you have just built up a huge debt for one project, and it's trying to work that out.
If you paste all the messages here, and tell us what your projects are, what their resource shares are, what your cache setting is, and how many WUs from each project you have and their shortest deadlines, plus what is running at present, we can narrow down exactly what the problem is. 100 to 1 though that it's too large a cache; with five projects (at least) the maximum you should have is 3 days, and even that would be tight.
Last messages are (after
)
Last messages are (after restart):
10-01-06 00:12:04||Starting BOINC client version 5.2.6 for windows_intelx86
10-01-06 00:12:04||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
10-01-06 00:12:04||Data directory: C:\\Program Files\\BOINC
10-01-06 00:12:04||Invalid account filename: account_.xml
10-01-06 00:12:05||Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 CPU 2.66GHz
10-01-06 00:12:05||Memory: 255.48 MB physical, 718.00 MB virtual
10-01-06 00:12:05||Disk: 70.51 GB total, 10.33 GB free
10-01-06 00:12:05|rosetta@home|Computer ID: 102019; location: ; project prefs: default
10-01-06 00:12:05|climateprediction.net|Computer ID: 161076; location: work; project prefs: default
10-01-06 00:12:05|Einstein@Home|Computer ID: 510664; location: home; project prefs: default
10-01-06 00:12:05|LHC@home|Computer ID: 55578; location: 0; project prefs: default
10-01-06 00:12:05|SETI@home|Computer ID: 462722; location: work; project prefs: default
10-01-06 00:12:05||General prefs: from LHC@home (last modified 2006-01-09 23:56:20)
10-01-06 00:12:05||General prefs: no separate prefs for 0; using your defaults
10-01-06 00:12:05||Remote control not allowed; using loopback address
10-01-06 00:12:05|climateprediction.net|Resuming computation for result sulphur_ga6k_000759692_0 using sulphur_cycle version 422
10-01-06 00:12:05||Suspending work fetch because computer is overcommitted.
10-01-06 00:12:05||Using earliest-deadline-first scheduling because computer is overcommitted.
10-01-06 00:12:13|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
10-01-06 00:12:13|climateprediction.net|Reason: To send trickle-up message
10-01-06 00:12:13|climateprediction.net|Note: not requesting new work or reporting results
10-01-06 00:12:16|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
My preferences:
Processor usage
Do work while computer is running on batteries?
(matters only for portable computers) no
Do work while computer is in use? no
Do work only after computer is idle for 2 minutes
Do work only between the hours of (no restriction)
Leave applications in memory while preempted?
(suspended applications will consume swap space if 'yes') yes
Switch between applications every
(recommended: 60 minutes) 60 minutes
On multiprocessors, use at most 2 processors
Disk and memory usage
Use no more than 1.5 GB disk space
Leave at least 2 GB disk space free
Use no more than 50% of total disk space
Write to disk at most every 60 seconds
Use no more than 50% of total virtual memory
Network usage
Connect to network about every
(determines size of work cache; maximum 10 days) 0.1 days
Confirm before connecting to Internet?
(matters only if you have a modem, ISDN or VPN connection) no
Disconnect when done?
(matters only if you have a modem, ISDN or VPN connection) no
Maximum download rate: no limit
Maximum upload rate: no limit
Use network only between the hours of
Enforced by versions 4.46 and greater (no restriction)
Skip image file verification?
Check this ONLY if your Internet provider modifies image files (UMTS does this, for example).
Skipping verification reduces the security of BOINC. no
Thank you for your help...
RE: 10-01-06
)
Well, I lose my bet that it's because of too large a cache... :-( And it's not just a debt situation.
You show overcommitted, and working entirely on CPDN; but this is a "sulphur" WU, which I don't think _can_ be more than a month or two old, and should have at least 10 months left to deadline. This makes me think there is some reason BOINC thinks that even in 10 months, it's not going to have enough time to finish the CPDN result. The only setting I see that _could_ lead to this is the "Do work only after computer is idle for 2 minutes" part. If for some reason your computer was not able to give BOINC any reasonable amount of time, for a day or so, the "active frac" could be very low. Here is the bottom part of the page for one of my hosts, from SETI:
% of time BOINC client is running 86.8507 %
While BOINC running, % of time work is allowed 99.9806 %
Average CPU efficiency 0.969016
Result duration correction factor 0.181145
If that "While BOINC running, % of time work is allowed" figure is very small, you may need to manually correct it. (It will correct itself, but that could take days, during which time you'll run only CPDN.) If that number is something like 0.5%, then you can completely exit BOINC, open the client_state.xml file in the BOINC folder using Notepad (or equivalent text editor; NOT a word processor) and about 30 lines down you'll see "active_frac". Change that to a "1", save and close, then restart BOINC.
If the numbers for your computer are close to the numbers for mine, then I'm totally lost - hopefully someone else will have some ideas. It will help if you tell us what the resource shares are for the projects and how many WUs from each project you have in your cache (probably none) for anything other than CPDN.