Can't upgrade to 2.2.3 from 2.2.2. Memory limit reachedException Error: “Memory limit has been reached.”AvaTax exceeds memory limitMagento2 CE Memory limit has been reached when saving productMagento 2: “Memory limit has been reached” when resizing imagesUpgrade Magento from 2.1.10 to 2.2.2Fatal Error - Magento update 2.1.2 --> 2.2.2 Manual Update (overwrite files) Fatal error: Uncaught Error: Cannot instantiate interfaceCan't upgrade to Magento Commerce 2.2.3Memory Limit Reached while upgrading Magento 2.1.11 to 2.1.12PHP mem error after updating from 2.1.x to 2.2.x #17021composer connection refused

Last-minute canceled work-trip mean I'll lose thousands of dollars on planned vacation

Why do the digits of a number squared follow a similar quotient?

Applying for jobs with an obvious scar

What would be the safest way to drop thousands of small, hard objects from a typical, high wing, GA airplane?

How to belay quickly ascending top-rope climbers?

Did Hitler say this quote about homeschooling?

How to tell readers that I know my story is factually incorrect?

How to interpret a promising preprint that was never published in peer-review?

Three Subway Escalators

How important are the Author's mood and feelings for writing a story?

How to tell if JDK is available from within running JVM?

Who would use the word "manky"?

How much solution to fill Paterson Universal Tank when developing film?

Who or what determines if a curse is valid or not?

Which modern firearm should a time traveler bring to be easily reproducible for a historic civilization?

Changing iteration variable in Do loop

"Je suis petite, moi?", purpose of the "moi"?

Why is Google approaching my VPS machine?

How was Luke's prosthetic hand in Episode V filmed?

Inscriptio Labyrinthica

Diagram of Methods to Solve Differential Equations

How did Jayne know when to shoot?

Is encryption still applied if you ignore the SSL certificate warning for self-signed certs?

How to extract interesting piece of output in bash



Can't upgrade to 2.2.3 from 2.2.2. Memory limit reached


Exception Error: “Memory limit has been reached.”AvaTax exceeds memory limitMagento2 CE Memory limit has been reached when saving productMagento 2: “Memory limit has been reached” when resizing imagesUpgrade Magento from 2.1.10 to 2.2.2Fatal Error - Magento update 2.1.2 --> 2.2.2 Manual Update (overwrite files) Fatal error: Uncaught Error: Cannot instantiate interfaceCan't upgrade to Magento Commerce 2.2.3Memory Limit Reached while upgrading Magento 2.1.11 to 2.1.12PHP mem error after updating from 2.1.x to 2.2.x #17021composer connection refused






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















I'm trying to upgrade my Magento installation but experiencing problems with the process:



I was trying to update my site to the latest release as advised and I did so via the command line but I ran out of memory trying to do so.



Commands I ran were:



composer require magento/product-community-edition 2.2.3 --no-update
composer update


It was running fine but then a fatal error occurred:



Updating magento/magento2-base (2.2.2 => 2.2.3): Downloading (90%)
mmap() failed: [12] Cannot allocate memory

mmap() failed: [12] Cannot allocate memory

Fatal error: Out of memory (allocated 848302080) (tried to allocate 14680096 bytes) in phar:///usr/local/bin/composer.phar/src/Comp


Any ideas as my RAM allocation is fixed to 768? (I tried boosting it already).
I'm trying to upgrade to 2.2.3 from 2.2.2.



Thank you so much for any advice you may have.










