From Comcast High-Speed Internet, Fort Wayne, Indiana, USA:
Quote:
The connection has timed out
The server at nesdevwiki.ath.cx is taking too long to respond.
qmt.ath.cx is down too.
As I've said before, the QMT server is currently hosted on a residential network connection.
If you think
you're annoyed about the downtime, that's
nothing compared to how I feel about it.
The only reason the new NESdev wiki was hosted on my own site is because I couldn't host it here on parodius without having to have koitsu set everything up for me - it was my
original intent that, once the wiki was set up and working smoothly, it could be moved over onto parodius and the old wiki could be properly decommissioned.
For the record, it's back online now; if you guys want this wiki to get moved over to nesdev.com, just say so and I'll package up the database and configuration files.
[edit] And offline again, likely for the rest of the weekend. The text visible on its console from its last downtime was somewhat troubling - "kernel tr pkernel tr pkernel tr pkernel tr pkernel tr pkernel tr pkernel tr pkernel tr pkernel tr p"...
Quietust wrote:
The text visible on its console from its last downtime was somewhat troubling - "kernel tr pkernel tr pkernel tr pkernel tr pkernel tr pkernel tr pkernel tr pkernel tr pkernel tr p"...
Like
this?
tepples wrote:
Quietust wrote:
The text visible on its console from its last downtime was somewhat troubling - "kernel tr pkernel tr pkernel tr pkernel tr pkernel tr pkernel tr pkernel tr pkernel tr pkernel tr p"...
Like
this?
If you think it's that goddamn funny, then why don't
you offer to host the wiki
yourself?
A short excerpt of my ICQ log from my friend who actually owns the server:
Quote:
[Morvandium] well, that was interesting.... there was a line of bright white (perhaps what bold looks like in FreeBSD) "k"s (about 12 or so of them), and the console was unresponsive.
[Morvandium] There's not exactly much to see by looking into the case, and not much is visible in the power supply...
oh, god.
[Morvandium] It may be offline for a while
[Morvandium] Ok, maybe not, but now I'm very worried. It just detected an invalid CMOS checksum and opted to use a default configuration...
[Morvandium] I'm not sure if this will shed any light on the situation, but, here's what the server just spit out after sitting at the login prompt for a few minutes (all in bright white):
"F t l double f ult:
e p = 0xkernel tr p kernel tr p kernel tr p kernel tr p kernel tr p kernel tr p kernel tr p kernel tr p kernel tr p kernel tr p kernel tr p kernel tr p kernel tr p kernel tr p kernel tr p"
I'm going to be leaving around noon today (Friday) and I'll be out of town until Sunday.)
[Morvandium] Strange readings in the bios... I never picked up on this before, but the first set of readings (~80C values) change the moment you refresh... they're all sitting in the 53C-61C range, which is a lot more realistic.
For those who aren't aware, the actual messages are "Fatal double fault", interrupted by a long string of "kernel trap" messages (but with all of the 'a's missing), meaning that the server is suffering from some sort of hardware failure.
I apologize for making a joke that you would find so offensive.
I pointed out that the server is dying, and you proceeded to make a joke about it. How did you expect me to react?
Whatever. Unless Morv or I are able to repair the server, its instability will likely continue to the point where it will be offline permanently.
Quietust wrote:
I pointed out that the server is dying, and you proceeded to make a joke about it.
I did not know at the time that the error message represented a dying server.
Well, I just extracted about 10-15 cubic centimeters of dust (big clumps of it) from beneath the two CPU fans, enough to block a majority of the airflow across the heatsinks. I also reseated the two CPUs and heatsinks, put on fresh thermal paste, and reseated both DIMMs (one sounded slightly loose). Hopefully, the site should be staying online a bit longer now, but we'll have to wait and see.
Yes! Excellent. I've been looking into getting expansion sound covered on there (got VRC6 and N106 so far).
But if the unthinkable happens and the server up and dies completely, would everything be lost? Or are backups made every so often?
If we start adding pages and pages of content... it'd be a real shame if all of that just disappeared.
The server crashed again this afternoon, so it would appear that either there's some problem other than overheating, or one of the CPUs in the server was damaged from overheating (during the previous crashes).
I'm making nightly backups of the wiki database, in the (somewhat unlikely) event that something manages to get corrupted.
Update: the server did not crash - Morv powercycled the router and it grabbed a new IP address, and FreeBSD got confused; not knowing how to reset DHCP, he rebooted the server.
He now knows the proper method to reset DHCP (dhclient -r; dhclient xl0), so this hopefully shouldn't happen again.
So it looks like there were some other problems, after the server crashed two times in the span of one hour over the weekend. Memtest86+ showed errors on one of the 256MB DIMMs.
Removing one DIMM seemed to make the errors go away, but Morv wasn't able to test the "bad" DIMM before leaving for work; he likely tested it about an hour ago (during which a "The System is Down" page was visible), but I won't know the results until I get home from work (in about 5 and a half hours).
I'm going to be getting a 2 year lvl 3 plan at dreamhost within the next few months, so if you can't host it on this server I'm sure I could host it.
I could throw the nesdevwiki on dwedit.org if you want, but I'm not sure how long Mudi will be hosting me for free.
Out of curiosity, what sort of server/connection is Mudi hosting your stuff (i.e. animutationportal) on?
In other news, qmt appears to be temporarily offline; I'll find out why later tonight.
Ah.
In related news, qmt's reason for being offline is that the router reset and its IP address changed - once I get Morv's attention, it'll come back. One of these days, I need to get in there and figure out how to assign a static IP address for it (the last time I tried, the network interface refused to work properly).