GuildWiki talk:Server status

Hopefully this page will become reliably informative of the server status.--Ender A 07:41, 16 November 2006 (CST)
 * How could it? How should anybody even find it? Nothing links to it currently. And if the server is down, you can't access the status page to find out why. Doh! I don't see this as a solution. Instead, the server admins should set up a page on gamewiki.org, or a sticky thread on the GuildWiki forums on gamewikis.org or GWGuru. --[[Image:TurningL sml.gif|Tetris L]] 05:43, 17 November 2006 (CST)
 * Depending on the nature of the hypothetical problem, we won't be able to post the status on our own servers at all. At the moment everything but Hammer/NWN are on the same machine (and those will probably end up on this one).  --Fyren 06:08, 17 November 2006 (CST)
 * I understand that if there are severe server problems, to the point at which none of GuildWiki is responsive, that this page will not function. However, that doesn't mean that it is pointless. First, if there are server issues like the past few weeks', then people will be able to get through to the page, it will simply be challenging. Second, people can find the page by searching for the word "Server" in the search box (presuming they choose to search amongst GuildWiki sub-pages.) Third, this page is relatively new, and I would expect that pages will begin to link to it once they know of its existence. Fourth, this page also serves as a reference for external status pages in case the server does go down. The point is to provide GuildWiki with an informative page simply about the Server status, since I cannot find a preexisting one.


 * Case example: My experience over the past few weeks. I was able to use GuildWiki (quite slow, but possible,) so if I had searched for Server or if someone else had linked the page in a Talk page when complaining of the usage difficulties, then I would have been able to find this page. Presumably this page would have had the external references to the GWG forums so I could refer to them, would have explained that the server issues were caused by a cpu-overload, and would have explained that a server was due to arrive soon. And now, after the issues are gone, this page can serve as an explanatory page of those past issues, as well as a reference point to the GWG forums where things are explained more fully, and where people can remember to look to should other server issues occur.--Ender A 23:48, 19 November 2006 (CST)

Ugrade
Kudos to the people who financed and performed the upgrade. The wiki is incredibly responsive now. --Delia Rashesh (talk) 02:04, 18 November 2006 (CST)
 * Ditto.--Ender A 23:15, 19 November 2006 (CST)
 * V> Ditto Raxous 07:17, 23 November 2006 (CST)

Upgrading MW, rebooting
I'm going to upgrade to MW 1.8.2 since there are some changes that we care about for the backend. Since it'll mean a little downtime anyway, I'm going to reboot one of the other machines to change something at the same time. I'm not sure if I'm going to do it tomorrow night or the night after since I might be going out tomorrow night. --Fyren 03:31, 21 November 2006 (CST)

Where the hell is it
where the hell is the sever nad how do i download builds and stuff from it


 * I have no idea what you're talking about. We do not have a server from which you can download builds. Please be more polite.  &lt;LordBiro&gt;/&lt;Talk&gt; 16:30, 22 November 2006 (CST)

Techie Info
Any chance we could get a page of info about the techical setup being used? Hosting company, Server Spec, Bandwidth, Bandwidth usage, OS & App versions etc. For us technophiles. Also if you need any help or want to consider mirroring etc then I'd be happy to help / contribute:-) Raxous 07:17, 23 November 2006 (CST)
 * All the machines are running FreeBSD (since that's what Gravewit chose, there doesn't appear to be a deep reason behind it). There's a P4 in front right now running squid 2.6S3 (which used to run apache/apache+squid when things were incredibly slow).  Behind it is a dual Xeon (the new machine) running apache 2.0(.59? don't remember) and memcached 1.1.12.  mysqld is running on another dual Xeon.  All the machines have 3-3.5 gigs of RAM.  war and nwn are running on apache 2.2 on the DB machine right now, but will be moved over at some point.  I don't know specific info about our hosts/bandwidth besides that Steadfast/Nozonenet is the company and we're pretty much using all the bandwidth we have (I only have squid logs to go off of at the moment).  Gravewit would have more info.  --Fyren 22:09, 23 November 2006 (CST)

Boom
Sometime in the afternoon squid died and Gravewit rebooted the machine. I see why squid died, but not why it didn't boot, since nothing had changed since last boot that matters. I also rebooted the machine a few minutes ago. --Fyren 20:32, 23 November 2006 (CST)

Hiccup
Today seems like a bad day. As far as I could tell, our host or someone upstream of them was having network problems sometimes. A few people mentioned that they couldn't get to the wiki randomly but it would work minutes later. Now the DB server freaked out; not sure what's up with that yet. Had to kick it in the head to get it going again. --Fyren 20:29, 21 December 2006 (CST)

Latest hiccup
Wasn't us, it was our host. Even their own web site was unreachable. Quality! --Fyren 16:27, 25 April 2007 (CDT)

Latest latest hiccup
Frankly, no clue. The web server machine went poof. After I contacted Gravewit and he contacted our host, the machine eventually came up. I don't really have more info than that. --Fyren 06:01, 11 June 2007 (CDT)