Status 4 mins old, 116,377 MBs ready to send, still getting no jobs available. This happens often for quite some time, I think there's something wrong. At least it's unnecessary extra work for the servers, and the message is wrong since there's plenty of jobs ready.

Status 4 mins old, 116,377 MBs ready to send, still getting no jobs available. This happens often for quite some time, I think there's something wrong. At least it's unnecessary extra work for the servers, and the message is wrong since there's plenty of jobs ready.

"Ready" and "available" are two different things in the BOINC world. "Ready" means the Transitioner has set up the database for the tasks, and they haven't been assigned to a host yet. The number in "ready" state can be any amount, but the project limits new work creation to keep the storage requirement reasonable.

"Available" means the Feeder has told the Scheduler about some tasks which haven't yet been sent, there are never more than 100 of those. When the servers are busy, sometimes the Feeder can't refill that list as often as needed to satisfy demand...

                                                                 Joe

My problem is not running out of work, yet, but inability to upload.
Losing credit isn't that important.
But missing the deadline because the servers can't cope means they'll go out for re-calculation again ?
That's just more bandwidth, and more crunching, that could be employed usefully.

I have only two CPU workunits left, then it's CUDA only for a couple of dya, then I'm out.
Just sitting with HTTP or Connect() errors waiting to upload.

---

PAul

[IMG][/IMG]

My problem is not running out of work, yet, but inability to upload.
Losing credit isn't that important.
But missing the deadline because the servers can't cope means they'll go out for re-calculation again ?
That's just more bandwidth, and more crunching, that could be employed usefully.

I have only two CPU workunits left, then it's CUDA only for a couple of dya, then I'm out.
Just sitting with HTTP or Connect() errors waiting to upload.

Hmmmmmmm....
I just checked all 8 rigs, and I have no hanging uploads.....
Bandwidth seems to have subsided...
Have you hit the 'retry' button on the uploads you have in the transfers tab?

---

"Time is simply the mechanism that keeps everything from happening all at once."

Have you hit the 'retry' button on the uploads you have in the transfers tab?

Sometimes a flushdns is better, or even a reboot.

Have you hit the 'retry' button on the uploads you have in the transfers tab?

Sometimes a flushdns is better, or even a reboot.

A reboot always beats a flush or a full house........LOL.

---

"Time is simply the mechanism that keeps everything from happening all at once."

This task as well as others I've completed, don't seem to be validating ATM either, even though they've been completed by myself and my wingman.

---

This task as well as others I've completed, don't seem to be validating ATM either, even though they've been completed by myself and my wingman.

Well, hang in there......

There's only about 147,000 of them left waiting to be processed......

The kitties are turning their last ones......got a day to go on one cruncher, a few days last on some others......

The kitties are not happy.

As to the state of the validators and other related problems.......

They seem to have sufficient HP, but hey are a bit blind.....

Kittie outta control...... LOL...

---

"Time is simply the mechanism that keeps everything from happening all at once."

latest info 144,000+ waiting to be sent at 10:50 UTC however the time was done 35 minutes before that so it looks like the status page is wrong as well. Getting no downloads since around 8:00 UTC have a few lines of no new work luckily I have got about a days work still to do.

---

Two bits: this morning, as is frequently the case, my work gets uploaded to the servers but the 'reporting' step is failing and has been for several hours. I don't understand/remember what the difference in the two steps is, except that the number ready to report on my client is increasing and I'm not getting new work. I only hook up for a few hours each day, so soon all this work will probably roll over until tomorroow. Not worried, just fueling the discussion.

Mine finally went in. All reported and happy now. :)

---

PROUD MEMBER OF Team Starfire World BOINC

Two bits: this morning, as is frequently the case, my work gets uploaded to the servers but the 'reporting' step is failing and has been for several hours. I don't understand/remember what the difference in the two steps is, except that the number ready to report on my client is increasing and I'm not getting new work. I only hook up for a few hours each day, so soon all this work will probably roll over until tomorroow. Not worried, just fueling the discussion.

