MORE PROBLEMS AT BERKELEY?

[Orange Kid]

All the Q's seem to be showing a lot of "problem" wu's and the stats are down

Set my Q to not connect to them for a while........

 

[micron]

 

[Confused]

Yeah, i have 2 problem results queued (out of a total of 2 results queued), and i can't get to the stats either. :|

I've also disabled my Queue connecting to Berkeley

ConfusedBW

 

[Poof]

It's like they're attention getters or something... Everytime things go smoothly, they do something to screw it up. :|

I'm seeing some weird "error code xxxxx" in my log. They can't leave well enough alone. :|

 

[paf077]

Well, I have had 5 problem Wus from work since Thursday and another 3 at home yersterday annd can't connet to Berzerkly's
stats page this morning!! :|

Do they really want people to crunch for them or NOT! :disgust:

 

[Poof]

They have this posted now at the site:

"? March 1, 2002 ?
OUTAGE NOTICE: There will be a network outage on Monday, 3/4/02, from 14:45 to 16:00 UT for local router maintenance. Our data server and web site will be unavailable during this time."

 

[JustStarting]

couple problem wu's here to. Nothing has uploaded since yesterday either.

 

[conjur]

Finally got my dual Athlon up and running again (took out my Promise Ultra133TX2 and a suspect HD) and fully expected to see a few WUs in the History log this morning but I see four Problem WUs and this in the logs:

9:36am: s@h_wrk Sending Result: Seti@home status: ErrorCode 0xfffffc74 -908
9:36am: Q0001 Seti returned: ErrorCode 0xfffffc74 -908

 

[Crazee]

Same problem here :|

I wish they would communicate problems better than they do!

 

[Smoke]

I see there is a problem this morning but I am showing 18 Results being Queued to be sent to the Seti@Home server in three (3) different colors?

I have seven that are colored with the normal grey background which are the last seven that have been uploaded to my Q by my mini-teammates between 0735 - 0852 CDT. I think that background is for "normal" WUs.

I have five uploaded between 0605 - 0637 CDT that have sort of a faded green background. I have no idea what that color background means ... can someone tell me?

And then I have seven that have been uploaded by my mini-teammates between 0410 - 0525 CDT that have a faded red/ light purple background. I think that is the color of "Duplicate" WUs.

I have now turned off my Q until things clear up.

Is this the same problem that OrangeKid et als reports some time ago as "Berkeley handing out Duplicates"? I would think not.

 

[Poof]

Conjur - same here about getting a new system online. Just brought up my new XP 1900 yesterday and now this happens. My logs indicate that they did something at 5am EST (2am PST) and right at that time, those funky error messages started. The results in the queue now that are stuck are highlighted red.

I wonder if this has anything to do with that new, bug-fixed GUI client and maybe that messing up their results filters (which maybe they're trying to fix)? Just some speculation...

 

[Crazee]

I am able to pull up my stats at Berkeley now. I wonder if the problem has cleared?

 

[m2kewl]

<< ...this in the logs: 9:36am: s@h_wrk Sending Result: Seti@home status: ErrorCode 0xfffffc74 -908 9:36am: Q0001 Seti returned: ErrorCode 0xfffffc74 -908 >>



Same here!! Looked at my setiQ and this started happening 5:46am ET. :disgust: and still down. :|

What does the r:2 (5) mean on the receive section on the lower right - i mean the "(5)"??

 

[Crazee]

I was just able to get a result uploaded and the one's in my queue that were showing as problems are not any longer. It looks like the problem may be past now.

 

[Smoke]

Crazee, did you have any WUs that had faded Red and Green backgrounds? And are they still that color after your last upload to Berk?

 

[Crazee]

Smoke,

I had WUs from all colors of the rainbow. They are all uploaded now and it reflects it when I check on SetiTeam so it looks like the problem is past

 

[Smoke]

Are the WUs that were "rainbow colors" now showing in your Q still colored or have they returned to the normal grey background?

And did you get credit for them at Berk?

I have seven that have the faded red background of "duplicates" which are rejected and get moved into a Duplicate Folder in SetiQueue. There is someway to resubmit these but I can never remember where you cut and paste them to have this happen. Could someone tell me the method?

 

[Confused]

m2kewl,

the number in brackets is the number of problem results, the other number is number of good results

ConfusedBW

 

[Crazee]

Smoke,

Mine never got to the duplicate folder. All mine have uploaded and I have received credit at Berkeley. OK probably knows how to move them from the dup result queue or there maybe something on the SetiQueue site.

 

[Smoke]

there maybe something on the SetiQueue site.

I've never found anything about this there.

I asked OK about this before and he told me. I'm a little embarrassed that I have to ask again. It is just that I only did it once, long ago, and I have now forgotten. /all right ... no smart comments now. :|

 

[Orange Kid]

The thing is I'm probably older than you Smoke!!!!!!!!!!!!!!

Here we go
Shut down the Q.........through windows explorer just move the wu's and corrosponding ini's from the 'duplicates' folder to the 'client' folder and then restart the Q........if they weren't really dupes Berkeley will accept them



EDIT:::my 'problem' wu's seen to going through ok---------for now

 

[GunDog]

SIGH.. When will berzkerely leave well enough alone! I would have broke the 500 mark at 2 am this morning. BUT NO, I have a queue full of rainbows

It does appear at 8:00 am PST they repaired another screwup however.

Force

 

[Smoke]

Thanks again OK. All right, let's settle this age thing.

My birthday is May 23, 1940 ... what's yours?

 

[Poof]

Smokeball - I think the reds are considered "dupes" (whether they really are or not). The greens may be "problem" WUs (a co-worker of mine who is on dialup says he used to get them all the time. He calls 'em "stuckees").

In this case, I think the "dup" indication here may have been what Setiqueue thought the error meant. A bunch of us have found that there are some errors that come out of SETI that Setiqueue doesn't understand so it lumps those WUs that get it, under a catchall "duplicate". Same with those "stuck" greenies.

Based on what people are saying here, I think someone must have changed a filter or something and thus the error... Since it doesn't look like it was a standard error, Setiqueue didn't know how to handle it.

I'm curious what non-queue-ers and/or Setidriver users saw with that error... It might have caused the clients to abort or perhaps retry.

[EDIT: LOL Smokeball!! The battle is on!!! ]

 

[Orange Kid]

Smokeball
you win