Fetching the hostslave profile from CVS Head, an install goes well (although the site whitescreens unless you explicitly type /install.php).
After this, I'm asked to execute drush provision setup:
[root@hm2 ~]$ cd /var/www/versions/d6trunk/webroot
[root@hm2 ~]$ sites/default/modules/drush/drush.php provision setup
This directory is naturally different from profiles/hostslave/modules/drush/drush.php. I'm not sure if it matters.
At any rate, running drush provision setup (or drush at all) returns a 'site off line' page in with no error messages or anything else I can find.
Useful output:
[root@sandboxes webroot] development # ls profiles/hostslave/modules/
. .. cvs_deploy drush provision
[root@sandboxes webroot] development # ls modules
. comment fileserver messaging path skype_status update
.. contact filter mimemail pathauto smsframework upload
activitystream contemplate forum moodle php sparql user
aes content_profile forward nice_menus ping statistics user_relationships
aggregator context_menus front node poll .svn views
apachesolr coresearches glossary node_translation privacy syslog views_or
auto_nodetitle cronplus help notifications profile system webform
bitcache css_injector httpauth og rdf tagadelic webmail_plus
block customerror imapwu_api og_mandatory_group README.txt taxonomy xmppclient
blog date ldap_integration og_vocab resource taxonomy_explorer zimbra
blogapi dav ldap_provisioning openid role_delegation throttle
book dblog locale openid_provider scheduler tinymce
calendar devel mail_api opensearch search token
cck exhibit mailhandler opensearch_aggregator simpletest tracker
coder feedapi masquerade password_policy simpletestauto translation
color fileframework menu password_reset simpletest_automator trigger
[root@sandboxes webroot] development # ls sites/default/modules/
. .. cvs_deploy cvs_deploy-6.x-1.0.tar.gz drush drush-6.x-1.1.tar.gz provision
[root@sandboxes webroot] development #
Comments
Comment #1
anarcat commentedHi,
This seems to be the intended behaviour: the hostslave install profiles only configures a few things on the "platform site" and then disables it. The next step is to create the platform node on the hostmaster site and verify it.
Did you follow the instructions given here:
http://groups.drupal.org/node/12059
Comment #2
adrian commentedNo longer relevant