For some reason, /var/aegir/config/foobar isn't created properly here:

Webserver custom pre-configuration ownership of                                                               [message]
/var/hostmaster/config/server_web1aegirdevkoumbitnet/apache/pre.d has been changed to hostmaster. [0.4 sec,
7.93 MB]
Webserver custom pre-configuration permissions of                                                             [message]
/var/hostmaster/config/server_web1aegirdevkoumbitnet/apache/pre.d have been changed to 700. [0.4 sec, 7.93
MB]
Webserver custom pre-configuration path /var/hostmaster/config/server_web1aegirdevkoumbitnet/apache/pre.d is  [message]
writable. [0.4 sec, 7.93 MB]
Executing: rsync -e 'ssh ' -azv --exclude="*.svn*" --stats --progress --omit-dir-times --delete                [notice]
'/var/hostmaster/config/server_web1aegirdevkoumbitnet/apache/pre.d'
'hostmaster@web1.aegirdev.koumbit.net:/var/hostmaster/config/server_web1aegirdevkoumbitnet/apache' [0.4 sec,
7.94 MB]
  sending incremental file list
  rsync: change_dir#3 "/var/hostmaster/config/server_web1aegirdevkoumbitnet" failed: No such file or directory (2)
  rsync error: errors selecting input/output files, dirs (code 3) at main.c(632) [receiver=3.0.3]
  rsync: connection unexpectedly closed (9 bytes received so far) [sender]
  rsync error: error in rsync protocol data stream (code 12) at io.c(635) [sender=3.0.3]
/var/hostmaster/config/server_web1aegirdevkoumbitnet/apache/pre.d could not be synced to remote server      [error]
web1.aegirdev.koumbit.net. Changes might not be available until this has been done. (error: sending
incremental file list
rsync: change_dir#3 "/var/hostmaster/config/server_web1aegirdevkoumbitnet" failed: No such file or
directory (2)

In fact, I don't see where that directory is created at all in the log. To add to the confusion, the apache.conf file transfer actually creates this... as a file!

Template loaded: /var/hostmaster/.drush/provision/http/apache_ssl/server_ssl.tpl.php [1.75 sec, 8 MB]          [notice]
Generated config encryption enabled webserver configuration [1.75 sec, 8.01 MB]                               [message]
Executing: rsync -e 'ssh ' -azv --exclude="*.svn*" --stats --progress --omit-dir-times --delete                [notice]
'/var/hostmaster/config/server_web1aegirdevkoumbitnet/apache.conf'
'hostmaster@web1.aegirdev.koumbit.net:/var/hostmaster/config/server_web1aegirdevkoumbitnet' [1.76 sec, 8.01
MB]
  sending incremental file list
  apache.conf
        1396 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)

fun fun, just before a demo. :)

Comments

Anonymous’s picture

I'm worried about a migression - check that this didn't break remote servers? Doubt it though

http://git.aegirproject.org/?p=provision.git;a=commit;h=1e85929b852d43d0...

Anonymous’s picture

I just set up a remote web server and my server node verification appears to have worked

http://pastie.org/private/ic05njrdlalkex1oaxtda

anarcat’s picture

Priority: Critical » Major
Status: Active » Postponed (maintainer needs more info)

i think you mean "this works for me", try again. :)

i'll see what i can do, we're going to rebuild the test server here next week. in the meantime, i'm downgrading this: we shouldn't block the upgrade based on that if it was tested as working.

anarcat’s picture

Title: remote server verification fails to create server-specific directory » new remote server verification fails to create server-specific directory
Priority: Major » Critical
Status: Postponed (maintainer needs more info) » Active

wait, miguel: do you mean you can verify an *existing* server? this is only with new servers...

adrian’s picture

i've been setting up remote web, db and dns servers and combinations of those, and they all appear to have worked.

Anonymous’s picture

@anarcat: no, I mean I prepared a *new* web server and added the new server node, and the Verify task worked fine. I was able to provision a site on this remote web server too.

anarcat’s picture

Status: Active » Postponed (maintainer needs more info)

I guess I'll just need to test that again... we shouldn't block a release on this.

Anonymous’s picture

For what it's worth, I've been setting up new remote web/db servers lately without any issue still. All working well (so long as your remote 'web group' (i.e www-data) is the same as the master server's.

anarcat’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

I will not try to reproduce this soon enough - don't want to block the release for this.