Re: Building MySQL 5.7 From Source on Windows
From: Jerry Stuckle <jstucklex_at_attglobal.net>
Date: Thu, 17 Oct 2019 19:44:28 -0400
Message-ID: <qoauck$a0t$1_at_jstuckle.eternal-september.org>
>
> Below is the entirety of the error log. When the mysqld processes reaches
> that point, it simply does not progress any farther. It doesn't fail; it
> appears to hang.
>
>
> 2019-10-17T22:20:53.465922Z 0 [Warning] option 'net_buffer_length':
> unsigned value 209715200 adjusted to 1048576
> 2019-10-17T22:20:53.465991Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE'
> and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode.
> They will be merged with strict mode in a future release.
> 2019-10-17T22:20:53.469628Z 0 [Note] bin\mysqld (mysqld 5.7.28-log)
> starting as process 5800 ...
> 2019-10-17T22:20:53.482179Z 0 [Note] InnoDB: Mutexes and rw_locks use
> Windows interlocked functions
> 2019-10-17T22:20:53.483425Z 0 [Note] InnoDB: Uses event mutexes
> 2019-10-17T22:20:53.484214Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence()
> are used for memory barrier
> 2019-10-17T22:20:53.485401Z 0 [Note] InnoDB: Compressed tables use zlib
> 1.2.11
> 2019-10-17T22:20:53.486397Z 0 [Note] InnoDB: Adjusting
> innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is
> less than 1024 MiB
> 2019-10-17T22:20:53.488865Z 0 [Note] InnoDB: Number of pools: 1
> 2019-10-17T22:20:53.490097Z 0 [Note] InnoDB: Not using CPU crc32
> instructions
> 2019-10-17T22:20:53.495533Z 0 [Note] InnoDB: Initializing buffer pool,
> total size = 256M, instances = 1, chunk size = 128M
> 2019-10-17T22:20:53.515671Z 0 [Note] InnoDB: Completed initialization of
> buffer pool
> 2019-10-17T22:20:53.546661Z 0 [Note] InnoDB: Highest supported file format
> is Barracuda.
> 2019-10-17T22:20:53.552589Z 0 [Note] InnoDB: Log scan progressed past the
> checkpoint lsn 1209961
> 2019-10-17T22:20:53.553989Z 0 [Note] InnoDB: Doing recovery: scanned up to
> log sequence number 1209970
> 2019-10-17T22:20:53.555315Z 0 [Note] InnoDB: Database was not shutdown
> normally!
> 2019-10-17T22:20:53.556377Z 0 [Note] InnoDB: Starting crash recovery.
> 2019-10-17T22:20:53.713888Z 0 [Note] InnoDB: Removed temporary tablespace
> data file: "ibtmp1"
> 2019-10-17T22:20:53.715192Z 0 [Note] InnoDB: Creating shared tablespace for
> temporary tables
> 2019-10-17T22:20:53.716919Z 0 [Note] InnoDB: Setting file '.\ibtmp1' size
> to 12 MB. Physically writing the file full; Please wait ...
> 2019-10-17T22:20:53.877057Z 0 [Note] InnoDB: File '.\ibtmp1' size is now 12
> MB.
> 2019-10-17T22:20:53.971319Z 0 [Note] InnoDB: 96 redo rollback segment(s)
> found. 96 redo rollback segment(s) are active.
> 2019-10-17T22:20:53.972288Z 0 [Note] InnoDB: 32 non-redo rollback segment
> (s) are active.
> 2019-10-17T22:20:53.973388Z 0 [Note] InnoDB: Waiting for purge to start
> 2019-10-17T22:20:54.035546Z 0 [Note] InnoDB: 5.7.28 started; log sequence
> number 1209970
> 2019-10-17T22:20:54.036643Z 0 [Note] Plugin 'FEDERATED' is disabled.
> 2019-10-17T22:20:54.036649Z 0 [Note] InnoDB: Loading buffer pool(s) from C:
> \MySQLfromSource\Data\ib_buffer_pool
> mysqld: Table 'mysql.plugin' doesn't exist
> 2019-10-17T22:20:54.038013Z 0 [ERROR] Can't open the mysql.plugin table.
> Please run mysql_upgrade to create it.
> 2019-10-17T22:20:54.038197Z 0 [ERROR] InnoDB: Cannot open 'C:
> \MySQLfromSource\Data\ib_buffer_pool' for reading: No such file or
> directory
> 2019-10-17T22:20:54.040389Z 0 [Warning] Gtid table is not ready to be used.
> Table 'mysql.gtid_executed' cannot be opened.
>
Date: Thu, 17 Oct 2019 19:44:28 -0400
Message-ID: <qoauck$a0t$1_at_jstuckle.eternal-september.org>
On 10/17/2019 6:23 PM, Lyle H. Gray wrote:
> Jerry Stuckle <jstucklex_at_attglobal.net> wrote in news:qoalhr$q7l$1
> _at_jstuckle.eternal-september.org:
>> Look at your error log. Something is stopping it from opening the port. >> It could be a lot of things. Without the log it's only a guess.
>
> Below is the entirety of the error log. When the mysqld processes reaches
> that point, it simply does not progress any farther. It doesn't fail; it
> appears to hang.
>
>
> 2019-10-17T22:20:53.465922Z 0 [Warning] option 'net_buffer_length':
> unsigned value 209715200 adjusted to 1048576
> 2019-10-17T22:20:53.465991Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE'
> and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode.
> They will be merged with strict mode in a future release.
> 2019-10-17T22:20:53.469628Z 0 [Note] bin\mysqld (mysqld 5.7.28-log)
> starting as process 5800 ...
> 2019-10-17T22:20:53.482179Z 0 [Note] InnoDB: Mutexes and rw_locks use
> Windows interlocked functions
> 2019-10-17T22:20:53.483425Z 0 [Note] InnoDB: Uses event mutexes
> 2019-10-17T22:20:53.484214Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence()
> are used for memory barrier
> 2019-10-17T22:20:53.485401Z 0 [Note] InnoDB: Compressed tables use zlib
> 1.2.11
> 2019-10-17T22:20:53.486397Z 0 [Note] InnoDB: Adjusting
> innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is
> less than 1024 MiB
> 2019-10-17T22:20:53.488865Z 0 [Note] InnoDB: Number of pools: 1
> 2019-10-17T22:20:53.490097Z 0 [Note] InnoDB: Not using CPU crc32
> instructions
> 2019-10-17T22:20:53.495533Z 0 [Note] InnoDB: Initializing buffer pool,
> total size = 256M, instances = 1, chunk size = 128M
> 2019-10-17T22:20:53.515671Z 0 [Note] InnoDB: Completed initialization of
> buffer pool
> 2019-10-17T22:20:53.546661Z 0 [Note] InnoDB: Highest supported file format
> is Barracuda.
> 2019-10-17T22:20:53.552589Z 0 [Note] InnoDB: Log scan progressed past the
> checkpoint lsn 1209961
> 2019-10-17T22:20:53.553989Z 0 [Note] InnoDB: Doing recovery: scanned up to
> log sequence number 1209970
> 2019-10-17T22:20:53.555315Z 0 [Note] InnoDB: Database was not shutdown
> normally!
> 2019-10-17T22:20:53.556377Z 0 [Note] InnoDB: Starting crash recovery.
> 2019-10-17T22:20:53.713888Z 0 [Note] InnoDB: Removed temporary tablespace
> data file: "ibtmp1"
> 2019-10-17T22:20:53.715192Z 0 [Note] InnoDB: Creating shared tablespace for
> temporary tables
> 2019-10-17T22:20:53.716919Z 0 [Note] InnoDB: Setting file '.\ibtmp1' size
> to 12 MB. Physically writing the file full; Please wait ...
> 2019-10-17T22:20:53.877057Z 0 [Note] InnoDB: File '.\ibtmp1' size is now 12
> MB.
> 2019-10-17T22:20:53.971319Z 0 [Note] InnoDB: 96 redo rollback segment(s)
> found. 96 redo rollback segment(s) are active.
> 2019-10-17T22:20:53.972288Z 0 [Note] InnoDB: 32 non-redo rollback segment
> (s) are active.
> 2019-10-17T22:20:53.973388Z 0 [Note] InnoDB: Waiting for purge to start
> 2019-10-17T22:20:54.035546Z 0 [Note] InnoDB: 5.7.28 started; log sequence
> number 1209970
> 2019-10-17T22:20:54.036643Z 0 [Note] Plugin 'FEDERATED' is disabled.
> 2019-10-17T22:20:54.036649Z 0 [Note] InnoDB: Loading buffer pool(s) from C:
> \MySQLfromSource\Data\ib_buffer_pool
> mysqld: Table 'mysql.plugin' doesn't exist
> 2019-10-17T22:20:54.038013Z 0 [ERROR] Can't open the mysql.plugin table.
> Please run mysql_upgrade to create it.
> 2019-10-17T22:20:54.038197Z 0 [ERROR] InnoDB: Cannot open 'C:
> \MySQLfromSource\Data\ib_buffer_pool' for reading: No such file or
> directory
> 2019-10-17T22:20:54.040389Z 0 [Warning] Gtid table is not ready to be used.
> Table 'mysql.gtid_executed' cannot be opened.
>
Well, start by getting rid of the errors and warnings. For instance - did you run mysql_upgrade as indicated? Did you follow the directions when upgrading MySQL?
-- ================== Remove the "x" from my email address Jerry Stuckle jstucklex_at_attglobal.net ==================Received on Fri Oct 18 2019 - 01:44:28 CEST