Closed (cannot reproduce)
Project:
Provision
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
16 Sep 2011 at 18:27 UTC
Updated:
25 Oct 2011 at 13:22 UTC
Using a BOA install. Is this the right place to be posting this?
aegir@second:~/platforms/test02$ drush provision-save '@test02.local' --context_type='site' --uri='test02.local' --platform='@platform_test02' --profile='miruku_test02' --db_server='@server_localhost' -d -v
Bootstrap to phase 0. [0.06 sec, 1.38 MB] [bootstrap]
Drush bootstrap phase : _drush_bootstrap_drush() [0.07 sec, 1.52 MB] [bootstrap]
Bootstrap to phase 0. [0.21 sec, 5.73 MB] [bootstrap]
Found command: provision-save (commandfile=provision) [0.21 sec, 5.74 MB] [bootstrap]
Initializing drush commandfile: drush_make [0.21 sec, 5.74 MB] [bootstrap]
Initializing drush commandfile: drush_make_d_o [0.21 sec, 5.74 MB] [bootstrap]
Initializing drush commandfile: provision [0.21 sec, 5.74 MB] [bootstrap]
Load alias @self [0.21 sec, 5.74 MB] [notice]
Load alias @server_localhost [0.22 sec, 5.75 MB] [notice]
Load alias @platform_test02 [0.22 sec, 5.76 MB] [notice]
Load alias @server_master [0.23 sec, 5.77 MB] [notice]
Loading mysql driver for the db service [0.23 sec, 5.79 MB] [notice]
Loading nginx driver for the http service [0.23 sec, 5.79 MB] [notice]
Segmentation faultprevious commands run;
drush make --working-copy /var/aegir/projects/test02/miruku_test02.make /var/aegir/platforms/test02
... [ok]
drush provision-save '@platform_test02' --root='/var/aegir/platforms/test02' --context_type='platform'
drush @hostmaster hosting-import '@platform_test02'
Task verify was added to the queue. Next queue run is 15:47:59+0000, server time is 15:47:58+0000. [status]
drush provision-save '@test02.local' --uri='test02.local' --context_type='site' --platform='@platform_test02' --profile='miruku_test02' --db_server='@server_localhost'Any ideas? Thanks.
Comments
Comment #1
mxmilkiib commentedAch, it was the make file, sorry.
Comment #2
mxmilkiib commentedNope, tried just loading core d7 in the make, got the same.
Comment #3
mxmilkiib commentedtried removing the "--db_server=@server_localhost" as the doc says it defaults to @server_master, got slightly further...;
Comment #4
steven jones commentedIf you turn debugging on by doing:
You might get more information, but it looks like something is trying to use drupal_get_path when the database is not around possibly?
Comment #5
mxmilkiib commentedthat gave me;
syslog is showing;
Sep 21 14:37:33 server kernel: php[23600]: segfault at bf7d7fe0 ip 083ab4fc sp bf7d7fe0 error 6 in php[8048000+628000]hmm..
Comment #6
mxmilkiib commentedphp limit is 256Mb
Comment #7
mxmilkiib commentedlooking at the syntax order in mig5's mailing list post, i tried;
drush --uri='d6coretest.thingsandstuff.org' provision-save '@d6coretest.thingsandstuff.org' --context_type='site' --platform='@platform_d6coretest' --profile='d6coretest'which that went through fine. surely segfaulting from having syntax flags in an altered order is a bit ott? :)
Comment #8
steven jones commentedWhat were the two different orders of options to drush?
Comment #9
mxmilkiib commentedthe order of command syntax on http://community.aegirproject.org/node/41 causes a php segfault for me. the format in #7 doesn't, i.e., using
drush --uri="$PROJECT_DOMAIN" provision-save "@$PROJECT_DOMAIN" --context_type='site' --platform="@platform_$PROJECT_NAME" --profile="$PROJECT_NAME"instead of
# drush provision-save "@$PROJECT_DOMAIN" --uri="$PROJECT_DOMAIN" --context_type='site' --platform="@platform_$PROJECT_NAME" --profile="$PROJECT_NAME"Comment #10
anarcat commentedI have seen PHP segfault when provision-save would reference non-existing aliases, maybe because it tries to load a non-existent class or something. Maybe there is a typo somewhere?
Comment #11
steven jones commentedJust did this both ways around, as per #9 and it was fine in PHP 5.3. Going to test in 5.2 now.
Comment #12
steven jones commentedYeah, so both of those formats work in PHP 5.2 also, so I think there must be a typo somewhere in your code, or some other random error. Unless you give us more information, I'm not sure there's much we can do.
Comment #13
mxmilkiib commenteddang, strange.. apologies for the extra ticket then!