13 October 2011, 0:17

Hi All,

In an attempt to spare server work our tech team set up our dev, test and pre-prod Mahara instances on the same server, where previously only pre-production was housed and was working successfully.

However, now that the server has been set up with the following folder structure:

• mahara0 - pre-prod instance
• mahara1 - dev instance
• mahara2 - test instance

they seem to be conflicting with each other's configs. Each has their own separate config file in mahara#/mahara, but they all seem to be using the dev config, as I'm recieving the following error for all three (note that itudl-postgres1.ml.unisa.edu.au is the dev database):

They all have separate databases and separate apache configs, however this is happening to all three. I've linked the apache configs in case there's an issue there.

I've contemplated nuking the databases and trying again, but is there anything I've done wrong here?

Cheers,

Scott

http://mahara.org/artefact/file/download.php?file=166784
http://mahara.org/artefact/file/download.php?file=166785
http://mahara.org/artefact/file/download.php?file=166782
http://mahara.org/artefact/file/download.php?file=166783

13 October 2011, 5:42

Hi Scott,

It won't be a database issue so don't go nuking your databases.

I see that you have three separate logs - do each see events, or are all three sites pointing to one of them?

With Apache, I believe it's the final VirtualHost definition that is used if none of the others match. My first instinct would be to check these logs and see whether you're not hitting the VirtualHost definition you expect.

If that's a no-go, I'd have a look at the config.php for each one to check that you're not doing something frutiy like including or requreing one of the other config files somehow.

Andrew