Malmoth

The pg gem fails to build, since apparently PostgreSQL development libraries aren't installed on the server.

Not really. The web site was running on the same config for months.

When I reach my website which resides on both malmoth.heliohost.org and malmoth.co.cc I find the web site to be offline. I see the "HelioHost Account Queued Ahoy! You're seeing this page because HelioHost has not gotten about to installing and configuring your account yet. ..." page when I try via malmoth.co.cc, and I see nothing but a browser specific error page when I try via malmoth.heliohost.org. However my account has been active and my website was functioning properly prior to this issue. I can't log in to the cPanel either. My username/password permutation doesnt work. I figured it has to be some issue with the server in general, and I opted not to report it so far, but it hasn't been back to normal. djbob, can you look into the issue when you have time?

Did you try switching to active mode? Give it a try; it might help.

It is now... Cheers.. By the way djbob, it's nice to see you solving server issues, spending your time in order to keep HelioHost up to a standard. We appreciate your efforts and the service you provide us for free. Thank you, sincerely..

Ubuntu at home. NetBSD and OpenSolaris at work.

Please, for the love of God, follow this thread..

Broken link... Why don't you paste the code here, in a codebox?

Why would you want to mix ASP.Net and PHP? You could do this all in PHP or vice versa. Are you planning to use PHP4Mono? And if so, I doubt HelioHost would be suitable. And as a side note, I think it would be best to build a core application server that handles calculations on a multithreaded pipeline basis. That's, of course, if your game uses some streamlined mechanics as in OGame. But of course that would require some sort of a dedicated server, in which case the technical requirements render any (whether free or not) shared web host unusable. So, you're stuck with the scripting language itself, and this will cause a performance penalty. Maybe the penalty can be avoided partially, by using stored procedures in a PostgreSQL database and storing preemptive results; but it has to be designed carefully. Anyway... I know it seems like a basic task to design and build such a game, and to an extent it is, but it's still a huge load to carry on just two shoulders. Wish you luck..

I have. Then I tried to see if fotomore.com does appear in the list, but it doesn't. And I can try to add it again without getting that "it's already bla bla" warning. But the weird thing is, just as I check my public_html via FTP, now I can see the fotomore.com directory which has been created today. Maybe waiting another 12 or so hours would do me good. Things seem to be somewhat in motion.. I'll give you an update in the morning. (GMT+2 over here...)

Just wait for 24 hours after you create an account. It can take anywhere between a minute and a day for the system to update. Check back tomorrow evening, around 8 or 9 pm. If the new account isn't still active by then, then I guess we have a problem in the sign-up script.

The most recent Ruby gem for PostgreSQL access is pg. However, since the required PostgreSQL headers do not exist on the server, gem can't build the native extension for pg. Is it possible to install PostgreSQL headers? INFO: `gem install -y` is now default and will be removed INFO: use --ignore-dependencies to install only the gems you list Building native extensions. This could take a while... ERROR: Error installing pg: ERROR: Failed to build gem native extension. /usr/bin/ruby extconf.rb install -y pg checking for main() in -lpq... no checking for main() in -llibpq... no checking for main() in -lms/libpq... no *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/usr/bin/ruby --with-pg-dir --without-pg-dir --with-pg-include --without-pg-include=${pg-dir}/include --with-pg-lib --without-pg-lib=${pg-dir}/lib --with-pqlib --without-pqlib --with-libpqlib --without-libpqlib --with-ms/libpqlib --without-ms/libpqlib Could not find PostgreSQL build environment (libraries & headers): Makefile not created Gem files will remain installed in /home/malmoth/ruby/gems/gems/pg-0.8.0 for inspection. Results logged to /home/malmoth/ruby/gems/gems/pg-0.8.0/ext/gem_make.out

Same problem... Error from domain wrapper: Bind reloading on stevie using rndc zone: [malmoth.heliohost.org] And the addon domain doesn't appear in the list. Also, I can try to add it over and over again; it doesn't say it's already active.

phpPgAdmin is back, running normal at the moment... Thank you, djbob..

I humbly revive my post, since I believe this issue to be a somewhat high priority one. I know there are many more issues in the queue to be dealt with. It's just that since PostgreSQL support is the main reason I'm drawn over here, and I think this is the case for quite some more users, the lack of a functioning phpPgAdmin embedded in the cPanel is a major concern in my opinion. djbob, can you take a look at the issue when you have time please?

I would say, let's go for these options. We should definitely clear out inactive accounts to free up some valuable resources, even if we go on with the virtual hosts option. And I don't think anyone would mind some ads on their cPanel pages. Also, although having some intrusive ads on HelioHost home page would make it look bad, I really think it's totally tolerable considering the potential income it offers; and the ads could be implemented in a neat way without sacrificing the page design totally.

It is a server-side problem. It's been this way for quite some long time now. Well, it has been the situation since I've joined HelioHost at least, and I've opened a thread on the issue back then. * I assume the issue will be addressed when djbob comes back from the shadowy realm of Mordor, but noone can estimate when that will happen.

Assuming you mean your main domain name, as in blablabla.heliohost.org, I would suggest you grab a new domain from co.cc or dyndns.org and use it as a parked domain.

Mono is disabled at the moment. It won't be fixed until djbob comes back, so I assume it will take some more time.

Despite my earlier remarks on another thread, I now think this is caused by the DNS on HelioNet side. Just a wild guess, but I think it's mainly because of the HelioNet server being unstable. It's possible that when HelioNet's DNS becomes unresponsive for a period of time (whether it's long or short), the domain propagates throughout the more frequently refreshing domain name servers as down.

If I'm not mistaken, it's mainly due to some Apache and/or Mono dump files, not the amount of unexpected users. djbob was working on the issue before he disappeared. If this is the case, the problem will probably be fixed when he comes back.

It just seems like the old database is not deleted... But I assume you've been through every step and checked the whole process before you post here, over and over again. And I also assume the same error has been plaguing the database creation step since your first try, and that you haven't created the database manually beforehand, at the first try. So, I think this could have something to do with the phpMyAdmin configuration, which pretty much leaves you out of an option till djbob handles the issue. But if I may suggest something: There's also a way off shot, which I doubt to be the case, that MySQL may sometimes have a problem parsing large chunks of SQL statement blocks having comments in them. I suggest you just copy and paste the code instead of uploading and importing it from your computer directly. Then remove the comment lines, and give it a try... This could also prevent any possible CR/LF problems (in case you're working on Windows or Mac OS on your local computer) which I've also experienced in the past. I hope this helps..

Since OpenDNS and TimeWarner works, it's probably an issue with Comcast DNS. There's really nothing to be done over here. Try contacting their support staff. Meanwhile, you could stick with OpenDNS.

I believe djbob was in the process of recompiling Apache without Mono support, just to see if a particular problem at the Apache daemon is caused by Mono. This could be the case, since you're not the only one to notice the lack of a properly functioning CLI environment. So, my suggestion would be a little more patience, since we won't be sure till we hear the exact results from him.