Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've moved a Moodle install from one machine to an identical machine and now it won't run. It gives no error on the screen, logs no error anywhere I can find, it just returns a completely blank page. The server is running PHP without issues and I've verified this with a simple helloworld-style PHP program that just print phpInfo();

When I say the two servers are identical I really do mean it. They are on identical hardlware bought at the same time and have the identical OS (RHEL5) with the identical packages, patches and upgrades installed.

I'm completely at sea on this one since there isn't even an error message to check for! In desperation I disabled SELinux but that didn't help either.

Has anyone ever seen anything like this, or does anyone have any suggestions I could try?



share|improve this question

My guess is that Moodle has snagged some part of the first machine's host information (hostname or ip address perhaps) into its configuration somewhere.

I've never done a move of an application before, unless it was a dump of its database, install the app on machine two, then import the database.

Might also explore the Moodle docs.

share|improve this answer
I've gone through the Moodle config to check for anything in there - everything that's set is set correctly. – Bart B Sep 8 '09 at 11:44
that was my guess - not sure where to go next - maybe the Moodle docs? – warren Sep 8 '09 at 16:09
up vote 0 down vote accepted

It turns out my packages weren't QUITE as identical as I thought - was missing just one, but it was an important one, pho-mysql! I had PHP, and I had MySQL, but not php-mysql. I'm shocked that Moodle failed without an error of any kind and returned just a blank page with an HTTP response code of 200 OK - surely there's nothing OK about failing to talk to the DB!

Anyhow, should anyone else stumble upon this problem, this was the solution for me.


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.