Tony

It's used to store various mysql system information. It's not something you should remove and I don't think you can remove it anyways.

This has been completed.

This has been completed.

Everything is back up now. This is clearly the fault of gremlins. We will work on making our machines gremlin proof. [ATTACH]31[/ATTACH]

To summarize what happened is the bad drive started throwing errors which in turn messed up the file system. We usually can just reboot the machine and handle the issue from the unfortunately in this case we could not. On site technicians were able to get the machine back into the OS after being able to run a fsck (we did not even get it to boot that far). The best case scenario the machine just runs as it should and we replace the bad drive without ever even rebooting the machine. This is not always the case depending on what the bad drive does. We did however not lose any data so the raid system did most of it's job. The drive reporting medium errors is being replaced right now and we'll keep this open until it's finished rebuilding the array.

The machine is back online but this isn't the end of it. Right now the i/o wait is through the roof and we're working on getting rid of the bad drives.

Okay so here's the latest I have after speaking with the guys working on it. I'll go with a full story though: We rebooted the machine and we noticed hey the raid card is reporting something funky. Usually that means we lost drives or something along those lines. So a bad drive spit bad things out caused the file system to lock itself and we reboot and problem solved. We'd just need to replace a bad drive no worries. This is not what happened though the machine just refused to boot any further. This is when we needed a more hands on look into the machine. The datacenter technician working on the issue reboots it again notices the same thing and says well that's odd. So their reboot did get further and we're running a fsck now on the file system. As that is happening we're also going to most likely be replacing a faulty drive or two. We hope it was just bad drives and the raid card was sleeping on the job and did not throw the bad drives out of the array before they could cause issues.

Really not sure when it'll be back up at this point. It would not surprise me if it's down for an hour or two. It depends on the problem as to how long it's down and we have not got confirmation on the issue which usually means it's not good.

I'll start with well I had plans of a being to sleep early tonight as I have to be up early. Unfortunately Brian alerted me to a problem and as I am a control freak I will be overseeing this until it's all resolved which could mean I may not sleep.

Discussion going on here: http://www.hawkhost.com/forums/showthread.php?t=399 Nothing to report right now technicians are still working on it.

Feel free to vent here about how you hate computers or specifically the hardware on this machine.

Right now we're having datacenter technicians look into this as this appears to be a hardware problem. We have reason to believe it may be an issue with either the raid card or even the motherboard. We'll post further when we have an ETA on things being back up.

We are currently investigating problems on the Jupiter server. We'll update further when we have more information.

This has been completed.

This has been completed.

They are not needed they're used for strictly frontpage.

Both are available

This has been completed.

This has been completed.

mod_security blocks query strings like ?url=http://anotherurl.com/ You can make a ticket and we'll disable it for that domain.

Date: 05.08.2009 Start time (CDT): 01:00 End time (CDT): 04:00 Services affected: 10G backbone link, Level3 Location: Dallas, TX Duration: 15 minutes ================================================== Level3 will be performing software maintenance on May 8th starting at 01:00 CDT. Expected down time is approximately 15 minutes. Customer Impact: Traffic on the Level3 link or destined for the Level3 link when it is taken off line may see latency or sub-optimal routing as traffic is routed through our other, redundant links. ==================================================

You're going to need to make a support ticket.

Add-on domains do not have their own cPanel while accounts under a reseller do that's the big difference. So if you're hosting your own sites then you probably do not need your own cPanel. The other thing to keep in mind is if one of your sites gets hacked from some PHP script exploit it will probably go through all the sites. That's the other thing to keep in mind as this situation will not happen when they're all their own accounts.

Make a ticket requesting the domain to be changed. Keep in mind this changes just the domain not any content so if it's currently an add-on domain you'd need to move it's contents into the public_html folder.

Good to hear! Tell your friends