Setup Issue on New Installation Magento 2.3.3 #26465

afavata · 2020-01-21T01:23:36Z

Environment
Ubuntu 18.04.3 LTS
Apache/2.4.29 (Ubuntu)
PHP 7.3.13
mysql Ver 8.0.19

I installed all the source file for Magento 2.3.3 using composer command.
Composer command ended with no issue
Configured apache2 host server and PHP
Configured mysql and created a new database DbMagento
Accessed through Browser to Magento Setup
Filled all the information requested and reached the last step:
1 - Readiness Check = no issue
2 - Add a Database = no issue
3 - Web Configuration = no issue
4 - Customize your store = no issue
5 - Create Admin Account = no issue
6 - install = ISSUE

During the last step "6" relating to install ... system performs initial installation and then stops ... see console Log herewith

`Starting Magento installation:
File permissions check...

Required extensions check...

Enabling Maintenance Mode...

Installing deployment configuration...

Installing database schema:
Schema creation/updates:
Module 'Magento_AdminAnalytics':

Module 'Magento_Store':

Module 'Magento_AdvancedPricingImportExport':

Module 'Magento_Directory':

Module 'Magento_Amqp':

Module 'Magento_AmqpStore':

Module 'Magento_Config':

Module 'Magento_Theme':

Module 'Magento_Backend':

Module 'Magento_Variable':

Module 'Magento_Eav':

Module 'Magento_Customer':

Module 'Magento_AuthorizenetGraphQl':

Module 'Magento_Search':

Module 'Magento_Backup':

Module 'Magento_AdminNotification':

Module 'Magento_BraintreeGraphQl':

Module 'Magento_Indexer':

Module 'Magento_Authorization':

Module 'Magento_BundleImportExport':

Module 'Magento_CacheInvalidate':

Module 'Magento_Cms':

Module 'Magento_Catalog':
[ERROR] Magento\Framework\Setup\Exception: Unable to apply patch Magento\Catalog\Setup\Patch\Schema\EnableSegmentation for module Magento_Catalog. Original exception message: Invalid column data type "" in /var/www/magento/vendor/magento/framework/Setup/Patch/PatchApplier.php:241
Stack trace:
#0 /var/www/magento/setup/src/Magento/Setup/Model/Installer.php(1004): Magento\Framework\Setup\Patch\PatchApplier->applySchemaPatch('Magento_Catalog')
#1 /var/www/magento/setup/src/Magento/Setup/Model/Installer.php(832): Magento\Setup\Model\Installer->handleDBSchemaData(Object(Magento\Setup\Module\Setup), 'schema', Array)
#2 [internal function]: Magento\Setup\Model\Installer->installSchema(Array)
#3 /var/www/magento/setup/src/Magento/Setup/Model/Installer.php(367): call_user_func_array(Array, Array)
#4 /var/www/magento/setup/src/Magento/Setup/Controller/Install.php(109): Magento\Setup\Model\Installer->install(Array)
#5 /var/www/magento/vendor/zendframework/zend-mvc/src/Controller/AbstractActionController.php(84): Magento\Setup\Controller\Install->startAction()
#6 /var/www/magento/vendor/zendframework/zend-eventmanager/src/EventManager.php(322): Zend\Mvc\Controller\AbstractActionController->onDispatch(Object(Zend\Mvc\MvcEvent))
#7 /var/www/magento/vendor/zendframework/zend-eventmanager/src/EventManager.php(179): Zend\EventManager\EventManager->triggerListeners(Object(Zend\Mvc\MvcEvent), Object(Closure))
#8 /var/www/magento/vendor/zendframework/zend-mvc/src/Controller/AbstractController.php(116): Zend\EventManager\EventManager->triggerEventUntil(Object(Closure), Object(Zend\Mvc\MvcEvent))
#9 /var/www/magento/vendor/zendframework/zend-mvc/src/DispatchListener.php(118): Zend\Mvc\Controller\AbstractController->dispatch(Object(Zend\Http\PhpEnvironment\Request), Object(Zend\Http\PhpEnvironment\Response))
#10 /var/www/magento/vendor/zendframework/zend-eventmanager/src/EventManager.php(322): Zend\Mvc\DispatchListener->onDispatch(Object(Zend\Mvc\MvcEvent))
#11 /var/www/magento/vendor/zendframework/zend-eventmanager/src/EventManager.php(179): Zend\EventManager\EventManager->triggerListeners(Object(Zend\Mvc\MvcEvent), Object(Closure))
#12 /var/www/magento/vendor/zendframework/zend-mvc/src/Application.php(340): Zend\EventManager\EventManager->triggerEventUntil(Object(Closure), Object(Zend\Mvc\MvcEvent))
#13 /var/www/magento/setup/index.php(39): Zend\Mvc\Application->run()
#14 {main}`

