Magento 2 MySQL server has gone awayIndex error after upgrade to EE 1.14.2.0: table...

Violin - Can double stops be played when the strings are not next to each other?

How to explain that I do not want to visit a country due to personal safety concern?

et qui - how do you really understand that kind of phraseology?

Is there a place to find the pricing for things not mentioned in the PHB? (non-magical)

Is it insecure to send a password in a `curl` command?

How to terminate ping <dest> &

How to pronounce "I ♥ Huckabees"?

Why one should not leave fingerprints on bulbs and plugs?

Why does a Star of David appear at a rally with Francisco Franco?

Have the tides ever turned twice on any open problem?

Why does energy conservation give me the wrong answer in this inelastic collision problem?

How to deal with taxi scam when on vacation?

Recruiter wants very extensive technical details about all of my previous work

A single argument pattern definition applies to multiple-argument patterns?

Is a party consisting of only a bard, a cleric, and a warlock functional long-term?

How do I change two letters closest to a string and one letter immediately after a string using Notepad++?

Employee lack of ownership

How are passwords stolen from companies if they only store hashes?

Shortcut for setting origin to vertex

Problem with FindRoot

Converting a variable frequency to TTL HIGH and LOW levels, based on a fixed (possible non-fixed?) frequency

Equivalents to the present tense

Is "upgrade" the right word to use in this context?

How to make healing in an exploration game interesting



Magento 2 MySQL server has gone away


Index error after upgrade to EE 1.14.2.0: table catalog_product_entity_tmp_indexer doesn't existMagento Installer - File Permission Check FailMagento 2 SQLSTATE[42S22]: while create product?Magento installation on live server is throwing errorMagento 2.2 : Cannot Add Subcategoryerror on magento 2 after update php 5 to 7, Warning: require(/var/www/html/vendor/magento/framework/registration.php):?Magento Setup on AWS server getting ErrorPDOException: SQLSTATE[HY000] [1698] Access denied for user 'root'@'localhost'Magento 2, Unable to save products (Catalog rule indexing failed. See details in exception log.)Getting error while adding category Magento2













0















I managed to migrate magento 1 to new magento 2.2.5
When I reindex for the first time I get in indexer




Category Products




[2019-02-07 21:58:57] main.CRITICAL: Warning: PDOStatement::execute(): MySQL server has gone away in /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Statement/Pdo.php on line 228 {"exception":"[object] (Exception(code: 0): Warning: PDOStatement::execute(): MySQL server has gone away in /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Statement/Pdo.php on line 228 at /var/www/html/vendor/magento/framework/App/ErrorHandler.php:61)"} []



mysql.conf settings are:




