Magento 2.3 Upgrade issueMagento 2: Upgrade Readiness Check Cron script readiness check failedMagento 2 update System Upgrade Status: Update pendingPackage sjparkinson/static-review is abandoned message in Magento 2Error Magento 2.3.0 upgrade ( php requirement )Upgrade Magento from 2.2.6 to 2.3Cannot upgrade to 2.3.0 using Web Setup WizardUpdate Magento 2.6 to Magento 2.3 Issuecomposer connection refusedUpgrade Issue - no matching package found. zendframework/zend-stdlib ^2.7.7 not foundMagento 2.2.5 After Upgrade To 2.3 CLI commands don't work

Are there any examples of a variable being normally distributed that is *not* due to the Central Limit Theorem?

Zip/Tar file compressed to larger size?

Bullying boss launched a smear campaign and made me unemployable

How can I determine if the org that I'm currently connected to is a scratch org?

Is there an expression that means doing something right before you will need it rather than doing it in case you might need it?

Should I cover my bicycle overnight while bikepacking?

How do I gain back my faith in my PhD degree?

What method can I use to design a dungeon difficult enough that the PCs can't make it through without killing them?

How could indestructible materials be used in power generation?

iPad being using in wall mount battery swollen

Is "remove commented out code" correct English?

Is it acceptable for a professor to tell male students to not think that they are smarter than female students?

What's the in-universe reasoning behind sorcerers needing material components?

One verb to replace 'be a member of' a club

Intersection Puzzle

Why didn't Boeing produce its own regional jet?

Why are the 737's rear doors unusable in a water landing?

What does the expression "A Mann!" means

How did the Super Star Destroyer Executor get destroyed exactly?

How do I know where to place holes on an instrument?

Why is this clock signal connected to a capacitor to gnd?

Detention in 1997

What historical events would have to change in order to make 19th century "steampunk" technology possible?

How to prevent "they're falling in love" trope



Magento 2.3 Upgrade issue


Magento 2: Upgrade Readiness Check Cron script readiness check failedMagento 2 update System Upgrade Status: Update pendingPackage sjparkinson/static-review is abandoned message in Magento 2Error Magento 2.3.0 upgrade ( php requirement )Upgrade Magento from 2.2.6 to 2.3Cannot upgrade to 2.3.0 using Web Setup WizardUpdate Magento 2.6 to Magento 2.3 Issuecomposer connection refusedUpgrade Issue - no matching package found. zendframework/zend-stdlib ^2.7.7 not foundMagento 2.2.5 After Upgrade To 2.3 CLI commands don't work













0















I'm trying to upgrade to Magento 2.3.1 and I'm running into a problem. I was on PHP 7.1.3 and noticed in the system requirements that it requires 7.1.3 and 7.2.X. We've upgraded the server PHP version to 7.2.16.



Running composer update after doing the other steps brings up this error:



[user@machine public_html]$ composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 138 installs, 163 updates, 0 removals
- Installing magento/inventory-composer-installer (1.1.0): Loading from cache

Warning: Unsupported declare 'strict_types' in /home/site/public_html/vendor/magento/inventory-composer-installer/src/Plugin.php on line 6

Parse error: syntax error, unexpected ':', expecting ';' or '{' in /home/site/public_html/vendor/magento/inventory-composer-installer/src/Plugin.php on line 55


Running $ php -v returns this info:



[user@machine public_html]$ php -v
PHP 7.2.16 (cli) (built: Mar 25 2019 18:26:43) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies


and in my composer.json I have:



... etc ...
"config":
"platform":
"php": "7.2.16"
,
"use-include-path": true
,
... etc ...


I've scoured the internet and it all leads back to upgrade PHP version - which ... it is. What step am I missing?



edit



question replies




Are you following the steps outlined in the Magento DevDocs or another resource? - Did you update using the Magento script at https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html#upgrade-cli-script?




following the steps for manual CLI upgrade.




Do you have a cache storage system like Redis or Memcached that needs to be cleared?




Nope.




Do you have any other errors if you disable the inventory-composer-installer module?




nope.




Are you upgrading php-fpm?




Not using it.




What version of Composer do you have after upgrading?




composer -V shows




Composer version 1.5.2 2017-09-11 16:59:25