The text was updated successfully, but these errors were encountered:

m2-assistant · 2020-01-21T01:23:39Z

Hi @afavata. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

Summary of the issue
Information on your environment
Steps to reproduce
Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@afavata do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

yes
no

Join Magento Community Engineering Slack and ask your questions in #github channel.

afavata · 2020-01-21T14:27:12Z

Any fast workaround to resolve this issue?

m2-assistant · 2020-01-22T12:07:37Z

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
Details
If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
4. Verify that the issue is reproducible on 2.4-develop branch
Details
- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
5. Add label Issue: Confirmed once verification is complete.
6. Make sure that automatic system confirms that report has been added to the backlog.

engcom-Hotel · 2020-01-22T12:11:50Z

Hello @afavata
The problem is your MySql version, Magento 2.3.3 supports only MySql 5.6, 5.7.

You can read more about Magento technology stack requirements here.

So i have to close this issue.

Thanks for your report and collaboration!

LucasMali · 2020-01-25T15:55:37Z

Hello @afavata
The problem is your MySql version, Magento 2.3.3 supports only MySql 5.6, 5.7.

You can read more about Magento technology stack requirements here.

So i have to close this issue.

Thanks for your report and collaboration!

I have mysql Ver 15.1 Distrib 10.2.30-MariaDB, for osx10.15 (x86_64) using readline 5.1 and I'm still seeing this error.

Tried with mysql Ver 14.14 Distrib 5.7.29, for osx10.15 (x86_64) using EditLine wrapper and still seeing the error.

LucasMali · 2020-01-25T15:57:40Z

Environment
Ubuntu 18.04.3 LTS
Apache/2.4.29 (Ubuntu)
PHP 7.3.13
mysql Ver 8.0.19

I installed all the source file for Magento 2.3.3 using composer command.
Composer command ended with no issue
Configured apache2 host server and PHP
Configured mysql and created a new database DbMagento
Accessed through Browser to Magento Setup
Filled all the information requested and reached the last step:
1 - Readiness Check = no issue
2 - Add a Database = no issue
3 - Web Configuration = no issue
4 - Customize your store = no issue
5 - Create Admin Account = no issue
6 - install = ISSUE

During the last step "6" relating to install ... system performs initial installation and then stops ... see console Log herewith

