Cody R.

Administrators
  • Posts

    781
  • Joined

  • Last visited

  • Days Won

    39

Everything posted by Cody R.

  1. It's likely triggering a mod_security rule. Use these instructions to disable it (I would enable it again once the install is finished): https://support.hawkhost.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=96
  2. Everything has been online for a bit so we'll be closing this thread.
  3. The machine is online and the VPS' are booting.
  4. The filesystem check is completed and the machine is now rebooting.
  5. It's now 85% completed.
  6. The filesystem check is 75% completed.
  7. The filesystem check is 60% completed.
  8. We've had to run a filesystem check on the /home partition. It's currently 10% complete.
  9. A few minutes ago we received notices from our internal monitoring of extremely high IO wait on the VPS node. It appears there are filesystem issues causing the machine to crash and to become unresponsive. We're in the midst of attempting to reboot it and may need to run a filesystem check on it shortly depending on the health of the filesystem(s). We'll post more information shortly.
  10. We've ran into unanticipated issues and will be rescheduling this at a later date.
  11. If you don't mind me asking which files are incorrect permissions? Unfortunately I'm not familiar with the software so I can't help you in regards to the other issue.
  12. On Friday 11/19/2010 we'll be performing an upgrade to the MySQL server which includes a patch to allow us to better track high resource users which cause stability issues. We anticipate little or no downtime during this upgrade. Date: 11/19/2010 Start time (PST): 9:00am End time (PST): 10:00am Estimated Down Time: 0-10 minutes Duration: 1 hour
  13. Everything is currently online. We'll be evaluating the health of the drives in the server to see if any need to be replaced.
  14. The machine is online and booting services. Please allow a few minutes for everything to be booted and settle down. cPanel may be turned off during the boot to help alleviate the startup process. This does not mean your website will not be accessible.
  15. The fsck is done and we're rebooting the machine now.
  16. The fsck is 80% completed.
  17. The fsck is 55% completed.
  18. We're currently at 30% and moving along fairly quickly.
  19. The fsck is 10% done
  20. The rescue OS has no network connectivity so we're manually consoling in currently to start the fsck.
  21. At around 5:25AM EST the servers /home partition went read-only. We're in the midst of booting into our rescue kernel to start a fsck on the partition. We'll post updates in this thread as this progresses.
  22. He yelled at me. I fixed it. We're all happy again.
  23. Absolutely! After your order is processed you'll receive all of that information in a welcome e-mail .
  24. The RAID is still rebuilding and IO has settled down / everything has been online and responsive for awhile. Once the RAID is done we'll still be swapping out the bad drive.
  25. Everything is online and the RAID is rebuilding. Once its completed and the RAID in is an optimal state we'll be swapping out the faulty drive. There may be some slowness in regards to IO during the rebuild.