Technical news and SETI@home daily stats for 22.03.2007.

[Rattledagger]

Just after I posted yesterday's tech news message we had to reboot kryten and penguin as they both lost NFS mounts. In fact, we had to boot kryten twice (as it came up immediately being unable to mount bruno's disks). I really wish I knew what was causing these to happen, but perhaps this problem will simply just "time out."

The first technical issue for today was the hill shuttle bus broke down, so I got in a few minutes later than expected. This at least afforded me an extra few minutes to complete a rather pesky sudoku puzzle. Take that, unruly numbers!

So what happened with the replica yesterday? Turns out, for some (currently) inexplicable reason the .MYD files under data/mysql were all zero length. None of the other files were affected, just the .MYD's. Oddly their time stamps were sane (they were rather old as they haven't been updated in a while). So what emptied out these very specific files but didn't update their time stamps? In any case, we're forced to recover the replica from scratch (not that big a deal). Bob was finally able to wiggle his way in to at least clean out the current database so we can drop everything and reload. We might have an outage soon to dump the current data for such a reload.

Meanwhile, bruno progresses. Making it the new upload server was held up on being able to compile a working fastcgi-enabled file_upload_handler. Jeff finally got one to compile. So we embarked on what should have been a quick transition - basically just moving a cable from one jack to another and updating DNS. However the file_upload_handler didn't work. Refusing to debug it I suggested we just use a normal garden variety handler without the fastcgi hooks. All the fastcgi was buying us was process spawning overhead. This was a major necessity on our old n' slow 3500, but bruno didn't even break a sweat once we fired it up. So bruno is now our upload server!

But wait! After a half hour or so I noticed the traffic graphs were a bit "dampened." Why weren't we sending out as much data as before? After finding no obvious bottlenecks we dug out a gigabit switch and split the Hurricane link so both kryten and bruno could act as simultaneous upload servers. Sure enough, a third of our clients were still trying to connect to the kryten address. This is odd as the DNS entry has a 5 minute TTL (time to live). Perhaps we're seeing the effect of DNS caching (in Windows or otherwise). Fair enough - we'll leave both kryten and bruno up as "mirror" servers as DNS (hopefully) corrects itself over the coming days. I'll reflect the changes in the server status page eventually.

- Matt

#____Total Work Done____Todays WD_____AWD________overtake_______Team-name
01______220.921.050______956.512____1.015.897______impossible______SETI.USA
02______212.608.676______388.577______389.979______impossible______SETI.Germany
03_______94.178.933_______84.490_______79.119______impossible______BroadbandReports.com Team Starfire
04_______80.206.374______228.086______194.462______impossible______L'Alliance Francophone
05_______76.111.633______109.967_______96.313______impossible______Czech National Team
06_______74.893.678______153.248______150.134______impossible______BOINC Synergy
07_______64.628.145______114.221______109.049______impossible______SETI@Netherlands
08_______43.728.066________8.804________6.763______impossible______OcUK - Overclockers UK
09_______38.498.408______137.785______132.788______impossible______The Knights Who Say Ni!
10_______33.369.411______-13.831______-14.745______2.263 days______BOINC.Italy
11_______28.615.111_______51.041_______47.686______impossible______Overclockers.com
12_______25.532.957_______98.794_______87.910______impossible______Team Art Bell
13_______23.466.305_______60.242_______59.278______impossible______Team 2ch
14_______19.408.356_______50.593_______47.962______impossible______The Planetary Society
15_______14.847.448_______38.474_______29.823______impossible______Ars Technica
16________8.906.178_______97.899______104.697______impossible______Team MacNN
17________2.295.600_______-4.858______-10.568________217 days______Universe Examiners
18_______46.700.901_______70.885_______76.217______notanoption_____TeAm AnandTech
19_______-2.635.580_______12.273________1.034______2.549 days______Phoenix Rising
20_______-7.151.809_______53.878_______37.504________191 days______SETI@Taiwan
21_______-9.210.955______-37.341______-40.763______impossible______Planet 3DNow!
22_______-9.743.106_______-6.811______-12.384______impossible______Amateur Radio Operators
23_______-9.775.233______-10.634_______-7.343______impossible______Hewlett-Packard
24______-10.216.078______-19.257______-24.186______impossible______PC Perspective Killer Frogs
25______-11.289.088______-30.061______-34.081______impossible______2CPU.com
26______-11.615.404_______-1.799_______-4.932______impossible______Canada
27______-13.180.677_______19.451________9.193______1.434 days______SETI@China
28______-14.995.888_______10.963________6.297______2.381 days______Team MacAddict
29______-15.293.888_______17.022_______17.580________870 days______Dutch Power Cows
30______-15.465.159_______-8.571______-13.900______impossible______Team NIPPON
31______-15.766.726_______80.027_______76.549________206 days______Team Starfire World BOINC
32______-16.532.722______-36.152______-38.877______impossible______Portugal@Home
33______-16.628.042______-51.800______-56.844______impossible______Picard
34______-16.762.668______-36.498______-38.551______impossible______BOINC@Denmark
35______-16.985.398______-18.532______-19.160______impossible______BOINC SETI@home RUSSIA
36______-18.325.454______-46.809______-51.492______impossible______LittleWhiteDog
37______-18.881.253________2.604_______-7.857______impossible______Hungary
38______-21.924.045______-40.250______-43.689______impossible______Team EDGE
39______-21.983.349_______18.304_______11.291______1.947 days______UK BOINC Team
40______-22.244.187______-23.044______-27.655______impossible______SETI@klamm.de
41______-23.111.155______-21.259______-27.125______impossible______HispaSeti&BOINC
42______-23.251.219_______-5.527______-10.355______impossible______U.S.Air Force
43______-23.486.662______-28.880______-29.525______impossible______BOINC@AUSTRALIA
44______-23.628.203________9.106________6.559______3.602 days______US NAVY
45______-24.170.644______-27.998______-32.021______impossible______SETI Sverige [Sweden]
46______-24.314.255________3.804_______-2.939______impossible______SETI.hr
47______-25.997.468______-30.537______-43.745______impossible______The Final Front Ear
48______-26.039.454______-26.687______-29.242______impossible______BOINC UK
49______-26.599.134______-34.660______-41.080______impossible______SETI@Home Poland
50______-26.638.859______-45.238______-51.590______impossible______World Wide S.E.T.I.

Appart for Anandtech's stats, it shows how much more/less than Anandtech.
Also shows based on Average Work Done how many days for Anandtech to overtake the team, or be overtaken by a team behind...

 

[BlackMountainCow]

Thx Rattle! :beer:

 

[petrusbroder]

Thanks, Rattledagger, for the numbers and the info. :sun:
It is very interesting reading about the problems seti@home is ahvin ... and thus to understand who big that project is!