Server status page


SETI@home server status information is also available in XML.

[As of 9 May 2008 23:50:12 UTC]

Server status

ProgramHostStatus
BOINC databasejocelynRunning
BOINC replica databasesidiousRunning
primary science databasethumperRunning
secondary science databasebambiRunning
data-driven web pagesthinmanRunning
scheduling serverptolemyRunning
scheduler processptolemyRunning
download server 1baneRunning
download server 2vaderRunning
upload serverbrunoRunning
feeder.i686ptolemyRunning
file_deleter1brunoRunning
file_deleter2brunoRunning
file_deleter3brunoRunning
file_deleter4brunoRunning
file_deleter5brunoRunning
file_deleter6brunoRunning
db_purge.x86_64thumperRunning
transitioner1vaderRunning
transitioner2vaderRunning
transitioner3brunoRunning
transitioner4brunoRunning
vote_monitorbrunoRunning
transitioner5vaderRunning
transitioner6vaderRunning
sah_validate1brunoRunning
sah_validate2brunoRunning
sah_validate3brunoRunning
sah_validate4brunoRunning
sah_validate5brunoRunning
sah_validate6brunoRunning
fix_missing_resultsptolemyDisabled
sah_assimilator1brunoRunning
sah_assimilator2brunoRunning
sah_assimilator3brunoRunning
sah_assimilator4brunoRunning
mb_splitter5landoDisabled
mb_splitter6landoRunning
mb_splitter7landoRunning
mb_splitter8landoRunning
mb_splitter9bambiRunning
mb_splitter10bambiRunning
mb_splitter11bambiRunning
mb_splitter12bambiRunning
mb_splitter13bambiRunning
mb_splitter14bambiRunning
Running: Program is operating normally
Not Running: Program failed or ran out of work
(or the project is down)
Disabled: Program has been disabled by staff
(for debugging/maintenance)

Database/file status

State#As of*
Results ready to send769,38140m
Current result creation rate1.50/sec0m
Results out in the field3,152,77940m
Results received in last hour41,4780m
Result turnaround time (last hour average)62.03 hours0m
Results returned and awaiting validation2,492,15540m
Workunits waiting for validation2540m
Workunits waiting for assimilation25,05040m
Workunit files waiting for deletion1240m
Result files waiting for deletion840m
Workunits waiting for db purging459,03040m
Results waiting for db purging973,14640m
Transitioner backlog (hours)00m
* minutes (m) or hours (h) since last checked

Splitter status

File nameSizeProgress
02mr08ag50.07 GB (14)
02mr08ah50.07 GB (13)
03mr08aa50.07 GB (12)
03mr08ab50.07 GB (13)
03mr08ac50.07 GB (10)
03mr08ad50.07 GB (13)
03mr08ae50.07 GB (11)
03mr08af50.07 GB (14)
03mr08ag50.07 GB (12)
03mr08ah50.07 GB (13)
03mr08ai50.07 GB (8)
03mr08aj50.07 GB (12)
04mr08aa50.07 GB (11)
04mr08ab34.89 GB
12mr08af50.20 GB (7)
17ap08ac1.63 GB
19ap08aa50.20 GB
21ap08aa50.20 GB
22mr08aa50.20 GB
22mr08ab50.20 GB
23mr08ae18.45 GB
26mr08ad20.33 GB (14)
27mr08aa17.94 GB (14)
28mr08ae50.20 GB
28mr08af50.20 GB
28mr08ag50.20 GB
28mr08ah50.20 GB
28mr08ai50.20 GB
28mr08aj50.20 GB
29mr08aa50.20 GB
total channels on disk:420
channels in progress:9
channels done:127
channels ended in error:55
total channels to do:229
: channels in progress
: completed channels
: channels with errors
(each file contains data for 14 channels)

Client Connection Statistics

For a periodically updated list of client types/versions that recently connected to our servers, click here.

 

Glossary