"Uploading" puts the actual result file on the upload server (which may not be the same machine as the download server or the scheduler). It's a straight HTTP "put" with the minimum amount of processing. It does not update the scheduler database.

Reporting updates the scheduler database. When the scheduler has enough results, that signals the validator to check.

The upload process is simple, and there is no advantage to allowing multiple uploads per contact.

The scheduler benefits from combining reports, because it does not have to repeatedly access the host record, and because it can post multiple results without closing and reopening the database.

It also means that the project can continue to collect uploads work while the scheduler is down for maintenance or due to a failure.

The whole project does not have to be 100% functional 100% of the time for things to work -- as is often reported on topics like this.

---

Geez, it figures, I Installed the combined Opti Apps for MB and AP, and now i cant get any work to see if i installed it correctly.
I just checked and have a WU but it say seti enhanced not anonymous platform, so i need to find out why.

---

[/quote]

Old James

Geez, it figures, I Installed the combined Opti Apps for MB and AP, and now i cant get any work to see if i installed it correctly.
I just checked and have a WU but it say seti enhanced not anonymous platform, so i need to find out why.

The "anonymous platform" message appears only at the beginning of your BM Messages after a restart as:

12/06/2009 16:28:29	SETI@home	Found app_info.xml; using anonymous platform
12/06/2009 16:28:29		Not using a proxy

The WU descriptions in BM says "setiathome_enhanced 6.03" for MB WU's. If this is your Windows machine, then the easiest way to see what is doing the crunching is to look in Windows Task Manager. If it your Darwin rig, then I suppose there is something equivalent to Task Manager?

F.

---

thanks i will look in my windows comp. for that message.

---

[/quote]

Old James

s6/12/2009 2:58:28 PM Starting BOINC client version 6.6.31 for windows_intelx86
6/12/2009 2:58:28 PM log flags: task, file_xfer, sched_ops
6/12/2009 2:58:28 PM Libraries: libcurl/7.19.4 OpenSSL/0.9.8j zlib/1.2.3
6/12/2009 2:58:28 PM Data directory: C:\Documents and Settings\All Users\Application Data\BOINC
6/12/2009 2:58:28 PM Running under account Owner
6/12/2009 2:58:28 PM Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 CPU 2.53GHz [x86 Family 15 Model 2 Stepping 7]
6/12/2009 2:58:28 PM Processor features: fpu tsc sse sse2 mmx
6/12/2009 2:58:28 PM OS: Microsoft Windows XP: Home x86 Edition, Service Pack 3, (05.01.2600.00)
6/12/2009 2:58:28 PM Memory: 2.00 GB physical, 3.85 GB virtual
6/12/2009 2:58:28 PM Disk: 76.33 GB total, 66.16 GB free
6/12/2009 2:58:28 PM Local time is UTC -4 hours
6/12/2009 2:58:29 PM No CUDA devices found
6/12/2009 2:58:29 PM No coprocessors
6/12/2009 2:58:29 PM Not using a proxy
6/12/2009 2:58:30 PM SETI@home URL: http://setiathome.berkeley.edu/; Computer ID: 4975817; location: home; project prefs: default
6/12/2009 2:58:30 PM SETI@home General prefs: from SETI@home (last modified 03-Apr-2009 11:01:52)
6/12/2009 2:58:30 PM SETI@home Computer location: home
6/12/2009 2:58:30 PM SETI@home General prefs: no separate prefs for home; using your defaults
6/12/2009 2:58:30 PM Preferences limit memory usage when active to 1022.90MB
6/12/2009 2:58:30 PM Preferences limit memory usage when idle to 2045.80MB
6/12/2009 2:58:30 PM Preferences limit disk usage to 38.16GB
6/12/2009 2:58:31 PM SETI@home Restarting task 21mr09ad.11794.4162.16.8.67_0 using setiathome_enhanced version 603
this is what i have after a restart.

---

[/quote]

Old James

