MySQL not starting automatically whenever system reboot

Vinod Nayal 1 Reputation point
2023-01-08T13:02:26.267+00:00

We are working on system having features: windows server 2019 Standard, 32GB RAM, Processor: Intel(R) Xeon® Silver 4310 CPU @2.1GHz (2 processors), 64-bit OS

Whenever system reboot or power interrupts, MySQL services stopped permanently. It cannot be started by Command prompt or services.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
8,165 questions
{count} votes

4 answers

Sort by: Most helpful
  1. Dave Patrick 329.1K Reputation points Microsoft MVP
    2023-01-08T15:02:11.397+00:00

    Sounds like something is broken. You could get support for your product here.
    https://www.mysql.com/support/

    or try asking for help in dedicated forums here.
    https://forums.mysql.com/

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  2. MotoX80 23,491 Reputation points
    2023-01-08T15:10:56.65+00:00

    Then your best bet is to contact MySQL support as @Dave Patrick suggested.

    Did you perform these steps and reference the pages?

    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
    InnoDB: If you get repeated assertion failures or crashes, even
    InnoDB: immediately after the mysqld startup, there may be
    InnoDB: corruption in the InnoDB tablespace. Please refer to
    InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
    InnoDB: about forcing recovery.
    2022-12-24T12:50:14Z UTC - mysqld got exception 0x16 ;
    Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
    Thread pointer: 0x2123ddc1a40
    Attempting backtrace. You can use the following information to find out
    where mysqld died. If you see no messages after this, something went
    terribly wrong...
    7ff6adb9fa68 mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
    7ff6acd29411 mysqld.exe!?print_fatal_signal@@YAXH@Z()
    7ff6acd29153 mysqld.exe!?my_server_abort@@YAXXZ()
    7ff6adb83a7a mysqld.exe!?my_abort@@YAXXZ()

    The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
    information that should help you find out what is causing the crash.


  3. Limitless Technology 9,046 Reputation points
    2023-01-10T09:22:56.083+00:00

    Hello there,

    Even with correct ownership, MySQL might fail to start up if there is other security software running on your system that manages application access to various parts of the file system. In this case, reconfigure that software to enable mysqld to access the directories it uses during normal operation.

    Certain versions of MySQL add invalid hex values at the beginning of the my.ini configuration file. Deleting the first three hex values using a hex editor should resolve this issue. This occurs because of an issue with a script line. The line specifies that each file must have a unique ID, which then appends the byte order to mark the text file.

    If you have a backup of the original my.ini file, you can copy the contents of this file and manually paste them onto the current my.ini to resolve this issue.

    Hope this resolves your Query !!

    --If the reply is helpful, please Upvote and Accept it as an answer–

    No comments

  4. MotoX80 23,491 Reputation points
    2023-01-15T16:08:41.0133333+00:00

    Please suggest the solution.

    A while back I built a "Is Windows healthy" bat file to run basic analysis tools on a machine. Run that from an admin command prompt and see if it detects anything.

    https://learn.microsoft.com/en-us/answers/questions/118183/how-to-fix-error-0x80070543-in-windows-10.html

    Have you applied all outstanding patches in Windows Update? Make sure that Windows is up to date.

    Check your page file settings to verify that you have sufficient virtual memory available.

    Next, I would reboot. When the server comes back up, check to see that all of your services have started. Then check the task manager on the cpu and memory tabs. Make note of the values like handle count, paged/non-paged pool, available memory, etc. Maybe take a screen snapshot of the values and then if (when) you get the 4005 error compare the values to see if you see anything strange, like a radically high number of handles. You might have a memory leak.

    At the time you get a 4005 error, check the security and system eventlogs for additional events that might help you figure out what is going on.

    https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc734097(v=ws.10)?redirectedfrom=MSDN

    No comments