Page 1 of 1

MySql crashes when trying to open WordPress local host

PostPosted: 04. March 2018 23:46
by ashleykaplan
Hello,

I'm a newbie to XAMPP, but I have used it with no issues (until now!) for the last month or so. I've been working on building a WordPress site, and today I was trying to take it live. After I transferred my files using FileZilla, I tried to open my site locally. Both Apache and MySql were running at that time. However, as soon as I tried to open my site locally, MySql shut down unexpectedly. Following are the error logs:

Code: Select all
2018-02-20 18:24:41 2918 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2018-02-20 18:24:41 10520 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-02-20 18:24:41 10520 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-02-20 18:24:41 10520 [Note] InnoDB: The InnoDB memory heap is disabled
2018-02-20 18:24:41 10520 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-02-20 18:24:41 10520 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-02-20 18:24:41 10520 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-02-20 18:24:41 10520 [Note] InnoDB: Using generic crc32 instructions
2018-02-20 18:24:41 10520 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-02-20 18:24:41 10520 [Note] InnoDB: Completed initialization of buffer pool
2018-02-20 18:24:41 10520 [Note] InnoDB: Highest supported file format is Barracuda.
2018-02-20 18:24:41 10520 [Note] InnoDB: 128 rollback segment(s) are active.
2018-02-20 18:24:41 10520 [Note] InnoDB: Waiting for purge to start
2018-02-20 18:24:41 10520 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 1835037
2018-02-20 18:24:41 11532 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-02-20 18:24:41 10520 [Note] Plugin 'FEEDBACK' is disabled.
2018-02-20 18:24:41 10520 [Note] Server socket created on IP: '::'.
2018-02-20 18:24:42 10520 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.30-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution


I've tried various solutions that I've found here and on other forums--although because I'm such a newbie, I have no idea if I've executed any of the solutions correctly. I have no idea what to do, but I am ready to pull out my hair!!! :shock: :oops:

Any help will be greatly appreciated. Thank you in advance!

Re: MySql crashes when trying to open WordPress local host

PostPosted: 06. March 2018 02:41
by ashleykaplan
Update: I was able to restore a previous version of ibdata1, and this resolved the issues I was having.

Re: MySql crashes when trying to open WordPress local host

PostPosted: 14. March 2018 13:24
by faospark
actually the solution lies on commenting out on your my.ini configuration the following
innodb_additional_mem_pool_size and innodb_use_sys_malloc