I'm running 6.x.-0.3-rc2 installed using install.sh on an Ubuntu 9.04/Apache2/PHP5/MYSQL5 stack.

I untarred an existing site into /var/aegir/platforms/example.
I ran 'chown -R aegir:aegir example' to ensure all files had correct ownership.

I imported the platform into aegir and the site. It verified okay.

Later I wanted to re-verify the site. This time it failed with the following errors

Could not change permissions sites/example.com to 493 (chmod to 755 failed on sites/example.com)
Could not change permissions sites/example.com/files to 1528 (chmod to 2770 failed on sites/example.com/files)

On checking i found that the ownership of these directories, and the settings.php file had been changed to be aegir:www-data.

My aegir user is a member of the www-data group. the site itself loads fine in a browser whether the group is set as aegir or www-data.

Running the following as root solves the problem of verifying in aegir
chown -R aegir:aegir sites/example.com

The site then verifies again. But resets the ownership to aegir:www-data - so it doesn't verify after that.

This doesn't seem to be a problem all the time. it happened on one other site i imported, but not others.

Comments

steveparks’s picture

Actually it doesn't seem to be necessarily to do with the group ownership of the files/dirs. I just had the issue again when verifying a site that had the ownership set to aegir:aegir on the directory it failed to chmod.

anarcat’s picture

Project: Hosting » Provision
Status: Active » Postponed (maintainer needs more info)

I've seen this before. Could you try the latest CVS of provision or apply the patch in #529382: proper recursive functions for chmod/chgrp/chown?

steveparks’s picture

Ok, I've applied that patch so I can test that change in isolation of any other potential change. I'll try lots of site verifications over the next couple of days and report back if the problem has gone, or if it re-occurs.
thanks!

steveparks’s picture

This patch seems to have fixed the problem. Thanks

anarcat’s picture

Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.