`Starting Magento installation:
File permissions check...

Required extensions check...

Enabling Maintenance Mode...

Installing deployment configuration...

Installing database schema:
Schema creation/updates:
Module 'Magento_AdminAnalytics':

Module 'Magento_Store':

Module 'Magento_AdvancedPricingImportExport':

Module 'Magento_Directory':

Module 'Magento_Amqp':

Module 'Magento_AmqpStore':

Module 'Magento_Config':

Module 'Magento_Theme':

Module 'Magento_Backend':

Module 'Magento_Variable':

Module 'Magento_Eav':

Module 'Magento_Customer':

Module 'Magento_AuthorizenetGraphQl':

Module 'Magento_Search':

Module 'Magento_Backup':

Module 'Magento_AdminNotification':

Module 'Magento_BraintreeGraphQl':

Module 'Magento_Indexer':

Module 'Magento_Authorization':

Module 'Magento_BundleImportExport':

Module 'Magento_CacheInvalidate':

Module 'Magento_Cms':

Module 'Magento_Catalog':
[ERROR] Magento\Framework\Setup\Exception: Unable to apply patch Magento\Catalog\Setup\Patch\Schema\EnableSegmentation for module Magento_Catalog. Original exception message: Invalid column data type "" in /var/www/magento/vendor/magento/framework/Setup/Patch/PatchApplier.php:241
Stack trace:
#0 /var/www/magento/setup/src/Magento/Setup/Model/Installer.php(1004): Magento\Framework\Setup\Patch\PatchApplier->applySchemaPatch('Magento_Catalog')
#1 /var/www/magento/setup/src/Magento/Setup/Model/Installer.php(832): Magento\Setup\Model\Installer->handleDBSchemaData(Object(Magento\Setup\Module\Setup), 'schema', Array)
#2 [internal function]: Magento\Setup\Model\Installer->installSchema(Array)
#3 /var/www/magento/setup/src/Magento/Setup/Model/Installer.php(367): call_user_func_array(Array, Array)
#4 /var/www/magento/setup/src/Magento/Setup/Controller/Install.php(109): Magento\Setup\Model\Installer->install(Array)
#5 /var/www/magento/vendor/zendframework/zend-mvc/src/Controller/AbstractActionController.php(84): Magento\Setup\Controller\Install->startAction()
#6 /var/www/magento/vendor/zendframework/zend-eventmanager/src/EventManager.php(322): Zend\Mvc\Controller\AbstractActionController->onDispatch(Object(Zend\Mvc\MvcEvent))
#7 /var/www/magento/vendor/zendframework/zend-eventmanager/src/EventManager.php(179): Zend\EventManager\EventManager->triggerListeners(Object(Zend\Mvc\MvcEvent), Object(Closure))
#8 /var/www/magento/vendor/zendframework/zend-mvc/src/Controller/AbstractController.php(116): Zend\EventManager\EventManager->triggerEventUntil(Object(Closure), Object(Zend\Mvc\MvcEvent))
#9 /var/www/magento/vendor/zendframework/zend-mvc/src/DispatchListener.php(118): Zend\Mvc\Controller\AbstractController->dispatch(Object(Zend\Http\PhpEnvironment\Request), Object(Zend\Http\PhpEnvironment\Response))
#10 /var/www/magento/vendor/zendframework/zend-eventmanager/src/EventManager.php(322): Zend\Mvc\DispatchListener->onDispatch(Object(Zend\Mvc\MvcEvent))
#11 /var/www/magento/vendor/zendframework/zend-eventmanager/src/EventManager.php(179): Zend\EventManager\EventManager->triggerListeners(Object(Zend\Mvc\MvcEvent), Object(Closure))
#12 /var/www/magento/vendor/zendframework/zend-mvc/src/Application.php(340): Zend\EventManager\EventManager->triggerEventUntil(Object(Closure), Object(Zend\Mvc\MvcEvent))
#13 /var/www/magento/setup/index.php(39): Zend\Mvc\Application->run()
#14 {main}`

Did you ever find a fix for this?

metalleg · 2020-01-28T18:16:41Z

Also running into this issue.

Clean M2.3.3 installation onto macOS Catalina.
php 7.1.3.3
mySql 5.7.29

afavata · 2020-01-29T09:48:15Z

Hello @LucasMaliszewski
thanks for the info...
I'm trying to downgrade MySQL from 8.0 to 5.7 but MySQL is giving many errors and doesn't start

engcom-Hotel · 2020-01-29T09:59:26Z

@metalleg @afavata
Magento 2 is not supported on MacOS:

