Aegir 0.4. alpha 6 fails after importing itself

gupi's picture

Hello to you all,

seems I am stucked in a loop-error and I cannot figure where's the catch.

I have successfully installed Aegir 0.4 alpha6 on a centos test server.
Immediatly after importing itself into the system, the site is not working, except the front-page.
Apparently, the errors are related to clean-urls.
For instance, I can access the page if manually build the URL as based on index.php?q=node/68, but cannot access it as /node/68

Any help is highly apreciated.

Stefaniu -gupi- Criste

Login or register to post comments

What version of Apache is

mig5's picture
mig5 - Sun, 2010-02-28 07:28

What version of Apache is your server running?


2.2.14

gupi's picture
gupi - Sun, 2010-02-28 08:47

httpd -v
Server version: Apache/2.2.14 (Unix)
Server built: Oct 14 2009 13:19:18

All extra modules were installed from Utter Ramblings repository.

The error is strange, as it appears only after successfuly verifying the self-imported site.


Issue solution identified - not sure how to patch - help on this

jaybhancock - Thu, 2010-03-11 08:16

I'm just had the same issue. Aegir seems to be tailored to maintain systems besides the hostmaster system. After I completed the Aegir wizard, the hostmaster system was listed as a Platform - something we don't want because we will not be provisioning them. Or if we do, then there's an adjustment to make in the vhost file (see below).

When Aegir imports the site, it:
* rewrites the settings.php file
* connects to the database and runs "drush_bootstrap_drupal_full"
* generats a virtual host file for the server (which overwrote the one I had created by hand and had working)

I did an experiment and:
* created my original virtual host file (I copied the /var/aegir/hostmaster-0.4-alpha6/profiles/hostmaster/apache2.conf.txt file into /var/aegir/conf/vhost.d - and then edited the settings to match my site)
* created my original settings.php file (I copied the traditional default.settings.php file and edited the database string as $db_url = 'mysql://aegir:secret@localhost/aegir'; -- that's it.)

The site works again. So the old files work, and the new ones don't. What's the difference?

If I reinstate the new files (the ones you are left with after import) and then I add the following from the old vhost file to the new vhost file (in /var/aegir/conf/vhost.d/websitename.com_80):

<Directory /var/aegir/hostmaster-0.4-alpha6>
    Options Indexes FollowSymLinks MultiViews
    AllowOverride All
    Order allow,deny
    allow from all
</Directory>

... then everything works. These settings were from the original file (apache2.conf.txt) above.

So that's the difference. Somehow these settings aren't being applied to the hostmaster directory. I'm not sure the best place to put them to prevent this issue in the future or if they are required for EVERY site that we create or just this one.

Help on this?

==

BTW, this is my first contribution ever to Drupal.org - I'm new, so let me know how I can be more helpful (more or less verbosity) - I'm deep into this Aegir project now, so thanks for the work to this point and I'll be helping out where I can.


thanks

gupi's picture
gupi - Thu, 2010-03-11 11:11

Jay, thanks a lot for the solution, I will try it on week-end.


More General Solution...

jaybhancock - Sat, 2010-03-13 06:36

I just imported a second site, and this same issue came up for me. I inserted the same code (changing the directory to that of the platform my site is installed on) into the generated vhost file, and my site again worked. It's annoying to have to redo this each time.

The general solution was to configure my /etc/httpd/conf.d/aegir.conf file to include a generic listing for the /var/aegir/platforms directory - that's where I put my platforms and live sites I will manage except for hostmaster (for now?).

i.e. I add:

<Directory /var/aegir/platforms>
    Options Indexes FollowSymLinks MultiViews
    AllowOverride All
    Order allow,deny
    allow from all
</Directory>

to the server level file - and everything works. Not sure if my apache default config is deficient with respect to the config of the author(s) of the apache config files - but I'm sure others will have this issue.


Jay : I had to implement this

kvvnn - Thu, 2010-05-13 16:15

Jay : I had to implement this as well. Thanks!

Now, is this using the platform's .htaccess directly???