Update script issue [#3026549]

Hello,

Getting a few issues with the script.

Updating Varbase...
./bin/update-varbase.sh: line 242: /dev/fd/62: No such file or directory
There was and error while updating Varbase to the latest version. Please check /.update-error-log for more information.
Would you like to abort the update process and restore the backup? (no): 
no
./bin/update-varbase.sh: line 255: /dev/fd/62: No such file or directory
Something went wrong while rebuilding the cache (drush cr), this might cause the update to fail.
Would you like to abort the update process and restore the backup? (no): 
no
Enabling new required modules for the latest Varbase version...
./bin/update-varbase.sh: line 158: /dev/fd/62: No such file or directory
Error while enabling entity_browser_generic_embed. Please check /.update-error-log for more info.
Would you like to abort the update process and restore the backup? (no): 
no
Updating the database for latest changes.
./bin/update-varbase.sh: line 267: /dev/fd/62: No such file or directory
There was and error while updating Drupal core. Please check /.update-error-log for more information.
Would you like to abort the update process and restore the backup? (no): 

Hoya! Updates are now done. We will add a link in the near future for here to link to common issues appearing after updates and how to fix them.
Please install composer-patches package from Vardot's repository to catch and handle errors when applying patches.
You are on vardot/varbase (8.4.28). A newer version (8.6.3) is now available.
Please run: ./bin/update-varbase.sh to update to vardot/varbase (8.6.3).

The error log shows

[32mPreparing composer.json for Varbase updates...(B[0m
[32mUpdating Varbase...(B[0m

However Drupal core does update to 8.6.3 but drush updb crashes the site.

Regards,

Comments

Comment #1

17 January 2019 at 11:49

mellowtothemax created an issue. See original summary.

Comment #2

mellowtothemax CreditAttribution: mellowtothemax commented 17 January 2019 at 15:39

Ok, so this seems to be caused by cloudlinux cagesfs if anyone else is having a similar issue. Disabling cagefs does not give this error.

Comment #3

Mohammed J. Razem

Santa Clara, CA

CreditAttribution: Mohammed J. Razem at Vardot for Vardot commented 17 January 2019 at 18:31

Let us know what happens when you disable cagefs

Comment #4

mellowtothemax CreditAttribution: mellowtothemax commented 17 January 2019 at 22:15

Ok, so disabling cagefs, the script executes however I am running my site in a subdomain and I have drush installed globally and using an alias in bashrc to run it and for some reason the script stops with the following error

./bin/update-varbase.sh: line 41: drush: command not found

Not sure why this is but I would appreciate some feedback/assistance.

Additionally I contacted cloudlinux support and they provided me with a command to allow the script to run with cagefs.

ln -s /proc/self/fd /usr/share/cagefs-skeleton/dev/fd

This command resolves the error /dev/fd/62: No such file or directory.

Regards,

Comment #5

Mohammed J. Razem

Santa Clara, CA

CreditAttribution: Mohammed J. Razem at Vardot for Vardot commented 17 January 2019 at 23:05

Assigned:

Unassigned

» waleedq

@waleedq can you shed some light on why the script would give line 41: drush: command not found

Comment #6

Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commented 18 January 2019 at 08:23

Seems that Drupal.org have made another release
Drupal 8.6.7 is out
https://www.drupal.org/project/drupal/releases/8.6.7

This is a hotfix release for a regression affecting some Drush installations that was introduced by the fix for SA-CORE-2019-002. No other fixes are included.

Sites on 8.5.x or earlier should update immediately to Drupal 8.5.10 instead, and plan to update to the latest 8.6.x release before May 2019.

If you continue to experience issues with Drush following this update, try the following:

Run update.php to ensure database updates are completed and to clear the site cache safely without Drush.
Check the site status report to confirm that 8.6.7 was successfully installed.
Test Drush again. If issues persist:
Rename your drush CLI file back to drush.phar.
Create a symlink named drush pointing to drush.phar

Alternately, try installing Drush with Composer instead of from a phar.
Known issues

#3026560: After upgrade to 7.63, 8.5.10, 8.6.7, 9.4.0 get TYPO3 phar error for drush
#3026470: ArchiveTar is throwing fatal error
#3026443: \Drupal\Core\Security\PharExtensionInterceptor is incompatible with GeoIP and other libraries that use phar aliases or Phar::mapPhar()

Comment #7

mellowtothemax CreditAttribution: mellowtothemax commented 18 January 2019 at 11:35

I managed to run the update successfully.

Not sure if the issue was due to drush 8 (drupal 8.4+ requires drush 9 according to requirements) as is installed on my top domain level (installed via composer global) that all subdomains used via the bashrc alias.

Anyway I installed drush 9 to the varbase installation and adjusted the update script line DRUSH="drush"; to look to the drush 9 executable.

However there has been some data loss specifically with images so will need to investigate a bit more to find out why and what exactly and post findings here.

Regards,

Here is the output during the update procedure

Varbase Updater

Please choose your Drupal installation folder. Type the folder name or hit enter to choose the default one: (docroot): 


Please install composer-patches package from Vardot's repository to catch and handle errors when applying patches.
Updating vardot/varbase (8.4.28) to vardot/varbase (8.6.3)

This command will guide you to update your Varbase project.

The update process will go through several tasks to update your Drupal core and modules. Please run this script on a development environment.
 
The command will go through the following steps:
         1. Backup your current installation (code and database)
         2. Cleanup and update your composer.json to prepare for Varbase updates
         3. Update Varbase using (composer update)
         4. Enable some required modules before running Drupal database updates
         5. Update Drupal database for latest changes (drush updatedb)
         6. Write log files and perform some cleanups
 
The update process will go through several tasks to update your Drupal core and modules. Please run this script on a development environment.
Do you want to start the update process? (yes): 

Do you want to create a backup snapshot before starting the update process? (yes): 

Preparing a backup snapshot before performing updates...
 [success] Database dump saved to /update_backups/db.sql
Preparing composer.json for Varbase updates...
Please install composer-patches package from Vardot's repository to catch and handle errors when applying patches.
Generating optimized autoload files
Please install composer-patches package from Vardot's repository to catch and handle errors when applying patches.
Refactoring composer.json
composer.json has been updated. Now is your chance to perform any manual changes. Please do your changes (if any) then press enter to continue... 

Updating Varbase...
Please install composer-patches package from Vardot's repository to catch and handle errors when applying patches.
Loading composer repositories with package information
Updating dependencies (including require-dev)                     
Package operations: 24 installs, 33 updates, 29 removals
  - Removing vardot/slick (1.6.0.1)
Deleting docroot/libraries/slick - deleted
  - Removing vardot/dropzone (4.3.0.1)
Deleting docroot/libraries/dropzone - deleted
  - Removing vardot/blazy (1.8.2.1)
Deleting docroot/libraries/blazy - deleted
  - Removing vardot/ace (1.2.8.1)
Deleting docroot/libraries/ace - deleted
  - Removing drupal/xmlsitemap (1.0.0-alpha3)
Deleting docroot/modules/contrib/xmlsitemap - deleted
  - Removing drupal/media_entity_image (1.3.0)
Deleting docroot/modules/contrib/media_entity_image - deleted
  - Removing drupal/layout_plugin (1.0.0-alpha23)
Deleting docroot/modules/contrib/layout_plugin - deleted
  - Removing drupal/media_entity_document (1.1.0)
Deleting docroot/modules/contrib/media_entity_document - deleted
  - Installing cweagans/composer-patches (1.7.4): Loading from cache
No patches supplied.
Gathering patches for dependencies. This might take a minute.
  - Installing oomphinc/composer-installers-extender (v1.1.2): Loading from cache
  - Installing drupal-composer/drupal-scaffold (2.5.4): Loading from cache
  - Updating drupal/entity (1.0.0-beta4 => 1.0.0-rc1): Loading from cache
  - Updating drupal/media_entity (1.8.0 => 2.0.0-beta3): Loading from cache
  - Updating drupal/vartheme_admin (4.0.0 => 6.3.0): Loading from cache
  - Updating drupal/vartheme (4.20.0 => 6.3.0): Loading from cache
  - Updating drupal/varbase_total_control (1.4.0 => 6.3.0): Loading from cache
  - Updating drupal/vmi (1.2.0 => 2.1.0): Loading from cache
  - Updating drupal/varbase_styleguide (5.2.0 => 6.1.0): Loading from cache
  - Updating drupal/varbase_seo (4.0.0 => 6.2.0): Loading from cache
  - Updating drupal/crop (1.5.0 => 2.0.0-rc1): Loading from cache
  - Updating drupal/video_embed_field (1.5.0 => 2.0.0): Loading from cache
  - Updating drupal/slick_media (1.1.0 => 2.0.0-alpha3): Loading from cache
  - Installing j7mbo/twitter-api-php (1.0.6): Loading from cache
  - Installing drupal/media_entity_twitter (2.0.0-alpha2): Loading from cache
  - Installing drupal/media_entity_instagram (2.0.0-alpha2): Loading from cache
  - Updating drupal/entity_browser (1.6.0 => 2.0.0): Loading from cache
  - Applying patches for drupal/entity_browser
    https://www.drupal.org/files/issues/entity-browser-view-context-2865928-14.patch (Issue #2865928: The View widget should filter based on field settings.)
    https://www.drupal.org/files/issues/2877751-27-8.x-2.x.patch (Issue #2877751: Inform users how many items they can add to a field that uses an entity browser.)

  - Updating drupal/dropzonejs (1.0.0-alpha8 => 2.0.0-alpha3): Loading from cache
  - Installing drupal/better_normalizers (1.0.0-beta3): Loading from cache
  - Installing drupal/layout_builder_restrictions (1.3.0): Loading from cache
  - Installing drupal/contribute (1.0.0-beta7): Loading from cache
  - Installing drupal/webform_views (5.0.0-alpha6): Loading from cache
  - Installing drupal/webform_analysis (1.0.0-beta7): Loading from cache
  - Updating drupal/varbase_core (4.1.0 => 6.4.0): Loading from cache
  - Updating drupal/varbase_search (4.0.0 => 6.1.0): Loading from cache
  - Installing drupal/media_entity_googledocs (4.0.0): Loading from cache
  - Installing npm-asset/slick-carousel (1.8.1): Loading from cache
  - Installing npm-asset/blazy (1.8.2): Loading from cache
  - Installing npm-asset/dropzone (4.3.0): Loading from cache
  - Updating drupal/varbase_media (4.1.0 => 6.2.0): Loading from cache
  - Updating drupal/varbase_bootstrap_paragraphs (4.1.0 => 6.3.0): Loading from cache
  - Updating drupal/varbase_landing (4.1.0 => 6.1.0): Loading from cache
  - Updating drupal/varbase_heroslider_media (4.1.0 => 6.2.0): Loading from cache
  - Installing npm-asset/ace-builds (1.4.2): Loading from cache
  - Updating drupal/varbase_editor (4.19.0 => 6.2.0): Loading from cache
  - Updating drupal/varbase_carousels (4.1.0 => 6.0.0): Downloading (100%)         
  - Updating drupal/taxonomy_menu (dev-3.x ac79afd => 3.4.0):     Update failed (The .git directory is missing from docroot/modules/contrib/taxonomy_menu, see https://getcomposer.org/commit-deps for more information)
    Would you like to try reinstalling the package instead [yes]? 
  - Removing drupal/taxonomy_menu (dev-3.x)
  - Installing drupal/taxonomy_menu (3.4.0): Cloning 8.x-3.4 from cache
taxonomy_menu: 
Previous HEAD position was ac79afd Issue #2826415 by heldercor, dstol: Allow altering the built menu definition
HEAD is now at 1103ad0 Issue #2861460 by mirom: Menu Order Reset (Cache Flush, Term Save)
  - Applying patches for drupal/taxonomy_menu
    https://www.drupal.org/files/issues/2018-12-23/2939143-10.patch (Issue #2939143: Fixed Undefined method TaxonomyMenu::generateTaxonomyLinks())

  - Updating drupal/varbase_blog (4.1.0 => 6.1.0): Loading from cache
  - Updating drupal/varbase_auth (4.0.0 => 6.2.0): Loading from cache
  - Updating vardot/varbase (8.4.28 => 8.6.3): Downloading (100%)         
  - Installing vardot/entity_browser_generic_embed (dev-8.x-1.x c73c603): Cloning c73c603ad0 from cache
  - Installing drupal/imce (1.7.0): Loading from cache
  - Installing drupal/masonry_views (1.0.0-rc1): Downloading (100%)         
  - Installing drupal/material_admin (1.0.0-alpha7): Downloading (100%)         
  - Installing drupal/vartheme_material (4.0.0-alpha3): Downloading (100%)         
  - Installing drupal/vartheme_material_admin (4.0.0-alpha1): Downloading (100%)         
  - Updating drupal/entity_clone dev-1.x (6d0ce05 => ccb607c):     Update failed (The .git directory is missing from docroot/modules/contrib/entity_clone, see https://getcomposer.org/commit-deps for more information)
    Would you like to try reinstalling the package instead [yes]? 
  - Removing drupal/entity_clone (dev-1.x)
  - Installing drupal/entity_clone (dev-1.x ccb607c): Cloning ccb607c1b4 from cache
entity_clone: 
Previous HEAD position was ccb607c Issue #3008195 by acbramley: Move update hook to post update hook
HEAD is now at 6d0ce05 Issue #2912430 by Mars0atack: Get entity by form object
  - Applying patches for drupal/entity_clone
    https://www.drupal.org/files/issues/2018-08-26/2743379-18.patch (Issue #2743379: Clone operation shows regardless of permission)

  - Updating drupal/image_resize_filter dev-1.x (c3f4b23 => 3557d71):     Update failed (The .git directory is missing from docroot/modules/contrib/image_resize_filter, see https://getcomposer.org/commit-deps for more information)
    Would you like to try reinstalling the package instead [yes]? 
  - Removing drupal/image_resize_filter (dev-1.x)
  - Installing drupal/image_resize_filter (dev-1.x 3557d71): Cloning 3557d71ea4 from cache
image_resize_filter: 
Previous HEAD position was 3557d71 Issue #2955937 by gnuget, mlncn: InvalidArgumentException on settings
HEAD is now at c3f4b23 Issue #2700165 by mlncn: Port Image Resize Filter module into Drupal 8
  - Updating drupal/l10n_client dev-1.x (9bf8d59 => 3c44126):     Update failed (The .git directory is missing from docroot/modules/contrib/l10n_client, see https://getcomposer.org/commit-deps for more information)
    Would you like to try reinstalling the package instead [yes]? 
  - Removing drupal/l10n_client (dev-1.x)
  - Installing drupal/l10n_client (dev-1.x 3c44126): Cloning 3c44126865 from cache
l10n_client: 
Previous HEAD position was 3c44126 Remove wrong patch file
HEAD is now at 9bf8d59 Issue #2730919 by segi: Port tests to Drupal 8 — skip form UI testing for now while that does not work well yet
  - Applying patches for drupal/l10n_client
    https://www.drupal.org/files/issues/2867460-2.patch (Issue #2867460: Incompatible with this version of Drupal core ~8.0)
    https://www.drupal.org/files/issues/l10n_client-hook_toolbar-fix-2872668-3.patch (Issue #2872668: User error: 0 is an invalid render array key)

  - Updating drupal/menu_position dev-1.x (d134276 => 552e5b1):     Update failed (The .git directory is missing from docroot/modules/contrib/menu_position, see https://getcomposer.org/commit-deps for more information)
    Would you like to try reinstalling the package instead [yes]? 
  - Removing drupal/menu_position (dev-1.x)
  - Installing drupal/menu_position (dev-1.x 552e5b1): Cloning 552e5b1fc5 from cache
menu_position: 
Previous HEAD position was 552e5b1 Issue #2893782 by Fonski, ckaotik, sassafrass, jmuzz, BarisW: Filter on menu name when getting active link
HEAD is now at d134276 Issue #2883131 by akalata, sassafrass, Znak, ckaotik: Fatal error: Call to undefined method when creating a rule
  - Updating drupal/security_review dev-1.x (35ebae4 => 9b8a34a):     Update failed (The .git directory is missing from docroot/modules/contrib/security_review, see https://getcomposer.org/commit-deps for more information)
    Would you like to try reinstalling the package instead [yes]? 
  - Removing drupal/security_review (dev-1.x)
  - Installing drupal/security_review (dev-1.x 9b8a34a): Cloning 9b8a34a21c from cache
security_review: 
Previous HEAD position was 9b8a34a Issue #2988514 by dsnopek: Field check gets fatal error when using Paragraphs (or other entity without edit or canonical routes)
HEAD is now at 35ebae4 Issue #2820556 by kerasai, dsnopek: Utilize Drush Output Format
  - Updating drupal/tour_builder dev-1.x (d70e898 => 7421b0f):     Update failed (The .git directory is missing from docroot/modules/contrib/tour_builder, see https://getcomposer.org/commit-deps for more information)
    Would you like to try reinstalling the package instead [yes]? 
  - Removing drupal/tour_builder (dev-1.x)
  - Installing drupal/tour_builder (dev-1.x 7421b0f): Cloning 7421b0f370 from cache
tour_builder: 
Previous HEAD position was 7421b0f Issue #3004787 by chipway: Update Dependencies to new Format in .info.yml + capitalize name
HEAD is now at d70e898 Wrap export configuration by correct permission.
Writing lock file
Generating autoload files
> Varbase\composer\ScriptHandler::createRequiredFiles
> Varbase\composer\ScriptHandler::removeGitDirectories
 [success] Cache rebuild complete.
Enabling new required modules for the latest Varbase version...
 [success] Successfully enabled: entity_browser_generic_embed
Updating the database for latest changes.
 ---------------------- ----------- --------------- --------------------------------------------------------------------------- 
  Module                 Update ID   Type            Description                                                                
 ---------------------- ----------- --------------- --------------------------------------------------------------------------- 
  dropzonejs_eb_widget   8201        hook_update_n   Update configurations for configuration key renaming.                      
  dropzonejs_eb_widget   8202        hook_update_n   Update configurations for new keys.                                        
  entity_browser         8201        hook_update_n   Updates entity browsers to use the new media image upload widget plugin.   
  media_entity           8200        hook_update_n   Clears the module handler's hook implementation cache.                     
  media_entity           8201        hook_update_n   Replace Media Entity with Media.                                           
  varbase_webform        8601        hook_update_n   Enable [Webform Analysis] module.                                          
  varbase_webform        8602        hook_update_n   Enable [Webform Views Integration] module.                                 
 ---------------------- ----------- --------------- --------------------------------------------------------------------------- 

 // Do you wish to run the specified pending updates?: yes.                                                             

 [notice] Update started: media_entity_update_8200
 [ok] Update completed: media_entity_update_8200
 [notice] Update started: media_entity_update_8201
 [ok] Update completed: media_entity_update_8201
 [notice] Update started: dropzonejs_eb_widget_update_8201
 [ok] Update completed: dropzonejs_eb_widget_update_8201
 [notice] Update started: varbase_webform_update_8601
 [ok] Update completed: varbase_webform_update_8601
 [notice] Update started: dropzonejs_eb_widget_update_8202
 [ok] Update completed: dropzonejs_eb_widget_update_8202
 [notice] Update started: entity_browser_update_8201
 [ok] Update completed: entity_browser_update_8201
 [notice] Update started: varbase_webform_update_8602
 [ok] Update completed: varbase_webform_update_8602
 [success] Finished performing updates.
Hoya! Updates are now done. We will add a link in the near future for here to link to common issues appearing after updates and how to fix them.
Congratulations! You are on the latest vardot/varbase version now.

Comment #8

mellowtothemax CreditAttribution: mellowtothemax commented 23 January 2019 at 15:22

Upon further investigation there doesnt seem to be any image data loss however the paragraphs > styling settings > background image doesn't seem to render in the front end.

Edit: It seems that this only affects sites upgrading from 8.4.28. Run the upgrade script on a site running 8.5 and it worked fine. Run the script on a vanilla varbase 8.4.28 and it was affected by this issue also.

Do you happen to know why this could be?

Regards,

Comment #9

mellowtothemax CreditAttribution: mellowtothemax commented 26 January 2019 at 20:27

Does anyone have any idea how this can be fixed?

regards

Comment #10

Rik CreditAttribution: Rik commented 17 February 2019 at 15:29

Hi, I have the same issue on a clean install using composer create-project Vardot/varbase-project:^8.6 . --no-dev --no-interaction as described here: https://docs.varbase.vardot.com/updating-varbase
Website running properly after following the installation steps.
Then running ./bin/update-varbase.sh in the corresponding directory results in this output:

...
The update process will go through several tasks to update your Drupal core and modules. Please run this script on a development environment.
Do you want to start the update process? (yes): 

Do you want to create a backup snapshot before starting the update process? (yes): 

Preparing a backup snapshot before performing updates...
./bin/update-varbase.sh: line 41: /dev/fd/62: No such file or directory
Error in creating a backup, exiting update process! Please check /home/u123456/domains/somedomain.nl/varbase/.update-error-log for more info.

The actual error log is empty.

I'm on shared hosting and cagefs does not exist on the filesystem, at least outside of my control.

Any suggestions how to overcome this issue? Or suggestions how to workaround it to update the installation?

kind regards,
Rik

Comment #11

Mohammed J. Razem

Santa Clara, CA

CreditAttribution: Mohammed J. Razem at Vardot for Vardot commented 20 February 2019 at 08:24

@Rik, you're supposed to perform the updates on a local or development environment.

The updater writes files and assumes the updating process does not happen on production.
Please see the notices here: https://docs.varbase.vardot.com/updating-varbase#before-you-update

Comment #12

mellowtothemax CreditAttribution: mellowtothemax commented 23 February 2019 at 17:44

So with a little more digging I noticed that the background image issue when upgrading from 8.4.28 is due to the change in varbase_bootstrap_paragraphs.module from patch https://www.drupal.org/files/issues/2018-06-25/2981604-4.patch

The update script doesn't update the machine name from field_image to field_media_image to the bp_image_field so it doesn't return the correct value in varbase_bootstrap_paragraphs.module to allow the background image to render in the template.

What would be the best way to fix?