got

The command could not be executed successfully (returned: sh: line 1: 3735 Segmentation fault /data/disk/o1/tools/drush/drush.php --client_email='myemai@gmail.com' @mysitename.com provision-install-backend --backend 2>&1 , code: 139)

when adding new site

It is similar to http://drupal.org/node/1366084

debian squeeze 64bit, php 5.3.13, nginx, Aegir BOA 2.0.3 stable
platform verify was ok.

CommentFileSizeAuthor
#22 commons-7.x-3.x-dev-failed-aegir.txt26.7 KBomega8cc
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

SocialNicheGuru’s picture

i get the same error but on ubuntu 10.04, php 5.3.13

ezra-g’s picture

Status: Active » Postponed (maintainer needs more info)

Is there any evidence around why this happens with Aegir and whether the problem is in fact specific to Commons and not a duplicate of #1366084: PHP segmentation fault on install with Aegir?

PlayfulWolf’s picture

I tryed to reproduce the same error with very latest dev, october 12th and got another error when creating a site. The error mentioned in this ticket is gone and have no clue if it is related to issue you mentioned or the one I paste below

Drush was not able to start (bootstrap) the Drupal database. Hint: This error often occurs when Drush is trying to bootstrap a site that has not been installed or does not have a configured database. Drush was attempting to connect to : Drupal version : 7.15 Site URI : dev.2.mysite.com Default theme : garland Administration theme: garland PHP configuration : /opt/local/lib/php.ini Drush version : 4.6-dev Drush configuration: /data/disk/o1/static/platforms/commons/sites/dev.2.mysite.com/drushrc.php /data/disk/o1/static/platforms/commons/drushrc.php Drush alias files : /data/disk/o1/.drush/dev.2.mysite.com.alias.drushrc.php /data/disk/o1/.drush/server_master.alias.drushrc.php /data/disk/o1/.drush/platform_Commons.alias.drushrc.php /data/disk/o1/.drush/hostmaster.alias.drushrc.php 

(more info listing all the sites in aegir server)

Array You can select another site with a working database setup by specifying the URI to use with the --uri parameter on the command line or $options['uri'] in your drushrc.php file. 
Topcheese’s picture

I'm now having trouble installing the latest dev version. I can't give you a straight answer yet, because I also made changes to my dev setup, so I have to make sure that's not the problem. Here were the problems.
The database timed out on install, but a refresh continued it to the configuration screen. After entering config info I get the following error.
Fatal error: Call to undefined function field_attach_load() in C:\xampp\htdocs\includes\entity.inc on line 320

What I've not done is made sure that all of the commons modules from Git are present before install as I did before and it would install fine. I'm still looking into it.

SocialNicheGuru’s picture

did you do it via aegir?

openpublic has/had a similar issue

Topcheese’s picture

Long story short, no. I had just read that they weren't sure if it was related to another problem, and I just ran into some install problems which I'll post a new issue for. I forgot to reboot after configuring was one problem.

PlayfulWolf’s picture

my issue? yes, with Aegir, BOA 2.0.3

mxmilkiib’s picture

I couldn't get a Commons site setup up on BOA 2.0.3 the other day. I could create a platform, but not a site. There was no error for me - the task just hung.

Trying again just now. Given the platform is there, I started using the command-line to create a site on it.

drush provision-save @commons.mydomain.org --uri=commons.mydomain.org --context_type='site' --platform=@platform_Commons --profile=commons --verbose

went through ok and created the drush context file

drush @commons.mydomain.org provision-install --verbose

gave me;

Initialized Drupal site commons.thingsandstuff.org at sites/commons.mydomain.org [notice]
The external command could not be executed due to an application error. [error]
...
Drush command terminated abnormally due to an unrecoverable error. [error]
Error: syntax error, unexpected T_FUNCTION in
/var/aegir/platforms/commons/profiles/commons/modules/contrib/aloha/filter_true_wysiwyg/filter_true_wysiwyg.module, line 231
Drush was not able to start (bootstrap) the Drupal database.

A quick googling says this is a 'you're not using php 5.3 issue'. No idea if this is the cause or what other folk are having trouble on. Barracuda should be using 5.3...

Edit: Directly using /usr/local/bin/php /var/aegir/drush/drush.php @commons.mydomain.org provision-install --verbose gives;

...
Running: /var/aegir/drush/drush.php @commons.mydomain.org provision-install-backend --backend 2>&1 [0.68 sec, 8.36 MB] [command]
The command could not be executed successfully (returned: Killed, code: 137) [78.81 sec, 8.36 MB]
...

So not a seg fault for me, rather something just kill -9'd it...??

mxmilkiib’s picture

Scratch that, repeated once more this morn and got a seg fault error 139.

omega8cc’s picture