share|improve this question






























    0















    I'm trying to upgrade my Magento installation but experiencing problems with the process:



    I was trying to update my site to the latest release as advised and I did so via the command line but I ran out of memory trying to do so.



    Commands I ran were:



    composer require magento/product-community-edition 2.2.3 --no-update
    composer update


    It was running fine but then a fatal error occurred:



    Updating magento/magento2-base (2.2.2 => 2.2.3): Downloading (90%)
    mmap() failed: [12] Cannot allocate memory

    mmap() failed: [12] Cannot allocate memory

    Fatal error: Out of memory (allocated 848302080) (tried to allocate 14680096 bytes) in phar:///usr/local/bin/composer.phar/src/Comp


    Any ideas as my RAM allocation is fixed to 768? (I tried boosting it already).
    I'm trying to upgrade to 2.2.3 from 2.2.2.



    Thank you so much for any advice you may have.










    share|improve this question


























      0












      0








      0








      I'm trying to upgrade my Magento installation but experiencing problems with the process:



      I was trying to update my site to the latest release as advised and I did so via the command line but I ran out of memory trying to do so.



      Commands I ran were:



      composer require magento/product-community-edition 2.2.3 --no-update
      composer update


      It was running fine but then a fatal error occurred:



      Updating magento/magento2-base (2.2.2 => 2.2.3): Downloading (90%)
      mmap() failed: [12] Cannot allocate memory

      mmap() failed: [12] Cannot allocate memory

      Fatal error: Out of memory (allocated 848302080) (tried to allocate 14680096 bytes) in phar:///usr/local/bin/composer.phar/src/Comp


      Any ideas as my RAM allocation is fixed to 768? (I tried boosting it already).
      I'm trying to upgrade to 2.2.3 from 2.2.2.



      Thank you so much for any advice you may have.










      share|improve this question
















      I'm trying to upgrade my Magento installation but experiencing problems with the process:



      I was trying to update my site to the latest release as advised and I did so via the command line but I ran out of memory trying to do so.



      Commands I ran were:



      composer require magento/product-community-edition 2.2.3 --no-update
      composer update


      It was running fine but then a fatal error occurred:



      Updating magento/magento2-base (2.2.2 => 2.2.3): Downloading (90%)
      mmap() failed: [12] Cannot allocate memory

      mmap() failed: [12] Cannot allocate memory

      Fatal error: Out of memory (allocated 848302080) (tried to allocate 14680096 bytes) in phar:///usr/local/bin/composer.phar/src/Comp


      Any ideas as my RAM allocation is fixed to 768? (I tried boosting it already).
      I'm trying to upgrade to 2.2.3 from 2.2.2.



      Thank you so much for any advice you may have.







      magento-2.1 upgrade composer memory






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 2 '18 at 10:39







      Rushed89

















      asked Mar 2 '18 at 10:16









      Rushed89Rushed89

      11 bronze badge




      11 bronze badge




















          2 Answers
          2






          active

          oldest

          votes


















          0














          Try:



          php -d memory_limit=2048M composer require magento/product-community-edition 2.2.3 --no-update


          php -d memory_limit=2048M composer update



          If this fails go for memory_limit=-1.



          If you haven't linked composer to your users bash, then replace composer with $(which composer).
          It will return the path to the composer executable in your server. For example: /usr/local/bin/composer and the command will look like:



          php -d memory_limit=2048M /usr/local/bin/composer require magento/product-community-edition 2.2.3 --no-update composer update


          Same goes for php. If you got multiple php versions you should use the php7 version. Run $which php and it will return the paths that php in installed in. The parenthesis just execute the return as well so you can use them in commands like the one i gave you.
          Please do this with care. Open a second terminal and monitor your processes, try htop, for possible memory leaks(so you can kill the processes with kill $pid of the memory eating one).



          As for the hard limit you face.
          What kind of webserver are you using and what php version/package for php code?
          What kind of values exist on your php.ini and if you are using php-fpm on your fpm-pool for this user?



          Magento 2 example configurations for both apache and nginx set the value for memory limit via .htaccess, .user.ini or FastCGI memory_limit to 768 and might be overriding your values.



          If you are on a shared hosting with many restriction then try this:
          find - /name php.ini
          Find the one that fits your php-version.
          Edit this file and set memory_limit=2048M or memory_limit=-1. DO NOT FORGET TO REVERT THE CHANGE AFTER YOU ARE DONE.



          If you are using Apache then:



          • create a php.ini file in your Magento installation root folder(copy
            php's default we found above. cp /path/to/php7/etc/php.ini
            /path/to/magento/root/php.ini).


          • edit memory_limit value as said above.


          • create .htaccess file on your Magento installation root folder and
            add this line SetEnv PHPRC /path/to/magento/root/php.ini.






          share|improve this answer

























          • Hi Thanks for replying! So I'm using cpanel if that helps? Any command I run using PHP I have to do as /usr/local/php70/bin/php-cli While I'm technically able linux / magento are still fairly new to me and I'm not sure how to find any memory leaks using cpanel etc.

            – Rushed89
            Mar 2 '18 at 11:13












          • We don't really care for cPanel at this point. Simply login to your server via ssh and navigate to your Magentos root path.This should be the directory that contains the var/ pub/ etc/ update/ lib/ generated/ directories and more. From there run: /usr/local/php70/bin/php-cli -d memory_limit=2048M $(which composer) require magento/product-community-edition 2.2.3 --no-update composer update

            – 1337_sanc
            Mar 2 '18 at 11:23











          • Let me know how it went or if you are still facing problems.

            – 1337_sanc
            Mar 2 '18 at 12:13











          • I think because I'm using a shared server setup I can't set PHP limits higher than 756 and I don't have the ability to install htop. All a bit of a mess really. I'm thinking maybe restating my php service might help and kill any mem leaks long enough for me to upgrade?

            – Rushed89
            Mar 2 '18 at 12:28











          • Don't take the leaks statement for granted. I just mentioned it because in rare cases you might face one. This is a standard procedure you are about to do, i just had to let you know. Since this is a shared setup my scenario should never happen so just go for the command i gave you. Also restarting php would also kill the process as well and since it was a process you spawned manually without schedule it should not come up again. I think there was a certain tab on cpanel that you can monitor your processes aswell.

            – 1337_sanc
            Mar 2 '18 at 12:32


















          0














          Your help was close thanks. Not sure why I needed to state composer.phar but there we go. I can follow copy and paste for next time! Commands I ran were:



          /usr/local/php70/bin/php-cli composer.phar require magento/product-community-edition 2.2.3 --no-update



          ./composer.json has been updated



          /usr/local/php70/bin/php-cli composer.phar update






          share|improve this answer

























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "479"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f215750%2fcant-upgrade-to-2-2-3-from-2-2-2-memory-limit-reached%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Try:



            php -d memory_limit=2048M composer require magento/product-community-edition 2.2.3 --no-update


            php -d memory_limit=2048M composer update



            If this fails go for memory_limit=-1.



            If you haven't linked composer to your users bash, then replace composer with $(which composer).
            It will return the path to the composer executable in your server. For example: /usr/local/bin/composer and the command will look like:



            php -d memory_limit=2048M /usr/local/bin/composer require magento/product-community-edition 2.2.3 --no-update composer update


            Same goes for php. If you got multiple php versions you should use the php7 version. Run $which php and it will return the paths that php in installed in. The parenthesis just execute the return as well so you can use them in commands like the one i gave you.
            Please do this with care. Open a second terminal and monitor your processes, try htop, for possible memory leaks(so you can kill the processes with kill $pid of the memory eating one).



            As for the hard limit you face.
            What kind of webserver are you using and what php version/package for php code?
            What kind of values exist on your php.ini and if you are using php-fpm on your fpm-pool for this user?



            Magento 2 example configurations for both apache and nginx set the value for memory limit via .htaccess, .user.ini or FastCGI memory_limit to 768 and might be overriding your values.



            If you are on a shared hosting with many restriction then try this:
            find - /name php.ini
            Find the one that fits your php-version.
            Edit this file and set memory_limit=2048M or memory_limit=-1. DO NOT FORGET TO REVERT THE CHANGE AFTER YOU ARE DONE.



            If you are using Apache then:



            • create a php.ini file in your Magento installation root folder(copy
              php's default we found above. cp /path/to/php7/etc/php.ini
              /path/to/magento/root/php.ini).


            • edit memory_limit value as said above.


            • create .htaccess file on your Magento installation root folder and
              add this line SetEnv PHPRC /path/to/magento/root/php.ini.






            share|improve this answer

























            • Hi Thanks for replying! So I'm using cpanel if that helps? Any command I run using PHP I have to do as /usr/local/php70/bin/php-cli While I'm technically able linux / magento are still fairly new to me and I'm not sure how to find any memory leaks using cpanel etc.

              – Rushed89
              Mar 2 '18 at 11:13












            • We don't really care for cPanel at this point. Simply login to your server via ssh and navigate to your Magentos root path.This should be the directory that contains the var/ pub/ etc/ update/ lib/ generated/ directories and more. From there run: /usr/local/php70/bin/php-cli -d memory_limit=2048M $(which composer) require magento/product-community-edition 2.2.3 --no-update composer update

              – 1337_sanc
              Mar 2 '18 at 11:23











            • Let me know how it went or if you are still facing problems.

              – 1337_sanc
              Mar 2 '18 at 12:13











            • I think because I'm using a shared server setup I can't set PHP limits higher than 756 and I don't have the ability to install htop. All a bit of a mess really. I'm thinking maybe restating my php service might help and kill any mem leaks long enough for me to upgrade?

              – Rushed89
              Mar 2 '18 at 12:28











            • Don't take the leaks statement for granted. I just mentioned it because in rare cases you might face one. This is a standard procedure you are about to do, i just had to let you know. Since this is a shared setup my scenario should never happen so just go for the command i gave you. Also restarting php would also kill the process as well and since it was a process you spawned manually without schedule it should not come up again. I think there was a certain tab on cpanel that you can monitor your processes aswell.

              – 1337_sanc
              Mar 2 '18 at 12:32















            0














            Try:



            php -d memory_limit=2048M composer require magento/product-community-edition 2.2.3 --no-update


            php -d memory_limit=2048M composer update



            If this fails go for memory_limit=-1.



            If you haven't linked composer to your users bash, then replace composer with $(which composer).
            It will return the path to the composer executable in your server. For example: /usr/local/bin/composer and the command will look like:



            php -d memory_limit=2048M /usr/local/bin/composer require magento/product-community-edition 2.2.3 --no-update composer update


            Same goes for php. If you got multiple php versions you should use the php7 version. Run $which php and it will return the paths that php in installed in. The parenthesis just execute the return as well so you can use them in commands like the one i gave you.
            Please do this with care. Open a second terminal and monitor your processes, try htop, for possible memory leaks(so you can kill the processes with kill $pid of the memory eating one).



            As for the hard limit you face.
            What kind of webserver are you using and what php version/package for php code?
            What kind of values exist on your php.ini and if you are using php-fpm on your fpm-pool for this user?



            Magento 2 example configurations for both apache and nginx set the value for memory limit via .htaccess, .user.ini or FastCGI memory_limit to 768 and might be overriding your values.



            If you are on a shared hosting with many restriction then try this:
            find - /name php.ini
            Find the one that fits your php-version.
            Edit this file and set memory_limit=2048M or memory_limit=-1. DO NOT FORGET TO REVERT THE CHANGE AFTER YOU ARE DONE.



            If you are using Apache then:



            • create a php.ini file in your Magento installation root folder(copy
              php's default we found above. cp /path/to/php7/etc/php.ini
              /path/to/magento/root/php.ini).


            • edit memory_limit value as said above.


            • create .htaccess file on your Magento installation root folder and
              add this line SetEnv PHPRC /path/to/magento/root/php.ini.






            share|improve this answer

























            • Hi Thanks for replying! So I'm using cpanel if that helps? Any command I run using PHP I have to do as /usr/local/php70/bin/php-cli While I'm technically able linux / magento are still fairly new to me and I'm not sure how to find any memory leaks using cpanel etc.

              – Rushed89
              Mar 2 '18 at 11:13












            • We don't really care for cPanel at this point. Simply login to your server via ssh and navigate to your Magentos root path.This should be the directory that contains the var/ pub/ etc/ update/ lib/ generated/ directories and more. From there run: /usr/local/php70/bin/php-cli -d memory_limit=2048M $(which composer) require magento/product-community-edition 2.2.3 --no-update composer update

              – 1337_sanc
              Mar 2 '18 at 11:23











            • Let me know how it went or if you are still facing problems.

              – 1337_sanc
              Mar 2 '18 at 12:13











            • I think because I'm using a shared server setup I can't set PHP limits higher than 756 and I don't have the ability to install htop. All a bit of a mess really. I'm thinking maybe restating my php service might help and kill any mem leaks long enough for me to upgrade?

              – Rushed89
              Mar 2 '18 at 12:28











            • Don't take the leaks statement for granted. I just mentioned it because in rare cases you might face one. This is a standard procedure you are about to do, i just had to let you know. Since this is a shared setup my scenario should never happen so just go for the command i gave you. Also restarting php would also kill the process as well and since it was a process you spawned manually without schedule it should not come up again. I think there was a certain tab on cpanel that you can monitor your processes aswell.

              – 1337_sanc
              Mar 2 '18 at 12:32













            0












            0








            0







            Try:



            php -d memory_limit=2048M composer require magento/product-community-edition 2.2.3 --no-update


            php -d memory_limit=2048M composer update



            If this fails go for memory_limit=-1.



            If you haven't linked composer to your users bash, then replace composer with $(which composer).
            It will return the path to the composer executable in your server. For example: /usr/local/bin/composer and the command will look like:



            php -d memory_limit=2048M /usr/local/bin/composer require magento/product-community-edition 2.2.3 --no-update composer update


            Same goes for php. If you got multiple php versions you should use the php7 version. Run $which php and it will return the paths that php in installed in. The parenthesis just execute the return as well so you can use them in commands like the one i gave you.
            Please do this with care. Open a second terminal and monitor your processes, try htop, for possible memory leaks(so you can kill the processes with kill $pid of the memory eating one).



            As for the hard limit you face.
            What kind of webserver are you using and what php version/package for php code?
            What kind of values exist on your php.ini and if you are using php-fpm on your fpm-pool for this user?



            Magento 2 example configurations for both apache and nginx set the value for memory limit via .htaccess, .user.ini or FastCGI memory_limit to 768 and might be overriding your values.



            If you are on a shared hosting with many restriction then try this:
            find - /name php.ini
            Find the one that fits your php-version.
            Edit this file and set memory_limit=2048M or memory_limit=-1. DO NOT FORGET TO REVERT THE CHANGE AFTER YOU ARE DONE.



            If you are using Apache then:



            • create a php.ini file in your Magento installation root folder(copy
              php's default we found above. cp /path/to/php7/etc/php.ini
              /path/to/magento/root/php.ini).


            • edit memory_limit value as said above.


            • create .htaccess file on your Magento installation root folder and
              add this line SetEnv PHPRC /path/to/magento/root/php.ini.






            share|improve this answer















            Try:



            php -d memory_limit=2048M composer require magento/product-community-edition 2.2.3 --no-update


            php -d memory_limit=2048M composer update



            If this fails go for memory_limit=-1.



            If you haven't linked composer to your users bash, then replace composer with $(which composer).
            It will return the path to the composer executable in your server. For example: /usr/local/bin/composer and the command will look like:



            php -d memory_limit=2048M /usr/local/bin/composer require magento/product-community-edition 2.2.3 --no-update composer update


            Same goes for php. If you got multiple php versions you should use the php7 version. Run $which php and it will return the paths that php in installed in. The parenthesis just execute the return as well so you can use them in commands like the one i gave you.
            Please do this with care. Open a second terminal and monitor your processes, try htop, for possible memory leaks(so you can kill the processes with kill $pid of the memory eating one).



            As for the hard limit you face.
            What kind of webserver are you using and what php version/package for php code?
            What kind of values exist on your php.ini and if you are using php-fpm on your fpm-pool for this user?



            Magento 2 example configurations for both apache and nginx set the value for memory limit via .htaccess, .user.ini or FastCGI memory_limit to 768 and might be overriding your values.



            If you are on a shared hosting with many restriction then try this:
            find - /name php.ini
            Find the one that fits your php-version.
            Edit this file and set memory_limit=2048M or memory_limit=-1. DO NOT FORGET TO REVERT THE CHANGE AFTER YOU ARE DONE.



            If you are using Apache then:



            • create a php.ini file in your Magento installation root folder(copy
              php's default we found above. cp /path/to/php7/etc/php.ini
              /path/to/magento/root/php.ini).


            • edit memory_limit value as said above.


            • create .htaccess file on your Magento installation root folder and
              add this line SetEnv PHPRC /path/to/magento/root/php.ini.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Mar 2 '18 at 13:49

























            answered Mar 2 '18 at 10:38









            1337_sanc1337_sanc

            14410 bronze badges




            14410 bronze badges












            • Hi Thanks for replying! So I'm using cpanel if that helps? Any command I run using PHP I have to do as /usr/local/php70/bin/php-cli While I'm technically able linux / magento are still fairly new to me and I'm not sure how to find any memory leaks using cpanel etc.

              – Rushed89
              Mar 2 '18 at 11:13












            • We don't really care for cPanel at this point. Simply login to your server via ssh and navigate to your Magentos root path.This should be the directory that contains the var/ pub/ etc/ update/ lib/ generated/ directories and more. From there run: /usr/local/php70/bin/php-cli -d memory_limit=2048M $(which composer) require magento/product-community-edition 2.2.3 --no-update composer update

              – 1337_sanc
              Mar 2 '18 at 11:23











            • Let me know how it went or if you are still facing problems.

              – 1337_sanc
              Mar 2 '18 at 12:13











            • I think because I'm using a shared server setup I can't set PHP limits higher than 756 and I don't have the ability to install htop. All a bit of a mess really. I'm thinking maybe restating my php service might help and kill any mem leaks long enough for me to upgrade?

              – Rushed89
              Mar 2 '18 at 12:28











            • Don't take the leaks statement for granted. I just mentioned it because in rare cases you might face one. This is a standard procedure you are about to do, i just had to let you know. Since this is a shared setup my scenario should never happen so just go for the command i gave you. Also restarting php would also kill the process as well and since it was a process you spawned manually without schedule it should not come up again. I think there was a certain tab on cpanel that you can monitor your processes aswell.

              – 1337_sanc
              Mar 2 '18 at 12:32

















            • Hi Thanks for replying! So I'm using cpanel if that helps? Any command I run using PHP I have to do as /usr/local/php70/bin/php-cli While I'm technically able linux / magento are still fairly new to me and I'm not sure how to find any memory leaks using cpanel etc.

              – Rushed89
              Mar 2 '18 at 11:13












            • We don't really care for cPanel at this point. Simply login to your server via ssh and navigate to your Magentos root path.This should be the directory that contains the var/ pub/ etc/ update/ lib/ generated/ directories and more. From there run: /usr/local/php70/bin/php-cli -d memory_limit=2048M $(which composer) require magento/product-community-edition 2.2.3 --no-update composer update

              – 1337_sanc
              Mar 2 '18 at 11:23











            • Let me know how it went or if you are still facing problems.

              – 1337_sanc
              Mar 2 '18 at 12:13











            • I think because I'm using a shared server setup I can't set PHP limits higher than 756 and I don't have the ability to install htop. All a bit of a mess really. I'm thinking maybe restating my php service might help and kill any mem leaks long enough for me to upgrade?

              – Rushed89
              Mar 2 '18 at 12:28











            • Don't take the leaks statement for granted. I just mentioned it because in rare cases you might face one. This is a standard procedure you are about to do, i just had to let you know. Since this is a shared setup my scenario should never happen so just go for the command i gave you. Also restarting php would also kill the process as well and since it was a process you spawned manually without schedule it should not come up again. I think there was a certain tab on cpanel that you can monitor your processes aswell.

              – 1337_sanc
              Mar 2 '18 at 12:32
















            Hi Thanks for replying! So I'm using cpanel if that helps? Any command I run using PHP I have to do as /usr/local/php70/bin/php-cli While I'm technically able linux / magento are still fairly new to me and I'm not sure how to find any memory leaks using cpanel etc.

            – Rushed89
            Mar 2 '18 at 11:13






            Hi Thanks for replying! So I'm using cpanel if that helps? Any command I run using PHP I have to do as /usr/local/php70/bin/php-cli While I'm technically able linux / magento are still fairly new to me and I'm not sure how to find any memory leaks using cpanel etc.

            – Rushed89
            Mar 2 '18 at 11:13














            We don't really care for cPanel at this point. Simply login to your server via ssh and navigate to your Magentos root path.This should be the directory that contains the var/ pub/ etc/ update/ lib/ generated/ directories and more. From there run: /usr/local/php70/bin/php-cli -d memory_limit=2048M $(which composer) require magento/product-community-edition 2.2.3 --no-update composer update

            – 1337_sanc
            Mar 2 '18 at 11:23





            We don't really care for cPanel at this point. Simply login to your server via ssh and navigate to your Magentos root path.This should be the directory that contains the var/ pub/ etc/ update/ lib/ generated/ directories and more. From there run: /usr/local/php70/bin/php-cli -d memory_limit=2048M $(which composer) require magento/product-community-edition 2.2.3 --no-update composer update

            – 1337_sanc
            Mar 2 '18 at 11:23













            Let me know how it went or if you are still facing problems.

            – 1337_sanc
            Mar 2 '18 at 12:13





            Let me know how it went or if you are still facing problems.

            – 1337_sanc
            Mar 2 '18 at 12:13













            I think because I'm using a shared server setup I can't set PHP limits higher than 756 and I don't have the ability to install htop. All a bit of a mess really. I'm thinking maybe restating my php service might help and kill any mem leaks long enough for me to upgrade?

            – Rushed89
            Mar 2 '18 at 12:28





            I think because I'm using a shared server setup I can't set PHP limits higher than 756 and I don't have the ability to install htop. All a bit of a mess really. I'm thinking maybe restating my php service might help and kill any mem leaks long enough for me to upgrade?

            – Rushed89
            Mar 2 '18 at 12:28













            Don't take the leaks statement for granted. I just mentioned it because in rare cases you might face one. This is a standard procedure you are about to do, i just had to let you know. Since this is a shared setup my scenario should never happen so just go for the command i gave you. Also restarting php would also kill the process as well and since it was a process you spawned manually without schedule it should not come up again. I think there was a certain tab on cpanel that you can monitor your processes aswell.

            – 1337_sanc
            Mar 2 '18 at 12:32





            Don't take the leaks statement for granted. I just mentioned it because in rare cases you might face one. This is a standard procedure you are about to do, i just had to let you know. Since this is a shared setup my scenario should never happen so just go for the command i gave you. Also restarting php would also kill the process as well and since it was a process you spawned manually without schedule it should not come up again. I think there was a certain tab on cpanel that you can monitor your processes aswell.

            – 1337_sanc
            Mar 2 '18 at 12:32













            0














            Your help was close thanks. Not sure why I needed to state composer.phar but there we go. I can follow copy and paste for next time! Commands I ran were:



            /usr/local/php70/bin/php-cli composer.phar require magento/product-community-edition 2.2.3 --no-update



            ./composer.json has been updated



            /usr/local/php70/bin/php-cli composer.phar update






            share|improve this answer



























              0














              Your help was close thanks. Not sure why I needed to state composer.phar but there we go. I can follow copy and paste for next time! Commands I ran were:



              /usr/local/php70/bin/php-cli composer.phar require magento/product-community-edition 2.2.3 --no-update



              ./composer.json has been updated



              /usr/local/php70/bin/php-cli composer.phar update






              share|improve this answer

























                0












                0








                0







                Your help was close thanks. Not sure why I needed to state composer.phar but there we go. I can follow copy and paste for next time! Commands I ran were:



                /usr/local/php70/bin/php-cli composer.phar require magento/product-community-edition 2.2.3 --no-update



                ./composer.json has been updated



                /usr/local/php70/bin/php-cli composer.phar update






                share|improve this answer













                Your help was close thanks. Not sure why I needed to state composer.phar but there we go. I can follow copy and paste for next time! Commands I ran were:



                /usr/local/php70/bin/php-cli composer.phar require magento/product-community-edition 2.2.3 --no-update



                ./composer.json has been updated



                /usr/local/php70/bin/php-cli composer.phar update







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 3 '18 at 17:23









                Rushed89Rushed89

                11 bronze badge




                11 bronze badge



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Magento Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f215750%2fcant-upgrade-to-2-2-3-from-2-2-2-memory-limit-reached%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Category:9 (number) SubcategoriesMedia in category "9 (number)"Navigation menuUpload mediaGND ID: 4485639-8Library of Congress authority ID: sh85091979ReasonatorScholiaStatistics

                    Circuit construction for execution of conditional statements using least significant bitHow are two different registers being used as “control”?How exactly is the stated composite state of the two registers being produced using the $R_zz$ controlled rotations?Efficiently performing controlled rotations in HHLWould this quantum algorithm implementation work?How to prepare a superposed states of odd integers from $1$ to $sqrtN$?Why is this implementation of the order finding algorithm not working?Circuit construction for Hamiltonian simulationHow can I invert the least significant bit of a certain term of a superposed state?Implementing an oracleImplementing a controlled sum operation

                    Magento 2 “No Payment Methods” in Admin New OrderHow to integrate Paypal Express Checkout with the Magento APIMagento 1.5 - Sales > Order > edit order and shipping methods disappearAuto Invoice Check/Money Order Payment methodAdd more simple payment methods?Shipping methods not showingWhat should I do to change payment methods if changing the configuration has no effects?1.9 - No Payment Methods showing upMy Payment Methods not Showing for downloadable/virtual product when checkout?Magento2 API to access internal payment methodHow to call an existing payment methods in the registration form?