share|improve this question




























    0















    I'm trying to upgrade to Magento 2.3.1 and I'm running into a problem. I was on PHP 7.1.3 and noticed in the system requirements that it requires 7.1.3 and 7.2.X. We've upgraded the server PHP version to 7.2.16.



    Running composer update after doing the other steps brings up this error:



    [user@machine public_html]$ composer update
    Loading composer repositories with package information
    Updating dependencies (including require-dev)
    Package operations: 138 installs, 163 updates, 0 removals
    - Installing magento/inventory-composer-installer (1.1.0): Loading from cache

    Warning: Unsupported declare 'strict_types' in /home/site/public_html/vendor/magento/inventory-composer-installer/src/Plugin.php on line 6

    Parse error: syntax error, unexpected ':', expecting ';' or '{' in /home/site/public_html/vendor/magento/inventory-composer-installer/src/Plugin.php on line 55


    Running $ php -v returns this info:



    [user@machine public_html]$ php -v
    PHP 7.2.16 (cli) (built: Mar 25 2019 18:26:43) ( NTS )
    Copyright (c) 1997-2018 The PHP Group
    Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies


    and in my composer.json I have:



    ... etc ...
    "config":
    "platform":
    "php": "7.2.16"
    ,
    "use-include-path": true
    ,
    ... etc ...


    I've scoured the internet and it all leads back to upgrade PHP version - which ... it is. What step am I missing?



    edit



    question replies




    Are you following the steps outlined in the Magento DevDocs or another resource? - Did you update using the Magento script at https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html#upgrade-cli-script?




    following the steps for manual CLI upgrade.




    Do you have a cache storage system like Redis or Memcached that needs to be cleared?




    Nope.




    Do you have any other errors if you disable the inventory-composer-installer module?




    nope.




    Are you upgrading php-fpm?




    Not using it.




    What version of Composer do you have after upgrading?




    composer -V shows




    Composer version 1.5.2 2017-09-11 16:59:25











    share|improve this question


























      0












      0








      0








      I'm trying to upgrade to Magento 2.3.1 and I'm running into a problem. I was on PHP 7.1.3 and noticed in the system requirements that it requires 7.1.3 and 7.2.X. We've upgraded the server PHP version to 7.2.16.



      Running composer update after doing the other steps brings up this error:



      [user@machine public_html]$ composer update
      Loading composer repositories with package information
      Updating dependencies (including require-dev)
      Package operations: 138 installs, 163 updates, 0 removals
      - Installing magento/inventory-composer-installer (1.1.0): Loading from cache

      Warning: Unsupported declare 'strict_types' in /home/site/public_html/vendor/magento/inventory-composer-installer/src/Plugin.php on line 6

      Parse error: syntax error, unexpected ':', expecting ';' or '{' in /home/site/public_html/vendor/magento/inventory-composer-installer/src/Plugin.php on line 55


      Running $ php -v returns this info:



      [user@machine public_html]$ php -v
      PHP 7.2.16 (cli) (built: Mar 25 2019 18:26:43) ( NTS )
      Copyright (c) 1997-2018 The PHP Group
      Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies


      and in my composer.json I have:



      ... etc ...
      "config":
      "platform":
      "php": "7.2.16"
      ,
      "use-include-path": true
      ,
      ... etc ...


      I've scoured the internet and it all leads back to upgrade PHP version - which ... it is. What step am I missing?



      edit



      question replies




      Are you following the steps outlined in the Magento DevDocs or another resource? - Did you update using the Magento script at https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html#upgrade-cli-script?




      following the steps for manual CLI upgrade.




      Do you have a cache storage system like Redis or Memcached that needs to be cleared?




      Nope.




      Do you have any other errors if you disable the inventory-composer-installer module?




      nope.




      Are you upgrading php-fpm?




      Not using it.




      What version of Composer do you have after upgrading?




      composer -V shows




      Composer version 1.5.2 2017-09-11 16:59:25











      share|improve this question
















      I'm trying to upgrade to Magento 2.3.1 and I'm running into a problem. I was on PHP 7.1.3 and noticed in the system requirements that it requires 7.1.3 and 7.2.X. We've upgraded the server PHP version to 7.2.16.



      Running composer update after doing the other steps brings up this error:



      [user@machine public_html]$ composer update
      Loading composer repositories with package information
      Updating dependencies (including require-dev)
      Package operations: 138 installs, 163 updates, 0 removals
      - Installing magento/inventory-composer-installer (1.1.0): Loading from cache

      Warning: Unsupported declare 'strict_types' in /home/site/public_html/vendor/magento/inventory-composer-installer/src/Plugin.php on line 6

      Parse error: syntax error, unexpected ':', expecting ';' or '{' in /home/site/public_html/vendor/magento/inventory-composer-installer/src/Plugin.php on line 55


      Running $ php -v returns this info:



      [user@machine public_html]$ php -v
      PHP 7.2.16 (cli) (built: Mar 25 2019 18:26:43) ( NTS )
      Copyright (c) 1997-2018 The PHP Group
      Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies


      and in my composer.json I have:



      ... etc ...
      "config":
      "platform":
      "php": "7.2.16"
      ,
      "use-include-path": true
      ,
      ... etc ...


      I've scoured the internet and it all leads back to upgrade PHP version - which ... it is. What step am I missing?



      edit



      question replies




      Are you following the steps outlined in the Magento DevDocs or another resource? - Did you update using the Magento script at https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html#upgrade-cli-script?




      following the steps for manual CLI upgrade.




      Do you have a cache storage system like Redis or Memcached that needs to be cleared?




      Nope.




      Do you have any other errors if you disable the inventory-composer-installer module?




      nope.




      Are you upgrading php-fpm?




      Not using it.




      What version of Composer do you have after upgrading?




      composer -V shows




      Composer version 1.5.2 2017-09-11 16:59:25








      upgrade magento2.3 composer magento-upgrade






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 2 days ago







      treyBake

















      asked 2 days ago









      treyBaketreyBake

      120118




      120118




















          1 Answer
          1






          active

          oldest

          votes


















          0














          Updates:



          Does it show any other PHP versions if you run?
          sudo update-alternatives --display php

          If, so then try to set PHP manually or via a command:
          sudo update-alternatives --set php /usr/bin/php7.2

          or sudo update-alternatives --config php


          How about trying to run something like?
          php7.2 /path/to/composer upgrade



          End updates



          Here are a couple of troubleshooting questions that may help get you in the right direction or get more info to help you further:



          Are you following the steps outlined in the Magento DevDocs or another resource?
          - Did you update using the Magento script at https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html#upgrade-cli-script?



          Do you have a cache storage system like Redis or Memcached that needs to be cleared?



          Do you have any other errors if you disable the inventory-composer-installer module?



          Are you upgrading php-fpm?



          What version of Composer do you have after upgrading?



          Good Luck, these are some of the pain points that I had while upgrading and I hope you can get it sorted out soon.






          share|improve this answer

























          • see my q edit :)

            – treyBake
            2 days ago











          • Thanks for more info. I made some updates to my post as well. What hosting environment are you using?

            – Mike Dubs
            2 days ago











          • there are a range of others version - but, everything in WHM and cli shows php7.2 - and the php7.2 /path/to/composer upgrade returns Could not open input file: /home/virtfs/site/usr/local/bin/composer

            – treyBake
            2 days ago











          • Several Stack sites point to PHP version. Is there a way to confirm PHP version through WHM like: Home »Software »MultiPHP Manager»System PHP Version click edit button and choose PHP 7.2 Maybe try chatting with host support to see if they have to make any manual changes on their end. I've seen this on BlueHost before

            – Mike Dubs
            2 days ago











          • Yeah it says PHP7.2 and doing php -v in CLI shows version 7.2.16 - host upgraded version this morning - but the error was happening before and after update

            – treyBake
            2 days ago











          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%2f268205%2fmagento-2-3-upgrade-issue%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          Updates:



          Does it show any other PHP versions if you run?
          sudo update-alternatives --display php

          If, so then try to set PHP manually or via a command:
          sudo update-alternatives --set php /usr/bin/php7.2

          or sudo update-alternatives --config php


          How about trying to run something like?
          php7.2 /path/to/composer upgrade



          End updates



          Here are a couple of troubleshooting questions that may help get you in the right direction or get more info to help you further:



          Are you following the steps outlined in the Magento DevDocs or another resource?
          - Did you update using the Magento script at https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html#upgrade-cli-script?



          Do you have a cache storage system like Redis or Memcached that needs to be cleared?



          Do you have any other errors if you disable the inventory-composer-installer module?



          Are you upgrading php-fpm?



          What version of Composer do you have after upgrading?



          Good Luck, these are some of the pain points that I had while upgrading and I hope you can get it sorted out soon.






          share|improve this answer

























          • see my q edit :)

            – treyBake
            2 days ago











          • Thanks for more info. I made some updates to my post as well. What hosting environment are you using?

            – Mike Dubs
            2 days ago











          • there are a range of others version - but, everything in WHM and cli shows php7.2 - and the php7.2 /path/to/composer upgrade returns Could not open input file: /home/virtfs/site/usr/local/bin/composer

            – treyBake
            2 days ago











          • Several Stack sites point to PHP version. Is there a way to confirm PHP version through WHM like: Home »Software »MultiPHP Manager»System PHP Version click edit button and choose PHP 7.2 Maybe try chatting with host support to see if they have to make any manual changes on their end. I've seen this on BlueHost before

            – Mike Dubs
            2 days ago











          • Yeah it says PHP7.2 and doing php -v in CLI shows version 7.2.16 - host upgraded version this morning - but the error was happening before and after update

            – treyBake
            2 days ago















          0














          Updates:



          Does it show any other PHP versions if you run?
          sudo update-alternatives --display php

          If, so then try to set PHP manually or via a command:
          sudo update-alternatives --set php /usr/bin/php7.2

          or sudo update-alternatives --config php


          How about trying to run something like?
          php7.2 /path/to/composer upgrade



          End updates



          Here are a couple of troubleshooting questions that may help get you in the right direction or get more info to help you further:



          Are you following the steps outlined in the Magento DevDocs or another resource?
          - Did you update using the Magento script at https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html#upgrade-cli-script?



          Do you have a cache storage system like Redis or Memcached that needs to be cleared?



          Do you have any other errors if you disable the inventory-composer-installer module?



          Are you upgrading php-fpm?



          What version of Composer do you have after upgrading?



          Good Luck, these are some of the pain points that I had while upgrading and I hope you can get it sorted out soon.






          share|improve this answer

























          • see my q edit :)

            – treyBake
            2 days ago











          • Thanks for more info. I made some updates to my post as well. What hosting environment are you using?

            – Mike Dubs
            2 days ago











          • there are a range of others version - but, everything in WHM and cli shows php7.2 - and the php7.2 /path/to/composer upgrade returns Could not open input file: /home/virtfs/site/usr/local/bin/composer

            – treyBake
            2 days ago











          • Several Stack sites point to PHP version. Is there a way to confirm PHP version through WHM like: Home »Software »MultiPHP Manager»System PHP Version click edit button and choose PHP 7.2 Maybe try chatting with host support to see if they have to make any manual changes on their end. I've seen this on BlueHost before

            – Mike Dubs
            2 days ago











          • Yeah it says PHP7.2 and doing php -v in CLI shows version 7.2.16 - host upgraded version this morning - but the error was happening before and after update

            – treyBake
            2 days ago













          0












          0








          0







          Updates:



          Does it show any other PHP versions if you run?
          sudo update-alternatives --display php

          If, so then try to set PHP manually or via a command:
          sudo update-alternatives --set php /usr/bin/php7.2

          or sudo update-alternatives --config php


          How about trying to run something like?
          php7.2 /path/to/composer upgrade



          End updates



          Here are a couple of troubleshooting questions that may help get you in the right direction or get more info to help you further:



          Are you following the steps outlined in the Magento DevDocs or another resource?
          - Did you update using the Magento script at https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html#upgrade-cli-script?



          Do you have a cache storage system like Redis or Memcached that needs to be cleared?



          Do you have any other errors if you disable the inventory-composer-installer module?



          Are you upgrading php-fpm?



          What version of Composer do you have after upgrading?



          Good Luck, these are some of the pain points that I had while upgrading and I hope you can get it sorted out soon.






          share|improve this answer















          Updates:



          Does it show any other PHP versions if you run?
          sudo update-alternatives --display php

          If, so then try to set PHP manually or via a command:
          sudo update-alternatives --set php /usr/bin/php7.2

          or sudo update-alternatives --config php


          How about trying to run something like?
          php7.2 /path/to/composer upgrade



          End updates



          Here are a couple of troubleshooting questions that may help get you in the right direction or get more info to help you further:



          Are you following the steps outlined in the Magento DevDocs or another resource?
          - Did you update using the Magento script at https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html#upgrade-cli-script?



          Do you have a cache storage system like Redis or Memcached that needs to be cleared?



          Do you have any other errors if you disable the inventory-composer-installer module?



          Are you upgrading php-fpm?



          What version of Composer do you have after upgrading?



          Good Luck, these are some of the pain points that I had while upgrading and I hope you can get it sorted out soon.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 2 days ago

























          answered 2 days ago









          Mike DubsMike Dubs

          316




          316












          • see my q edit :)

            – treyBake
            2 days ago











          • Thanks for more info. I made some updates to my post as well. What hosting environment are you using?

            – Mike Dubs
            2 days ago











          • there are a range of others version - but, everything in WHM and cli shows php7.2 - and the php7.2 /path/to/composer upgrade returns Could not open input file: /home/virtfs/site/usr/local/bin/composer

            – treyBake
            2 days ago











          • Several Stack sites point to PHP version. Is there a way to confirm PHP version through WHM like: Home »Software »MultiPHP Manager»System PHP Version click edit button and choose PHP 7.2 Maybe try chatting with host support to see if they have to make any manual changes on their end. I've seen this on BlueHost before

            – Mike Dubs
            2 days ago











          • Yeah it says PHP7.2 and doing php -v in CLI shows version 7.2.16 - host upgraded version this morning - but the error was happening before and after update

            – treyBake
            2 days ago

















          • see my q edit :)

            – treyBake
            2 days ago











          • Thanks for more info. I made some updates to my post as well. What hosting environment are you using?

            – Mike Dubs
            2 days ago











          • there are a range of others version - but, everything in WHM and cli shows php7.2 - and the php7.2 /path/to/composer upgrade returns Could not open input file: /home/virtfs/site/usr/local/bin/composer

            – treyBake
            2 days ago











          • Several Stack sites point to PHP version. Is there a way to confirm PHP version through WHM like: Home »Software »MultiPHP Manager»System PHP Version click edit button and choose PHP 7.2 Maybe try chatting with host support to see if they have to make any manual changes on their end. I've seen this on BlueHost before

            – Mike Dubs
            2 days ago











          • Yeah it says PHP7.2 and doing php -v in CLI shows version 7.2.16 - host upgraded version this morning - but the error was happening before and after update

            – treyBake
            2 days ago
















          see my q edit :)

          – treyBake
          2 days ago





          see my q edit :)

          – treyBake
          2 days ago













          Thanks for more info. I made some updates to my post as well. What hosting environment are you using?

          – Mike Dubs
          2 days ago





          Thanks for more info. I made some updates to my post as well. What hosting environment are you using?

          – Mike Dubs
          2 days ago













          there are a range of others version - but, everything in WHM and cli shows php7.2 - and the php7.2 /path/to/composer upgrade returns Could not open input file: /home/virtfs/site/usr/local/bin/composer

          – treyBake
          2 days ago





          there are a range of others version - but, everything in WHM and cli shows php7.2 - and the php7.2 /path/to/composer upgrade returns Could not open input file: /home/virtfs/site/usr/local/bin/composer

          – treyBake
          2 days ago













          Several Stack sites point to PHP version. Is there a way to confirm PHP version through WHM like: Home »Software »MultiPHP Manager»System PHP Version click edit button and choose PHP 7.2 Maybe try chatting with host support to see if they have to make any manual changes on their end. I've seen this on BlueHost before

          – Mike Dubs
          2 days ago





          Several Stack sites point to PHP version. Is there a way to confirm PHP version through WHM like: Home »Software »MultiPHP Manager»System PHP Version click edit button and choose PHP 7.2 Maybe try chatting with host support to see if they have to make any manual changes on their end. I've seen this on BlueHost before

          – Mike Dubs
          2 days ago













          Yeah it says PHP7.2 and doing php -v in CLI shows version 7.2.16 - host upgraded version this morning - but the error was happening before and after update

          – treyBake
          2 days ago





          Yeah it says PHP7.2 and doing php -v in CLI shows version 7.2.16 - host upgraded version this morning - but the error was happening before and after update

          – treyBake
          2 days ago

















          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%2f268205%2fmagento-2-3-upgrade-issue%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

          Sum ergo cogito? 1 nng

          三茅街道4182Guuntc Dn precexpngmageondP