[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = localhost
#
# * Fine Tuning
#
key_buffer_size = 512M
max_allowed_packet = 1024M
thread_stack = 192K
thread_cache_size = 256
connect_timeout=320 # default 10
table_open_cache = 4096
table_definition_cache = 4096
sort_buffer_size = 16M
max_heap_table_size = 512M
tmp_table_size = 512M
interactive_timeout = 3600
max_connections = 400
max_connect_errors = 1000000
skip_name_resolve
#skip_secure_auth
wait_timeout = 28800
innodb_buffer_pool_size = 2G
myisam_sort_buffer_size = 128M
innodb_log_file_size = 256M
innodb_thread_concurrency = 18
innodb_flush_log_at_trx_commit = 2
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover-options = BACKUP
#max_connections = 100
#table_open_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 64M
query_cache_type = 1


Tried to increase the limits in mysql with no luck.
Any suggestions please?










share|improve this question

























  • what are your MySQL configuration parameters for wait_timeout, max_allowed_packet, tmp_table_size and max_heap_table_size?

    – HelgeB
    Feb 8 at 8:23











  • HelgeB I edited the post with my settings

    – G. G.
    Feb 8 at 8:28






  • 1





    Additional information request. Post on pastebin.com and share the links. RAM size of your MySQL Host server Text results of: B) SHOW GLOBAL STATUS; after minimum 24 hours UPTIME C) SHOW GLOBAL VARIABLES; D) SHOW FULL PROCESSLIST; E) complete MySQLTuner report AND Optional very helpful information, if available includes - htop OR top OR mytop for most active apps, ulimit -a for a linux/unix list of limits, iostat -xm 5 3 for IOPS by device and core/cpu count, df -h for a linux/unix free space list by device, for server tuning analysis.

    – Wilson Hauck
    Feb 28 at 1:16






  • 1





    Glad you are back together. Providing the information requested yesterday will allow meaningful suggestions to improve your system performance. Why are are you allowing hacker/cracker 1 million attempts to guess a password with the max_connect_errors at 1 million?

    – Wilson Hauck
    Feb 28 at 21:30








  • 1





    @G.G. With secondary review of your config, it looks like you accidentally have innodb_log_buffer_size much larger than innodb_log_file_size. The buffer should always be smaller than the log_file_size. Sorry I missed this earlier. Still willing to help with tuning, if SHOW GLOBAL STATUS; and SHOW GLOBAL VARIABLES; could be posted, even for DEV or PROD instance.

    – Wilson Hauck
    1 hour ago


















0















I managed to migrate magento 1 to new magento 2.2.5
When I reindex for the first time I get in indexer




Category Products




[2019-02-07 21:58:57] main.CRITICAL: Warning: PDOStatement::execute(): MySQL server has gone away in /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Statement/Pdo.php on line 228 {"exception":"[object] (Exception(code: 0): Warning: PDOStatement::execute(): MySQL server has gone away in /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Statement/Pdo.php on line 228 at /var/www/html/vendor/magento/framework/App/ErrorHandler.php:61)"} []



mysql.conf settings are:




[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = localhost
#
# * Fine Tuning
#
key_buffer_size = 512M
max_allowed_packet = 1024M
thread_stack = 192K
thread_cache_size = 256
connect_timeout=320 # default 10
table_open_cache = 4096
table_definition_cache = 4096
sort_buffer_size = 16M
max_heap_table_size = 512M
tmp_table_size = 512M
interactive_timeout = 3600
max_connections = 400
max_connect_errors = 1000000
skip_name_resolve
#skip_secure_auth
wait_timeout = 28800
innodb_buffer_pool_size = 2G
myisam_sort_buffer_size = 128M
innodb_log_file_size = 256M
innodb_thread_concurrency = 18
innodb_flush_log_at_trx_commit = 2
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover-options = BACKUP
#max_connections = 100
#table_open_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 64M
query_cache_type = 1


Tried to increase the limits in mysql with no luck.
Any suggestions please?










share|improve this question

























  • what are your MySQL configuration parameters for wait_timeout, max_allowed_packet, tmp_table_size and max_heap_table_size?

    – HelgeB
    Feb 8 at 8:23











  • HelgeB I edited the post with my settings

    – G. G.
    Feb 8 at 8:28






  • 1





    Additional information request. Post on pastebin.com and share the links. RAM size of your MySQL Host server Text results of: B) SHOW GLOBAL STATUS; after minimum 24 hours UPTIME C) SHOW GLOBAL VARIABLES; D) SHOW FULL PROCESSLIST; E) complete MySQLTuner report AND Optional very helpful information, if available includes - htop OR top OR mytop for most active apps, ulimit -a for a linux/unix list of limits, iostat -xm 5 3 for IOPS by device and core/cpu count, df -h for a linux/unix free space list by device, for server tuning analysis.

    – Wilson Hauck
    Feb 28 at 1:16






  • 1





    Glad you are back together. Providing the information requested yesterday will allow meaningful suggestions to improve your system performance. Why are are you allowing hacker/cracker 1 million attempts to guess a password with the max_connect_errors at 1 million?

    – Wilson Hauck
    Feb 28 at 21:30








  • 1





    @G.G. With secondary review of your config, it looks like you accidentally have innodb_log_buffer_size much larger than innodb_log_file_size. The buffer should always be smaller than the log_file_size. Sorry I missed this earlier. Still willing to help with tuning, if SHOW GLOBAL STATUS; and SHOW GLOBAL VARIABLES; could be posted, even for DEV or PROD instance.

    – Wilson Hauck
    1 hour ago
