Programs:

  • BOINC database: The mysql database that contains all BOINC related information (user stats, forum messages, basic workunit/result information, etc.).
  • BOINC replica database: A back-up server which contains an identical copy of everything in the BOINC database. Read-only queries can be aimed at this server to lessen the load on the BOINC database.
  • primary science database: The informix database that contains final science products returned by SETI@home clients.
  • secondary science database: Like the BOINC replica database, this is a back-up redundant read-only science database server.
  • data-driven web pages: Pages that require database access to be generated. Pages like the forums, or ones that contain statistics or client version information, etc. are occasionally turned off (by hand) when the database is down.
  • upload/download server: Handles workunit/result transactions initiated by BOINC clients. When a client requests a workunit, this server sends it out. When a client has a result to send back, this server reads it and saves it to disk for later validation/assimilation/etc.
  • scheduler: Determines what work is going to be sent to/received from requesting clients. Clients go to the scheduler first to request work, and the scheduler tells the client what to get and where to get it. If this is off, you cannot get any new work. After a client sends a result back, it then contacts the scheduler which then marks it as received.
  • feeder: Fills up the scheduler work queue with workunits ready to be sent. The scheduler is usually too busy handling client transactions to maintain such a queue itself.
  • transitioner: Handles state transitions of workunits and results. Basically, the transitioners keep track of the results in progress and makes sure they properly move down the pipeline. It is always asking the questions: Is this workunit ready to send out? Has this result been received yet? Is this a valid result? Can we delete it now?
  • sah_validate: Validates SETI@home results by comparing them with similar results returned by other users. If enough results for the same workunit have been returned, the validator compares the data, deems one result from the set the "canonical" result, and issues credit to all responsible users accordingly.
  • sah_assimilator: Takes scientific data from validated results and puts them in the SETI@home master database for later analysis.
  • file_deleter: Deletes input/output files when no longer needed (i.e. after assimilation). This program keeps our upload/download disks as empty as possible.
  • sah_splitter: Reads tapes (or tape images on disk) containing raw telescope data and creates workunits for the BOINC/SETI@home clients. At least one needs to be running to produce work, and that's usually enough.
Hosts
  • bambi: Intel Server (2 x 2.66GHz Xeon, 8 GB RAM)
  • bane: Intel Server (2 x quad-core 2.66GHz Xeon, 4 GB RAM)
  • bruno: Intel Server (2 x 2.8GHz Xeon, 12 GB RAM)
  • jocelyn: Sun V40z (4 x 2.2GHz Opteron, 28 GB RAM)
  • lando: Intel Server (4 x 3.20GHz Xeon, 4 GB RAM)
  • ptolemy: Intel Server (2 x 3.06GHz Xeon, 12 GB RAM)
  • sidious: Intel Server (3 x dual-core 3GHz Xeon, 24 GB RAM)
  • thinman: AMD Server (2 x 2.4GHz Opteron, 16 GB RAM)
  • thumper: Sun Fire X4500 (2 x dual-core 2.6GHz Opteron, 16 GB RAM)
  • vader: Intel Server (4 x dual-core 3GHz Xeon, 16 GB RAM)
Database/file status states
  • Results ready to send: For each workunit, "empty" results are generated that are then sent out to individual users to be filled with data. This is the number of excess empty results ready to be sent out, i.e. a backlog in case demand exceeds the current rate of creation.
  • Results out in the field: Number of results currently being processed by clients.
  • Result turnaround time: The average "wall time," taken over the last hour, between when a workunit was downloaded and its result was uploaded.
  • Results returned and awaiting validation: Number of finished results that have been uploaded to our servers, but their constituent workunit has yet to reach quorum (usually because the redundant result is still being process by another client).
  • Workunits waiting for validation: The number of workunits that reached quorum and are waiting to be validated.
  • Workunits waiting for assimilation: The number of workunits waiting to have data from their canonical result input into the master science database.
  • Workunit/Result files waiting for deletion: The number of workunit or result files which can be deleted from disk, as the workunit has been assimilated, and there is no more use for it or its constituent results.
  • Workunits/Results waiting for db purging: The number of workunits or results which have been deleted from disk and, after a short grace period (currently 24 hours), will be purged from the database. It is during this grace period that completed results can still be viewed in your personal account pages. For safety, important information is written to disk and archived before these rows are deleted.
  • Transitioner backlog: Amount of time that the transitioner is behind (i.e. the age of the oldest result in the database waiting to be transitioned to another state).
 

Copyright © 2008 University of California