Cody R.

Administrators
 View Profile  See their activity

  • Posts

    781

  • Joined

  • Last visited

  • Days Won

    39

 Content Type 

Everything posted by Cody R.

  1. Cody R.
    Maintenance has been completed on this server and the VM's are starting up. This concludes this maintenance window.
  2. Cody R.
    Maintenance is starting on this server now.
  3. Cody R.
    The FSCK is complete and the server is now online. This concludes this maintenance window.
  4. Cody R.
    The FSCK is 80% complete.
  5. Cody R.
    The FSCK is 25% complete.
  6. Cody R.
    Due to some file system inconsistencies we've decided to perform a FSCK during this maintenance window to prevent any data issues down the road. We'll be updating this thread as it progresses.
  7. Cody R.
    The maintneance on this server has been completed.
  8. Cody R.
    Maintenance is starting on this server now.
  9. Cody R.
    Maintenance is starting on this server now.
  10. Cody R.
    We will be updating the kernel on the Jupiter server to the latest version between 11:00PM and 1:00AM EDT. The maintenance window is for 2 hours however the estimated downtime is 5 to 10 minutes. Date: 04/04/2012 Start time (EDT): 04/04/2012 11:00PM End time (EDT): 04/04/2012 1:00AM Duration: 2 hours Estimated Down Time: 5-10 minutes
  11. Cody R.
    We will be updating the kernel on the Yoda VPS node to the latest version between 11:00PM and 1:00AM EDT. The maintenance window is for 2 hours however the estimated downtime is 5 to 10 minutes. Date: 04/04/2012 Start time (EDT): 04/04/2012 11:00PM End time (EDT): 04/04/2012 1:00AM Duration: 2 hours Estimated Down Time: 5-10 minutes
  12. Cody R.
    We will be updating the kernel on the Jedi VPS node to the latest version between 11:00PM and 1:00AM EDT. The maintenance window is for 2 hours however the estimated downtime is 5 to 10 minutes. Date: 04/04/2012 Start time (EDT): 04/04/2012 11:00PM End time (EDT): 04/04/2012 1:00AM Duration: 2 hours Estimated Down Time: 5-10 minutes
  13. Cody R.
    Unfortunately I don't think you fully understand how RHEL releases / backporting works. I'd recommend doing some research prior to jumping to such grandiose conclusions .
  14. Cody R.
    The version has been backported with the patches. If you believe otherwise please contact our support department .
  15. Cody R.
    The machine is fully online at this time. This concludes this maintenance window.
  16. Cody R.
    The FSCK is done at this time and we're rebooting the machine.
  17. Cody R.
    The FSCK is currently at 85%
  18. Cody R.
    The FSCK is currently at 75%
  19. Cody R.
    The FSCK is currently at 25%
  20. Cody R.
    The FSCK is currently at 10%
  21. Cody R.
    Unfortunately this machine appears to need a FSCK due to file system inconsistencies so we'll be performing this now. Usually this takes about an hour so it should still be within the maintenance window. We'll post updates in this thread.
  22. Cody R.
    Maintenance has been completed on this server so this maintenance window is now closed.
  23. Cody R.
    Maintenance is starting on this server now. We'll update the ticket upon completion.
  24. Cody R.
    Maintenance is starting on this server now. We'll update the ticket upon completion.
  25. Cody R.
    In an environment like ours we strive for stability / consistency so we try to run the most stable releases which are generally a few versions behind (or in the case of RHEL a few versions behind with important security fixes backported). If you require a more up-to-date environment we recommend a more customizable environment such as a dedicated server or VPS / a provider who supports the versions you need. I do understand your frustration here however - we've just found that in an environment with so many users per machine a major upgrade to something like PHP or MySQL will tend to break things so we've opted for a slower more graceful upgrade cycle.