Still investigating why that happens. I'm experiencing this on the server with more than one IP available. Otherwise, it is the same Debian configuration we are using already on hundreds of servers (VPS) without such issues, and I never seen anything like that.

Example of test.o1.domain.com.alias.drushrc.php it created for site (the same happened for a few platforms):

<?php
$aliases['test.o1.domain.com'] = array (
  'context_type' => 'server',
  'server' => '@server_master',
  'remote_host' => 'localhost',
  'aegir_root' => '/data/disk/o1',
  'script_user' => 'o1',
  'ip_addresses' =>
  array (
  ),
  'backup_path' => '/data/disk/o1/backups',
  'config_path' => '/data/disk/o1/config/test.o1.domain.com',
  'include_path' => '/data/disk/o1/config/includes',
  'master_url' => NULL,
  'admin_email' => 'admin@localhost',
);

Comments

adrian’s picture

adrian commented

this happens when the --context_type=X is not passed during provision-save

it uses that to bootstrap the object which determines the properties that are loaded.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Postponed (maintainer needs more info)

This sounds like a 'by design' thing, then, but I want to know what task was being run that generated that drushrc.

Omega8cc, when that alias was generated, was this on a command executed from CLI (in which case #1 might explain why this occurred), or did this happen on a stock-standard Install or Verify or similar, issued from the frontend?

omega8cc’s picture

omega8cc commented

This happened (many times!) while using stock Aegir install, just clicking in the front-end, not cli/command line used at all, so no mistakes possible. The symptoms was: every create site task failed (on vanilla d6 platform) with error about missing/wrong domain used, every platform verify failed with errors (but generating server-like alias files).

That all mess started with attempt to install the site with "drupal" in the domain name. Then everything just stopped to work, Aegir started to create wrong alias drushrc files (platforms and sites) etc.

Then we just created a new/vanilla Aegir instance, (without any "drupal" name in any site), and still some working elsewhere platforms failed to verify with server-like configs, and only deleting the platform node and re-creating them helped. Very very odd. We are still working on debugging it on that server. BTW: it is a Xen based VPS with a few IPs at liquidweb.com with Debian Lenny.

adrian’s picture

adrian commented

i jsut created a site called 'drupal' fine.

it created a new alias called '@drupal', and set up the permissions correctly.

we need more info to be able to reproduce, i suspect the 'drupal' trigger was a red herring.

adrian’s picture

adrian commented

oh. was it not perhaps a side effect of #949044: It is possible to create broken site or duplicate sites nodes because there is not enough strtolower(trim(domain)) used

if you created a second site with the same url, it would not be able to get the right site alias, and may end up being called completely incorrectly.

anarcat’s picture

anarcat commented
Status: Postponed (maintainer needs more info) » Closed (fixed)