- <app_info>
- <app>
<name>setiathome_enhanced</name>
</app>
- <file_info>
<name>AK_v8_win_SSE2.exe</name>
<executable />
</file_info>
- <app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
- <file_ref>
<file_name>AK_v8_win_SSE2.exe</file_name>
<main_program />
</file_ref>
</app_version>
- <app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
- <file_ref>
<file_name>AK_v8_win_SSE2.exe</file_name>
<main_program />
</file_ref>
</app_version>
- <app>
<name>astropulse</name>
</app>
- <file_info>
<name>ap_5.00r69_SSE.exe</name>
<executable />
</file_info>
- <file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable />
</file_info>
- <app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
- <file_ref>
<file_name>ap_5.00r69_SSE.exe</file_name>
<main_program />
</file_ref>
- <file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
</app_info>
this is the ap info file

---

[/quote]

Old James

"Ready" and "available" are two different things in the BOINC world. "Ready" means the Transitioner has set up the database for the tasks, and they haven't been assigned to a host yet. The number in "ready" state can be any amount, but the project limits new work creation to keep the storage requirement reasonable.

"Available" means the Feeder has told the Scheduler about some tasks which haven't yet been sent, there are never more than 100 of those. When the servers are busy, sometimes the Feeder can't refill that list as often as needed to satisfy demand...

                                                                 Joe

OK, makes sense. Than my next question is if there have been many new users the last I guess about 2-3 weeks? Be course before those 2-3 weeks I didn't get all these no jobs available, only now and then.

(Just come to think that it could be the lack of APs and people now get much more MBs)

I've taken out all the -'s that shouldn't be there and the Extra Spaces
(which are known as Claggy's Space), it happen's because the app_info
was edit with I.E, only use notepad as that formats it properly.
It's a bit out of Date, as there are none of the old astropulse (5.00) work about,
and you don't have entries for the astropulse_v5, let alone v505.
You could try the new Lunatics Installer to update the apps.

<app_info>
<app>
<name>setiathome_enhanced</name> 
</app>
<file_info>
<name>AK_v8_win_SSE2.exe</name> 
<executable/> 
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name> 
<version_num>528</version_num> 
<file_ref>
<file_name>AK_v8_win_SSE2.exe</file_name> 
<main_program/> 
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name> 
<version_num>603</version_num> 
<file_ref>
<file_name>AK_v8_win_SSE2.exe</file_name> 
<main_program/> 
</file_ref>
</app_version>
<app>
<name>astropulse</name> 
</app>
<file_info>
<name>ap_5.00r69_SSE.exe</name> 
<executable/> 
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name> 
<executable/> 
</file_info>
<app_version>
<app_name>astropulse</app_name> 
<version_num>500</version_num> 
<file_ref>
<file_name>ap_5.00r69_SSE.exe</file_name> 
<main_program/> 
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name> 
</file_ref>
</app_version>
</app_info>

Claggy

"Ready" and "available" are two different things in the BOINC world. "Ready" means the Transitioner has set up the database for the tasks, and they haven't been assigned to a host yet. The number in "ready" state can be any amount, but the project limits new work creation to keep the storage requirement reasonable.

"Available" means the Feeder has told the Scheduler about some tasks which haven't yet been sent, there are never more than 100 of those. When the servers are busy, sometimes the Feeder can't refill that list as often as needed to satisfy demand...

                                                                 Joe

OK, makes sense. Than my next question is if there have been many new users the last I guess about 2-3 weeks? Be course before those 2-3 weeks I didn't get all these no jobs available, only now and then.

SETI@Home does not control the telescope while recording is done, some other study controls the telescope and we're all along for the ride.

Some of the studies produce work units that are "short" -- they just don't take very long to search.

When we hit a batch of "shorties" the project tends to run low on work.

Please remember too that, unlike most internet applications, consumers are not waiting to buy a product, and if the project can't supply work, the BOINC client will wait a bit and check again. It isn't really a problem.

I normally have my cache size set around 4 days (4 "extra days") and I can't remember when I last ran out of work.

---