Error Message

Note:  All screenshots and logs are from a test lab.  All user names and server names are fictitious.

From Windows Services trying to start service EsaApplicationService : FireDaemon

Windows could not start the EsaApplicationService:
FireDaemon service on Local Computer.
Error 1068:  The dependency service or group failed to start.

From MySQL Error log (Example path and file name: D:\MySQLData\data\eDP-App1.err):
InnoDB: ###### Diagnostic info printed to the standard error stream
2023-08-30T20:07:42.379039Z 0 [ERROR] [MY-012872] [InnoDB] [FATAL] Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
2023-08-30T20:07:42.395010Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: srv0srv.cc:1867:ib::fatal triggered thread 12368
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.
20:07:42 UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x0
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...
7ff67bd50848    mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff67aeee92b    mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff67aeee6f3    mysqld.exe!?my_server_abort@@YAXXZ()
7ff67bd347ea    mysqld.exe!?my_abort@@YAXXZ()
7ff67bf7ca89    mysqld.exe!?deallocate@?$allocator@V?$sub_match@V?$_String_const_iterator@V?$_String_val@U?$_Simple_types@D@std@@@std@@@std@@@std@@@std@@QEAAXQEAV?$sub_match@V?$_String_const_iterator@V?$_String_val@U?$_Simple_types@D@std@@@std@@@std@@@2@_K@Z()
7ff67be59633    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff67be549f6    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff67bf1032d    mysqld.exe!?deallocate@?$allocator@V?$sub_match@V?$_String_const_iterator@V?$_String_val@U?$_Simple_types@D@std@@@std@@@std@@@std@@@std@@QEAAXQEAV?$sub_match@V?$_String_const_iterator@V?$_String_val@U?$_Simple_types@D@std@@@std@@@std@@@2@_K@Z()
7fff0efefb80    ucrtbase.dll!_o__realloc_base()
7fff0fa584d4    KERNEL32.DLL!BaseThreadInitThunk()
7fff12381791    ntdll.dll!RtlUserThreadStart()
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.
2023-08-31T14:11:37.486428Z 0 [Warning] [MY-010086] [Server] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-08-31T14:11:37.486479Z 0 [Warning] [MY-010915] [Server] '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.
2023-08-31T14:11:37.488982Z 0 [Warning] [MY-010097] [Server] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2023-08-31T14:11:37.489138Z 0 [System] [MY-010116] [Server] D:\MySQL\bin\mysqld.exe (mysqld 8.0.30-commercial) starting as process 11300
2023-08-31T14:11:38.125377Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-08-31T14:14:29.882739Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2023-08-31T14:14:42.910658Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2023-08-31T14:14:42.912351Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2023-08-31T14:14:45.062868Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060
2023-08-31T14:14:45.063478Z 0 [System] [MY-010931] [Server] D:\MySQL\bin\mysqld.exe: ready for connections. Version: '8.0.30-commercial'  socket: ''  port: 3306  MySQL Enterprise Server - Commercial.
2023-08-31T14:14:45.663048Z 0 [Warning] [MY-011825] [InnoDB] Cannot add field `STATISTICS` in table `esadb_lds_appliance_2`.`t_jobrun` because after adding it, the row size is 8659 which is greater than maximum allowed size (8126) for a record on index leaf page.

On each startup attempt, the MySql service is instructed to insert a row of data containing 8,659 bytes, which exceeds the maximum default row size limit of 8,126 bytes.  This prevents the service from starting.

Note:  Customers experiencing this issue are encouraged to contact Veritas Support as a work-around is available.  Please reference this Article number or link within the support case.