Close [x]

Set ulimit for the web server user

Edit this page on GitHub

Issue

Rolling back to a previous backup using either the Component Manager or System Upgrade can silently fail, resulting in incomplete data being written to the file system or database.

Details

In some cases, a very long query string causes the user鈥檚 allocated memory space to run out of memory because of too many recursive calls. We鈥檙e aware of this issue and are working on a solution.

Workaround

Until a solution is available, we recommend setting the ulimit for the Magento file system user to a value of 65536 or more.

You can do this either on the command line or you can make it a permanent setting for the user by editing their shell script.

If you haven鈥檛 done so already, switch to the Magento file system owner.

Command:

ulimit -s 65536

You can change this to a larger value if needed.

The syntax for ulimit depends on the UNIX shell you use. The preceding setting should work with CentOS and Ubuntu with the Bash shell. However, for Mac OS, the correct setting is ulimit -S 65532. Consult a man page or operating system reference for more information.

To optionally set the value in the user鈥檚 Bash shell:

  1. If you haven鈥檛 done so already, switch to the Magento file system owner.
  2. Open /home/<username>/.bashrc in a text editor.

  3. Add the following line:

    ulimit -s 65536
  4. Save your changes to .bashrc and exit the text editor.

We recommend you avoid setting a value for pcre.recursion_limit in php.ini because it can result in incomplete rollbacks with no failure notice.