Running. In a few months, the server will move to Braunschweig (in fact, I'll move and take the server with me :) ), so there will be at least a day downtime then. OTOH, there'll be a 100 MBit internet connection :)
The server is on the move now. It is scheduled to be back online by tomorrow, 31.03.2008.
It would be nice to have an automatic mechanism to move the buildbots between the servers. Both servers could watch each other - if one of them goes offline, the other would wait a few minutes and then forcibly take it's role. When the first one comes back online, it would see that it has lost it's role, and would wait for an administrator that would give it it's role back (it shall not take it's role back automatically, because it cannot be sure that it won't go back offline soon again). I feel like tinkering :> --Martin von Wittich 21:43, 9 February 2008 (CET)
|Start date (UTC)||End date (UTC)||Reason|
|30.03.2008 11:20||31.03.2007 15:00||
EDIT: still need more time. The new kernel is running fine, I've even correctly configured grub for falling back to an older kernel when a kernel update should fail. Now I still gotta fix that buildbot setup. I'll try to leave it running most of the time, though.
EDIT: I'm done now. I've fixed the buildbot mess, it's installed via portage again now. Wasn't able to fix the non-working serial console in grub though :/
YET ANOTHER EDIT: fixed some permissions problems my brother had caused.
|06.12.2007 10:25||06.12.2007 10:30||
|05.12.2007 21:00||05.12.2007 21:45||
|21.11.2007 15:20||21.11.2007 17:10||
|01.10.2007 ~15:00||01.10.2007 ~21:00||
|05.09.2007 07:55||05.09.2007 08:30||
|04.09.2007 21:05||04.09.2007 21:10||
|25.08.2007 16:00||25.08.2007 17:00||
|28.06.2007 15:00||28.06.2007 18:00||
|27.06.2007 21:30||28.06.2007 15:00||
|CPU||2x Intel Xeon 5310|
|Memory||Kingston ValueRAM FB-DIMM 8 GB DDR2-667|
|Hard disks||3x 305GiB, 1x 27GiB|
/dev/md0: RAID5 (3x 297GiB); /dev/md1: RAID0 (3x 1027MiB)
|Host operating system||FC7|
|VM operating system||FC7|
- May 2007: We finally got a replacement mainboard from Alternate, not the one we sent in, but a very similar one, so the server is now back up. The object files are now placed on a RAID0 with three disks, improviving the build time from ~15 to ~10 minutes.
- March 2007: As long as the new server doesn't work, the old server is back online.
- February 2007: Martin comes up with the idea to put plenty new SATA hard disks into the server, but the old mainboard has no SATA support, so the whole server needs to be replaced. The ReactOS team decides to co-fund the upgrade and instead of consumer level hardware, a full-blown Xeon QuadCore server is bought. Due to problems with the online shop, it took a few weeks to get the new server up and running - only to find out that the mainboard sometimes simply won't boot and has to be sent back for replacement.
- Long ago: Christoph installs the buildbot on Martin's private server, then an old AMD 800MHz with 512 MB RAM. The RAM is later upgraded to 1024MB, the CPU is replaced with a Sempron 2500+.