5/8/07 - Emergency cpanel17 Upgrade

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • AndrewT
    Administrator
    • Mar 2004
    • 3653

    5/8/07 - Emergency cpanel17 Upgrade

    I apologize for the late notice on this but due to some problems with cpanel17 we've decided to go ahead and perform an emergency upgrade.

    ATTN ALL customers located on cpanel17, please read and understand this entire thread thoroughly.

    On May 8th (today) starting at around 10AM CST cpanel17 will be upgraded to our new platform. More information on this can be found here:
    I just wanted to keep everyone updated on what is happening behind the scenes here, I apologize for the long read but I think it's well worth it. ;) New Server Platform & Server Upgrades First and foremost, our previous routine for upgrading servers is going to change. Instead of replacing old servers with new ones, we


    Instead of being on cpanel17, users will now be on cpanel59.

    Server: cpanel59.gzo.com - 75.126.144.68
    DNS #1: dns117.gzo.com - 75.126.196.8
    DNS #2: dns118.gzo.com - 75.126.202.33

    IMPORTANT
    Anyone that has custom nameservers or that has used the cpanel17 DNS IP addresses (69.41.236.100 and 69.41.236.101) for anything will need to update their entries to the new nameservers and IPs listed above.

    To avoid all possible downtime on your domains, do not make any DNS changes until we have confirmed here in the forums that the cpanel17 account transfers have been completed.

    Those that are using the cpanel17 gzo.com nameservers (dns33/dns34) without IPs, do not need to change anything. They will be updated to the new IPs automatically.

    We advise all users to disable anything involving MySQL updates (order forms, forums, CMS, etc.) until it is up and running on the new server. This will avoid updates being lost during the transfer and ending up with a database that is out of sync. If this is not an option, you can leave everything active, cpanel17 will still be online for a few days following the upgrade. But you will be responsible for transfering any database updates that might be needed.

    Once again, if you have any questions or comments, please post in the forum thread that is linked above or submit a trouble ticket.
    Last edited by AndrewT; 05-08-2007, 06:51 PM.
  • AndrewT
    Administrator
    • Mar 2004
    • 3653

    #2
    Note that as a result of this upgrade you will no longer be able to access WHM on cpanel17.

    All cpanel17 customers should now be able to login to WHM on cpanel59 with the same login information as they used for cpanel17. Please do not do anything with this yet, however, as the domain accounts have not been transfered yet.

    If you login to the customer control panel and view your welcome e-mail, it should now list cpanel59 as your server.

    We're now transfering accounts from cpanel17 to cpanel59. This process may take 24 hours or so to complete.

    Comment

    • AndrewT
      Administrator
      • Mar 2004
      • 3653

      #3
      The account transfers are coming along very well. Everything should be completed by late tomorrow morning.

      Comment

      • AndrewT
        Administrator
        • Mar 2004
        • 3653

        #4
        This is taking a little longer than expected. But everything should be completed by sometime this afternoon or early this evening.

        Comment

        • AndrewT
          Administrator
          • Mar 2004
          • 3653

          #5
          All accounts have now been transfered. You should now change your DNS/nameservers to the new cpanel59 nameservers if necessary.

          You may need to re-install SSL certificates on the new server (cpanel59). If you purchased one from us simply submit a ticket and we can re-install it for you.

          Also, if your scripts require PHP's register_globals to be enabled, you will need to create a php.ini file in the exact directory of the script that requires the setting with the following line in it:

          register_globals = On

          If you encounter any further problems, please submit a trouble ticket.

          Comment

          • AndrewT
            Administrator
            • Mar 2004
            • 3653

            #6
            HTTP on cpanel17 will be disabled next Wednesday (5/16/07). Please be sure that all DNS updates are made prior to that.

            Comment

            • AndrewT
              Administrator
              • Mar 2004
              • 3653

              #7
              HTTP has been disabled on cpanel17. cpanel17 will be taken offline entirely next Wednesday (5/23/07).

              Comment

              • AndrewT
                Administrator
                • Mar 2004
                • 3653

                #8
                cpanel17 has now been taken offline entirely.

                Comment

                Working...