Berkeley Problem !!??!?

[chawken]

Well, I headed off on Friday, and all my machines were crunching away just fine through Saturday. Sometime after about 3pm on Saturday it seems that Berkeley started having problems.
On Sunday morning when I checked my home machines - they were waiting to transmit. Tried to transmit but only one of the machines transmitted and Berkeley didn't register the completed WU.
When I noticed the lower than expected total WU count on my stats I decided to go to work and check my machines there. Every one of them were ready to transmit - but even weirder - they had all stopped processing - like a stop_after_send. Rebooted all the machines - spent over an hour transmitting 16 WU's. Before I started transmitting, I had a total of 4114 WU's.
I got all my work machines working again, and when I got home, I tried to send a WU off of one of the home machines. After transmitting I checked my stats page and to my dismay - the total was 4118. 17 WU's sent - 4 credited.
On Monday, it seemed that things were O.K., but for Sunday - I calculate that I lost about 30 WU's. Of all my machines I should have produced 56 WU's but only got credit for 26.
Did anyone else have a simular problem?

[TC]

There's an entire thread about this same problem, but the odd thing is I've hardly had any trouble at all - only one unit was waiting to upload yesterday. I have a friend here that also runs seti and he hasn't had a problem either. There have been times when I was having problems like you but nobody else was - really weird.

[chawken]

Originally posted by TC
There's an entire thread about this same problem, but the odd thing is I've hardly had any trouble at all - only one unit was waiting to upload yesterday. I have a friend here that also runs seti and he hasn't had a problem either. There have been times when I was having problems like you but nobody else was - really weird.

Actually, I saw the other thread after I started this one - but my problems went well beyond just upload and download problems. 17 WU's sent and only 4 credited - every machine that I run had stopped processing, as if it had a 'stop_after_send' command. 12 processes just sitting there at 0%. I have never had that happen before.
All in all, calculating how many WU's should have been sent - according to my .csv files, 25+ WU's never got credited.
One machine, as I responded to you, TC, in another thread - Seti Driver would not fire up at all. Ended up having to delete everything off and reloading.
Weird weekend. Plus I updated my top 100 Teams forcast sheet and noticed a lot of teams way under par with WU production this weekend. O/C Seti Team went way down in average - from over 1000 per day to just a little over 700 per day. Team Lamb Chop went from over 4000+ per day to under 500 per day.

[Basher]

Originally posted by chawken

O/C Seti Team went way down in average - from over 1000 per day to just a little over 700 per day. Team Lamb Chop went from over 4000+ per day to under 500 per day.
WOW, I guess we did not do as bad this weekend as I thought :D As far as I know I got credit for all my WU's sent.

[TC]

That is really weird. I'm not showing any loss of units for my account. Seems like every so often they have some major problems. I'm glad they're not providing me internet access.

[chawken]

Originally posted by TC
That is really weird. I'm not showing any loss of units for my account. Seems like every so often they have some major problems. I'm glad they're not providing me internet access.

I'll second that. Bad enough having PacBell as my ISP. But what was really weird - transmit was really slow when I came in to work to manually transmit. On one machine it kind of hung at the end for a second, and in the last transmit section there was a line that said 'stop_after_send'. Now, I'm not sure if that is normal, but it sure is strange that 12 processes were stopped. This was at about 2pm on Sunday.

[DeltaSierra]

I had similar problems over the weekend. I don't think I lost any WUs (I'm too lazy to keep close track), but I had slow transmit rates. At one time, the transmit completely stalled, so I disconnected and tried again, but had the same problems. I also had some difficulty in downloading new WUs to cache. But, as of this a.m., I seem to be back to "normal."

[[Oc]acaridans]

Im having problems again...This morning it was like nothing was wrong....Now I have 5 WU's on this computer to send, the firsy 2 wouldnt connect the 3rd and now 4th have gone throught but ist taking about 5min each....I checked my stats no loss of credited WU's

[chawken]

Originally posted by [Oc]acaridans
Im having problems again...This morning it was like nothing was wrong....Now I have 5 WU's on this computer to send, the firsy 2 wouldnt connect the 3rd and now 4th have gone throught but ist taking about 5min each....I checked my stats no loss of credited WU's

I have been watching all but my home machines very closely - and so far only 1 transmit has not registered. 1 every now and then could simply be a dup - but 25+ in 1 day...

Oh well - chalk it up to one day in Seti hell.

[[Oc]acaridans]

Originally posted by chawken


Oh well - chalk it up to one day in Seti hell.

Well said.
I just sent a WU and got miscredited for it..Might have been a duplicate it registered as WU #585 when it should have been 643.
Seti hell it is.

[Morpheus]

SETI hell... oh, bugger....

Same here too... :(

[Basher]

I lost 1 WU this am :(

[chawken]

Originally posted by Basher
I lost 1 WU this am :(

Another 2 this morning. No wonder we can't STAY ahead of LKSAB, Seti keeps ripping me off for WU's.

[chawken]

Boy, I can't win for losing. If it isn't WU's not being credited, then it's a ton of VLAR's. Over half of my processors are running <.050 WU's.
The Seti god is definately ticked off at me - anyone got a good Chant that will please him. Maybe sacrificing a Lamp Chop.

[[Oc]acaridans]

Its not a chant but.
Dear seti gods,
Please start giving Chawken good WU's again or, Go n-ithe an diabhal do dhiosca crua.


Its pronounced: guh NYIH-huh uhn JOWL duh YISS-kuh KROO-uh.
Lossly translated: May the devil eat your hard disk.