afavata · 2020-01-29T11:23:36Z

Hello @engcom-Hotel

I'm not running Magento on Windows or MAC...
It is installed on Ubuntu 18.04

thanks

engcom-Hotel · 2020-01-29T11:31:59Z

@afavata but your mySql version is wrong

afavata · 2020-01-29T11:52:29Z

yes... You are right.... Mysql is wrong ... I'm trying to downgrade it but It's painful

metalleg · 2020-01-29T22:21:49Z

Really good eye - didn't even consider that compatibility based on guides I'd read. I'm operating through MAMP as an intermediary and all is well. Thank you!

Edit: Nope, ultimately ran into the same issue when trying to run setup:upgrade. Magento installed and ran fine but the magento commands are a no go. Perhaps it is just macOS.

nik4152 · 2020-02-02T18:03:44Z

Hi @afavata @LucasMaliszewski
you can add the code in file
vendor/magento/framework/DB/Adapter/Pdo/Mysql.php
line 1846
after line
case 'smallint':
add
case 'smallint unsigned':
and
after line
case 'int':
add
"case 'int unsigned':"

or full method code

    protected function _getColumnTypeByDdl($column)
    {
        switch ($column['DATA_TYPE']) {
            case 'bool':
                return Table::TYPE_BOOLEAN;
            case 'tinytext':
            case 'char':
            case 'varchar':
            case 'text':
            case 'mediumtext':
            case 'longtext':
                return Table::TYPE_TEXT;
            case 'blob':
            case 'mediumblob':
            case 'longblob':
                return Table::TYPE_BLOB;
            case 'tinyint':
            case 'smallint':
            case 'smallint unsigned':
                return Table::TYPE_SMALLINT;
            case 'mediumint':
            case 'int':
            case 'int unsigned':
                return Table::TYPE_INTEGER;
            case 'bigint':
                return Table::TYPE_BIGINT;
            case 'datetime':
                return Table::TYPE_DATETIME;
            case 'timestamp':
                return Table::TYPE_TIMESTAMP;
            case 'date':
                return Table::TYPE_DATE;
            case 'float':
                return Table::TYPE_FLOAT;
            case 'decimal':
            case 'numeric':
                return Table::TYPE_DECIMAL;
        }
    }

Please let me know if works

alex-vk · 2020-02-08T00:00:42Z

@nik4152 , your solution helped, thanks a lot.
Next the installation process may generate additional errors. In my case it was something like "You do not have the SUPER privilege and binary logging is enabled", so, the best solution is to downgrade mysql version.

kunjesh · 2020-03-22T09:11:53Z

Hello @afavata
I had installed mysql version 8.0.x and the same issue I have faced. But when I uninstalled mysql 8.0.x and reinstalled mysql version 5.7.28, than patch was easily installed. So its an issue with mysql version.

djbolya · 2020-04-13T13:04:05Z

Hi @afavata @LucasMaliszewski
you can add the code in file
vendor/magento/framework/DB/Adapter/Pdo/Mysql.php
line 1846
after line
case 'smallint':
add
case 'smallint unsigned':
and
after line
case 'int':
add
"case 'int unsigned':"

or full method code

    protected function _getColumnTypeByDdl($column)
    {
        switch ($column['DATA_TYPE']) {
            case 'bool':
                return Table::TYPE_BOOLEAN;
            case 'tinytext':
            case 'char':
            case 'varchar':
            case 'text':
            case 'mediumtext':
            case 'longtext':
                return Table::TYPE_TEXT;
            case 'blob':
            case 'mediumblob':
            case 'longblob':
                return Table::TYPE_BLOB;
            case 'tinyint':
            case 'smallint':
            case 'smallint unsigned':
                return Table::TYPE_SMALLINT;
            case 'mediumint':
            case 'int':
            case 'int unsigned':
                return Table::TYPE_INTEGER;
            case 'bigint':
                return Table::TYPE_BIGINT;
            case 'datetime':
                return Table::TYPE_DATETIME;
            case 'timestamp':
                return Table::TYPE_TIMESTAMP;
            case 'date':
                return Table::TYPE_DATE;
            case 'float':
                return Table::TYPE_FLOAT;
            case 'decimal':
            case 'numeric':
                return Table::TYPE_DECIMAL;
        }
    }

