ESET inspect -- Mysql80 not working

[tgr 1]

Hello together

Maybe you can help me:

I had a running ESET Inspect Server.

I have restartet the Server and now I can not start it.

The problem is the mysql80 service: Start and then stopped with the following message: mysql80 serviced on local computer started and then stopped some services stop automatically if they are not in user by other services or programms

The ESET Inspect Server trying to start but not working not right because the the database not work.

 

Thanks for the help!

 

 

 

[thae 12]

Anything useful in the log?

C:\ProgramData\ESET\Inspect Server\logs\EISERVER-$DATE.log

Or maybe in the Event viewer?

[tgr 1]

Error: Sql error 2006. HY000 Server has gone away. Failing statement: 'SELECT 1'

Error: Sql error 2002. HY000 Can't connect to server on 'localhost' (10061)
01f84 Error: Sql error 2002. HY000 Can't connect to server on 'localhost' (10061)

Error: ESMCAuditExportTask: Error occurred, when extracting audit data from DB. Can't connect to server on 'localhost' (10061)
Error: ESMCMachinesMetadataSyncTask: Error occurred when accessing DB. Can't connect to server on 'localhost' (10061)

Error: ERADetectionEventsSyncTask: Error occurred, when extracting alarm data from DB. Can't connect to server on 'localhost' (10061)

 

I am not sure if this error messages just appear because the mysql80 service is not running so eset can not connect

[tgr 1]

In the event viewer is just an application error from this path:

Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe

 

[thae 12]

What about the MySQL log file at C:\ProgramData\MySQL\MySQL Server 8.0\Data\$Servername.err

[tgr 1]

Hier is the MYSQL log:

2024-08-20T11:26:12.195515Z 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.
2024-08-20T11:26:12.198011Z 0 [System] [MY-010116] [Server] D:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.29) starting as process 7992
2024-08-20T11:26:12.208885Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-08-20T11:26:12.244884Z 1 [ERROR] [MY-012209] [InnoDB] Multiple files found for the same tablespace ID:
2024-08-20T11:26:12.245281Z 1 [ERROR] [MY-012202] [InnoDB] Tablespace ID: 86589 = ['eidb\module_status.ibd', 'eidb\unique_alarms.ibd']
2024-08-20T11:26:12.245777Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Failed, retry may succeed.
2024-08-20T11:26:12.246262Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2024-08-20T11:26:12.247019Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2024-08-20T11:26:12.247502Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-08-20T11:26:12.248166Z 0 [System] [MY-010910] [Server] D:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe: Shutdown complete (mysqld 8.0.29)  MySQL Community Server - GPL.

[tgr 1]

I also found this in the logs:
[ERROR] [MY-011971] [InnoDB] Tablespace 'eidb/modules_statistics' Page [page id: space=224, page number=33277] log sequence number 324345200806 is in the future! Current system log sequence number 323351341503.