Ashoat

As soon as our new server (Charlie) is up and running, we'll have HelioHost and HelioNet on an isolated virtual machine. I got the email. The admin team is considering your offer and we'll get back to you once we've come to a consensus

Okay, so this problem was pretty complicated. Turns out that some system upgrade or something made it so when batch (not bash) scripts run, they don't show up in the process list. So that made one of our cron scripts, that checks if it's running already by checking the process list, basically start spawning off lots of copies. But it only did that when another conditional was met, which explains common recent downtimes. However, it took the server down one morning, and I was forced to hard reset the server. This caused some data corruption. On boot, some mounted partitions would decide to set themselves to read-only, despite not being mounted as such. This would cause unexplainable errors that took a while to debug. Once I figured out the problem, I knew the fix was to run fsck before boot. This had some problems of its own, as apparently the standard fsck command broke, so I had to get the datacenter tech to run a command that wouldn't prompt the user. Looks like everything's working now, though...

Working on it...

Hmm... isn't that a Mongrel error? Have you checked error_log folders around your directories (not the global one in cPanel)?

coody: Please wait until "Server Load" under "Service Status" in your cPanel is below 4, and then try adding the domain again once. You will have to wait 24 hours after adding your domain for it to become active.

stgeorge: Turns out that some witty fellow decided to register "co.uk". I've deleted the account; try adding your domain again.

Sorry, but we can't let you run those crons. That's far too often.

stgeorge: winfoes.co.uk seems to be loading fine from my end. evolving: please wait 24 hours for djyaah.co.cc. As for testthiswebsite.co.cc: please wait until "Server Load" under "Service Status" in your cPanel is below 4, and then try adding the domain again once. You will have to wait 24 hours after adding your domain for it to become active.

Glad everything worked out; I'm closing this thread now

Your addon domain isn't misconfigured by our system, or else it would be giving you an "Account Queued" page. My guess is that you haven't configured your nameservers correctly, as the directions state. Please open a new thread for these issues.

Closing due to inactivity.

No...

Glad you got it working

Okay, try now.

Okay, I guess... In the future, don't run SSH servers?

You were running a ssh server off a jailshell that you were never given. PS: how did you manage to do that, anyways?

song_zl: Please wait until "Server Load" under "Service Status" in your cPanel is below 4, and then try adding the domain again once. You will have to wait 24 hours after adding your domain for it to become active.

There was a .htaccess in the public_html directory redirecting all traffic to cgi-sys/suspended_page.cgi. Removed, and everything is fine now.

Okay, so after a manual search through the php.ini extension directives I'm pretty sure I've identified the problem: pdo_sqlite. Either it doesn't play nice with ODBC, or it sucks on its own. Either way, the installation should hopefully work fine now. Thanks for looking through the source code and helping figure out the problem, rvt!

Your domain's nameservers aren't pointed to us. Are you using A records instead of NS ones?

Try again now?

We will never implement their web server. However, I imagine there's a way to get it working on Apache? I suggest looking into it.

Okay, so here's what we know: something in php.ini is causing phpinfo() to break before it finishes. Am I correct?

Closing this thread now.

That was actually a security vulnerability; thanks for catching it. php.ini overrides are now disabled (again). So, there is something wrong with our php.ini. Does Wordpress mention that it requires any specific functions, or how much memory it usually takes?