Update and upgrade checklist
Before you continue, to avoid errors during your installation or update, make sure you verify all of the following:
- You set up a Magento file system owner and shared that owner’s group with the web server user group
- Your cron jobs are set up and running
- Set a value for DATA_CONVERTER_BATCH_SIZE
- File system permissions are set properly
Do not continue without performing these checks. Failure to do so could result in errors.
Set a value for DATA_CONVERTER_BATCH_SIZE
Magento 2.2 includes security enhancements that requires some data to be converted from serialized data format to JSON encoded format. This conversion occurs during the upgrade and it can take a long time, depending on how much data is in your Magento database.
One or more fields in the following tables are affected:
catalogrule. (This is not a complete list.)
If you have a large amount of data, you can improve performance by setting the value of an environment variable,
DATA_CONVERTER_BATCH_SIZE. By default, it’s set to a value of 50,000.
To set the variable, before the upgrade starts enter the following command as the Magento file system owner in a bash shell prompt:
export DATA_CONVERTER_BATCH_SIZE <value>
export DATA_CONVERTER_BATCH_SIZE 100000
After your upgrade completes, you can unset the variable as follows:
DATA_CONVERTER_BATCH_SIZE requires memory; avoid setting it to a very large value (approximately 1GB) without testing it first.
Magento file system owner and group
The Magento file system owner group must have write access to Magento directories and files.
Cron jobs are running
Magento requires three cron jobs, all running as the Magento file system owner.
To verify your cron jobs are set up properly, enter the following command as the Magento file system owner:
Results similar to the following should display:
* * * * * /usr/bin/php /var/www/magento2/bin/magento cron:run | grep -v "Ran jobs by schedule" >> /var/www/magento2/var/log/magento.cron.log * * * * * /usr/bin/php /var/www/magento2/update/cron.php >> /var/www/magento2/var/log/update.cron.log * * * * * /usr/bin/php /var/www/magento2/bin/magento setup:cron:run >> /var/www/magento2/var/log/setup.cron.log
Another symptom of cron not running is the following error in the Magento Admin:
To see the error, you might need to click System Messages at the top of the window as follows:
For details, see Set up cron.
File system permissions
For security reasons, Magento requires certain permissions on the file system. Permissions are different from ownership. Ownership determines who can perform actions on the file system; permissions determine what the user can do.
Directories in the Magento file system must be writable by the Magento file system owner’s group.
To verify your file system permissions are set properly, either log in to the Magento server or use your hosting provider’s file manager application.
For example, enter the following commands on a Linux system if the Magento application is installed in
ls -al /var/www/html/magento2
A sample result follows:
In the preceding example, the Magento file system owner is
magento_user. Directories in the Magento file system have
drwxrwx--- permissions (775) and files have
-rw-rw-rw- permissions (664).
To get more detailed information, you can optionally enter the following command:
ls -al /var/www/html/magento2/pub
Because Magento deploys static file assets to subdirectories of
pub, it’s a good idea to verify permissions and ownership there as well.
For more information, see File system permissions and ownership.