Please let me know if works

Thanks a lot!

lasdou · 2020-04-30T13:48:12Z

Hi all,

Is there a PR to push the @nik4152 suggested and confirmed correction on the current magento version ?

djbolya · 2020-04-30T13:52:24Z

I think that this was very helpful

nackie99 · 2020-05-16T18:25:24Z

When you get to this error "You do not have the SUPER privilege and binary logging is enabled", you can fix it by:

mysql -u root_USERNAME -p
set global log_bin_trust_function_creators=1;

Install seems to have finished on Mysql 8, no idea if thee will be problems down the line though

magento-engcom-team added the Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed label Jan 21, 2020

engcom-Hotel self-assigned this Jan 22, 2020

engcom-Hotel closed this as completed Jan 22, 2020

gz-devops mentioned this issue Mar 24, 2020

Hello! nik4152/nik4152#1

Closed

sdzhepa added the Progress: done label Mar 26, 2020

magento-engcom-team added the Reported on 2.3.3 Indicates original Magento version for the Issue report. label Nov 13, 2020

This issue was closed.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Setup Issue on New Installation Magento 2.3.3 #26465

Setup Issue on New Installation Magento 2.3.3 #26465

afavata commented Jan 21, 2020 •

edited

Loading

m2-assistant bot commented Jan 21, 2020

afavata commented Jan 21, 2020

m2-assistant bot commented Jan 22, 2020

engcom-Hotel commented Jan 22, 2020

LucasMali commented Jan 25, 2020 •

edited

Loading

LucasMali commented Jan 25, 2020

metalleg commented Jan 28, 2020

afavata commented Jan 29, 2020

engcom-Hotel commented Jan 29, 2020

afavata commented Jan 29, 2020

engcom-Hotel commented Jan 29, 2020

afavata commented Jan 29, 2020

metalleg commented Jan 29, 2020 •

edited

Loading

nik4152 commented Feb 2, 2020

alex-vk commented Feb 8, 2020

kunjesh commented Mar 22, 2020

djbolya commented Apr 13, 2020

lasdou commented Apr 30, 2020

djbolya commented Apr 30, 2020

nackie99 commented May 16, 2020

Setup Issue on New Installation Magento 2.3.3 #26465

Setup Issue on New Installation Magento 2.3.3 #26465

Comments

afavata commented Jan 21, 2020 • edited Loading

m2-assistant bot commented Jan 21, 2020

afavata commented Jan 21, 2020

m2-assistant bot commented Jan 22, 2020

engcom-Hotel commented Jan 22, 2020

LucasMali commented Jan 25, 2020 • edited Loading

LucasMali commented Jan 25, 2020

metalleg commented Jan 28, 2020

afavata commented Jan 29, 2020

engcom-Hotel commented Jan 29, 2020

afavata commented Jan 29, 2020

engcom-Hotel commented Jan 29, 2020

afavata commented Jan 29, 2020

metalleg commented Jan 29, 2020 • edited Loading

nik4152 commented Feb 2, 2020

alex-vk commented Feb 8, 2020

kunjesh commented Mar 22, 2020

djbolya commented Apr 13, 2020

lasdou commented Apr 30, 2020

djbolya commented Apr 30, 2020

nackie99 commented May 16, 2020

afavata commented Jan 21, 2020 •

edited

Loading

LucasMali commented Jan 25, 2020 •

edited

Loading

metalleg commented Jan 29, 2020 •

edited

Loading