Jump to content

Ashoat

Chief Financial Officer
  • Posts

    6,455
  • Joined

  • Last visited

  • Days Won

    37

Everything posted by Ashoat

  1. Is it working now?
  2. Should be better now.
  3. You should be getting much less coredumps now. Let me know if a problem persists.
  4. Signups have now been reenabled.
  5. Ashoat

    PhpPgAdmin

    Should be working now.
  6. Your forum doesn't seem to be getting any connection errors to me. Can you specify a URL that shows the error?
  7. Signups have been reennabled.
  8. Try signing up again with the correct domain. Let me know how it goes.
  9. Ashoat

    PHP Question.

    The Zend Framework does not require PDO or PDO_SQLITE. I went ahead and installed them anyways, though.
  10. We cap PHP scripts at 128mb of RAM. Using more than that is a little absurd for a PHP script.
  11. I'm not exactly aware about how the Army System works and how much resources it takes. You can try hosting it and if you take too much resources I'll suspend your site (and unsuspend it once you contact me). My guess is that it's probably fine.
  12. Ashoat

    co.cc domain

    This issue should be fixed now.
  13. Ashoat

    Name servers

    Should be fixed now.
  14. Hey Victor and Ric: do you guys still need dedicated IPs? Let me know and I'll set you guys up.
  15. @co.cc problem: It was our bad. This problem is now fixed. Sorry... ASP.NET was taking a lot of resources. We currently have it disabled, but might reenable it in the near future. Is this still occurring? I believe it should be fixed now. This shouldn't be affecting you guys, but I am aware of the problem. Sendmail is functional for me. Are you sure this isn't your bad? Fixed. Should be better now. Is this still occurring? I've considered this, but with all the accounts on Stevie this might take a really long while. I usually get emails from lawyers and the such when a phishing site is identified, and I try to take it down ASAP. I'm going to wait a month to see if Stevie remains stable with the signups re-enabled and then resubmit. I very much doubt that you are the sole cause of that jump in server load, but yes cPanel is a problem. Unfortunately at this point it is absolutely necessary for HelioHost - neither LayeredPanel nor DirectAdmin offer many of the features that we require. @laozing: Do you really need more bandwidth and space, though?
  16. Ashoat

    PhpPgAdmin

    I'll take a look and get back to you.
  17. Ashoat

    I'm back

    Kyougi's right about putting ad on users' accounts. It never made us much money, and nobody will choose an ad-based plan. Not going to do that. I looked into this for about an hour yesterday. It actually seems like a viable solution, except for some security configuration options that might cause some difficulty. I'll look into it some more, and get back to everyone with details.
  18. Hey everyone, Since I've been gone so long, I've probably missed some major problems we've been having. I'm not exactly sure as to what they are, so I'm posting this thread so that everyone can post MAJOR concerns. To be considered major, there have to be at least two people with the same problem. I'll address these issues as quickly as possible. Thanks, djbob
  19. Ashoat

    I'm back

    Hey everyone, Sorry about disappearing for like four months. Heh. I suppose I'm back now. This should sufficiently explain my absence. Right, onto more relevant news. HelioHost has been running into some major financial issues as of late. Why? A few months ago, the number of accounts on Stevie hit a critical mass. With more than 17,000 accounts, he was hosting more accounts than even the heaviest loaded cPanel test servers. The issue with this was that Apache now had to process an absolutely huge configuration file every restart. It took almost a minute to start up. cPanel needs to restart Apache for every new account it creates, which meant that HelioHost had about a minute-long downtime every ten minutes. This was not acceptable.I decided to close signups for the immediate future to at least keep the current accounts stable. However, this caused yet more problems, this time of a financial nature. With signups closed, HelioHost was taken off all the major free hosting directories, which comprised about 90% of our traffic. Since HelioHost is financed exclusively off of ad revenue generated by our home page, we are now making about 10% of what we used to make. That is not enough to sustain this service. Options at this point: Try to prune enough existing accounts to reopen signups. Possibilities to achieve this goal: Reinstate account auto-deletion script (was taken off due to some problems with the script).Shorten inactivity period required for deletion from three months to one month.Force all existing account holders to request that their account be preserved. Kill all accounts that are not requested to be kept within a month.Try to convert Stevie into eight or more virtual servers. With eight servers, each would host 1/8 the accounts that Stevie does (meaning each would restart eight times faster), and would receive 1/8 the new signups (meaning each would have to restart eight times less often). This would mean a 0.16% downtime for most accounts, instead of the current 10% downtime as a result of opening new signups. Problems with this idea: Converting Stevie into a virtual server host would be dangerous and difficult. If I screw something up, accounts could be lost.I would have to ship Stevie over to my house again, which would take about $50 for both ways and would cause about a week-long downtime. The biggest problem is that eight cPanel VPS licenses would cost about three times as much as the current single standard license. We don't have the funds for this, as a result.Try to secure financial support of a non-profit nature. Possibilities to achieve this goal: Try to get somebody to donate a new server. A new server would be able to handle new signups, and as such we could reopen signups. However, a new server would require more cPanel licensing fees and probably more colocation fees. We could also apply point #2 to the new server, but this would require even more licensing fees. Ideal places to ask for free servers: datacenters, hosting companies.Try to get somebody to give us free colocation. Colocation is now taking more money than any other single cost for HelioHost. The best option would be to have colocation in the Seattle area, because this would mean I would be able to service the server more directly. Ideal places to ask for free colocation: datacenters, organizations with datacenters.Try to get somebody to donate cPanel licenses. cPanel licenses are a major cost to HelioHost, especially if want to try point #2. I have asked cPanel for free licenses, but they are not willing to provide us with them because we may be hosting commercial sites. Ideal places to ask for free cPanel licenses: cPanel executives, cPanel license resellers.Try to secure financial support of a for-profit nature. Possibilities to achieve this goal: Place more intrusive ads on the HelioHost home page.Place more intrusive ads on users' cPanel pages.Ask users to complete surveys when signing up, the profit from which would go to HelioHost.Ask users to join a mailing list when signing up, which would solicit them with offers and advertising. The profits would go to HelioHost. What are your guys' opinions? Which options make the most sense? Which are the most viable? Let me know what you think. Thanks, djbob
  20. Try again now.
  21. Please go here and enter your password in the text area. Get the md5 hash, and PM it to me with the subject "Delete HelioHost account: njunkie".
  22. I'll need your HelioHost username and domain name to take a look.
  23. I've changed some DNS settings around, but they'll take time to propagate. Let me know if the issues persist after 24 hours.
  24. You need to change your nameservers to HelioHost, and then once that is done you can change your MX records in cPanel to Google Apps.
×
×
  • Create New...