Previous · 1 . . . 8 · 9 · 10 · 11 · 12 · Next
|We are back up after restarting the Snap Appliance and making sure
everything is OK
||1||5207||30 Aug 2004|
|After fixing a few inevitable gotchas,
we are back up with the major version upgrade to 4.x.
The servers may be slow in responding as all clients will be
getting a new supply of work.
Everyone will need to download a new c
||1||5239||29 Aug 2004|
|A fix to scheduler code to get around a possible memory leak
was causing it to bomb after a number of connections.
We have backed out this change for
now and the scheduler seems to be working OK at this point.
||1||5382||29 Aug 2004|
|The migration plan has been rescheduled for tomorrow the 29th at 10am PDT
||1||6857||28 Aug 2004|
|The last set of hardware issues have been resolved
||1||4825||27 Aug 2004|
|We are currently experiencing a hardware issue with our scheduling server,
we expect this issue to be resolved within the hour
||1||5710||27 Aug 2004|
|We have brought down the splitters, transitioners, and scheduler until a
bug in the splitter can be resolved which was causing a bogus URL to be
posted for the work-unit.
||1||4952||26 Aug 2004|
|We fixed the bogus URL bug and all servers are back up
||1||4754||26 Aug 2004|
|A trio of splitters are now up and producing new work.
We plan to release major version 4 of BOINC and SETI@Home
A clarification about last week's fallback to an earlier
DB state: all work that was uploaded
||1||5245||25 Aug 2004|
|The validator is up and running and credit is now being calculated
for all those backlogged results.
||1||4869||23 Aug 2004|
|We are currently working on getting the alpha/beta projects working again, as well
as getting new workunits generated so that when we restart the public SETI@home project
there will be work to send out to the clients.
||1||6282||20 Aug 2004|
|The database has been restored and is being checked now
||1||5320||19 Aug 2004|
|We are now recovering the database from a snapshot made
a few days ago
||1||4996||18 Aug 2004|
|The project ended up running all night despite the dropouts, but this
afternoon we encountered a sudden raid failure that caused some data
||1||4949||17 Aug 2004|
|Currently the project is up, as we were unable to recreate the
problems we were seeing on Friday
||1||4995||16 Aug 2004|
|Today we are continuing to work with Snap technical support to
solve our mounting problems
||1||5184||16 Aug 2004|
|We encourage everyone to run SETI@home Classic
during our server outages.
SETI@home Classic makes the same scientific contribution
||1||4901||14 Aug 2004|
|All the data has been copied to the Snap device
||1||5602||13 Aug 2004|
|The download directory is fully transferred at this point, but we
are still waiting for the upload directory to finish
||1||5227||12 Aug 2004|
|The DB is now on the Snap Appliance and the web site is back up.
The project itself is still down as the transfer of the upload and
download directories is still under way.
||1||4864||12 Aug 2004|
|The project is now down for the move of the DB and the upload
directory to the Snap Appliance
||1||4762||11 Aug 2004|
|We have started the copy of the download directory to the Snap
||1||4948||10 Aug 2004|
|The servers are back up as far as receiving results but not as
far as distributing new workunits
||1||5393||8 Aug 2004|
|The scheduling server is down while we work on a download storage
||1||5179||7 Aug 2004|
|We developed a hierarchical directory structure to get around the
big directory problem (see August 4, below)
||1||6002||6 Aug 2004|
|A misconfigured scheduling server ran for about an hour this morning,
misinforming users that they had to upgrade to version 4 of the
||1||5293||5 Aug 2004|
|We discovered that the sheer number of files in the upload directory
was killing NFS performance for the file_upload_handler
||1||5812||4 Aug 2004|
|While the project is up and functioning normally, the database and
web servers are overloaded
||1||4834||3 Aug 2004|
|The project remained down all weekend, but we are back up now.
To add insult to injury, the entire lab lost network connectivity
to the rest of the world for a few hours this morning.
In light of the unexpected length of this las
||1||5415||2 Aug 2004|
|The project is *still* down
||1||5074||30 Jul 2004|
|The project is currently down
||1||4804||28 Jul 2004|
|We have shutdown the schedulers and file upload handlers so the transitioners
can play catch up again
||1||5094||25 Jul 2004|
|The project is down while we deal with a backup problem
||1||4928||25 Jul 2004|
|The good news is that the scheduler is now running as a fast cgi
which means it maintains a persistent connection to the DB
||1||5599||23 Jul 2004|
|We are now up and running again, during the night we generated 400k
results to be sent out
||1||5135||23 Jul 2004|
|Yesterday we introduced a bunch of performance enhancements to the
||1||5245||22 Jul 2004|
|We found and fixed the no results bug
||1||5199||22 Jul 2004|
|The log files are currently being compressed, after thats done the
project should return to normal.
||1||5318||21 Jul 2004|
|We have brought up an additional transitioner to try and cut through
the backlog we have accrued
||1||5468||19 Jul 2004|
|Sometime between 5pm and 12am PDT, the splitters seem to have
stopped producing new workunits
||1||5222||19 Jul 2004|
|A server bug was preventing
new results from being created in response to failed results.
If 2 out of 3 results for a WU succeeded and the 3rd failed,
the 2 successful results would not be validated or credited.
This is no
||1||5214||17 Jul 2004|
|Our database server hung and had to be forcibly terminated.
It took several hours to check all the tables and indices.
Then we ran into problems with our
Network Attached Storage device, which we rebooted
for the first tim
||1||5663||13 Jul 2004|
|It looks as though the server components
(splitter, transitioner, feeder, scheduler)
are now keeping up with demand.
||1||5399||9 Jul 2004|
|Since yesterday evening we have distributed over
||1||6129||8 Jul 2004|
|We have moved the scheduling server to another machine in
order to free up CPU and memory for the DB server
||1||5292||8 Jul 2004|
|We're making some major changes to deal with
server performance problems.
The project will be shut down for several hours today.
||1||5424||7 Jul 2004|
|We made some progress and are turning the project on.
You may still have problems getting work.
If that is the case, you might consider switching
back to SETI@home Classic for the next few days.
||1||5765||2 Jul 2004|
|We've been having problems with server performance.
To address these problems we're making some changes to our database.
The project will be shut down most of today while this is being done.
||1||6100||2 Jul 2004|
|Yesterday morning we shut down the front end of the system
to let the transitioners catch up with several days worth
of backlogged work, which is why some of you were noticing
three results and no credit assignment
||1||5754||30 Jun 2004|
|The web site has been reenabled.
We have several upgrades scheduled throughout
the week which should help with the performance problems.
If the project runs out of work again you are welcome to
revert back to the original
||1||5252||27 Jun 2004|
This message board is available as an RSS feed
©2018 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.