[MDEV-23129] I can not start the service of the current version 10.5.4 again. Created: 2020-07-09  Updated: 2020-07-10  Resolved: 2020-07-10

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.5.4
Fix Version/s: 10.5.5

Type: Bug Priority: Major
Reporter: Stefan Marczuk Assignee: Vladislav Vaintroub
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Windows 10


Attachments: Text File result_1.txt     Text File result_2.txt    
Issue Links:
Duplicate
duplicates MDEV-23038 Service registered with deprecated "m... Closed

 Description   

Hi,

I can not start the service of the current version 10.5.4 again.
Is it correct that the size of MYSQLD.EXE is only 26.9kb?

Stefan



 Comments   
Comment by Stefan Marczuk [ 2020-07-09 ]

I'm sorry that I created the process twice.

Comment by Vladislav Vaintroub [ 2020-07-09 ]

Yes, it is correct that mysqld.exe is small. But , it uses server.dll , which is big

Comment by Stefan Marczuk [ 2020-07-09 ]

The hint with the server.dll was crucial
I did not copy the file.

I always use the ZIP file and manually copy the necessary files.

What other files must be in the BIN folder?

It runs. thank you

Stefan.

Comment by Stefan Marczuk [ 2020-07-09 ]

Hi,

I have to revise myself. It runs on one computer, but not on another. There I get the error message 1067

Stefan

Comment by Vladislav Vaintroub [ 2020-07-09 ]

mysqld.exe, and server.dll and it should run on Windows 10.
1067 is catch-all message, nothing telling.

please run "mysqld --help" on the commandline, maybe it will tell you what's up.

Comment by Stefan Marczuk [ 2020-07-09 ]

mysqld --help doesn't report (Result 01.txt)
Maybe you can do something (Result_02.txt) with mysqld --help --verbose?

Comment by Vladislav Vaintroub [ 2020-07-09 ]

ok , so mysqld can start.

Comment by Vladislav Vaintroub [ 2020-07-09 ]

But if the server does not startup, you'd have to provide error log. or Windows event log, the Application\MariaDB entries.

My crystal ball says that perhaps, you did not stop server with --innodb-fast-shutdown=0 previously. Therefore it does not come up. But it can be wrong.

Comment by Stefan Marczuk [ 2020-07-10 ]

I tried on several computers. The same is happening everywhere.

I have added an extract from the event log below:

Name der fehlerhaften Anwendung: mysqld.exe, Version: 10.5.4.0, Zeitstempel: 0x5ef224e3
Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.19041.1, Zeitstempel: 0xbd1e2564
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000024e28
ID des fehlerhaften Prozesses: 0x1444
Startzeit der fehlerhaften Anwendung: 0x01d656abf9895681
Pfad der fehlerhaften Anwendung: d:\Programme\MySQL\bin\mysqld.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\ucrtbase.dll

Comment by Vladislav Vaintroub [ 2020-07-10 ]

I'd rather had the error log with full info, but the crystal call tells me you were using deprecated
mysqld --install <service_name> , not the blessed mysql_install_db.exe

This is broken in 10.5.4, and corrected later. https://jira.mariadb.org/browse/MDEV-23038 has details, and workaround
https://jira.mariadb.org/browse/MDEV-23038?focusedCommentId=158259&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-158259

Comment by Vladislav Vaintroub [ 2020-07-10 ]

I'm closing this, because of strong suspicion of the duplicate. If there was anything else please provide a reproducible test case.

Generated at Thu Feb 08 09:20:03 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.