By Support on 12/27/2007 6:17 PM

What do the Yugo, Chinese lead tainted toys and the V22 Osprey have in common?

 

Their engineer rejects all work for Plesk.

By Support on 12/27/2007 3:30 PM

Today and tonight we are migrating all clients on the Firebird server to the latest server in our fleet, Elvis. Please email support@amhosting.com if you have any issues to report and we will take care of them ASAP. The migration is in process right now. We will post another entry when the migration is complete.  

 

By Support on 12/19/2007 9:56 PM

Our engineers are looking into a problem on the Kong server where apache is just dropping offline.  They are currently upgrading the cPanel software, and then are going to rebuild apache.  We expect that it should be working soon.  Sorry if this has caused you any troubles.

By Support on 12/12/2007 8:40 AM

The very old server that was once Asteroids, a P4 1.6 with 512 megs of RAM (Very old) is now in Elvis.  Asteroids was a server that had very few customers on it (try like 32) and did not need its own server. 

Asteroids customers should notice a HUGE performance increase.  Asteroids has been very reliable over the past 10 years, and we expect the same for the Elvis server.

Our next server being migrated is p38. We may be doing that today or tomorrow.

By Support on 12/10/2007 10:31 PM

Today Ryan started and finished our first migration in months.  B29 is not online with Plesk 8.2.1, brand new hardware with HUGE hard drives and large amounts of memory.  The old server was a PIII with 768 megs or Ram.   it ran for many years, and got a nice refresh today.

You should see a huge performance increase.

We will be migrating p38 and asteroids tomorrow hopefully.  

Please let us know if you have any problems.  So far we have not seen any issues and no problems have been reported.

Good job Ryan on this migration!

By Support on 12/2/2007 11:30 AM

Well, I am very tired of having to deal with windows 3 and its problems. I have determined it to be hardware related, and the most odd things I have ever seen.  I had to down clock the memory, and put the old hardware back in, and its running so far without any issues.  

In a couple of weeks, I will down it again (late at night when there is low traffic), and switch the hardware with totally brand-new equipment that we will pre-Q/A.

Anyhow, its where it was before I started messing with it.

Sorry everyone. This was totally unexpected, and I really did not want have anyone down for as much as it was today. 

Seems to be steady now.

Travis

By Support on 12/2/2007 3:16 AM

Well,

We have been watching windows 3 after our hardware upgrades yesterday.  It was moving very fast, but we started to see some random reboots.  I came in tonight to try and figure out what was going on. I thought that maybe the motherboard was going bad. I upgraded the bios, I tried different processors, and I even did a Q/A check on the memory. 

What I didn’t even think to check was the CPU temperature.  Because the processor was so much faster then the previous one, the system was pumping out way more heat then expected. Even in our cold colo room, it could not maintain a normal temp. As soon as it started to get loaded up, it would just restart.. with no reason or anything.

Anyhow, I just now put in a HUGE heatsink on it, and we are running it in our development room over night away from all of the other servers.   So far, it has not rebooted.

I am going to go home, sleep for a few hours, and then check on it again when I get up.  If it has not rebooted, then I have the restart problem pinned, and will re-locate the server to another rack where we have a boat load of cold air.

Sorry for the down time everyone.  I tried very hard to keep it at a min. -- heading home. 3:15 am.

~Travis

By Support on 11/30/2007 11:09 PM

Sorry everyone for the down time on windows 3.  A simple hardware upgrade turned into a nightmare.  I had to call on Ryan to come back and fix the server.   Its about 11pm, and the server is re-syncing mirrored disks. 

The good news is that the processor is WAY faster then the last one we upgraded too, and we also moved the memory speed way up. For some reason it was set to 266 instead of 400.  Anyhow, this thing is MOVING FAST now!

We do apologize again for the down time.

We have some more upgrades for that box coming, but we are testing to make sure they work ok on separate backups of the server on development machines.   The new upgrade will move you to plesk 8.2, from the ancient plesk 7.

~Travis Whidden - 11/30/2007

By Support on 9/26/2007 4:27 PM

Windows4 has been acting up lately with strange issues and we feel the problem exists with a shared application pool. Shared app pools save resources on the server but a disadvantage is that if someone crashes the app pool, thing end up being really funky. This server is a powerhouse and only uses 20% of the resources, so we took it to the next level.

To solve this, We just enabled the server to assign individual application pools to each user.  This way, if you crash your own website, you don’t affect the rest of the users on the server.

The process is currently setting up each pool right now.  Please let us know if it does something funny as we want to make sure it does not do it again for you. 

Sincerely,

Travis Whidden

By Support on 9/7/2007 8:15 AM

We just updated windows 3 with a new faster processor, and are doing a few other things to make it faster. It seems that the older server needed a little upgrade.  There will be a few restarts this morning, but the performance of your websites should increase quite a bit. --TW