Last Call... Seti@home v3.0

[Escalade]

From the SETI@home web page:

SETI@home version 3.03 is mandatory for all supported platforms.
On February 1, 2001, earlier versions will cease to be able to contact
our server, so please upgrade to version 3.03.

 

[Wiz]

Yeah I see. hmmm does anyone know what will happen if I have several finished WU's waiting to be turned in at that time? Any guesses? Sounds like my comps won't be able to send them in. Oh boy, what am I gonna do? Any advice out there?

 

[BadThad]

Just crunch the wu's with v3.03.

 

[Jalapeno]

 

[JWMiddleton]

Wiz: I assume that you are caching the WUs, if so tell us what program you are using and it will be easier to help. Do you have access to those systems today?

I have moved all of my SetiQ cached WUs into systems with Setidriver. Then I upgraded the clients to 3.03. Then as the last 3.0 processed WUs are completed, I am uploading them to S&H. They are still taking them as of a few minutes ago.

I have installed beta version of the new SetiQ on my office machine and it is a nice improvement over the previous console version.

If I hadn't had so many WUs cached here at the last few days of Jan, I would not have had to go to so much trouble. And, that is due to my travel schedule. I just didn't want to trash any WUs.

The worst that can happen is that you delete all of the sh!t and start over. Yes, you will loose a few WUs.

 

[Assimilator1]

Wiz

Also what net connection are those PC's on?

 

[Wiz]

Hi guys, I have been using SetiDriver and you know sometimes it cant connect to the seti site so it sits there with several units waiting to be transmitted. I think I have it under control, I reduced the cache sizes to one and so they have been decreasing. At the end of the day I will load 3.03 and tell it I have a new client and let it work on whatever units are left over.
I am on ATT@home cable with the three machines here at the home farm.

 

[Assimilator1]

Hmm ,I dunno if you can remote access SETIdriver ,but I fairly sure you don't have to run the cache down to switch clients.

Escalade
Thanks for the confirmation

 

[blade47]

Assim1 is right you don't have to empty SetiDriver to update the client. The newest version of setiDriver will finish the current wu with the old client then start the next wu with the new client.

BTW thanks for the reminder I am already running v3.03 but using the old version of SetiQ. I'll get right on fixing everything up.

 

[Yo Ma Ma]

What are these latest updates doing exactly? Is it strictly "more science" or something else going on?

 

[blade47]

v3.03 does more science & seti is moving the server so anything before v3.03 won't be able to even connect to the seti server. So you must upgrade to the new client.

 

[Poof]

v3.03 does more science & seti is moving the server so anything before v3.03 won't be able to even connect to the seti server

Actually blade, they're not moving the server (if they had that many servers, maybe they wouldn't be b1tching so much... ), they're changing the DNS hostname of the existing server (IP stays the same). Since clients contact the data server by hostname rather than IP and that hostname is hardcoded in the client, the thought was that if you change the server's hostname, then the old clients (that wouldn't have the new hostname hardcoded), wouldn't be able to contact the data server (because that name no longer exists...).

Of course, this whole issue impacts those of us who still have 2.x clients that had 3.03 ports purportedly "in progress" (like my alpha linux with a 2.4 client and my sparc linux with a 2.0 client)...

But I'll see what happens... If they screw my Alpha while I await the port that was supposed to be available 2 weeks ago, TA RC5 is gonna get a crunchomaniacalsuperduperoldbutstillgoing Alpha 433Mhz EV 5.5 cracker!

 

[networkman]

Yeah, Poof, I know what you mean. :disgust: Any machines that I get my hands(claws?) on that don't have a 3.03 S@H client available will go to the RC5 effort for TA!

 

[Assimilator1]

Poof

BTW are we 100% sure that the old SETIQ will connect to the new server name using that hosts.txt fix? ,mine seems to be OK atm but I don't know if they have killed the old name.
I'm sticking to the old SETIQ until I (a) run the WU's out & (b) figure out if the new 1 will do a result log like the old one does.

 

[Poof]

Assim1 - I'm still on the old Setiqueue (haven't had time to putz around with the new one yet). It uploaded okay at around 3am EST (~8am UTC) this morning and downloaded new WUs. That would have been just after midnite PST where Berkeley is... This is using the hosts file addition.

I won't know for sure about whether it will continue to upload okay unless I try it manually this afternoon or just let it go at its regular time tomorrow morning. I'd rather not mess with it today as I've had very good luck getting connected when I let it go in those early morning hours my time...

 

[BLACKBEARD]

Just returned a result with v3.0 and the message from S@H was:

Warning: discarding result because it was from an obsolete version of
SETI@home.

Looks like its over.

 

[Assimilator1]

Thanks for the info ,looks like its time for you to switch to v3.03

So I guess the old server name has been killed ,I have just successfully uploaded a result so it looks like the fix has worked

 

[Poof]

Yep - folks are reporting rejects and/or non-credits for pre-3.03s... But they're also reporting that the older Setiqueue is still working.

Now... I need to determine whether my 2.4 Alpha's WUs will be accepted, being that there's no 3.03 for it yet...

 

[Hellburner]

Verified, just "lost" 16 wu's when I flushed my Q, have a 3.03 client due in about 1.5 hrs. Will see if the old Setiq can handle it and flush it or if it barfs.

 

[Assimilator1]

Ouch! ,16 lost WU's! that hurts ,my sympathies to you HB ,
you not hear about the client change? hehe

 

[Hellburner]

The old Q loaded a new wu just fine after hacking a config file to reflect 3.03 client results. Should be good to go

Have a feeling in the next day or so there may be a few "surprises" from people not realizing that they never upgraded their clients

 

[ElFenix]

*sniff*

good bye fast seti client, i hope you return soon!

 

[Hellburner]

the old Setiq sent v3.03 results and the results were credited just fine. Additionally new work units were sent without trouble.

PS, this includes proxy settings for the new address, I think using your HOSTS file will work too.