News

October 9, 2004
A problem with file uploads has existed for the last few days. This problem causes file uploads to fail. We now understand the problem and are working on a fix - it will probably require upgrading your BOINC client. Please stay tuned.

> News
>
> October 9, 2004
> A problem with file uploads has existed for the last few days. This problem
> causes file uploads to fail. We now understand the problem and are working on
> a fix - it will probably require upgrading your BOINC client. Please stay
> tuned.
>
>

Here we go again....! Just another umpteenth client upgrade. It figures....

L8R....

---




Rick A. - BOINCing right along now.... It can only get better!

"There is no fate except that which we create for ourselves."

Live Long and Prosper....

>
> Here we go again....! Just another umpteenth client upgrade. It figures....
>

Now, now play nice...they'll provide a fix...

>
> >
> > Here we go again....! Just another umpteenth client upgrade. It
> figures....
> >
>
> Now, now play nice...they'll provide a fix...
>
>

Uhhh.... Where did you find this message? I just checked the front page and there is no message stating this for todays date, 10/9/04.

L8R....

---




Rick A. - BOINCing right along now.... It can only get better!

"There is no fate except that which we create for ourselves."

Live Long and Prosper....

It's on the front page now

> Uhhh.... Where did you find this message? I just checked the front page and
> there is no message stating this for todays date, 10/9/04.
>
>

Read my lips...:)

>
> >
> > Here we go again....! Just another umpteenth client upgrade. It
> figures....
> >
>
> Now, now play nice...they'll provide a fix...
>

But it will be a fix to Boinc 4.1x, and not 4.09..

What this means is we'll have to "discover" all the other stuff in 4.1x which "kinda works".. Look at when win98 got really broken a few weeks back..

If it's Boinc, why is LHC working just fine? (when they have work) and why did Seti work fine until last week?


They changed something on the server which now requires a client change, is my bet!

> >
> > >
> > > Here we go again....! Just another umpteenth client upgrade. It
> > figures....
> > >
> >
> > Now, now play nice...they'll provide a fix...
> >
>
> But it will be a fix to Boinc 4.1x, and not 4.09..
>
> What this means is we'll have to "discover" all the other stuff in 4.1x which
> "kinda works".. Look at when win98 got really broken a few weeks back..
>
> If it's Boinc, why is LHC working just fine? (when they have work) and why did
> Seti work fine until last week?
>
>

BOINC works just fine, it's the SETI Client v4.05 that is somehow hosed up, from what I have interpreted.

L8R....

---




Rick A. - BOINCing right along now.... It can only get better!

"There is no fate except that which we create for ourselves."

Live Long and Prosper....

> But it will be a fix to Boinc 4.1x, and not 4.09..


First you "bitch" that they are not fixing it, then you "bitch" when they try to...:)

P.S. Perhaps not the swiftest response by SETI, but response never the less. :)
No offence...:)

> BOINC works just fine, it's the SETI Client v4.05 that is somehow hosed up,
> from what I have interpreted.

Read the news again:

"it will probably require upgrading your BOINC client. Please stay tuned."

Not "seti client/cruncher" but BOINC Client...

On Linux, I'm still running the same Seti Cruncher as I downloaded a long time back (4.02).. And that's the box I've seen the problem most often! They are saying the CC!

>
> > But it will be a fix to Boinc 4.1x, and not 4.09..
>
>
> First you "bitch" that they are not fixing it, then you "bitch" when they try
> to...:)
>
> P.S. Perhaps not the swiftest response by SETI, but response never the less.
> :)
> No offence...:)
>


You must be a "newbie" as if it were a "fix to 4.09", it would probably go smoothly, but as a "fix to 4.1x" it will include untested code! 4.1x isn't bugfixes after 4.09, it's new code and functionality, which might be as green as a shamrock on St Patty's day!

It's not an inconsistant statement - it's called "fix what we're running" and not "fix what you have in development which is unstable in other areas"!

>
> > But it will be a fix to Boinc 4.1x, and not 4.09..
>
>
> First you "bitch" that they are not fixing it, then you "bitch" when they try
> to...:)
>
> P.S. Perhaps not the swiftest response by SETI, but response never the less.
> :)
> No offence...:)
>
>
>

The problem is if they fix Boinc to work with Seti, chances are they'll mess up LHC or CPDN.

> You must be a "newbie" as if it were a "fix to 4.09", it would probably go

Check my score... a sole...

>
> > BOINC works just fine, it's the SETI Client v4.05 that is somehow hosed
> up,
> > from what I have interpreted.
>
> Read the news again:
>
> "it will probably require upgrading your BOINC client. Please stay tuned."
>
> Not "seti client/cruncher" but BOINC Client...
>
> On Linux, I'm still running the same Seti Cruncher as I downloaded a long time
> back (4.02).. And that's the box I've seen the problem most often! They are
> saying the CC!
>
>

Yes, I discovered my blunder when I was in another thread. The CC will be upgraded again. Calm down, I'm only Vulcan. ;-) Even Vulcans can make an occasional error. :-(

L8R....

---




Rick A. - BOINCing right along now.... It can only get better!

"There is no fate except that which we create for ourselves."

Live Long and Prosper....

If you check the check-in notes daily for all the changes made to the boinc code, you will see that the latest bunch have involved changes to the server side, which can require an upgrade of the core client. This should come as no suprise or cause anyone problems. It is a very complex system and making a little change here in one section can have a huge effect in another and sometimes the effect is unforseen. So quit the bitchin', download and install the upgrade, or detach and uninstall and go run one of the other distributed computing systems.

> If you check the check-in notes daily for all the changes made to the boinc
> code, you will see that the latest bunch have involved changes to the server
> side, which can require an upgrade of the core client.

Uh... Seems the whole idea of BOINC was "multi project", and a change to server code on one requiring a change in client code could (and has) had adverse effects on the other projects!

Heck, Predictor is STILL moving from 3.0 to 4.0, and CPredictor has month long WU's! When will LHC adapt to the new client server code?

I don't read the CVS stuff, but, I sure as heck hope when the make server changes, it doesn't impact the running projects! (ok, I'm wrong, as what ever they did to seti impacted a boatload of users and a boatload of crunched wu's!)

The devs have not learned the meaning of "backward compatabile"!

Hey, two Seti WU's to go, and my queues are drained of seti (I won't "reset" or "detach" as I don't want to see someone wait 4 weeks for credits, as they might get thru!), and I just sit back with Seti....

Maybe the devs will graduate in Dec!

---

While we are "staying tuned" should we continue crunching units
knowing that they won't upload ??? When will be that new release ?
If it's in 10 days I won't be wasting my time crunching for nothing.
I am going to classic untill it is solved.

I see nothing to be affraid of in the 4.11 boinc client. I've been using it for the last 2 weeks or so on two boxes without issue, other than the last couple days when everyone has been having trouble. It's been working fine again for the last 24 hours.

Ned


2004-10-09 04:13:32 [---] Starting BOINC client version 4.11 for i686-pc-linux-gnu
2004-10-09 04:13:32 [SETI@home] Project prefs: no separate prefs for home; using your defaults
2004-10-09 04:13:32 [SETI@home] Host ID is XXXXXX
2004-10-09 04:13:32 [---] General prefs: from SETI@home (last modified 2004-10-07 10:03:08)
2004-10-09 04:13:32 [---] General prefs: no separate prefs for home; using your defaults
2004-10-09 04:13:35 [SETI@home] Starting result 14mr04aa.17223.18338.928404.102_2 using setiathome version 4.02
2004-10-09 09:12:18 [SETI@home] Computation for result 14mr04aa.17223.18338.928404.102 finished
2004-10-09 09:12:18 [SETI@home] Starting result 14mr04aa.17223.18338.928404.75_2 using setiathome version 4.02
2004-10-09 09:12:18 [SETI@home] Started upload of 14mr04aa.17223.18338.928404.102_2_0
2004-10-09 09:12:20 [SETI@home] Finished upload of 14mr04aa.17223.18338.928404.102_2_0
2004-10-09 09:12:20 [SETI@home] Throughput 41243 bytes/sec
2004-10-09 13:14:09 [SETI@home] Computation for result 14mr04aa.17223.18338.928404.75 finished
2004-10-09 13:14:09 [SETI@home] Starting result 14mr04aa.17223.18338.928404.77_0 using setiathome version 4.02
2004-10-09 13:14:09 [SETI@home] Started upload of 14mr04aa.17223.18338.928404.75_2_0
2004-10-09 13:14:11 [SETI@home] Finished upload of 14mr04aa.17223.18338.928404.75_2_0
2004-10-09 13:14:11 [SETI@home] Throughput 28071 bytes/sec
2004-10-09 17:22:53 [SETI@home] Computation for result 14mr04aa.17223.18338.928404.77 finished
2004-10-09 17:22:53 [SETI@home] Starting result 14mr04aa.17223.18338.928404.61_2 using setiathome version 4.02
2004-10-09 17:22:53 [SETI@home] Started upload of 14mr04aa.17223.18338.928404.77_0_0
2004-10-09 17:22:54 [SETI@home] Finished upload of 14mr04aa.17223.18338.928404.77_0_0
2004-10-09 17:22:54 [SETI@home] Throughput 40361 bytes/sec
2004-10-09 21:39:47 [SETI@home] Computation for result 14mr04aa.17223.18338.928404.61 finished
2004-10-09 21:39:47 [SETI@home] Starting result 14mr04aa.17223.18338.928404.76_1 using setiathome version 4.02
2004-10-09 21:39:47 [SETI@home] Started upload of 14mr04aa.17223.18338.928404.61_2_0
2004-10-09 21:39:48 [SETI@home] Finished upload of 14mr04aa.17223.18338.928404.61_2_0
2004-10-09 21:39:48 [SETI@home] Throughput 40189 bytes/sec
2004-10-10 01:38:25 [SETI@home] Computation for result 14mr04aa.17223.18338.928404.76 finished
2004-10-10 01:38:25 [SETI@home] Starting result 14mr04aa.17223.18338.928404.78_1 using setiathome version 4.02
2004-10-10 01:38:25 [SETI@home] Started upload of 14mr04aa.17223.18338.928404.76_1_0
2004-10-10 01:38:26 [SETI@home] Finished upload of 14mr04aa.17223.18338.928404.76_1_0
2004-10-10 01:38:26 [SETI@home] Throughput 40794 bytes/sec

---

*** My Guide to Compiling Optimised BOINC and SETI Clients ***
*** Download Optimised BOINC and SETI Clients for Linux Here ***

> If you check the check-in notes daily for all the changes made to the boinc
> code, you will see that the latest bunch have involved changes to the server
> side, which can require an upgrade of the core client. This should come as no
> suprise or cause anyone problems. It is a very complex system and making a
> little change here in one section can have a huge effect in another and
> sometimes the effect is unforseen. So quit the bitchin', download and install
> the upgrade, or detach and uninstall and go run one of the other distributed
> computing systems.
>
>

Check what check-in notes? And, what crawled up you arss to cause you to make such a statement as you last?

L8R....

---

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

> I see nothing to be affraid of in the 4.11 boinc client. I've been using it
> for the last 2 weeks or so on two boxes without issue, other than the last
> couple days when everyone has been having trouble. It's been working fine
> again for the last 24 hours.
>
> Ned
>

So, did you provide the same recommendation for Boinc 4.09 and SETI 4.05?