Magento2: Magento 2.2.0 CLI commands not working on PHP 7.1.9

Created on 28 Sep 2017  路  10Comments  路  Source: magento/magento2

Preconditions

Magento v2.2.0
PHP 7.1.9

Steps to reproduce

  1. Update source file with Magento 2.2.0
  2. Install PHP 7.1.9 on server
  3. Run Magento command to upgrade: php bin/magento setup:upgrade
  4. Try other Magento commands: php bin/magento indexer:reindex, php bin/magento cache:flush

Expected Result:

  1. System should start upgrading Magento 2.2.0
  2. Indexer should reindex

Actual result

  1. Nothing happens

image

Format is valid needs update

Most helpful comment

Looks like an issue with your environment.

Try to enable display_errors https://github.com/magento/magento2/blob/2.2-develop/app/bootstrap.php#L11 to see what is actually happening.

All 10 comments

Looks like an issue with your environment.

Try to enable display_errors https://github.com/magento/magento2/blob/2.2-develop/app/bootstrap.php#L11 to see what is actually happening.

does other php commands ex.php -v gives you a result ?

Thanks @orlangur. The environment was not displaying errors so I was unable to see what was the issue.
By displaying the error I found issue and was able to fix. Thanks

However upgrade failed with error message:
Upgrading data.. Warning: SessionHandler::read(): open(tcp://localhost:11211/sess_32ed440814b6bdd8ec417334d5f28ee6, O_RDWR) failed: No such file or directory (2) in dev/vendor/magento/framework/Session/SaveHandler/Native.php on line 22

I did not configure to use memcache. What is cause of this error?

Fixed by commenting out session.save.handler in memcache.ini

Thanks all

1 exception(s):
Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'referenceBlock', attribute 'ifconfig': The attribute 'ifconfig' is not allowed.
Line: 682

Can you assist with this issue as well?

@msawyers see https://github.com/magento/magento2/issues/11116#issuecomment-332877310, layout declarations shall correspond to XSD schema - most likely such ifconfig worked only for <block declaration anyway.

Could you please close this issue and report a new one if you meet any Magento bug?

Was this page helpful?
0 / 5 - 0 ratings