Fools walk in where angels fear to tread...

About to install it now.

---

GL! I did too since I needed to resolve my installation setting issues anyway. So far so good... (crossing fingers) XXXXX

---

15/05/2005 12:53:00||Too many projects have work.
15/05/2005 12:53:00||New work fetch policy: no work fetch allowed.

At least it now has a full cache... (2 CPDN units again... got to wonder about that one). Let's see if it wants to download any additional work when my cache clears!

---

Three hosts updated to 4.41.

On one something odd:

15/05/2005 12:11:59||Finished CPU benchmarks
15/05/2005 12:11:59|SETI@home|Resuming computation for result 19dc04aa.1338.15010.786080.191_1 using setiathome version 4.11
15/05/2005 12:11:59||Resuming computation and network activity
15/05/2005 12:11:59|SETI@home|Deferring communication with project for 1 weeks, 4 days, 0 hours, 48 minutes, and 6 seconds
15/05/2005 12:11:59||schedule_cpus: must schedule
15/05/2005 12:12:25||request_reschedule_cpus: project op
15/05/2005 12:12:25||schedule_cpus: must schedule

Deferred for 1 week 4 days !?

There were no communication problems in the past few days.
Some variable not properly initialised?

---

[Insert general disclaimer] 4.41 is developmental software, use at own risk. blah blah. stick with "official release" versions if you're squimish.

Happy now AZ?

Is anyone one else able to do a manual Project Update? I'm not.

All I get is this:

5/15/2005 7:28:11 AM||request_reschedule_cpus: project op
5/15/2005 7:28:11 AM||schedule_cpus: must schedule

No problems here, Tony:

15/05/2005 13:40:54|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
15/05/2005 13:40:55|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
15/05/2005 13:41:36|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/05/2005 13:41:37|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded

---

<blockquote>[Insert general disclaimer] 4.41 is developmental software, use at own risk. blah blah. stick with "official release" versions if you're squimish.

Happy now AZ?

Is anyone one else able to do a manual Project Update? I'm not.

All I get is this:

5/15/2005 7:28:11 AM||request_reschedule_cpus: project op
5/15/2005 7:28:11 AM||schedule_cpus: must schedule
</blockquote>

Me too...damn development software...back to 4.40 I go. Gotta love it!

Live long and crunch!

---

Paul
(S@H1 8888)
And proud of it!

One out of 3 hosts won't update (the one with the 1 week 4 day defer).

Not panicking yet, It's got a 3 day cache. I'll see what happens when one or two have uploaded and the cache is re-calculated.

---

<blockquote>Three hosts updated to 4.41.

On one something odd:

15/05/2005 12:11:59||Finished CPU benchmarks
15/05/2005 12:11:59|SETI@home|Resuming computation for result 19dc04aa.1338.15010.786080.191_1 using setiathome version 4.11
15/05/2005 12:11:59||Resuming computation and network activity
</blockquote>
Another strange thing: using setiathome version 4.11.??!!

The last download on my host is from 15 May 2005 11:06:33 UTC and will still be crunched by setiathome version 4.09.

Using Boinc v4.30.

<blockquote><blockquote>Three hosts updated to 4.41.

On one something odd:

15/05/2005 12:11:59||Finished CPU benchmarks
15/05/2005 12:11:59|SETI@home|Resuming computation for result 19dc04aa.1338.15010.786080.191_1 using setiathome version 4.11
15/05/2005 12:11:59||Resuming computation and network activity
</blockquote>
Another strange thing: using setiathome version 4.11.??!!

The last download on my host is from 15 May 2005 11:06:33 UTC and will still be crunched by setiathome version 4.09.

Using Boinc v4.30.</blockquote>

4.11 is one of the optimized clients.
I don't know where you are getting the "will still be crunched by setiathome version 4.09" bit from though.
Assuming you are running one of the optimized hosts, I guess this information must be comming from the app_info.xml - AFAIK one version had entries for both 4.09 app and 4.11 to prevent loss of outstanding 4.09 work in the cache.

---

<blockquote>Is anyone one else able to do a manual Project Update? I'm not.</blockquote>
No, not any more with version 4.41.



But... it looks like the "connection failed popup window error" is solved on one of my PC's. To test it I rebooted 5 times, no error until now.
The other PC's that had the problem I can not access until Tuesday.

Anyone else seen this improvement?

(maybe I was just lucky and at the next reboot it's there again ;-) )

Hi

Yes I have seen this issue

it is partly resolved. You can't connect with pc name anymore.

I have posted my finding in another thread "Minor Issues with 4.41"

WOuld like to know the stated procedure for running with remote access allowed.

as this may have something to do with the issue.

The client also logs wanting more work. when I have set no new work. I believe the feature is working thou.

---

Hi All

Just a note of Caution

I think the seti upload scheduler has gone AWOL

I can't return results since 12.19 UTC

I don't think this is anything to do with the client 4.41

---

<blockquote>WOuld like to know the stated procedure for running with remote access allowed.</blockquote>
Do you mean when starting Boinc you get a message remote controll is not allowed?

For remote control you need a text file "remote_hosts.cfg" in your Boinc folder, containing the IP addresses (one address per line) of the computers that are allowed to contact Boinc on your PC.

:-)

<blockquote>Hi All

Just a note of Caution

I think the seti upload scheduler has gone AWOL

I can't return results since 12.19 UTC

I don't think this is anything to do with the client 4.41</blockquote>

Okay, soon after installing 4.41, it finished up WU started on 4.40 for mine, & stated that it had uploaded in messages, but it kept sitting in the manager. Update didn't clear it, closing it and restarting didn't clear it, but when the next WU was ready to upload and had finished uploading they both cleared. Thanks for sharing this, maybe that was it instead of 4.41. Will see on the next couple.

---

From my testing, it seems that if a project requires work, a manual update will work:

15/05/2005 10:51:23 PM||request_reschedule_cpus: project op
15/05/2005 10:51:23 PM||schedule_cpus: must schedule
15/05/2005 10:51:23 PM||earliest deadline: 1116537960.000000 h0007A_1_64066_3
15/05/2005 10:51:24 PM|LHC@home|Requesting 530264.86 seconds of work
15/05/2005 10:51:24 PM|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
15/05/2005 10:51:28 PM|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded

However, if a project has enough work, or is close to capacity, it seems takes a couple of tries to get it to send the RPC.

---

Hi

4.42 will comming soon i think.

I remember in beta times.

greetz Mike

---

With each crime and every kindness we birth our future.

I used BOINC 4.3x and most of them worked, then 4.40 didn't work and reverted to 4.25. Should I stay there (ie, is 4.41 buggy beyond use?)

---

<a href="http://tinyurl.com/9hemz"><img src="http://www.boincsynergy.com/images/stats/comb-1441.jpg"></img></a>

<blockquote>Hi All

Just a note of Caution

I think the seti upload scheduler has gone AWOL

I can't return results since 12.19 UTC

I don't think this is anything to do with the client 4.41</blockquote>

Works fine in 4.25

---

<a href="http://tinyurl.com/9hemz"><img src="http://www.boincsynergy.com/images/stats/comb-1441.jpg"></img></a>

Yeah, Upload does not work on 4.41. Reverted back to 4.26, uploaded, and renewed my caches of protien, Einstein, and Seti. Still no LHC Wu's.

Respectfully,

Rocky

---

www.boincsynergy.com