I've installed seotools using a drush make file for Drupal 7.14 and aegir hostmaster-6.x-1.8. The xmlsitemap subdirectory is created in the proper place (/path-to-platform/sites/domain-name/files/xmlsitemap/) and is owned by "aegir.www-data". The xmlsitemap cache directory is created in this subdirectory, but is owned by "aegir.aegir", so consequently the directory isn't writeable by the apache user until I manually change the group owner to www-data.. I'm not sure if this is a bug or a configuration issue on my end or if there's a simple work-around.

#6 Screenshot from 2014-04-23 20:05:32.png36.13 KBm.stenta


berkas1’s picture

same problem here, but I think this is problem of aegir, not the sitemap module....

valkum’s picture

anything new?

redben’s picture

Project: Drupal SEO Tools » Hostmaster (Aegir)
Version: 7.x-1.0-alpha5 » 6.x-1.8

Aegir problem or xmlsitemap's ?

valkum’s picture

not sure. dir is created thorugh file_prepare_directory with these flags: FILE_CREATE_DIRECTORY | FILE_MODIFY_PERMISSIONS

maybe aegir should check permission in files directories every 10 cron runs.

set user to aegir:www-data for files -R
and check permissions.

valkum’s picture

Issue summary: View changes

Fix typos (auto-spell correction aegis -> aegir)

ergonlogic’s picture

Version: 6.x-1.8 » 6.x-2.x-dev
Issue summary: View changes
Status: Active » Postponed (maintainer needs more info)

Please try again with Aegir 2.x, as Aegir 1.x is deprecated. If it remains an issue, please post the results here, and we'll take another look.

m.stenta’s picture

Status: Postponed (maintainer needs more info) » Active
36.13 KB

I am experiencing this issue with Aegir 2.x, using a custom installation profile that includes and depends on XML Sitemap. Attached is a screenshot of my Status report page after a new site is installed via Aegir.

The file mentioned in my Status report page appears to have the wrong group - "aegir" instead of "www-data", which means Apache is unable to modify it.

Here is what an "ls -al" gives me in the directory. Notice that the group of the file is "aegir", not "www-data".

drwxrwxr-x  2 aegir aegir    4096 Apr  8 16:40 NXhscRe0440PFpI5dSznEVgmauL25KojD7u4e9aZwOM
mengi’s picture

Using Aegir 2.1

The folder (public://xmlsitemap) ownership is www-data:www-data and the cache file directory ownership is aegir:aegir. And then the actually sitemap file is aegir:aegir.

This throws a warning in the status report saying

The following directories were not found or are not writable by the server.

I verified the site through aegir's frontend but it didn't change anything, so I manually changed the above directory to aegir:www-data and that removes the warning in the status report.

dagomar’s picture

I have the same problem. No solution yet? My problem is worse because I don't have chown rights.

helmo’s picture

This is the relevant commit. It introduced the code with which we do not blindly chown recursively.

commit 1da8abb3f592b1f203d4195b9e65eadb63baa8d1
Author: Antoine Beaupré
Date: Fri Dec 10 15:34:35 2010 -0500

do not attempt to chown files/ dir during verification

the rationale here is that we're not running as root, and therefore
chown is likely to fail, unless the file already has the right owner,
in which case a chown is not necessary.

To quote chown(2):

Only a privileged process (Linux: one with the CAP_CHOWN
capability) may change the owner of a file. The owner of a
file may change the group of the file to any group of which
that owner is a member. A privileged process (Linux: with
CAP_CHOWN) may change the group arbitrarily.

So this was just a cause of trouble without any possible benefit
unless we run with capabilities, and we shouldn't assume this (right

Via an implementation of provision_drupal_chgrp_directories_alter() you could probably add the xmlsitemap path.

helmo’s picture

Status: Active » Closed (cannot reproduce)

Marking as closed as due to a lack of activity.
This is a templated response, please re-open or comment if you think it's in error.