Jump to content

wolstech

Chief Risk Officer
  • Posts

    18,473
  • Joined

  • Last visited

  • Days Won

    715

Everything posted by wolstech

  1. cPanel appears to be working now. I just logged in without an issue.
  2. I'm not seeing any issues and can see your site as well as cPanel normally.
  3. The server is working fine for me, and I see the login page for your forum just fine. There have been some...strange...things happening randomly, but they're transient issues (they go away just as quickly as they come, likely leftover issues from the 3 crashes). It should smooth out as time passes and we put that downtime behind us. Three is a lot for Stevie by the way, especially considering he's been fully stable for over a year before this happened. Also, that last squid error is not ours. We don't use squid here (squid is a caching proxy, often used on corporate networks and some smaller ISPs for performance).
  4. It's not hijacked. We're rebuilding Johnny. What you're seeing is the unbranded cPanel default queued page. Eventually that'll turn into our queued page once we configure it. As part of that process, we backed up the accounts on Johnny, then wiped the server. Since there's no accounts on johnny right now, you cant log in either. I'm not sure whether it'll go back to your content or not when the rebuild is done, but I do know most of the user data was backed up at the beginning of the process.
  5. Johnny isn't actually online. He's being rebuilt, and what you're seeing is a brand new, unconfigured install of cpanel, since we backed up the data and nuked the server yesterday. There are actually no accounts on Johnny right now. Once it's configured, krydos will probably restore all the user backups. Our account system still thinks all the Johnny accounts exist though, since they should be coming back concerned the server is rebuilt, which is why you can't reuse the name. Not sure why support@heliohost.org is bouncing for you. Doesn't matter in terms of actual support, since emailing that address actually just posts your email on the forum, but I'd guess the spam filters are being a little oversensitive. I'll check the log when I get a chance and see if the raw email even made it to us. Tommy isn't released yet, hence why he's always "full". It's currently an invite-only beta. Your best bet for now is to pick a different username and sign up in Stevie. If you had domains associated with your Johnny account you want to reuse, let me know and I'll have a root admin remove them for you.
  6. The server basically froze. Your files should be there when it comes back up. The only thing I'd worry about is InnoDB database tables...those have a history of going corrupt after crashes.
  7. You're not suspended, the server crashed. It's been rebooted and is currently running a disk check.
  8. Thanks for the update Byron. Any idea on what happened to Charlie/Johnny in the meantime? He seems to have also died late last night.
  9. Moved.
  10. We currently do not have an estimate for when this will be restored. It's being actively worked on.
  11. As Byron said, we don't keep backups. You have to make them yourself if you want them. In the same boat myself...I made a backup before an update I did over the holiday last week, then forgot to actually download the thing when it finished... I'm now missing that backup, plus all the work I did Thursday and Friday, and all the new data that got collected by my software on Monday and Tuesday. Oh well...I always preach "make backups!", and didn't follow my own advice.
  12. how to move to tommy You can't unless you were invited since he's invitation only right now (he's not released). I just have an unused account on tommy since I'm an admin here...I finally have reason to put it to use. Wait for Stevie to come back up. Not sure what's going on with the second crash. Byron said krydos is aware of it.
  13. Yeah, cPanel seems to have broken in the crash earlier. The websites themselves are back up, but cP and NS1 are still not working correctly. This support request is being escalated to our root admin.
  14. Websites should be back up. cPanel seem to still be down though (returns a 500 error for no such file or directory in the sessions directory), and NS1 is also still not back yet. EDIT: Looks like he crashed again. If he comes back up enough for me to get into cP, I think I'll grab a backup and consider moving to Tommy.
  15. No, the server is down. See http://www.helionet.org/index/topic/26650-stevie-down/?view=getnewpost
  16. It's already been rebooted as of a half hour ago: http://www.helionet.org/index/topic/26650-stevie-down/?view=getnewpost It takes quite some time for him to come back up though (disk checking and the like have to run).
  17. Got 4 reds on the monitor and a pile of timeout alerts by email...
  18. That domain is already configured as the main domain for that account. Is this the domain you want? It's showing queued, but they do take 24-48 hours to start working, so that's normal if you just changed it. Give it a day or so to finish setting up, then clear your cache. If it still doesn't work after that, let me know and we'll look into it further. EDIT: Byron beat me to it.
  19. What account needs the domain changed?
  20. Please clear your cache.
  21. 3 cron jobs. As you're aware, the limit is 2 per day. Unsuspended.
  22. This support request is being escalated to our root admin.
×
×
  • Create New...