MySQL 5.5 Gone AwayHow to change data location on Ubuntumysql wont start after increasing...

How to draw a node with two options using TikZ graphs in LaTeX

How can find the 2D Voronoi cell area distribution?

Can you say "leftside right"?

Is there any danger of my neighbor having my wife's signature?

How do I avoid the "chosen hero" feeling?

Sing Baby Shark

What species should be used for storage of human minds?

Why did Ylvis use "go" instead of "say" in phrases like "Dog goes 'woof'"?

How do I fight with Heavy Armor as a Wizard with Tenser's Transformation?

Minimum Viable Product for RTS game?

Is it recommended to be 100% delegated for a baker?

What's the reason that we have a different number of days each month?

Calculating the strength of an ionic bond that contains poly-atomic ions

Explicit Riemann Hilbert correspondence

What does an unprocessed RAW file look like?

How can I handle players killing my NPC outside of combat?

How can I prevent an oracle who can see into the past from knowing everything that has happened?

Trying to detect if any checked values contains a specific string

Dealing with an internal ScriptKiddie

"I showed the monkey himself in the mirror". Why is this sentence grammatical?

Crack the bank account's password!

Would water spill from a bowl in a Bag of Holding?

In the Lost in Space intro why was Dr. Smith actor listed as a special guest star?

What happened to Hermione’s clothing and other possessions after the memory wipe in Deathly Hallows?



MySQL 5.5 Gone Away


How to change data location on Ubuntumysql wont start after increasing innodb_buffer_pool_size and innodb_log_file_sizemysqld_safe version different than mysqld?Mysql Server Crashing RegularlyMySQL InnoDB Configuration with 60Gb of MemoryMySQL replication - ibdata1 hugeError 1236 'Found old binary log without GTIDs' after master restartMysql server does not start if binary logging is disabledMysql will no longer start after DB import and password changeMySQL root login email notification













3















I'm trying to import a database in preparation for an upgrade from 5.0 to 5.5. The database isn't that large, only 37GB but I can't manage to import it without ERROR 2006. My most recent attempt when like this:



db01 # mysqldump -u root -p$password --databases $db --max_allowed_packet=2G --skip-extended-insert --add-drop-table  --force > /mydatabase.dmp

db02 # mysql --max_allowed_packet=2G -u root -p$password -e "source /mydatabase.dmp"
ERROR 2006 (HY000) at line 7292 in file: '/mydatabase.dmp': MySQL server has gone away


Here's my my.cnf:



[mysqld]
innodb_buffer_pool_size = 3G
server-id = 4
log_bin = /var/lib/mysql/mysql-bin.log
binlog_do_db = my_database
port = 3306
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

# Recommended in standard MySQL setup
sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid


There is memory available on the server at the time - nothing else is running there. There's nothing in mysqld.log regarding this error. How can I get past this error?










share|improve this question














