Seeing SetiClassic off in style!

Warning....

Wu's would not be count. You can sent and receive seti classic wu's but it seems so that they got lost in space. Hold your wu's for our great finish between OcUK and SG. I hope that Berkeley will fix their database problem.

I've lost 20 Wu's by this case.

Greetings from germany

Andreas Seti.Germany
 
Seems our German friend may be right. OcUK and Seti Germany are way down on normal output so far today. This is not good. :eek:

Danke für die Warnung, Hund!
 
Last edited:
Damn that will be real difficult for me to organise, all my nodes running as a service connect to the outside directly through a proxy :(
 
Hund said:
Warning....

Wu's would not be count. You can sent and receive seti classic wu's but it seems so that they got lost in space. Hold your wu's for our great finish between OcUK and SG. I hope that Berkeley will fix their database problem.

I've lost 20 Wu's by this case.

Greetings from germany

Andreas Seti.Germany
Click to expand...

I'm guessing the reason they are not been counted yet is due to seti's servers been down. I'm guessing when they are working again the ones sent to the queue will be uploaded to the datebase at borkeley


I
 
mark128 said:
I'm guessing the reason they are not been counted yet is due to seti's servers been down. I'm guessing when they are working again the ones sent to the queue will be uploaded to the datebase at borkeley


I
Click to expand...

Aye, I can't see how any WUs could possibly just go AWOL. All of mine appear to be accounted for at the minute although, even though crunched WUs are sent off with no problems, Seti Driver won't automatically download new WUs :confused:

I suppose though that absolutely nothing is beyond the realms of impossibility with B0rkeley :D
 
I've got this message in the textclient:

Sending result - connecting to server.
You are running a client from the original SETI@home project. This project will
be shutting down on 12/15/2005. Please join the new SETI@Home project at http:
//setiathome.ssl.berkeley.edu/
Attempt to send duplicate result
CLI command: seti -cpu 0 -stop_after_xfer
SETI@home client.
Platform: i386-winnt-cmdline
Version: 3.03

I have checked 5 computer and on all the same. Two of them in Berlin, the other 650 km away. Perhaps it will be importend when you receive the Wu's. I am shure that my Wu's are not send duplicate.

Normally I am crunching between 50 - 100 Wu's/day. Today only 6 will be counted.

Greetings

Hund
 
Last edited:
Hund said:
I've got this message in the textclient:

Sending result - connecting to server.
You are running a client from the original SETI@home project. This project will
be shutting down on 12/15/2005. Please join the new SETI@Home project at http:
//setiathome.ssl.berkeley.edu/
Attempt to send duplicate result
CLI command: seti -cpu 0 -stop_after_xfer
SETI@home client.
Platform: i386-winnt-cmdline
Version: 3.03

I have checked 5 computer and on all the same. Two of them in Berlin, the other 650 km away. Perhaps it will be importend when you receive the Wu's. I am shure that my Wu's are not send duplicate.

Normally I am crunching between 50 - 100 Wu's/day. Today only 6 will be counted.

Greetings

Hund
Click to expand...

Thats funny i'm sure i remember reading something about that happening today at the seti official message boards. Looks like its well and truely borked!

However things are looking up, just had a look at the server status page and....

The data server is up and running

If you are experiencing problems connecting to our server, this may be due to network problems on your end, network problems on the University campus, or our server being swamped with requests.

For more information about previous outages, please check our Technical News page.
 
Have managed to move from squid over to setiqueue for proper WU caching and rerolled the service to my clients. Would have lost any half finished WU's but what with the servers being down recently I doubt much would have gone. Crunching again now anyway with a nice big queue.
 
I don't seem to be having too much trouble, all my boxes seem to have been able to upload their results.

Drinky said:
Thus far I have:
Dual 3.6GHz HT Xeon
Dual 3.2GHz HT Xeon
Dual 2.8GHz HT Xeon
Dual 2.6GHz HT Xeon
Dual PIII 866
Pentium M 1.6GHz
Celeron 750MHz
Pentium III 750MHz
Click to expand...
Added:
2 Dual 1.0GHz Xeon's
P4 3.0GHz HT
another Celeron 750Mhz

:)
 
Hund said:
I've got this message in the textclient:

Sending result - connecting to server.
You are running a client from the original SETI@home project. This project will
be shutting down on 12/15/2005. Please join the new SETI@Home project at http://setiathome.ssl.berkeley.edu/
Click to expand...

I've been getting that message for several weeks now.

I guess we'll just have to wait this one out and see what happens.
 
Looks like thier servers are down again. They were up for a bit earlier on and the WU's I sent to the seti queue have been seen to borkeley and credited :) If you can fill up ** cache's with enough WU's to last a few days. Never know what could go wrong.
 
Still dodgy for me. I can download, but I can't upload. The results are stacking up in my SetiQueue - I have 20 to send in now from my 2 rigs.
 
I am able to connect but after it has finished analsing a Wu it closes the cmdline down so i have to re-load the program then it send the result (take about 40-30secs to connect and send one WU) then it closes again, so i have to re-load it again to get it to download another WU anbd start analysing.

So i decided to download SetiDriver to cache a few WUs but i have noticed that it is taking an hour longer than normal(normal take 3 and a bit hours with SetiDrive it take over 4hrs). So i think i will ditch SetiDriver and use SetiMonitor or sumthing.

No idea why the above is happening though i guess the closure of the cmdline program is due to berkeley? I dunno.

All seems to be going belly up.
 
Can't get any units in my seti queue :/ what public queue can I use to grab some?

ed: keep getting s@h_wrk Download wu: SendRequest to shserver2.ssl.berkeley.edu failed: Connection Timeout :/
 
Last edited:
Whats going on, according to this site we have dropped production by about 50% in the last 2 days, are we all crunching in vain, has borkley borked our chance of beating the germans, hope all the WU's im crunching are not being lost, used to get a message on the transmit box of my running total, now it just says no result header found on all three of my crunchers :confused:
 
h2ocooler said:
Whats going on, according to this site we have dropped production by about 50% in the last 2 days, are we all crunching in vain, has borkley borked our chance of beating the germans, hope all the WU's im crunching are not being lost, used to get a message on the transmit box of my running total, now it just says no result header found on all three of my crunchers :confused:
Click to expand...

I'm getting the same 'no result header found' on my rigs, but all my WUs seem to be going to my account fine. As far as the 50% drop is concerned, that could be due to some people not being able to dump them - I've had some issues with that over the past few days myself, though with me the main problem is being able to download new ones :(. Also, MoS and sneezy don't make use of any caching apps, so they need to download WUs one by one as they send crunched ones off, so if b0rkely's servers are down then these two are heavily affected - and they produce a good bulk of the WUs we do as a team, so it's very noticeable when their output is reduced.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom