• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Technical News, and SETI@home daily stats for 17. - 20.12.2007.

Rattledagger

Elite Member
Aftaglid (Dec 17 2007)

Another Monday back on the farm. Due to faulty log rotation (and overly wordy logs) our /home partition filled up over the weekend, which didn't do much damage except it caused some BOINC backend processes to stop (and fail to restart). No big deal - the assimilators/splitters are catching up now. Jeff just kicked the validators, too. The hidden real problem is that the server start/stop script is 735 lines of python. In our copious free time we'll re-write a better, smarter version in a different scripting language (which will be, by default, easier to debug) - and it'll probably be only 100 lines or so, I imagine. Okay.. maybe 200.

The mass mail pleading for donations is wrapping up without much ado, except a large number of them got blocked/spam filtered. No big surprise there, but we need to do more research about how to get around all that.

- Matt
Take a Pebble (Dec 18 2007)

Our Tuesday outage ran a little long this week because we're no longer dumping to the super fast Snap Appliance as we converted that space into more workunit storage. Instead we're currently writing to the internal disk space on thumper, which is vast but much slower for some reason. This situation will evolve, so nothing really to worry about.

We also made the database change to fix the cryptic bug noted in this thread. Pretty much just adding a new row to the middle of the application table so it was in sync with the data structs in the code. And yep, after that it was behaving normally, even without our "force" to set values to where they should be regardless of what was erroneously culled from the database. So we're calling this fixed.

I also got the new server "bane" on line as a third redundant public web server. Perhaps you noticed a speedup? Perhaps you noticed some unexpected garbage, broken links, or weird php behavior? Let me know via this thread if you see anything obviously (and suddenly) wrong with the web site. Over the coming days we will retire the current web servers kosh and penguin. Bane is a system with two Intel quad-core 2.66GHz CPUs and 4GB RAM in 1U of rack space. Alone it is more powerful than kosh and penguin combined, which together account for about 6U of rack space.

- Matt
Onions Wrapped in Rubber (Dec 19 2007)

There were some minor headaches during the outage recovery last night, mostly due to the scheduler apache processes choking. They needed to simply be restarted, which happens automatically every half hour due to log rotation. Or they should be restarted - I just discovered this rotation script was broken on bruno and other machines. I fixed it.

I'm still breaking in the new web server "bane" - still having to make minor tweaks here and there. Of course I asked people to troubleshoot it during the outage recovery and the ensuing problems noted above - not very smart. Should be nice and zippy now. In fact, as I type this it's the only public web server running. I'm "stress testing" right now, but will turn the old redundant servers back on before too long.

There's a push to get BOINC version 6 compiled/tested/released, so all questions regarding BOINC behavior are taking a back seat. Please stay tuned! These type of questions are usually answered better/faster in the Number Crunchers forum. I'm mostly focused on the servers and the SETI science side of things (though I do some minor BOINC development from time to time - but usually not anything involving credit or deadlines).

- Matt


#____Total Work Done____Todays WD_______AWD________overtake________Team-name
01______382.567.530______587.690______553.023______impossible______SETI.USA
02______311.793.010______823.758______561.583______impossible______SETI.Germany
03______133.327.396______185.468______171.195______impossible______L'Alliance Francophone
04______114.603.794_______71.805_______63.273______impossible______BroadbandReports.com Team Starfire
05______111.177.032______137.905______123.713______impossible______BOINC Synergy
06_______96.612.755_______69.351_______54.240______impossible______Czech National Team
07_______89.530.371______111.161_______92.986______impossible______SETI@Netherlands
08_______78.890.277______142.426______119.808______impossible______The Knights Who Say Ni!
09_______42.334.540_______52.023_______57.410______impossible______Overclockers.com
10_______41.383.206______-38.821______-37.256______1.111 days______OcUK - Overclockers UK
11_______39.677.206_______34.273_______29.955______impossible______Team Art Bell
12_______33.377.456_______11.923________5.737______impossible______Team 2ch
13_______28.760.171_______11.448________2.874______impossible______The Planetary Society
14_______27.961.484_______36.698_______29.540______impossible______Team MacNN
15_______24.580.837______-91.301______-87.872________280 days______BOINC.Italy
16_______13.276.374______-40.454______-50.509________263 days______Ars Technica
17_______71.690.270______166.131______158.682______notanoption_____TeAm AnandTech
18__________-84.509_______-2.834_______-7.985______impossible______SETI@Taiwan
19_________-240.535_______66.600_______58.382__________4 days______Team China
20_________-521.795______-57.328______-60.714______impossible______Universe Examiners
21_______-1.739.870______-29.404______-26.376______impossible______Phoenix Rising
22_______-4.544.136_______65.289_______42.716________106 days______Team Starfire World BOINC
23______-14.008.864______-33.589______-37.935______impossible______Canada
24______-14.147.808______-58.012______-51.119______impossible______Dutch Power Cows
25______-16.032.436______-65.820______-67.515______impossible______Amateur Radio Operators
26______-16.102.695______-94.943______-94.217______impossible______Hewlett-Packard
27______-16.186.376______-94.254______-74.571______impossible______PC Perspective Killer Frogs
28______-20.725.648______-30.005______-29.925______impossible______UK BOINC Team
29______-22.518.012______-78.973______-82.135______impossible______Team MacAddict
30______-22.528.939______-62.007______-61.910______impossible______Team NIPPON
31______-23.365.166______-32.402______-34.342______impossible______US NAVY
32______-23.457.328______-40.038______-46.793______impossible______BOINC SETI@home RUSSIA
33______-23.923.660______-49.126______-51.705______impossible______BOINC@AUSTRALIA
34______-24.035.086_______20.684_______13.360______1.799 days______AUSTRIA - NATIONAL - TEAM
35______-25.002.664______-54.592______-62.576______impossible______BOINC@Denmark
36______-25.268.245_____-106.836_____-105.110______impossible______2CPU.com
37______-25.350.101______-63.685______-68.111______impossible______Hungary
38______-25.762.212_____-123.489_____-120.376______impossible______Planet 3DNow!
39______-26.867.452______-35.131______-37.261______impossible______U.S.Air Force
40______-31.054.008_____-113.082_____-112.405______impossible______Portugal@Home
41______-32.672.372______-94.265______-91.719______impossible______SETI.hr
42______-33.370.476______-81.495______-83.369______impossible______SETI@klamm.de
43______-36.534.250_____-115.787_____-112.310______impossible______Team EDGE
44______-36.671.082_____-109.445_____-107.241______impossible______HispaSeti & BOINC
45______-37.086.753______-94.912______-91.018______impossible______BOINC.SK
46______-37.099.359_____-142.385_____-136.905______impossible______Picard
47______-37.935.410_____-148.422_____-141.081______impossible______LittleWhiteDog
48______-37.974.799______-99.876______-99.085______impossible______SETI Sverige [Sweden]
49______-40.097.960______-62.489______-59.404______impossible______BOINC@Poland
50______-41.307.836_____-112.953_____-113.699______impossible______BOINC UK

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...


Stats averaged for last 4 days. For the 1st. day there wasn't any stats generated, and I've been extremely busy the last couple days, meaning haven't had the time for stats before now. :beer:


 
i've got a question for everyone..
I just loaded 64bit Ubuntu on an AMD64 3000+.... when I go to the boinc site to download seti... the site is automatically choosing the 32bit version..... I can choose the 64bit, so i'm not concerned about not being able to get the 64 bit version...

my question is... is there something wrong that I don't know about... should I run the 32bit version or the 64bit version of seti on 64bit Ubuntu?

I have a preference for the 64bit version.
 
Originally posted by: dajeepster
i've got a question for everyone..
I just loaded 64bit Ubuntu on an AMD64 3000+.... when I go to the boinc site to download seti... the site is automatically choosing the 32bit version..... I can choose the 64bit, so i'm not concerned about not being able to get the 64 bit version...

my question is... is there something wrong that I don't know about... should I run the 32bit version or the 64bit version of seti on 64bit Ubuntu?

I have a preference for the 64bit version.
Well, I'm not running linux, but as long as you're not running one of the projects that haven't bothered to upgrade to be 64-bit compatible yet, I'm not aware of any reasons for not running 64-bit client.

Most likely it's just a browser/download-selection-mis-match of some sort that chooses the wrong linux-version.

Atleast under windows, I've not seen any 64-bit specific problems in any of the resent clients, AFAIK these was fixed around v5.10.5.


 
Originally posted by: dajeepster
i've got a question for everyone..
I just loaded 64bit Ubuntu on an AMD64 3000+.... when I go to the boinc site to download seti... the site is automatically choosing the 32bit version..... I can choose the 64bit, so i'm not concerned about not being able to get the 64 bit version...

my question is... is there something wrong that I don't know about... should I run the 32bit version or the 64bit version of seti on 64bit Ubuntu?

I have a preference for the 64bit version.

BOINC's website will choose the x86 BOINC app when you visit it on a nix box, i figure it's because not all projects support x86_64 yet. Go to the "see all apps" page to dl the 64 bit version.

IMHO, SETI under Linux x86_64 seems slower than x86 in windows on the same box.

If you still plan on using Linux 64bit, make sure to use an optimized science application compiled for amd64.
 
right now I can't get seti 64bit to connect to the server 🙁

for this box... i'm going to run Ubuntu 64... I only have 1 gig of ram in it.
 
Originally posted by: dajeepster
right now I can't get seti 64bit to connect to the server 🙁

for this box... i'm going to run Ubuntu 64... I only have 1 gig of ram in it.

doh... it just started working... I was just randomly executing files in the folder and it started working 😀
 
there's a version 5.10.30 out now... or did I just miss it or something... well anyways.. when I loaded my phenom up last weekend, it was at 5.10.28

I've only loaded it on a few computers so far.
 
Back
Top