0












0








0








I managed to migrate magento 1 to new magento 2.2.5
When I reindex for the first time I get in indexer




Category Products




[2019-02-07 21:58:57] main.CRITICAL: Warning: PDOStatement::execute(): MySQL server has gone away in /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Statement/Pdo.php on line 228 {"exception":"[object] (Exception(code: 0): Warning: PDOStatement::execute(): MySQL server has gone away in /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Statement/Pdo.php on line 228 at /var/www/html/vendor/magento/framework/App/ErrorHandler.php:61)"} []



mysql.conf settings are:




[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = localhost
#
# * Fine Tuning
#
key_buffer_size = 512M
max_allowed_packet = 1024M
thread_stack = 192K
thread_cache_size = 256
connect_timeout=320 # default 10
table_open_cache = 4096
table_definition_cache = 4096
sort_buffer_size = 16M
max_heap_table_size = 512M
tmp_table_size = 512M
interactive_timeout = 3600
max_connections = 400
max_connect_errors = 1000000
skip_name_resolve
#skip_secure_auth
wait_timeout = 28800
innodb_buffer_pool_size = 2G
myisam_sort_buffer_size = 128M
innodb_log_file_size = 256M
innodb_thread_concurrency = 18
innodb_flush_log_at_trx_commit = 2
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover-options = BACKUP
#max_connections = 100
#table_open_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 64M
query_cache_type = 1


Tried to increase the limits in mysql with no luck.
Any suggestions please?










share|improve this question
















I managed to migrate magento 1 to new magento 2.2.5
When I reindex for the first time I get in indexer




Category Products




[2019-02-07 21:58:57] main.CRITICAL: Warning: PDOStatement::execute(): MySQL server has gone away in /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Statement/Pdo.php on line 228 {"exception":"[object] (Exception(code: 0): Warning: PDOStatement::execute(): MySQL server has gone away in /var/www/html/vendor/magento/zendframework1/library/Zend/Db/Statement/Pdo.php on line 228 at /var/www/html/vendor/magento/framework/App/ErrorHandler.php:61)"} []



mysql.conf settings are:




[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = localhost
#
# * Fine Tuning
#
key_buffer_size = 512M
max_allowed_packet = 1024M
thread_stack = 192K
thread_cache_size = 256
connect_timeout=320 # default 10
table_open_cache = 4096
table_definition_cache = 4096
sort_buffer_size = 16M
max_heap_table_size = 512M
tmp_table_size = 512M
interactive_timeout = 3600
max_connections = 400
max_connect_errors = 1000000
skip_name_resolve
#skip_secure_auth
wait_timeout = 28800
innodb_buffer_pool_size = 2G
myisam_sort_buffer_size = 128M
innodb_log_file_size = 256M
innodb_thread_concurrency = 18
innodb_flush_log_at_trx_commit = 2
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover-options = BACKUP
#max_connections = 100
#table_open_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 64M
query_cache_type = 1


Tried to increase the limits in mysql with no luck.
Any suggestions please?







magento2 database reindex






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 8 at 8:28







G. G.

















asked Feb 8 at 7:58









G. G.G. G.

607




607













  • what are your MySQL configuration parameters for wait_timeout, max_allowed_packet, tmp_table_size and max_heap_table_size?

    – HelgeB
    Feb 8 at 8:23











  • HelgeB I edited the post with my settings

    – G. G.
    Feb 8 at 8:28






  • 1





    Additional information request. Post on pastebin.com and share the links. RAM size of your MySQL Host server Text results of: B) SHOW GLOBAL STATUS; after minimum 24 hours UPTIME C) SHOW GLOBAL VARIABLES; D) SHOW FULL PROCESSLIST; E) complete MySQLTuner report AND Optional very helpful information, if available includes - htop OR top OR mytop for most active apps, ulimit -a for a linux/unix list of limits, iostat -xm 5 3 for IOPS by device and core/cpu count, df -h for a linux/unix free space list by device, for server tuning analysis.

    – Wilson Hauck
    Feb 28 at 1:16






  • 1





    Glad you are back together. Providing the information requested yesterday will allow meaningful suggestions to improve your system performance. Why are are you allowing hacker/cracker 1 million attempts to guess a password with the max_connect_errors at 1 million?

    – Wilson Hauck
    Feb 28 at 21:30








  • 1





    @G.G. With secondary review of your config, it looks like you accidentally have innodb_log_buffer_size much larger than innodb_log_file_size. The buffer should always be smaller than the log_file_size. Sorry I missed this earlier. Still willing to help with tuning, if SHOW GLOBAL STATUS; and SHOW GLOBAL VARIABLES; could be posted, even for DEV or PROD instance.

    – Wilson Hauck
    1 hour ago





















  • what are your MySQL configuration parameters for wait_timeout, max_allowed_packet, tmp_table_size and max_heap_table_size?

    – HelgeB
    Feb 8 at 8:23











  • HelgeB I edited the post with my settings

    – G. G.
    Feb 8 at 8:28






  • 1





    Additional information request. Post on pastebin.com and share the links. RAM size of your MySQL Host server Text results of: B) SHOW GLOBAL STATUS; after minimum 24 hours UPTIME C) SHOW GLOBAL VARIABLES; D) SHOW FULL PROCESSLIST; E) complete MySQLTuner report AND Optional very helpful information, if available includes - htop OR top OR mytop for most active apps, ulimit -a for a linux/unix list of limits, iostat -xm 5 3 for IOPS by device and core/cpu count, df -h for a linux/unix free space list by device, for server tuning analysis.

    – Wilson Hauck
    Feb 28 at 1:16






  • 1





    Glad you are back together. Providing the information requested yesterday will allow meaningful suggestions to improve your system performance. Why are are you allowing hacker/cracker 1 million attempts to guess a password with the max_connect_errors at 1 million?

    – Wilson Hauck
    Feb 28 at 21:30








  • 1





    @G.G. With secondary review of your config, it looks like you accidentally have innodb_log_buffer_size much larger than innodb_log_file_size. The buffer should always be smaller than the log_file_size. Sorry I missed this earlier. Still willing to help with tuning, if SHOW GLOBAL STATUS; and SHOW GLOBAL VARIABLES; could be posted, even for DEV or PROD instance.

    – Wilson Hauck
    1 hour ago



















