Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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 #2
mellowtothemax CreditAttribution: mellowtothemax commentedOk, 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. RazemLet us know what happens when you disable cagefs
Comment #4
mellowtothemax CreditAttribution: mellowtothemax commentedOk, 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@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 commentedSeems that Drupal.org have made another release
Drupal 8.6.7 is out
https://www.drupal.org/project/drupal/releases/8.6.7
Comment #7
mellowtothemax CreditAttribution: mellowtothemax commentedI 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
Comment #8
mellowtothemax CreditAttribution: mellowtothemax commentedUpon 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 commentedDoes anyone have any idea how this can be fixed?
regards
Comment #10
Rik CreditAttribution: Rik commentedHi, 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-varbaseWebsite running properly after following the installation steps.
Then running
./bin/update-varbase.sh
in the corresponding directory results in this output: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@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 commentedSo 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
tofield_media_image
to thebp_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?
Comment #13
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commentedComment #14
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commentedComment #15
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commented