Tony

We will be migrating the accounts on the Jupiter server starting on Friday November 6th and this will last until Tuesday November 10th. The reason for this upgrade is our continued commitment to having exceptional quality of service. The Jupiter server is showing it's age in specification so we feel everyone would benefit from a much needed upgrade. For the migration process we will be moving accounts in sections based on IP address. We anticipate no more than 5 minutes of down time per account in order to make the switch. We migrate the account data then re-route the IP address to the new server. Thus there is no down time associated with the upgrade. The time frame given we estimate will not be nearly this long. In the past we have migrated to other hardware without any down time in less than three days. So our 4 days just gives us plenty of time to do it right and make sure there is no interruption in service. The specifications of the server will be similar to our Dallas machines being Dual Xeon 5520's with 12GB ram and four 300GB SAS drives in raid-10. Old Jupiter: Xeon 5430 4GB RAM 4x250GB SATA II Raid-10 New Jupiter: Dual Xeon 5520 12GB RAM 4x300GB SAS Raid-10 You'll notice three times as much memory and SAS drives which are significantly faster than the SATA counterparts. It'll also have twice as many CPU's and will be using the newer 5520 CPU. If you have any concerns about this migration please do not hesitate to contact us. Start Date: 11/06/2009 End Date: 11/10/2009 Estimated Down Time: less than 5 minutes Duration: 4 days

We'd just skin it again the cost is not a big deal. As far as when the current one will be done I'll be contacting some people this week. It's been very busy I keep putting this on the back burner This should start slowing down a bit though with a large majority of the upgrading of servers completed.

This has been completed.

83% complete should be finished Sunday at some point

50% completed thus far probably be finished Sunday at some point.

I'd renew it a few days before it expires. You can generate a new CSR and such before it actually expires then install the new one. Thus at no point does anyone get any errors about the SSL certificate being expired.

This tutorial also walks you through doing it properly: http://akrabat.com/zend-framework-tutorial/

Well looks like this machine is a 55xx series system as well due to availability issues with 54xx series. So the final specifications are as follows: Dual Xeon 5520 12GB RAM 4x300GB SAS 15K RPM Raid-10 We'll be starting the migration tomorrow :-)

You: Please make it possible to do automatic upgrades via the client area I can finally say this is possible for all shared hosting accounts. You can upgrade and downgrade via our client area. This is not possible on reseller or vps accounts though you'd need to make a ticket in that case. Any issues with it make a ticket otherwise one more thing that should have been automated ages ago but finally is.

The shark in the picture is big just imagine the one that bit this one! http://news.sky.com/skynews/Home/World-News/Shark-Mauls-Great-White-Fears-In-Australia-After-Shark-Bitten-Off-Stradbroke-Island-Near-Brisbane/Article/200910415419981?lpos=World_News_Carousel_Region_4

We probably would. I'll throw this out there any customer of ours who's interested contact me via pm here and we'll see. We probably should do the blog as well while we're at it. We obviously can pay or give free hosting goodies or whatever we're flexible. I might actually just contact some of our customers who run design companies might get a better response. It's funny with thousands of customers our forum only has about 50 actual registered users who are customers. That might even be on the high end.

My understanding is someone resolved the issue. Pluto has had a fun month with abuse of it Several users started mass deleting add-on domains triggering an annoying bug in cPanel that will not be resolved until some time in 11.25. It basically causing stats runs for each deletion. Users delete 20 add-on domains and we now have 20 stats runs going on all at once. It also then does restarts for each so we now have the web server doing rolling restarts. Abuse of system resources. Several users have made themselves known after their proxy like web sites started receiving 10,000 times as much traffic as before and obviously as a result got booted since proxy's are against our aup for this exact reason. No matter how much we try always one server where somethings go wrong. It's either hardware or abuse of the server or something. You simply cannot win with shared hosting.

You're best to make a ticket I imagine we forgot to set something on the crontab and an OS update change the permissions on us. But you'd need to make a ticket so we can figure out what server you're on.

We will be migrating the accounts on the Mercury server starting on Friday October 30th and this will last until Tuesday November 3rd. The reason for this upgrade is our continued commitment to having exceptional quality of service. The Mercury server is showing it's age in specification so we feel everyone would benefit from a much needed upgrade. For the migration process we will be moving accounts in sections based on IP address. We anticipate no more than 5 minutes of down time per account in order to make the switch. We migrate the account data then re-route the IP address to the new server. Thus there is no down time associated with the upgrade. The time frame given we estimate will not be nearly this long. In the past we have migrated to other hardware without any down time in less than three days. So our 4 days just gives us plenty of time to do it right and make sure there is no interruption in service. The specifications of the server will be similar to that of the Skyline & Skyline servers that received their upgrades recently. Old Mercury: Xeon 5430 4GB RAM 4x250GB SATA II Raid-10 New Mercury: Dual Xeon 54xx 12GB RAM 4x300GB SAS Raid-10 You'll notice three times as much memory and SAS drives which are significantly faster than the SATA counterparts. The CPU's is still something that is up in the air at this point. It's subject to availability but it'll be at least Dual 5430 so the new machine will have twice as many CPU cores. If you have any concerns about this migration please do not hesitate to contact us. Start Date: 10/30/2009 End Date: 11/03/2009 Estimated Down Time: less than 5 minutes Duration: 4 days

This has been completed.

75% completed should be finished mid day Sunday.

This has started.

It only emails when there is output. Is there any actual output? If you redirect to say /dev/null there will not be or if you use -q on a PHP script. There are other cases to but I cannot remember those off the top of my head.

I say that and now it's back on although it might not get started until late tomorrow due to the hardware availability issues. We're going to be using a Dual Xeon 5520 instead as we were able to put on onto our current Dallas VLAN.

This has been canceled due to availability problems of the server specifications.

This has been completed. It was basically completed since early this afternoon except for one VPS we did later in the day.

We will be migrating the Yoda node to new hardware starting on October 21st and it will last up until October 24th although we estimate it'll take not even 24 hours to migrate the entire node to new hardware. There will be no down time during this migration we will move VPS's using the migration tools in OpenVZ to minimize the impact of the move as much as possible. We're sorry about the short notice regarding this we were waiting on availability of hardware before posting any notice and we found out today the hardware was available and we'd like to use it immediately. Specification break down: Old Yoda Dual Xeon 5430 8GB RAM 4x250GB SATA Raid-10 New Yoda Dual Xeon 5520 24GB RAM 4x300GB SAS Raid-10 So this is a significant jump in specifications on this node. If you have any questions or concerns about this migration do not hesitate to make a VPS ticket. Start Date: 10/21/2009 End Date: 10/24/2009 Estimated Down Time: less than 5 minutes Duration: 4 days

Well you could run ns1 and ns2 on the same server most users do that. If you want ns2 to specifically be on another server then you'd need to arrange something yourself.

This was resolved and the guard did it's job.

http://www.candystand.com/play/vector-td Cody linked me to it I just had to play it once. First try my score was: 2,834,960