Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,334
  • Joined

  • Last visited

  • Days Won

    639

Everything posted by wolstech

  1. This support request is being escalated to our root admin.
  2. Something is wrong with registrations on Stevie. A few others have posted today about that "Unable to add user XXXXX" error too. Using different usernames doesn't seem to make a difference, as one user tried numerous names unsuccessfully: http://www.helionet.org/index/topic/19512-encountered-an-error-during-installation-unable-to-add-user-xyz/ http://www.helionet.org/index/topic/19509-encountered-an-error-during-installation-unable-to-add-user-suphi/
  3. Hussam gave a very thorough response on the technical aspect of getting site exposure, and summed it up quite nicely. What you're doing is comment spam, and what you're asking is basically the same as asking how to be a successful spammer. The solution: Don't spam. We all hate having to invest time and resources on filters and spam removal. Messages such as what you want to post are not welcomed on nearly all websites.
  4. That is indeed the form you should use. Alternately, you can log in by visiting http://stevie.heliohost.org:2082 or http://johnny.heliohost.org:2082 (choose the appropriate one depending on the server your account is on). There is no way to see your last login date.
  5. Im pretty certain that we generally only use the versions supplied by cpanel since those are what it is tested with. If we do upgrade outside of cP updates, it is usually minor versions only. Mysql 5.6 is only officially supported by a very new release of cP (11.42 from Jan 2014). The versions of cP we use are much older. In addition, 5.6 has been shown to use more memory and CPU, something which Johnny is already short on. Long story short, we may see an update on Stevie if cPanel is upgraded again, so that may get a newer version at some point (which will likely still be very outdated). I would not expect 5.6 anytime soon on Johnny.
  6. We actually just updated this a few weeks back as part of a cpanel upgrade. As for the new tables causing crashes, I don't know the exact causes, however we do have innodb set to read only at the moment.
  7. It takes 5 to 6 months based on current estimates. We only add java to people's accounts when it is removed from other accounts due to suspension or inactivity.
  8. Unfortunately, few if anybody here knows ASP.NET/Mono, so I can't help with this exact issue. What I can say though is that the most common cause of problems with ASP.NET applications though is incorrect target platform. Heliohost only supports .NET 3.5. If you build applications targeted for .NET 4 and newer, they will not work properly.
  9. I see this: http://imgur.com/nNz1K7T Try another browser (or computer). If no change, try a different internet connection. It may be your network or ISP caching the queued page.
  10. If you SELECT from the tables, it works fine. If you UPDATE/INSERT/DELETE data in such a table, it fails with "Got -1 from storage engine" but generally won't crash. Creating/altering/dropping the tables themselves (or databases containing them) seems to frequently cause a crash.
  11. That domain is working fine. Please clear your cache.
  12. wolstech

    Johnny Down ?

    It's because status data for Johnny isn't available. Johnny's load shows as white "no data" on that monitor. The load graphics we use also say "down" at the moment.
  13. As you found in the wiki, it's disabled. If you want stats of some sort, you need to find web statistics software and install that to do it, or use one of the many free website analytical services out there.
  14. Username or password is incorrect. I'd start by making sure the user exists and is assigned to the database in cpanel.
  15. We don't specifically prohibit them. However, if you allow public uploads, you are responsible for what people upload and you only get 500MB of space, so a lot of things won't fit. Also, if any of the files are infected, you might get suspended for malware when the AV scan runs.
  16. I'm not seeing any account with that username. Did you receive a second email saying the creation failed?
  17. Did you create the subdomain? They need to be created in cpanel and take 24 hours to start working once you do. Subdomains for accounts on Johnny may take longer. Also, you used commas between the 1 and channel. Those should be periods, like http://1.channel.heliohost.org
  18. Ns2 is down and hasn't worked in months...Does your registrar requires two working nameservers?
  19. We don't offer that for security reasons. It would affect every one of the 1000+ users on the server. What specific reason makes you think this is necessary?
  20. You're on Johnny. Accounts on Johnny can take up to 5 days to come out of the queue. Just give it some more time. If it still isn't working on Friday, let us know and we'll look into it further.
  21. You were suspended for running 3 cron jobs. The limit is 2 executions per day. Your account has been unsuspended.
  22. Any unsuspension beyond 3 for the same reason is up to us, but we're usually pretty flexible as long as you're actually working on fixing the software issues that cause it. We have the limit because some users will just ask to be unsuspended over and over without fixing the problems. High load affects every account on your server (in this case Stevie), so letting people continuously do it over and over would just lead to performance issues and downtime. If you get suspended again before the admin posts the file causing this, we can unsuspend you again once the information is posted. It's not a hassle to unsuspend an account (it takes 30 seconds or so). As for recovering the content of an account that's suspended permanently, our official policy is that we don't make/keep/provide backups, so what you're doing is the best course of action...make plenty of backups on your own.
  23. We don't monitor bandwidth. You were suspended for excess resource usage (RAM and/or CPU) last time. Your suspension this time is for the same thing. Your account has been unsuspended. Do be aware that a third suspension for this reason will be permanent. This support request is being escalated to our root admin. He may be able to provide you with the name of the file that caused the load.
×
×
  • Create New...