Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Creating a site with 'dev' inside it's domain name fails, o1.ftp can't open it, get's forbidden syntax.
Here is the log of the creation.
http://pastebin.com/YafEMiEb
Creating a symlink makes the site accessible.
With dev in the name it also get's wrong file permissions and ownership.
Is this a feature? Is it documented?
Greetings, Daniel
Comments
Comment #1
omega8cc CreditAttribution: omega8cc commentedWhat you mean by "Creating a site with 'dev' inside it's domain name fails"? Attached task log shows properly provisioned site, without any errors. Using "dev" without the dot has no impact on anything, and your permissions issues are not related here - please provide more details on this.
The path access problem is separate. I guess it is because we have "eval" blacklisted in the limited shell configuration.
Also, please follow bug/support submission guidelines.
Comment #2
danielbeeke CreditAttribution: danielbeeke commentedNormally when we create a site the files get owned by the user o1.ftp, when using 'eval' inside the domain name the files get owned by o1 instead of o1.ftp also the group is wrong.
First I thought it was because of dev inside the domain name but it looks it is because of eval.
So the log shows a site that is working fine, but not with the user o1.ftp. That is the bug.
cat octopus_log.txt
cat /var/aegir/config/includes/barracuda_log.txt
cat .o1.octopus.cnf
Comment #3
omega8cc CreditAttribution: omega8cc commentedIt is correct and expected behaviour because Aegir system user is separate, yet, it manages correct permissions and if you will mess them up, the running daily script fixes them and to make it easier, changes also ownership to your SSH/FTPS user, where applicable, but it doesn't mean that Aegir itself is doing anything wrong with permissions/ownership. The "eval" thing is completely unrelated to permissions/ownership.
I'm going to close this issue, because I can't reproduce the permissions problem, while the original problem has been fixed in HEAD: http://drupalcode.org/project/octopus.git/commit/bcec1f1
Feel free to open separate issue if you can provide a list of steps to reproduce the permissions related problem you are experiencing.
Thanks for the report!
Comment #4
omega8cc CreditAttribution: omega8cc commentedFixed the subject.
Comment #5
danielbeeke CreditAttribution: danielbeeke commentedOkay, thanks, will try to recreate in head and reopen the ticket if so.
Thanks!