Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,065
  • Joined

  • Last visited

  • Days Won

    618

Everything posted by wolstech

  1. Johnny's file system is damaged, likely beyond repair, so it will never properly work again, at least not as you know him. You need to move to Stevie. Please back up your files over FTP as Krydos mentioned, then list your database names so we can get them backed up and sent to you.
  2. InnoDB went corrupt again. You will need to drop the database, then create a new one and restore your latest backup.
  3. No. FTP is currently the only functioning service on Johnny due to file system damage. Please see http://www.helionet.org/index/topic/25786-johnny-backups/ for information. You can retrieve your files over FTP. If you need databases, please list their names and I'll escalate to have them backed up. Please note that databases and tables using InnoDB cannot be backed up.
  4. You were suspended for sending spam. Krydos or Byron may have more information since I'm unable to find an abuse report your incident.
  5. Johnny hasn't worked in several days now. cPanel is also broken on Johnny.
  6. You can, but MySQL is currently broken on Stevie... If you want to do so anyway, if you have your data backed up, you can just delete your account and sign up again. If you don't have a recent backup, then you can't move since there's no way to make a backup with cPanel broken.
  7. Yeah, you'd need to be willing to sacrifice some of the niceties of InnoDB to use MyISAM. The only reason we recommend it though, is that this will be the 4th InnoDB failure (3 on Stevie, 1 on Johnny) in 3 years, while we've never had a single MyISAM failure in all the years we've been operating. MyISAM by nature of how it works doesn't have nearly as many risks associated with file corruption, and data recovery from the raw .MYI is also much easier if you ever needed to do it. I used to use InnoDB for the same reasons you do, foreign key constraints. It makes it very easy to handle data and easier to develop software for since you can safely assume the foreign key will actually point to a meaningful value or be null (if allowed). You can also do things like CASCADE. If you do convert, you'll need to add code to your program to replicate these benefits on the software side since the database won't do it for you anymore. When he becomes available, you could consider moving to Tommy, since that server will be brand new.
  8. You can't. Krydos has to fix InnoDB...it probably got damaged again from the DB server crashing. We recommend using MyISAM as the storage engine since it's significantly more reliable that InnoDB is. Escalating.
  9. That account is not suspended. However, Johnny is broken at the moment. See http://www.helionet.org/index/topic/25752-johnny-var/ and http://www.helionet.org/index/topic/25748-johnny-usr/
  10. Yes. Johnny is rather broken at the moment. He's up, but thing like php didn't seem to be working. Cpanel is also down. It's related to http://www.helionet.org/index/topic/25752-johnny-var/?view=getnewpost and http://www.helionet.org/index/topic/25748-johnny-usr/ most likely.
  11. We can't reset accounts. You should delete your account, then sign up again.
  12. Seems to have crashed again...
  13. The account can't be reactivated because doing so would cause the malware to reactivate as well. Usually he sends a PM or email with a link where you can download the database. Once you have the database, you can create a new account and restore the database, or you can take the database elsewhere and use it with another service. You will also need to download wordpress from their site and set it up to use the restored database.
  14. We do not have any files that are safe to give you, only the database. The ones we had were damaged/infected by the malware and cannot be used. Krydos will need to get the database for you.
  15. Johnny is down. See http://www.helionet.org/index/topic/25748-johnny-usr/ and http://www.helionet.org/index/topic/25752-johnny-var/
  16. You will not be getting a full backup due to the malware. Krydos offered you the database, the only part that's safe to back up, and as he said above, you've shown no interest his offer.
  17. He's already being helped here: http://www.helionet.org/index/topic/25739-help-me-support-ticket/
  18. Don't bump your posts. Krydos will get to it when he has time. All of us are volunteers that run heliohost in our free time.
  19. Change your password here: http://stevie.heliohost.org:2082/cpsess6801965998/frontend/x3/passwd/index.html Make sure to select "Synchronize MySQL" password before you change it. Then log out and in again. PhpMyAdmin should work after that.
  20. You need to wait for Krydos at this point, if he decides to provide your database.
  21. The records need to be pointed to 216.218.192.170. The 65.19.143.2 address is for outgoing connections only (when our server connects to others, it appears from this address). I just removed and re-added your domain to your account to make it regenerate the DNS for it. You will need to also change your nameservers to NS1.heliohost.org and NS2.heliohost.org as nyten instructed (do not use the rehost.com.ua servers I currently see on your domain). We do not support the use of A records for joining a domain. Your domain's records: http://bybyron.net/php/tools/dns_records.php?domain=raketa.co.ua&rec=ALL A properly configured domain: http://bybyron.net/php/tools/dns_records.php?domain=raxsoft.com&rec=ALL (ignore the SOA record) Make the required changes, then clear your cache, wait 24 hours, and try again. Let us know if it still doesn't work.
  22. You won't get the files because they're infected, and you don't need them anyway. If you get the database, you should to download a fresh copy of the software, install it, restore your database, and point the software to the database. That will get rid of the malware and leave you with a way to use your content.
  23. We don't provide backups for malware suspensions.
×
×
  • Create New...