CANCELLED: cpanel16 Upgrade on 9/20/06

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

    #1

    CANCELLED: cpanel16 Upgrade on 9/20/06

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

    On September 20th, cpanel16 will be upgraded to our new platform. More information on this can be found here: http://forums.dathorn.com/showthread.php?t=2094

    Instead of being on cpanel16, users will now be on cpanel53.

    Server: cpanel53.gzo.com - 70.86.110.226
    DNS #1: dns105.gzo.com - 70.86.110.228
    DNS #2: dns106.gzo.com - 70.86.81.88

    IMPORTANT
    Anyone that has custom nameservers or that has used the cpanel16 DNS IP addresses (69.41.231.10 and 69.41.231.11) 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 cpanel16 account transfers have been completed.

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

    Beginning on September 20th, we also advise all users to disable anything involving MySQL updates (order forms, forums, CMS, etc.) until it is running on the new servers. This will avoid updates being lost during the transfer and ending up with a database that is a few hours old. If this is not an option, you can leave everything active, cpanel16 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.
  • AndrewT
    Administrator
    • Mar 2004
    • 3657

    #2
    Note that during this upgrade any domain usernames that have dashes or underscores in them will be renamed to exclude these symbols. Customer usernames with dashes in them will remain the same.

    Comment

    • AndrewT
      Administrator
      • Mar 2004
      • 3657

      #3
      We are beginning to transfer the actual dis#### reseller accounts, when each one is done you will no longer be able to access WHM on cpanel16. We have to do this so that we can get them properly transfered to the new server with the appropriate permissions prior to the actual domain accounts being transfered. I apologize for any inconvenience this may cause.

      We will begin transfering the domain accounts as early as we can today so that we can go ahead and get this move completed.

      Updates on our current progress will be posted in this thread throughout the entire process.

      Comment

      • AndrewT
        Administrator
        • Mar 2004
        • 3657

        #4
        All cpanel16 customers should now be able to login to WHM on cpanel53 with the same login information as they used for cpanel16. 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 cpanel53 as your server.

        All remaining domain accounts are now being transfered from cpanel16 to cpanel53.

        Comment

        • AndrewT
          Administrator
          • Mar 2004
          • 3657

          #5
          We just discovered incorrect hard drives installed in cpanel53. Due to this, we are going to go ahead and cancel the cpanel16 upgrade and perform it sometime next week. An entirely new thread will be posted here regarding the upgrade once we are prepared to proceed. I sincerely apologize for any inconvenience this might cause.

          WHM reseller access has been re-enabled on cpanel16 and we are in the process of reseting the access privileges for each user. This should be complete within an hour. The customer control panel should also list cpanel16 as your server once again. If you have any questions or experience any problems as a result of this, please submit a trouble ticket.

          Comment

          Working...