I now go for your option 2 as option one always led to getting stressed out.
I may go into the office tomorrow just to start my crunchers off agin, even though I'm on holiday.
It's not that I'm a stats whore, it's for the Team ...honest.
Could all people with complaints over this changeover post here? Rants are especially welcome!
Mine:
11am EST is 5pm UK time. By the time the servers come back, it's early evening and I'm at home. My office farm can't connect to the 'Net so I have two choices:
1) Crunch the old client until the next morning. Harvest the results. Upload the new client and set them running. Upload the old results right on the 24-hour deadline for full-credit but probably only get half-credit
2) Shut down the farm before I go home and upload the harvested results as the new client comes on-stream and half the world floods the servers. No crunching overnight for near 100GHz of farm.
Because it's less hassle, I will take option 2.
I now go for your option 2 as option one always led to getting stressed out.
I may go into the office tomorrow just to start my crunchers off agin, even though I'm on holiday.
It's not that I'm a stats whore, it's for the Team ...honest.
Hmmmmmmm.
The fact that it hasn't started yet, and therefore we can relax and get rested up?
HOME: A physical construct for keeping rain off your computers.
Nope, Stats server are down for maintance....
It seems like it has started....
Greets thor
Gotten the update via the daemon a few minutes before the server went down...fingers crossed for a good update
At this very moment it reads
"Server is down for protein changeover or maintenance. Please check back in a few hours."
So methinks the moment we've all been waiting for has arrived . . .
Maybe some of us can make extra mirrors, and report the corresponding links back here ?
DPC: We're going for the #1 again
anyone else have this in their error.log during the server downtime:
?Code:<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <HTML><HEAD> <TITLE>404 Not Found</TITLE> </HEAD><BODY> <H1>Not Found</H1> The requested URL /cgi-bin/fileUploader was not found on this server.<P> <HR> <ADDRESS>Apache/1.3.23 Server at 127.0.0.1 Port 80</ADDRESS> </BODY></HTML> Tue Jun 08 20:05:02 2004 ERROR: [000.000] {foldtrajlite2.c, line 5071} Error during upload: HTTP/1.1 404 Not Found Date: Tue, 08 Jun 2004 19:05:03 GMT Server: Apache/1.3.23 (Unix) (Red-Hat/Linux) DAV/1.0.3 PHP/4.1.2 mod_perl/1.26 Connection: close Content-Type: text/html; charset=iso-8859-1
The machines getting that (all of them) aren't detecting any new updates either...
Last edited by pfb; 06-08-2004 at 03:44 PM.
Be it because of the ticketing system working as intended, but this time around the update seems to be going smoothly!
Just to check on new client/protein/server issue when uploading start....
have any of your PCs auto-updated?
None of my online machines have auto-updated and the three that I have manually updated so far are now refusing to recognise my handle as valid!
the one I did update manually is reporting 'Warning during upload: STATUS 908 INCORRECT PROTEIN'...
ho hum - least someone has upload 2 gens...
i got some of that goop in one of my error.log , but one box has updated and is spinning away on the 145 , no big deal right now
Use the right tool for the right job!
As I'm folding offline, I'll update them manually when they finish current sets.Originally posted by pfb
have any of your PCs auto-updated?
I tried on one spare client to auto-update from my daemon folder, and it went OK.
Maybe the "page not available" was during the peak time, so hopefully those clients will update a bit later.
DF Stats page is up, download page is up, too.
Digger,
No idea about the handle problem, unless it has become corrupted somehow?
Last edited by iggy; 06-08-2004 at 04:24 PM.
Not again!Originally posted by pfb
the one I did update manually is reporting 'Warning during upload: STATUS 908 INCORRECT PROTEIN'...
I'm trying to be cautious after the last changeover...
Someone else has the same message..uh oh !
I am not a Stats Ho, it is just more satisfying to see that my numbers are better than yours.
not sure if the 2 error messages (the HTML one and the incorrect protein) are connected...
just going to leave it for a while and see what happens...
weird - the update daemon is reporting that it can't connect to the DF server...
It may not be able to connect simply due to the heavier loads on the server, since everyone is downloading the update. Is it also producing errors?
Elena Garderman
I just tried to upload few generations with manually updated client, dated June 07 2004, protein 145.
Guess what - error 908, incorrect protein!
The worst thing is that the generations uploaded, and then have been deleted!
Does this mean I'll have to start again from generation 0?
Last edited by iggy; 06-08-2004 at 04:29 PM.
Stardragon,
I've pot the 3 errors/problems I'm getting into this post to make it easier to sort out...
Uploading here no errors. Using the old client to upload off-line folders with no problems so far :crossed fingers:
EDIT: uploading no longer working.
Date: Tue, 08 Jun 2004 20:28:35 GMT
Server: Apache/1.3.23 (Unix) (Red-Hat/Linux) DAV/1.0.3 PHP/4.1.2 mod_perl/1.26
Connection: close
Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>404 Not Found</TITLE>
</HEAD><BODY>
<H1>Not Found</H1>
The requested URL /cgi-bin/fileUploader was not found on this server.<P>
<HR>
<ADDRESS>Apache/1.3.23 Server at 127.0.0.1 Port 80</ADDRESS>
</BODY></HTML>
Last edited by HaloJones; 06-08-2004 at 04:33 PM.
old protein goes up OK - new one doesn'tOriginally posted by HaloJones
Uploading here no errors. Using the old client to upload off-line folders with no problems so far :crossed fingers:
According to the stats only 1 person is active on this new protein - and that was the 2nd update since the changeover...
Just going to try and sit it out without worrying...
/edit - and now the server is down
All together now...
"What's the use of worrying, smile boys that's the thing...."
I am not a Stats Ho, it is just more satisfying to see that my numbers are better than yours.
Just tried to reupload same generations that gave error before (from the backup). All went without errors!
I just get a 910 error (which is to be expected when the previous gen wasn't accepted by the server...)Originally posted by iggy
Just tried to reupload same generations that gave error before (from the backup). All went without errors!
Well... I had a backup for everything from generation 0.
unfortunately I didn't as I assumed that the update would go well - it was only when I checked and saw the HTML error in my non-updating clients that I noticed the 908 problem...
hopefully that client should be ok...now just need the other 9 to auto-update at some point...
/edit - nope, fresh start it is then...
Should be fine now, thanks for noticing so quickly. Just a slight 'hiccup' in DNS. If the server rejected and deleted your first few generations you would probably be best to reset it to gen 0 (i.e. delete filelist.txt), but this is only necessary if you are getting 910 errors in the error.log.
Howard Feldman
all seems ok - the auto-update issue seemed to be down to the protein.trj file failing the CRC check (or it does when I use WinRAR to view the archive)...
No failed CRC here... maybe your downloaded file was somehow corrupt.
tis odd...but did a manual update anyway as I can't delete the file (think it may be more something on the PC than anything DF related...)
I've got all my machines on autoupdate and none have yet to do so. They all seem to be uploading fine though with the older client/protein combo.
Has anyone had a successful changeover apart from doing it manually?
Crunching for OCAU
Had success earlier this evening, but tried now and it seems that DF servers are not sending orders for update, and/or may be down...
Not down, accepting gens (old 131) just fine. Just not updating.
Gonna let at least a couple run to see how long before they update, if ever.
HOME: A physical construct for keeping rain off your computers.
Is this another 131? The farm is sending up. Everything is still 131, though.
I know this protein is slow but this is a bit
Seriously though - it does seem that the autoupdate is broken as quite a few people haven't updated yet to the 145 protein...
There's only six of the Free-DC team with contributions to the current protein. Autoupdate is not functional. I know I've got at least five, maybe six boxen on DF and no contributions, i.e., no update so far.
HOME: A physical construct for keeping rain off your computers.
...the auto-update daemon is also still reporting that it is 'Unable to get latest version info, please check network connection'...not an issue for me now but likely to be for those waiting on the update via that method...
No autoupdate here. Scared to do a manual so I just let them sit there....
Proud member of the Dutch Power Cows