Jump to content
megaali3000

MySQL service stuck at starting after increasing 'innodb_log_file_size'

Recommended Posts

Good day everyone, We are trying to install the 'ESET Enterprise Inspector' on a server, after installing mysql and changing parameters according to these requirements, when we try to start the mysql service, the progress bar goes to end (takes two minutes) and it says "the service did not respond to the start or control request in a timely fashion" and it is stuck in starting status.

 The server has 32G of ram and we use innodb_buffer_pool_size=26G and innodb_log_file_size=13G as the parameters.

I've attached the my.ini file also. also the 'D11W19EEI01.err' file is empty.

Does anyone know why the service doesn't start? Thanks in advance.

my.ini.txt

Share this post


Link to post
Share on other sites

Please provide the latest EEI Server log EIServer-2019-*.log from C:\ProgramData\ESET\EnterpriseInspector\Server\logs.

Also logs collected with ESET Log Collector might be useful for us.

Share this post


Link to post
Share on other sites

One other thing.  If you are using Services.msc to start the service, it is not uncommon that the Services.msc GUI can not handle a service that takes a long time to start.  Instead, can you do the following after you get an error in Services.msc?

  1. Open the properties of your MySQL service and and copy the highlighted "Service Name:" at the top of the properties window.  This will likely be mysql57 or mysql8
  2. Open an administrative command prompt and issue the following command: sc query ServiceName
    • Replace ServiceName with the name you identified in step one.  Like: sc query mysql57

You should see that the service is still starting.  Its not uncommon that the MySQL service will take a long time to start.  It is allocating memory and hard drive space.

If the service is never starting, check how much free space is on your hard drives.  If none of the above works or helps, please ensure you gather the logs Marcos requested before replying.

Share this post


Link to post
Share on other sites
4 hours ago, Marcos said:

Please provide the latest EEI Server log EIServer-2019-*.log from C:\ProgramData\ESET\EnterpriseInspector\Server\logs.

Also logs collected with ESET Log Collector might be useful for us.

I don't have access to the logs right now, but it shouldn't matter, should it? we had this problem even before installing EDR. one time we got lucky and the service was installed, so we immediately installed EDR. since then the mysql80 service stops from time to time. this time the service was stopped and it couldn't start again. and we have installed 2 EDR servers and both times we had this problem with mysql.

Share this post


Link to post
Share on other sites
3 hours ago, JamesR said:

One other thing.  If you are using Services.msc to start the service, it is not uncommon that the Services.msc GUI can not handle a service that takes a long time to start.  Instead, can you do the following after you get an error in Services.msc?

  1. Open the properties of your MySQL service and and copy the highlighted "Service Name:" at the top of the properties window.  This will likely be mysql57 or mysql8
  2. Open an administrative command prompt and issue the following command: sc query ServiceName
    • Replace ServiceName with the name you identified in step one.  Like: sc query mysql57

You should see that the service is still starting.  Its not uncommon that the MySQL service will take a long time to start.  It is allocating memory and hard drive space.

If the service is never starting, check how much free space is on your hard drives.  If none of the above works or helps, please ensure you gather the logs Marcos requested before replying.

Thanks for the answer,

That's true, but we gave it a day and it didn't start. there is also no storage issue.

we don't know what else to do, the customer wanted to buy 20000 licenses but now we are losing the contract :(

if only EDR could support SQL Server, like any other product in the business do. 

Share this post


Link to post
Share on other sites

Hi, 

I've found the solution. In my case it worked with and older version of mysql, I don't know why but after  8.0.15.0 almost all updates of mysql have failed after made changes on my.ini file and it stuck at starting. 

In this case you have to install mysql installer community 8.0.15.0 as the kb says, after that you stop the service and make the changes. Finally you restart the service, if it stucks  just restart the server and that's all

Regards

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...