#2006 - MySQL server has gone away


  • | 2911 points

    Started getting this today, I may mention that win10 updated last night and before that everything was working. How do I get MariaDb working again?
    alt text
    from the log:

    2018-05-14 20:06:42 13720 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2018-05-14 20:06:42 13720 [Note] InnoDB: Uses event mutexes
    2018-05-14 20:06:42 13720 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2018-05-14 20:06:42 13720 [Note] InnoDB: Number of pools: 1
    2018-05-14 20:06:42 13720 [Note] InnoDB: Using generic crc32 instructions
    2018-05-14 20:06:43 13720 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
    2018-05-14 20:06:43 13720 [Note] InnoDB: Completed initialization of buffer pool
    2018-05-14 20:06:43 13720 [Note] InnoDB: Tablespace ID 0 name innodb_system:Default tablespace encryption mode scheme unencrypted
    2018-05-14 20:06:43 13720 [Note] InnoDB: Highest supported file format is Barracuda.
    2018-05-14 20:06:43 13720 [Note] InnoDB: Creating shared tablespace for temporary tables
    2018-05-14 20:06:43 13720 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
    2018-05-14 20:06:43 13720 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
    2018-05-14 20:06:43 13720 [Note] InnoDB: Tablespace ID 4294967294 name innodb_temporary:Default tablespace encryption mode scheme unencrypted
    2018-05-14 20:06:43 13720 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
    2018-05-14 20:06:43 13720 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
    2018-05-14 20:06:43 13720 [Note] InnoDB: Waiting for purge to start
    2018-05-14 20:06:43 13720 [Note] InnoDB: 5.7.14 started; log sequence number 279730563
    2018-05-14 20:06:43 10204 [Note] InnoDB: Loading buffer pool(s) from C:\laragon\data\ib_buffer_pool
    2018-05-14 20:06:43 13720 [Note] Plugin 'FEEDBACK' is disabled.
    2018-05-14 20:06:43 13720 [Note] Server socket created on IP: '::'.
    2018-05-14 20:06:43 10204 [Note] InnoDB: Buffer pool(s) load completed at 180514 20:06:43
    2018-05-14 20:06:52 10120 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2018-05-14 20:06:52 10120 [Note] InnoDB: Uses event mutexes
    2018-05-14 20:06:52 10120 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2018-05-14 20:06:52 10120 [Note] InnoDB: Number of pools: 1
    2018-05-14 20:06:52 10120 [Note] InnoDB: Using generic crc32 instructions
    2018-05-14 20:06:53 10120 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
    2018-05-14 20:06:53 10120 [Note] InnoDB: Completed initialization of buffer pool
    2018-05-14 20:06:53 10120 [Note] InnoDB: Tablespace ID 0 name innodb_system:Default tablespace encryption mode scheme unencrypted
    2018-05-14 20:06:53 10120 [Note] InnoDB: Highest supported file format is Barracuda.
    2018-05-14 20:06:53 10120 [Note] InnoDB: Creating shared tablespace for temporary tables
    2018-05-14 20:06:53 10120 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
    2018-05-14 20:06:53 10120 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
    2018-05-14 20:06:53 10120 [Note] InnoDB: Tablespace ID 4294967294 name innodb_temporary:Default tablespace encryption mode scheme unencrypted
    2018-05-14 20:06:53 10120 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
    2018-05-14 20:06:53 10120 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
    2018-05-14 20:06:53 10120 [Note] InnoDB: Waiting for purge to start
    2018-05-14 20:06:53 10120 [Note] InnoDB: 5.7.14 started; log sequence number 279730591
    2018-05-14 20:06:53 7388 [Note] InnoDB: Loading buffer pool(s) from C:\laragon\data\ib_buffer_pool
    2018-05-14 20:06:53 10120 [Note] Plugin 'FEEDBACK' is disabled.
    2018-05-14 20:06:53 10120 [Note] Server socket created on IP: '::'.
    2018-05-14 20:06:53 7388 [Note] InnoDB: Buffer pool(s) load completed at 180514 20:06:53
    2018-05-14 20:06:53 10120 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--log-basename=#' or '--relay-log=WebDev-relay-bin' to avoid this problem.
    2018-05-14 20:06:53 10120 [Note] Started replication for '2018-05-12 10:10:25 4736 [Note] C:\laragon\bin\mysql\mariadb-10.2.3-win32\bin\mysqld: ready for connections.
    '
    2018-05-14 20:06:53 8460 [ERROR] Master '2018-05-12 10:10:25 4736 [Note] C:\laragon\bin\mysql\mariadb-10.2.3-win32\bin\mysqld: ready for connections.
    ': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593
    2018-05-14 20:06:53 9180 [Note] Master '2018-05-12 10:10:25 4736 [Note] C:\laragon\bin\mysql\mariadb-10.2.3-win32\bin\mysqld: ready for connections.
    ': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '.\WebDev-relay-bin-2018@002d05@002d12@002010@003a10@003a25@00204736@0020@005bnote@005d@0020c@003a@005claragon@005cbin@005cmysql@005cmariadb@002d10@002e2@002e3@002dwin32@005cbin@005cmysqld@003a@0020ready@0020for@0020connections@002e@000d.000013' position: 4
    2018-05-14 20:06:53 8460 [Note] Master '2018-05-12 10:10:25 4736 [Note] C:\laragon\bin\mysql\mariadb-10.2.3-win32\bin\mysqld: ready for connections.
    ': Slave I/O thread killed while connecting to master
    2018-05-14 20:06:53 8460 [Note] Master '2018-05-12 10:10:25 4736 [Note] C:\laragon\bin\mysql\mariadb-10.2.3-win32\bin\mysqld: ready for connections.
    ': Slave I/O thread exiting, read up to log 'FIRST', position 4
    2018-05-14 20:06:53 10120 [Note] Started replication for 'Version: '10.2.3-MariaDB-log' socket: '' port: 3306 mariadb.org binary distribution
    '
    2018-05-14 20:06:53 12168 [ERROR] Master 'Version: '10.2.3-MariaDB-log' socket: '' port: 3306 mariadb.org binary distribution
    ': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593
    2018-05-14 20:06:53 12272 [Note] Master 'Version: '10.2.3-MariaDB-log' socket: '' port: 3306 mariadb.org binary distribution
    ': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '.\WebDev-relay-bin-version@003a@0020@002710@002e2@002e3@002dmariadb@002dlog@0027@0020@0020socket@003a@0020@0027@0027@0020@0020port@003a@00203306@0020@0020mariadb@002eorg@0020binary@0020distribution@000d.000013' position: 4
    2018-05-14 20:06:53 10120 [ERROR] mysqld: File 'C:\laragon\data\master-2018@002d05@002d14@0020@00202@003a59@003a30@002010888@0020@005bnote@005d@0020c@003a@005claragon@005cbin@005cmysql@005cmariadb@002d10@002e2@002e3@002dwin32@005cbin@005cmysqld@0020@0028root@005broot@005d@0020@0040@0020localhost@0020@005b@003a@003a1@005d@0029@003a@0020normal@0020shutdown@000d.info' not found (Errcode: 2 "No such file or directory")
    2018-05-14 20:06:53 12168 [Note] Master 'Version: '10.2.3-MariaDB-log' socket: '' port: 3306 mariadb.org binary distribution
    ': Slave I/O thread killed while connecting to master
    2018-05-14 20:06:53 10120 [ERROR] Failed to create a new master info file (file 'C:\laragon\data\master-2018@002d05@002d14@0020@00202@003a59@003a30@002010888@0020@005bnote@005d@0020c@003a@005claragon@005cbin@005cmysql@005cmariadb@002d10@002e2@002e3@002dwin32@005cbin@005cmysqld@0020@0028root@005broot@005d@0020@0040@0020localhost@0020@005b@003a@003a1@005d@0029@003a@0020normal@0020shutdown@000d.info', errno 2)
    2018-05-14 20:06:53 12168 [Note] Master 'Version: '10.2.3-MariaDB-log' socket: '' port: 3306 mariadb.org binary distribution
    ': Slave I/O thread exiting, read up to log 'FIRST', position 4
    2018-05-14 20:06:53 10120 [ERROR] Initialized Master_info from 'master-2018@002d05@002d14@0020@00202@003a59@003a30@002010888@0020@005bnote@005d@0020c@003a@005claragon@005cbin@005cmysql@005cmariadb@002d10@002e2@002e3@002dwin32@005cbin@005cmysqld@0020@0028root@005broot@005d@0020@0040@0020localhost@0020@005b@003a@003a1@005d@0029@003a@0020normal@0020shutdown@000d.info' failed
    2018-05-14 20:06:53 10120 [Note] Started replication for '
    '
    2018-05-14 20:06:53 2220 [ERROR] Master '
    ': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593
    2018-05-14 20:06:53 13572 [Note] Master '
    ': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '.\WebDev-relay-bin-@000d.000013' position: 4
    2018-05-14 20:06:53 2220 [Note] Master '
    ': Slave I/O thread killed while connecting to master
    2018-05-14 20:06:53 2220 [Note] Master '
    ': Slave I/O thread exiting, read up to log 'FIRST', position 4
    2018-05-14 20:06:53 10120 [Note] Started replication for '2018-05-14 2:59:30 10888 [Note] Event Scheduler: Purging the queue. 0 events
    '
    2018-05-14 20:06:53 14140 [ERROR] Master '2018-05-14 2:59:30 10888 [Note] Event Scheduler: Purging the queue. 0 events
    ': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593
    2018-05-14 20:06:53 6284 [Note] Master '2018-05-14 2:59:30 10888 [Note] Event Scheduler: Purging the queue. 0 events
    ': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '.\WebDev-relay-bin-2018@002d05@002d14@0020@00202@003a59@003a30@002010888@0020@005bnote@005d@0020event@0020scheduler@003a@0020purging@0020the@0020queue@002e@00200@0020events@000d.000013' position: 4
    2018-05-14 20:06:53 10120 [Warning] Reading of some Master_info entries failed
    2018-05-14 20:06:53 14140 [Note] Master '2018-05-14 2:59:30 10888 [Note] Event Scheduler: Purging the queue. 0 events
    ': Slave I/O thread killed while connecting to master
    2018-05-14 20:06:53 10120 [ERROR] Failed to initialize multi master structures
    2018-05-14 20:06:53 14140 [Note] Master '2018-05-14 2:59:30 10888 [Note] Event Scheduler: Purging the queue. 0 events
    ': Slave I/O thread exiting, read up to log 'FIRST', position 4
    2018-05-14 20:06:53 10120 [ERROR] Aborting


  • | 2911 points

    allways??? I've been working on this project with laragon for 13 months now and this has never happened, only today and I am thinking perhaps it has something to do with the win10 update but perhaps not?


  • | 2911 points

    fucking bot!!! I just realized I responded to a spamer!


  • administrators
    | 90764 points

    @nermamax : Hmm, I don't know why MariaDB said about Master/Slave issue. Especially this line:

    Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server
    

    However, if your former data is not a matter, just rename your Data Dir (C:\laragon\data) to data.bak, Laragon will revive MariaDB.


  • | 2911 points

    I switched to mySql which was also installed and that MySql worked. I may now continue with mySql as I am running Laravel, but I will try your suggestion to see if that helps.


Log in to reply
 

Looks like your connection to Laragon was lost, please wait while we try to reconnect.