what are your MySQL configuration parameters for wait_timeout, max_allowed_packet, tmp_table_size and max_heap_table_size?

– HelgeB
Feb 8 at 8:23





what are your MySQL configuration parameters for wait_timeout, max_allowed_packet, tmp_table_size and max_heap_table_size?

– HelgeB
Feb 8 at 8:23













HelgeB I edited the post with my settings

– G. G.
Feb 8 at 8:28





HelgeB I edited the post with my settings

– G. G.
Feb 8 at 8:28




1




1





Additional information request. Post on pastebin.com and share the links. RAM size of your MySQL Host server Text results of: B) SHOW GLOBAL STATUS; after minimum 24 hours UPTIME C) SHOW GLOBAL VARIABLES; D) SHOW FULL PROCESSLIST; E) complete MySQLTuner report AND Optional very helpful information, if available includes - htop OR top OR mytop for most active apps, ulimit -a for a linux/unix list of limits, iostat -xm 5 3 for IOPS by device and core/cpu count, df -h for a linux/unix free space list by device, for server tuning analysis.

– Wilson Hauck
Feb 28 at 1:16





Additional information request. Post on pastebin.com and share the links. RAM size of your MySQL Host server Text results of: B) SHOW GLOBAL STATUS; after minimum 24 hours UPTIME C) SHOW GLOBAL VARIABLES; D) SHOW FULL PROCESSLIST; E) complete MySQLTuner report AND Optional very helpful information, if available includes - htop OR top OR mytop for most active apps, ulimit -a for a linux/unix list of limits, iostat -xm 5 3 for IOPS by device and core/cpu count, df -h for a linux/unix free space list by device, for server tuning analysis.

