eLime Design Studio Blog

Update

noreply@blogger.com (Eric) — Thu, 21 Aug 2008 05:43:00 +0000

The issue has been narrowed down to a windows update.

Web sites/email should be back online now.

Update

noreply@blogger.com (Eric) — Thu, 21 Aug 2008 05:36:00 +0000

The high CPU usage cause has been found and fixed. There was a Microsoft/VZ update that need to be installed.

We are now experiencing random IIS crashes since the installed updates. We are working to fix the issues.

CPU Issue

noreply@blogger.com (Eric) — Wed, 20 Aug 2008 23:14:00 +0000

We have found the cause of the high CPU usage but will not be saying what it was until the issue is resolved 100%. The server was back online around 4:40PM MST.

CPU Usage Update

noreply@blogger.com (Eric) — Wed, 20 Aug 2008 22:26:00 +0000

At 4:20 PM MST we had to mount the server (take it offline) to dig deeper into the issue.

Sorry for the inconvenience.

High CPU Usage

noreply@blogger.com (Eric) — Wed, 20 Aug 2008 22:04:00 +0000

At 3:30 PM MST, I noticed very high CPU usage on the server and began investigating. The server is in the process of being rebooted and the investigation will continue to see what is causing the high CPU usage.

Scan Complete

noreply@blogger.com (Eric) — Fri, 15 Aug 2008 13:48:00 +0000

The virus scan ended around 2 AM. Infections were found and I am investigating to see how they got onto the server.

Scan Started

noreply@blogger.com (Eric) — Fri, 15 Aug 2008 01:55:00 +0000

The virus scan has been started.

Emergency Server Maintenance

noreply@blogger.com (Eric) — Fri, 15 Aug 2008 01:34:00 +0000

I will be performing an emergency virus scan on the server in about 15 mins.

The downtime will be 1-2 hours. The server has to be offline so the virus scanner will scan all the files instead of just a few.

Sorry for the inconvenience but this comprises the server security and has to be done.

High CPU Usage

noreply@blogger.com (Eric) — Fri, 15 Aug 2008 01:05:00 +0000

Right now I am seeing very high CPU usage on the server. I have already rebooted but the high usage came back immediately. I am keeping a close eye on the server and trying to get the CPU back to normal.

Horde

noreply@blogger.com (Eric) — Fri, 08 Aug 2008 23:08:00 +0000

POP3 is working with Horde now. MySQL is also working fine.

Move Completed

noreply@blogger.com (Eric) — Sun, 03 Aug 2008 16:28:00 +0000

I forgot to update last night but everything was online by 10 PM MST.

I have noticed some MySQL errors and HORDE doesn't work with POP3 at the moment. We are working to fix this issues A.S.A.P.

IP Switch

noreply@blogger.com (Eric) — Sun, 03 Aug 2008 01:16:00 +0000

The IP's have been switched but web sites are not finding their IP address. We are working on this as an emergency matter.

IP Switch

noreply@blogger.com (Eric) — Sun, 03 Aug 2008 00:17:00 +0000

We started switching IP addresses.

Plesk Restore

noreply@blogger.com (Eric) — Sat, 02 Aug 2008 22:26:00 +0000

The Plesk/mail server restore was successful.

We will be changing IP address here in the next 1-4 hours.

Downtime should be 20 mins or less.

Plesk Restore

noreply@blogger.com (Eric) — Sat, 02 Aug 2008 20:57:00 +0000

The plesk restore was started at about 2:30 PM MST. It's about 80% done. The mail server backup will be restored next, then IP's switched.

Plesk Restore

noreply@blogger.com (Eric) — Sat, 02 Aug 2008 19:15:00 +0000

We have ran into license issues with Plesk and working on getting a new license. Once a new lic. is obtained we will finish the restore.

Downtime of 20 mins or less is expected when we switch the IP's.

Plesk Backup

noreply@blogger.com (Eric) — Sat, 02 Aug 2008 17:06:00 +0000

Plesk is now backing up and websites/email are offline until the backup finishes.

Move

noreply@blogger.com (Eric) — Sat, 02 Aug 2008 16:53:00 +0000

Starting Plesk/mail server back up here in a few minutes.

Server Move: Update

noreply@blogger.com (Eric) — Sat, 02 Aug 2008 16:36:00 +0000

I have began installing the mail server, then will backup plesk and restore on the new server.

Update

noreply@blogger.com (Eric) — Sat, 02 Aug 2008 14:10:00 +0000

The server move will start after 12 PM MST this afternoon. There should be little downtime while we change the IP's.

Server Move: Update

noreply@blogger.com (Eric) — Sat, 02 Aug 2008 03:45:00 +0000

The move has not started yet. Still waiting on the server to finish being set up.

Server Move Update

noreply@blogger.com (Eric) — Sat, 02 Aug 2008 00:44:00 +0000

The new server is in the process of being set up and completed within the next 2 hours (8:45 pm MST). I will then start setting up the mail server and start the web site/email move after 9 PM MST.

For update to do status you can check out http://www.elimehostingonline.com/blog/ and Live chat will also be available at http://www.elimehostingonline.com starting at 9 PM MST.

Server Move: Phases

noreply@blogger.com (Eric) — Fri, 01 Aug 2008 17:04:00 +0000

Starting tonight (August 1, 2008) we will be moving to a new server due to issues on the current one.

The move process:
*times are estimated and may change* All clients have been emailed this info.

Phase 1: Set up temporary IP on the new server. Set up the mail server. 20-60 mins

Phase 2: Restore Plesk and mail server backups. 1-5 hours

Phase 3: Checking Plesk/mail server restore to make sure everything restored correctly 20 mins to 3 hours

Phase 4: Restore old IP's and make sure web sites and emails come back online 1-5 hours

The most downtime will occur during phase 4 when we are switching IP addresses. I am setting things up on the new server so everything is there when the old IP's are put back in place and DNS will work right away in some parts of US.

Horde Webmail

noreply@blogger.com (Eric) — Wed, 30 Jul 2008 23:43:00 +0000

We are working on Horde webmail since it is throwing MySQL errors. Horde still works and email can be viewed/sent from it. No client side issues just server side/backend.

Extended Maintenance Tonight

noreply@blogger.com (Eric) — Thu, 24 Jul 2008 15:02:00 +0000

Tonight (July 24) at 9 PM MST, I will be performing maintenance on the server to help with the issue that came up last night.

I will try to keep downtime to the minimum but the worm has attached its self to Plesk. I might have to turn Plesk off to run a full scan on the server. If this happens I will keep downtime to under 30 mins and try to leave the mail server online.