Error message

You are not authorized to post comments.

Hello,

In Aegir 3.160 and using PHP 7.2, I get an odd error:

The command could not be executed successfully (returned: Changed permissions of [success] /var/aegir/.drush/platform_D7.alias.drushrc.php to 640 Generated config in write(): Drush configuration file [success] (/var/aegir/.drush/platform_D7.alias.drushrc.php) Changed permissions of [success] /var/aegir/.drush/platform_D7.alias.drushrc.php to 440 , code: 0)

I can verify that the permissions are 440 on the platform_D7.alias.drushrc.php file. It also looks like the platform has been created. However, it is marked as 'failed' due to the error above.

CommentFileSizeAuthor
#6 result2.txt74.27 KBkdborg@gmail.com
#3 result.txt93.75 KBkdborg@gmail.com
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

kdborg created an issue. See original summary.

kdborg@gmail.com’s picture

This is on a CentOS 7 server with PHP 7.2.

The output for the command drush @hm hosting-task 160 --debug --force is in the report.txt file.

kdborg@gmail.com’s picture

FileSize
93.75 KB
helmo’s picture

Which drush version do you have ? I'm using 8.1.16

The 'sh: module: line 1: syntax error: unexpected end of file' at line 3 atleast looks wrong ;)

kdborg@gmail.com’s picture

I've got Drush 8.1.17 installed.

kdborg@gmail.com’s picture

FileSize
74.27 KB

The 'sh: module: line 1: syntax error: unexpected end of file' is a known issue: https://github.com/drush-ops/drush/issues/2065

Adding --verbose, output in result2.txt .

kdborg@gmail.com’s picture

CentOS:

Drush 7.x works for Drupal 7 websites.

Drush 8.x works for Drupal 8 websites.

kdborg@gmail.com’s picture

Since CentOS appears to be weird for Aegir, we're going with two Aegir servers with different versions of Drush.

This ticket can be closed.

colan’s picture

#8: I wouldn't say it's too weird for Aegir. It's just that none of the current maintainers are using it so we're not actively supporting it. However, we'd be more than happy for someone to step up and add support for it by either contributing patches to make it work, or providing funding for us to work on it. Just because there hasn't been a lot of interest doesn't mean that it's not important or worthwhile. We'd love to have it working on CentOS as well (and anything else, really).

See #2281423: Make RPMs to add support for RHEL/CentOS for some more info on this.