– Wilson Hauck
Feb 28 at 1:16




1




1





Glad you are back together. Providing the information requested yesterday will allow meaningful suggestions to improve your system performance. Why are are you allowing hacker/cracker 1 million attempts to guess a password with the max_connect_errors at 1 million?

– Wilson Hauck
Feb 28 at 21:30







Glad you are back together. Providing the information requested yesterday will allow meaningful suggestions to improve your system performance. Why are are you allowing hacker/cracker 1 million attempts to guess a password with the max_connect_errors at 1 million?

– Wilson Hauck
Feb 28 at 21:30






1




1





@G.G. With secondary review of your config, it looks like you accidentally have innodb_log_buffer_size much larger than innodb_log_file_size. The buffer should always be smaller than the log_file_size. Sorry I missed this earlier. Still willing to help with tuning, if SHOW GLOBAL STATUS; and SHOW GLOBAL VARIABLES; could be posted, even for DEV or PROD instance.

– Wilson Hauck
1 hour ago







@G.G. With secondary review of your config, it looks like you accidentally have innodb_log_buffer_size much larger than innodb_log_file_size. The buffer should always be smaller than the log_file_size. Sorry I missed this earlier. Still willing to help with tuning, if SHOW GLOBAL STATUS; and SHOW GLOBAL VARIABLES; could be posted, even for DEV or PROD instance.

– Wilson Hauck
1 hour ago












1 Answer
1






active

oldest

votes


















0














I managed to solved this.
Problem was not really on mysql.
Problem was because of wrong in the migration process. Although I got no errors there. This migration was the uber migration tool.



When did the process from start with magento native migration tool mysql and indexers are fine. Everything is working now





share























    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%2f260939%2fmagento-2-mysql-server-has-gone-away%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














    I managed to solved this.
    Problem was not really on mysql.
    Problem was because of wrong in the migration process. Although I got no errors there. This migration was the uber migration tool.



    When did the process from start with magento native migration tool mysql and indexers are fine. Everything is working now





    share




























      0














      I managed to solved this.
      Problem was not really on mysql.
      Problem was because of wrong in the migration process. Although I got no errors there. This migration was the uber migration tool.



      When did the process from start with magento native migration tool mysql and indexers are fine. Everything is working now





      share


























        0












        0








        0







        I managed to solved this.
        Problem was not really on mysql.
        Problem was because of wrong in the migration process. Although I got no errors there. This migration was the uber migration tool.



        When did the process from start with magento native migration tool mysql and indexers are fine. Everything is working now





        share













        I managed to solved this.
        Problem was not really on mysql.
        Problem was because of wrong in the migration process. Although I got no errors there. This migration was the uber migration tool.



        When did the process from start with magento native migration tool mysql and indexers are fine. Everything is working now






        share











        share


        share










        answered 6 mins ago









        G. G.G. G.

        607




        607






























            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%2f260939%2fmagento-2-mysql-server-has-gone-away%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

            迭戈·戈丁...

            A phrase ”follow into" in a context The 2019 Stack Overflow Developer Survey Results Are...

            1960s short story making fun of James Bond-style spy fiction The 2019 Stack Overflow Developer...