Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,332
  • Joined

  • Last visited

  • Days Won

    639

Everything posted by wolstech

  1. Did you target the program for .NET 3.5 when you built it? That tends to be the common cause of ASP.NET apps not working... Also, in my opinion, PHP and HTML/CSS/JS would be a better choice than an ASP.NET application if you're just developing it now and are planning to keep it hosted here, especially since you're trying to host on linux servers. Mono and ASP.NET can be picky sometimes...
  2. Seeing you have a VPS...can you reconfigure the game server itself to use 3 ports we already have open so your control panel won't have trouble talking to it?
  3. This support request is being escalated to our root admin.
  4. What exactly do you need them for? Also, is it possible to reconfigure whatever you're connecting to so it uses ports we already have open? An admin will decide based upon the reason for the request. Also, it is worth noting that getting one port opened for you is rather uncommon. The probability of getting all 3 of them opened is likely 0.
  5. Everybody is getting that, among other errors. I get it when I try dropping or creating tables. The errors I know of that are related to the crash are: #2002: Cannot connect to server (server just went down) #2013: Lost connection during query (usually happens when you CREATE TABLE or DROP TABLE, but also during other queries) #1030: Got -1 from storage engine (happens with any INSERT/UPDATE/DELETE to an InnoDB table, and probably on ALTER as well) There hasn't been any update on the progress of repairs as far as I know. When there are updates they'll likely be posted in one of these two topics: http://www.helionet.org/index/topic/18447-mysql-issues/ http://www.helionet.org/index/topic/18427-stevie-mysql-issues/
  6. No backup allowed. Also, I'm not sure why your account is suspended, but this suspension reason usually means it was involved in illegal activity of some form. If you want, I can escalate this and an admin might be able to tell you what happened.
  7. The entire images folder sounds like it was the dumping ground for the malware that the hacker installed. The JS and other stuff is just malware components and a link to what's likely either the malware maker or the group using the malware. My original directions were assuming you didn't have backups since the large majority don't bother to make them as they should. Since you have recent backups, restoring them is a good choice. The downside is that any files you might have added or upgraded (including plugins or upgrades you might have installed to prevent future hacks) will likely need to be redone. The upside is that you can guarantee the hack is gone.
  8. That account cannot be unsuspended.
  9. Are you on Stevie? If so, the issue is likely to do with the ongoing mysql issues on that server, and most you can do is wait. If not, it's possible that the issue is due to load or other reasons.
  10. I dont believe Wordpress is supposed to have an index.php in that folder. The hacker probably added it. As for being a false poitive, i doubt it. When I visited that file in my browser, it redirected me to some Russian hosting service... I have no way of checking if it is totally clean now though since only an Admin can re-run the scanner. If you get suspended again, it's not.
  11. This time it's for malware. The suspension reason explicitly named this file as malware: /public_html/wp-content/images/index.php Delete that file before you do anything else. In addition, I would recommend downloading a backup of your account and running a virus scanner on all of your files. Delete all infected files from your account. Since you are using wordpress, I would also recommend making sure that everything is up to date and that you aren't using any plugins from dubious websites. There are many plugins out there for wordpress that are full of security holes due to lack of support, and sometimes others (especially those from less-reputable websites) are malware disguised as a theme or plugin to make people install it. You have 24 hours from the time of this post to remove any malware from your account. If you don't, it'll be resuspended.
  12. It appears to be working fine now. Thank you for fixing this
  13. Replying to this because the user just reported his own post... We cannot provide database backups because it was suspended for phishing.
  14. You were suspended for running 3 cron jobs. The limit is 2 executions per day. Your account has been unsuspended.
  15. Your account has been unsuspended. Please clean it up quickly.
  16. It is, and as far as I know, there's no estimated time as to when it'll be fixed. The most I know is that the repair work is quite time-consuming, so I'd expect it to take a few days at least. In the mean time, tables using the MyISAM engine work fine assuming the DB server is up (there's been a lot of #2002 "Can't connect" errors too). MyISAM also tolerates abuse from issues like crashes much better than InnoDB. http://www.helionet.org/index/topic/18447-mysql-issues/
  17. Mysql has been broken on Stevie since the server crashed on Monday. Error 2002 (can't connect to database) and error 1036 (got -1 from storage engine) are the two common errors everybody is seeing. All tables using InnoDB are read-only. See http://www.helionet.org/index/topic/18427-stevie-mysql-issues/
  18. Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache.
  19. This is normal. Using cpanel opens several processes on your account. We limit the number of processes per user. With the cPanel processes, you can easily hit the limit with light web traffic. 500s result when apache can't start php processes in your account to run your scripts.
  20. It indeed did. Now all the InnoDB tables are giving that one instead when you try to do any sort of insert/update/delete. I suppose it's an improvement though, since we can read the data now. There's a topic on that error over here: http://www.helionet.org/index/topic/18437-1030-got-error-1-from-storage-engine/
  21. Changes not saving are probably InnoDB issues since all of my systems that use InnoDB are doing the exact same thing at the moment. I can see all my data, but editing any of it is gives -1 from storage engine and won't save the edits. For me, my issue that my systems are seeing 100s of calls/day at least (one of them might see 1000s, I don't track it), and I keep having to delete error_logs that pile up from database errors. Stevie is also having an abnormal amount of 500 errors today. I normally hear from my monitoring service once a week at best (when I log into cpanel)...I've gotten 37 (!) emails today alone.
  22. My applications are doing it too. I can read data, but editing it gives me "Got error -1 from storage engine." The issue seems to specifically affect InnoDB tables, so it's likely related to the InnoDB problem that's been affecting Stevie since Monday. On the bright side, at least we can read the data with this error...
  23. Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache.
  24. Your domain should work with just ns1.heliohost.org. Try adding ns2.heliohost.org again later. If it still won't work after several attempts at different times, see if you can get your registrar to set it for you. NS2 is often impacted by Johnny's load. In the past 24 hours, it was down more than it was up, so odds are it actually was down when you tried.
  25. This issue has indeed returned. It was working for me around 1PM today, but has since broken again.
×
×
  • Create New...