BOA allows you to use separate PHP version for CLI (command line) and FPM (browser), so if any distro (or its module) requires PHP 5.3, you should edit your /root/.o1.octopus.cnf config file and make sure it has _PHP_CLI_VERSION=5.3 and then upgrade this octopus instance to force use correct php-cli binary for Drush tasks - /opt/local/bin/php instead of /usr/local/bin/php.

Remember that while BOA will always force PHP 5.3 for all D7 based distros/sites for browser access, the php-cli used by Drush/Provision backend defaults to 5.2 for all older installs (since it still supported D5 and D6 distros not fully compatible with PHP 5.3). BOA uses PHP 5.3 for backend only for new installs, since it no longer installs PHP 5.2 and 5.3 by default, only 5.3.

omega8cc’s picture

The issue here is different than that with Open Public, because Open Public install via drush fails with segfault also when using PHP 5.3 for cli, while here, when using PHP 5.3 for cli/drush, the install fails with different error:

DRUPAL_INSTALL_FAILED
Exception Object ( [message:protected] => Required modules: Required modules not found. The following modules are required but were not found. Move them into the appropriate modules subdirectory, such as sites/all/modules. Missing modules: Commons_wikis [string:Exception:private] => [code:protected] => 0 
omega8cc’s picture

Status: Postponed (maintainer needs more info) » Active

Wow, just discovered what could be wrong - the distro is broken:

o2@linode:~/platforms/commons-7.x-3.x-dev/profiles/commons/modules/contrib/commons_wikis$ ls -la
total 28
drwxr-xr-x  2 o2 users 4096 Oct 12 20:11 .
drwxr-xr-x 60 o2 users 4096 Oct 12 20:11 ..
-rw-r--r--  1 o2 users  995 Oct 12 20:11 commons_wysiwyg.features.filter.inc
-rw-r--r--  1 o2 users  289 Oct 12 20:11 commons_wysiwyg.features.inc
-rw-r--r--  1 o2 users  514 Oct 12 20:11 commons_wysiwyg.info
-rw-r--r--  1 o2 users  110 Oct 12 20:11 commons_wysiwyg.module
-rw-r--r--  1 o2 users  482 Oct 12 20:11 commons_wysiwyg.strongarm.inc

As you can use, the commons_wikis directory includes duplicate code from commons_wysiwyg instead of its own code.

omega8cc’s picture

OK, after replacing the wrong module with correct one from http://drupal.org/project/commons_wikis, it now fails with not really helpful error:

The external command could not be executed due to an application error.
Drush was not able to start (bootstrap) the Drupal database. Hint: This error often occurs when Drush is trying to bootstrap a site that has not been installed or does not have a configured database. Drush was attempting to connect to : Drupal version : 7.15

So it is the same as in #3 above.

Note: all tests with Drush 4.6 - not sure if that could make a difference.

PlayfulWolf’s picture

can confirm #3 bug with the latest dev, october 15th
still critical

ezra-g’s picture

Category: bug » support
Status: Active » Postponed (maintainer needs more info)

Marking as "needs more info" pending information that clarifies how this is different from the issue installing distros on Aegir that also affects OpenPublic.

#1366084: PHP segmentation fault on install with Aegir.

PlayfulWolf’s picture

ezra, this now seems different case as fragmentation error is gone with the latest dev, right?

omega8cc’s picture

Category: support » bug
Status: Postponed (maintainer needs more info) » Active

This is different, as explained in comments above: #11 and #13 - in short, while all recent Open Public installs fail with the same *segfault* error, here is just mysterious Drush error - but it is not segfault.

ezra-g’s picture

Status: Active » Postponed (maintainer needs more info)

#11 is a duplicate of #1811644: Commons wikis points to wysiwyg in make file, which is now fixed.

Please try again with the latest version of the 5.x branch of Drush and post a description of the result. Or, please post information from your PHP/webserver error log to help track down the error. Note that it sounds similar to #1749990: Support for Aegir installs directly from the web interface.

omega8cc’s picture

Well, we can't use "5.x branch of Drush" yet, because Aegir stable still uses Drush 4.6

Also, how can you request errors from the "webserver" when it is related to drush/php-cli? There are no other errors in any logs (including system level syslog and logs for php-cli), also when running the same command with -d flag for debugging.

Is it mentioned anywhere that Commons 7.x requires Drush 5.x?

I don't see anything similar to #1749990: Support for Aegir installs directly from the web interface here.

ezra-g’s picture

Commons doesn't explicitly require Drush 5.

Do you get any more informative output from Drush by running it in verbose mode?

omega8cc’s picture

Title: PHP segmentation fault on install with Aegir » Site install fails when using Drush 4.6 - which is the only option in Aegir stable

I guess we should change the issue title, as there is no segfault here (unless you are using php-cli 5.2 maybe).

omega8cc’s picture

Here is the full output (attached).

omega8cc’s picture

Note that it fails after the provision-install-backend runs for more than 60 seconds:

The external command could not be executed due to an application error. [60.66 sec, 15.41 MB]

This may suggest some kind of timeout, but no idea where from it may come.

PlayfulWolf’s picture

what kind of help is needed to make it running?

mxmilkiib’s picture

Status: Postponed (maintainer needs more info) » Active

On a new BOA Octpous Aegir install, creating a Platform with build-commons.make with the project cloned locally due to the includes[] = "drupal-org-core.make";

sky downloaded from http://ftp.drupal.org/files/projects/sky-7.x-3.0-rc1.tar.gz.
commons_origins cloned from http://git.drupal.org/project/commons_origins.git.
Checked out branch 7.x-3.x.
Undefined property: DrushMakeProject_Library::$overwrite drush_make.project.inc:83
Directory not empty: /tmp/drush_make_tmp_1354064408_50b5621814f35/__build__/profiles/commons/modules/contrib/timeago
timeago downloaded from https://raw.github.com/rmm5t/jquery-timeago/master/jquery.timeago.js.
Command dispatch complete
Peak memory usage was 9.67 MB
Could not download platform using drush make. No platform present
Command dispatch complete
Peak memory usage was 7.18 MB
Changes made in drush_hosting_task have been rolled back.
Command dispatch complete
Peak memory usage was 17.34 MB

Full log

I wanted to full localise the build files but the recent relevant patch is for Drush 5.

I'm not sure about the Undefined property:, but maybe having "timeago" as both a module and library name in the make is breaking the build?

ezra-g’s picture

Status: Active » Closed (duplicate)
ezra-g’s picture

It would be great if folks running Aegir could review the patch at #1826586: Switch to specific hash of Timeago library/ Drush 4.6 Aegir Compatibility.

mxmilkiib’s picture

Status: Closed (duplicate) » Active

The above fixes building a Platform. Problem now is that creating a Site fails;

Initial exception

Exception Object ( [message:protected] => Welcome headline field is required. Welcome body text field is required. [string:Exception:private] => [code:protected] => 0 [file:protected] => /data/disk/o1/static/commons-7.3-alpha/includes/install.core.inc [line:protected] => 414 [trace:Exception:private] => Array ( [0] => Array ( [file] => /data/disk/o1/static/commons-7.3-alpha/includes/install.core.inc [line] => 339 [function] => install_run_task [args] => Array ( [0] => Array ( [display_name] => Enter Homepage welcome text [display] => 1 [type] => form [function] => commons_anonymous_welcome_text_form [run] => 3 ) [1] => Array ( [parameters] => Array ( [profile] => commons [locale] => en [q] => ) [settings_verified] => 1 [forms] => Array ( [install_settings_form] => Array ( [driver] => mysql [database] => b********* [username] => b********* [password] => ********** [host] => localhost [port] => 3306 [db_prefix] => ) [install_configure_form] => Array ( [site_name] => commons.example.org [site_mail] => site@example.org [account] => Array ( [name] => admin [mail] => site@example.org [pass] => Array ( [pass1] => ******** [pass2] => ******** ) ) [update_status_module] => Array ( [1] => 1 [2] => 1 ) [clean_url] => 1 ) ) [interactive] => [active_task] => commons_anonymous_message_homepage [completed_task] => [database_tables_exist] => 1 [installation_finished] => [locales] => Array ( [0] => stdClass Object ( [name] => en [langcode] => en ) ) [parameters_changed] => [profile_info] => Array ( [name] => Commons [project] => commons [distribution_name] => Drupal Commons [description] => Ready-to-use solution for building communities. [core] => 7.x [dependencies] => Array ( [0] => text [1] => field_sql_storage [2] => field [3] => user .... [cont.]

And later, after giving a one-time login url,

Sent welcome mail to site@example.org
Welcome headline field is required.
Welcome body text field is required.
...
Command dispatch complete
Peak memory usage was 82.73 MB
Drush was not able to start (bootstrap) the Drupal database.

Then it gives up and reverts everything. Does the install process require manual details or such?

mxmilkiib’s picture

Title: Site install fails when using Drush 4.6 - which is the only option in Aegir stable » commons.profile makes an Aegir install fail

I quickfix removed the commons_anonymous_message_homepage (and commons_create_first_group) from commons.profile and I can now build a site.

ezra-g’s picture

Status: Active » Postponed (maintainer needs more info)

Yes, the install process has a couple of additional fields in addition to what the Drupal core installer provides.

AFAIK that's relatively common for distributions. Does Aegir support passing parameters to these fields (eg via Drush)?

omega8cc’s picture

Status: Postponed (maintainer needs more info) » Active

No, it is not supported and most distros are aware of it. Also, it was already fixed in the past in Commons 6.x - see the patch: #1060250: Commons gets stuck in an infinite loop when being installed under Aegir - note the if (defined('DRUSH_BASE_PATH')) {} there.

ezra-g’s picture

Status: Active » Closed (duplicate)

I believe the action item here is the same as was provided in #1862310: Set default values for site-specific content in the installer.