bumped to the homepage by Community 16 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    3















    I'm trying to import a database in preparation for an upgrade from 5.0 to 5.5. The database isn't that large, only 37GB but I can't manage to import it without ERROR 2006. My most recent attempt when like this:



    db01 # mysqldump -u root -p$password --databases $db --max_allowed_packet=2G --skip-extended-insert --add-drop-table  --force > /mydatabase.dmp

    db02 # mysql --max_allowed_packet=2G -u root -p$password -e "source /mydatabase.dmp"
    ERROR 2006 (HY000) at line 7292 in file: '/mydatabase.dmp': MySQL server has gone away


    Here's my my.cnf:



    [mysqld]
    innodb_buffer_pool_size = 3G
    server-id = 4
    log_bin = /var/lib/mysql/mysql-bin.log
    binlog_do_db = my_database
    port = 3306
    datadir=/var/lib/mysql
    socket=/var/lib/mysql/mysql.sock

    # Disabling symbolic-links is recommended to prevent assorted security risks
    symbolic-links=0

    # Recommended in standard MySQL setup
    sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

    [mysqld_safe]
    log-error=/var/log/mysqld.log
    pid-file=/var/run/mysqld/mysqld.pid


    There is memory available on the server at the time - nothing else is running there. There's nothing in mysqld.log regarding this error. How can I get past this error?










    share|improve this question














    bumped to the homepage by Community 16 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      3












      3








      3








      I'm trying to import a database in preparation for an upgrade from 5.0 to 5.5. The database isn't that large, only 37GB but I can't manage to import it without ERROR 2006. My most recent attempt when like this:



      db01 # mysqldump -u root -p$password --databases $db --max_allowed_packet=2G --skip-extended-insert --add-drop-table  --force > /mydatabase.dmp

      db02 # mysql --max_allowed_packet=2G -u root -p$password -e "source /mydatabase.dmp"
      ERROR 2006 (HY000) at line 7292 in file: '/mydatabase.dmp': MySQL server has gone away


      Here's my my.cnf:



      [mysqld]
      innodb_buffer_pool_size = 3G
      server-id = 4
      log_bin = /var/lib/mysql/mysql-bin.log
      binlog_do_db = my_database
      port = 3306
      datadir=/var/lib/mysql
      socket=/var/lib/mysql/mysql.sock

      # Disabling symbolic-links is recommended to prevent assorted security risks
      symbolic-links=0

      # Recommended in standard MySQL setup
      sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

      [mysqld_safe]
      log-error=/var/log/mysqld.log
      pid-file=/var/run/mysqld/mysqld.pid


      There is memory available on the server at the time - nothing else is running there. There's nothing in mysqld.log regarding this error. How can I get past this error?










      share|improve this question














      I'm trying to import a database in preparation for an upgrade from 5.0 to 5.5. The database isn't that large, only 37GB but I can't manage to import it without ERROR 2006. My most recent attempt when like this:



      db01 # mysqldump -u root -p$password --databases $db --max_allowed_packet=2G --skip-extended-insert --add-drop-table  --force > /mydatabase.dmp

      db02 # mysql --max_allowed_packet=2G -u root -p$password -e "source /mydatabase.dmp"
      ERROR 2006 (HY000) at line 7292 in file: '/mydatabase.dmp': MySQL server has gone away


      Here's my my.cnf:



      [mysqld]
      innodb_buffer_pool_size = 3G
      server-id = 4
      log_bin = /var/lib/mysql/mysql-bin.log
      binlog_do_db = my_database
      port = 3306
      datadir=/var/lib/mysql
      socket=/var/lib/mysql/mysql.sock

      # Disabling symbolic-links is recommended to prevent assorted security risks
      symbolic-links=0

      # Recommended in standard MySQL setup
      sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

      [mysqld_safe]
      log-error=/var/log/mysqld.log
      pid-file=/var/run/mysqld/mysqld.pid


      There is memory available on the server at the time - nothing else is running there. There's nothing in mysqld.log regarding this error. How can I get past this error?







      mysql mysql-5.5






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Aug 14 '17 at 19:33









      Ken JKen J

      1616




      1616





      bumped to the homepage by Community 16 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 16 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          3 Answers
          3






          active

          oldest

          votes


















          0















          ERROR 2006 (HY000) at line 7292 in file: '/mydatabase.dmp': MySQL
          server has gone away




          Means that the connection got interrupted anormaly while the connection was on. There are many reasons why that can happen, one of the most common is that the server was killed during that.



          There is not enough information on your post to say something in particular, what I can suggest is:




          • Please paste the error log around that time- you said no error was show, but please let us see that by ourselves. In particular, let us see your database server's uptime to confirm it.

          • Please paste the queries around 7292 line of that file, that may provide some extra information of which query fails exactly. You could skip lines until it works, and then analyze why those doesn't work

          • You could have file corruption, or some configuration that kills a specific query, or some imcompatibility between versions, or you forgot to run mysql_upgrade, ...


          • doing mysql -e "source" is a very convoluting way of doing an import- you could just:



            cat [or pv] /mydatabase.dmp | mysql ...







          share|improve this answer
























          • I added max_allowed_packet = 50M to my my.cnf and ran the import again. It completed without errors but took 3.5 hours.

            – Ken J
            Aug 15 '17 at 0:10



















          0














          For innodb_buffer_pool_size = 3G and max_allowed_packet=2G, I assume you have at least 8GB of RAM? If only 4GB, then cut those values in half. Otherwise swapping will slow things to a crawl.






          share|improve this answer































            0














            There is a misunderstanding on how large max_allowed_packet may be.



            According to the following URL, the MAX is 1G.



            https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html






            share|improve this answer























              Your Answer








              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "182"
              };
              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%2fdba.stackexchange.com%2fquestions%2f183470%2fmysql-5-5-gone-away%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0















              ERROR 2006 (HY000) at line 7292 in file: '/mydatabase.dmp': MySQL
              server has gone away




              Means that the connection got interrupted anormaly while the connection was on. There are many reasons why that can happen, one of the most common is that the server was killed during that.



              There is not enough information on your post to say something in particular, what I can suggest is:




              • Please paste the error log around that time- you said no error was show, but please let us see that by ourselves. In particular, let us see your database server's uptime to confirm it.

              • Please paste the queries around 7292 line of that file, that may provide some extra information of which query fails exactly. You could skip lines until it works, and then analyze why those doesn't work

              • You could have file corruption, or some configuration that kills a specific query, or some imcompatibility between versions, or you forgot to run mysql_upgrade, ...


              • doing mysql -e "source" is a very convoluting way of doing an import- you could just:



                cat [or pv] /mydatabase.dmp | mysql ...







              share|improve this answer
























              • I added max_allowed_packet = 50M to my my.cnf and ran the import again. It completed without errors but took 3.5 hours.

                – Ken J
                Aug 15 '17 at 0:10
















              0















              ERROR 2006 (HY000) at line 7292 in file: '/mydatabase.dmp': MySQL
              server has gone away




              Means that the connection got interrupted anormaly while the connection was on. There are many reasons why that can happen, one of the most common is that the server was killed during that.



              There is not enough information on your post to say something in particular, what I can suggest is:




              • Please paste the error log around that time- you said no error was show, but please let us see that by ourselves. In particular, let us see your database server's uptime to confirm it.

              • Please paste the queries around 7292 line of that file, that may provide some extra information of which query fails exactly. You could skip lines until it works, and then analyze why those doesn't work

              • You could have file corruption, or some configuration that kills a specific query, or some imcompatibility between versions, or you forgot to run mysql_upgrade, ...


              • doing mysql -e "source" is a very convoluting way of doing an import- you could just:



                cat [or pv] /mydatabase.dmp | mysql ...







              share|improve this answer
























              • I added max_allowed_packet = 50M to my my.cnf and ran the import again. It completed without errors but took 3.5 hours.

                – Ken J
                Aug 15 '17 at 0:10














              0












              0








              0








              ERROR 2006 (HY000) at line 7292 in file: '/mydatabase.dmp': MySQL
              server has gone away




              Means that the connection got interrupted anormaly while the connection was on. There are many reasons why that can happen, one of the most common is that the server was killed during that.



              There is not enough information on your post to say something in particular, what I can suggest is:




              • Please paste the error log around that time- you said no error was show, but please let us see that by ourselves. In particular, let us see your database server's uptime to confirm it.

              • Please paste the queries around 7292 line of that file, that may provide some extra information of which query fails exactly. You could skip lines until it works, and then analyze why those doesn't work

              • You could have file corruption, or some configuration that kills a specific query, or some imcompatibility between versions, or you forgot to run mysql_upgrade, ...


              • doing mysql -e "source" is a very convoluting way of doing an import- you could just:



                cat [or pv] /mydatabase.dmp | mysql ...







              share|improve this answer














              ERROR 2006 (HY000) at line 7292 in file: '/mydatabase.dmp': MySQL
              server has gone away




              Means that the connection got interrupted anormaly while the connection was on. There are many reasons why that can happen, one of the most common is that the server was killed during that.



              There is not enough information on your post to say something in particular, what I can suggest is:




              • Please paste the error log around that time- you said no error was show, but please let us see that by ourselves. In particular, let us see your database server's uptime to confirm it.

              • Please paste the queries around 7292 line of that file, that may provide some extra information of which query fails exactly. You could skip lines until it works, and then analyze why those doesn't work

              • You could have file corruption, or some configuration that kills a specific query, or some imcompatibility between versions, or you forgot to run mysql_upgrade, ...


              • doing mysql -e "source" is a very convoluting way of doing an import- you could just:



                cat [or pv] /mydatabase.dmp | mysql ...








              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Aug 14 '17 at 19:46









              jynusjynus

              11.1k11832




              11.1k11832













              • I added max_allowed_packet = 50M to my my.cnf and ran the import again. It completed without errors but took 3.5 hours.

                – Ken J
                Aug 15 '17 at 0:10



















              • I added max_allowed_packet = 50M to my my.cnf and ran the import again. It completed without errors but took 3.5 hours.

                – Ken J
                Aug 15 '17 at 0:10

















              I added max_allowed_packet = 50M to my my.cnf and ran the import again. It completed without errors but took 3.5 hours.

              – Ken J
              Aug 15 '17 at 0:10





              I added max_allowed_packet = 50M to my my.cnf and ran the import again. It completed without errors but took 3.5 hours.

              – Ken J
              Aug 15 '17 at 0:10













              0














              For innodb_buffer_pool_size = 3G and max_allowed_packet=2G, I assume you have at least 8GB of RAM? If only 4GB, then cut those values in half. Otherwise swapping will slow things to a crawl.






              share|improve this answer




























                0














                For innodb_buffer_pool_size = 3G and max_allowed_packet=2G, I assume you have at least 8GB of RAM? If only 4GB, then cut those values in half. Otherwise swapping will slow things to a crawl.






                share|improve this answer


























                  0












                  0








                  0







                  For innodb_buffer_pool_size = 3G and max_allowed_packet=2G, I assume you have at least 8GB of RAM? If only 4GB, then cut those values in half. Otherwise swapping will slow things to a crawl.






                  share|improve this answer













                  For innodb_buffer_pool_size = 3G and max_allowed_packet=2G, I assume you have at least 8GB of RAM? If only 4GB, then cut those values in half. Otherwise swapping will slow things to a crawl.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Aug 19 '17 at 16:04









                  Rick JamesRick James

                  42.9k22259




                  42.9k22259























                      0














                      There is a misunderstanding on how large max_allowed_packet may be.



                      According to the following URL, the MAX is 1G.



                      https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html






                      share|improve this answer




























                        0














                        There is a misunderstanding on how large max_allowed_packet may be.



                        According to the following URL, the MAX is 1G.



                        https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html






                        share|improve this answer


























                          0












                          0








                          0







                          There is a misunderstanding on how large max_allowed_packet may be.



                          According to the following URL, the MAX is 1G.



                          https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html






                          share|improve this answer













                          There is a misunderstanding on how large max_allowed_packet may be.



                          According to the following URL, the MAX is 1G.



                          https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Aug 28 '18 at 23:49









                          Wilson HauckWilson Hauck

                          76149




                          76149






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Database Administrators 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%2fdba.stackexchange.com%2fquestions%2f183470%2fmysql-5-5-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

                              Szabolcs (Ungheria) Altri progetti | Menu di navigazione48°10′14.56″N 21°29′33.14″E /...

                              Discografia di Klaus Schulze Indice Album in studio | Album dal vivo | Singoli | Antologie | Colonne...

                              How to make inet_server_addr() return localhost in spite of ::1/128RETURN NEXT in Postgres FunctionConnect to...