Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,057
  • Joined

  • Last visited

  • Days Won

    618

Everything posted by wolstech

  1. You can't transfer it the way your thinking. Normally, you delete the Stevie account then just use the invite to sign up again. Then use the contents of the backup to rebuild your site. Your username/domains can be reused once the Stevie account is gone. It's also worth noting that the invite won't work if the email address your invitation was sent to has an existing Stevie account (hence why the Stevie account needs deleting). If you want your Stevie account deleted, post your username and any domains you need removed, and I'll escalate.
  2. The tommy invite issue is because you donated from an email that was already used here. Normally, the fix is to delete your Stevie account then try again. Of course, with Stevie down, you can't do that. Escalating.
  3. wolstech

    Stevie Backups

    If FTP is all that's running, Krydos would need to export them like he did for Johnny (he dumped them and left the dumps in your home folder). I doubt he plans to do that though since we're trying to troubleshoot a load-crash issue...last thing we want to do is cause load. Your only choices in that scenario would be to abandon your database and rebuild it elsewhere, or wait until he's fixed enough to get access and make the backup. Leaving cP running would be nice, not sure how that'd go over with the testing we're trying to conduct though. If it's causing the crash...it'd defeat our attempts at repair if left running.
  4. That won't work either. You cannot reset a password on a server that's not working. Nothing to do with your hosting account will work while the server is down.
  5. It came up, then crashed again.
  6. It's a little hard to do much of anything at the moment. Moving would be a manual process (backup, delete account, sign up on new server, restore site from backup), but since your existing Johnny account was deleted by the rebuild process anyway, you'll just sign up again when he reopens. Supposedly the data was backed up, but it's yet to be seen if/how any of that will be restored. The rebuild is still under way (he's working at this point, but there's still stuff Krydos needs to do before it could handle the load from the public). Steve is down due to repeated crashing (being worked on). Tommy is invite only.
  7. There's a donate button on our website here: http://www.heliohost.org/?_=new
  8. If you're trying to sign into any account on Stevie or Johnny right now, it won't work. You can't log into Stevie because he's down, and Johnny got rebuilt and no longer has any accounts on it.
  9. We do not. It comes up, but has been crashing again shortly after. Tommy is invite-only. You can donate to get an invite for that server, but be aware that the invite doesn't come instantly. Krydos manually sends them. For those who are interested in what Tommy is like...as someone who is currently on Tommy, I ask myself why I stayed on Stevie for so long Sure I had some minor code changes due to PHP 5.4 being the oldest I can get, but that was time well-spent in my opinion.
  10. Stevie crashed. It's being looked into already. Please see the news forum for more information. There are also posts in some of the related topics over in customer service you might find of interest if you want some more details on the progress of fixing Stevie. EDIT: Beaten again
  11. Yeah, that server isn't even up. We're working on it. It looks like it was rebooted again sometime around 10PM EST last night (you can tell because cP finally went red, in it's post-crash state cP stayed alive returning 500 errors), and will probably come up sometime later this morning (fsck usually takes ~12 hours on Stevie IIRC). Some info from last night: Ashoat seems to think the issue is extreme load of some form. Ashoat reported seeing a load average of 222 (!!!) during a crash, which he says is probably caused by excessive disk tasking since high CPU use would crash Linux long before it got that high. We need to wait for Stevie to come up first though to look into that idea.
  12. I don't control that, though I agree it'd be a good idea. It's up to Krydos.
  13. Probably, but we're more concerned with Stevie being down right now. Also, what is you accounts username?
  14. Krydos would need to delete the domain for you and open your ports on tommy, but technically yes. You also need to rebuild your site... I would wait until Stevie is up, make backups, then decide. Be aware that the tommy invite doesn't come instantly either. It comes when krydos sends them. Donors are just guaranteed to receive one before we randomly pick users.
  15. This time around it's because the whole server is down... Stevie has been rather unstable the past few days, we're looking into the cause. Check out the news forum and the other relevant posts in customer service for more information.
  16. Our website has been bouncing a bit today due to load that I suspect is related to cleanup work that's part of the Johnny rebuild. If it goes down, just try again in a few minutes. If you donated, you'll probably be getting a Tommy invite in your email at some point in the near future (I believe Krydos gets notifications when people donate).
  17. We do not offer alternative ways of donating at this time I'll ask, but I think you may need to just wait for the public release unfortunately.
  18. You're not banned, the server crashed. It's still down: http://heliohost.grd.net.pl/monitor/ It repeatedly comes up, then crashes a few hours later. Been doing that for several days now. EDIT: bdistler beat me to it
  19. Yeah, Cody (or more specifically the SQL server on Cody) is acting a bit odd. I suspect it might be load from cleanup activities related to the Johnny rebuild...Krydos was working on Johnny last night and this morning.
  20. Bdistler pretty much has it. Your access issue is not an account problem but rather the fact you're hosted on a server that crashed. The cause of the repeated crashes is still under investigation. Please see the news forum for more information regarding Stevie.
  21. Your account didnt get deleted, Stevie crashed. Please see the news and customer service posts related to this issue. The server is crashing repeatedly for unknown reasons. The cause is being investigated.
  22. It usually does. These repeated crashes are the first major whole-server crash incident I've seen on Stevie in the 5 years I've been here. Take a look at the server monitor history before thanksgiving week. Other than some load spikes from abuse/ddos, he's been great.
  23. We're just as frustrated as you are. We keep trying new things each time he comes up to identify the cause of the problem. So far, that's turning off cron and turning off the nameserver. Neither are to blame apparently. Follow our news for the next steps we take. In other news, we're making progress on the Johnny rebuild and Tommy in the background. One of the major blocking issues (to do with getting our admin tools to talk to the new cpanel installs) was fixed yesterday. The issue held up tommy progress and we hit it with Johnny as well when we began to rebuild Johnny.
  24. Indeed there are. Someone else reported this too. If it fails, try again. I believe the issue has to do with the new site reaching your hosting server to make the changes...hosting servers seeing high load or being down will keep it from working.
  25. The proper way to set it up is to set an A record to the shared IP of your account. The shared IP can be seen on the left in cPanel (x3 theme), or for paper_lantern click "server information" below the stats on the right to see it.
×
×
  • Create New...