[MDEV-21586] Unable to start the server after the update. Created: 2020-01-29  Updated: 2023-11-27  Resolved: 2020-01-30

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.2.31, 10.3.22, 10.4.12
Fix Version/s: 10.2.32, 10.3.23, 10.4.13

Type: Bug Priority: Blocker
Reporter: Frank Assignee: Vladislav Vaintroub
Resolution: Fixed Votes: 0
Labels: None
Environment:

CentOS 7.7 x86_64

Issue Links:
Duplicate
duplicates MDEV-21600 MariaDB 10.2.31, 10.3.22, 10.4.12 as ... Closed
Problem/Incident
is caused by MDEV-11345 Compile english error messages into m... Closed

 Description   

Hello,
version 10.2.30 works as expected.
But after update to 10.2.31, the can't start anymore.
In the log files, no errors are logged.
The only log that I can see is:

Jan 29 07:21:53 XXX mysqld[22954]: 2020-01-29  7:21:53 140517213755584 [Note] /usr/sbin/mysqld (mysqld 10.2.31-MariaDB) starting as process 22954 ...
 
Jan 29 07:21:53 XXX mysqld[22954]: 2020-01-29  7:21:53 140517213755584 [ERROR] Aborting

The only solution was to downgrade to 10.2.30.

 Comments   
Comment by Sergei Golubchik [ 2020-01-30 ]

Do you have lc_messages set in your my.cnf ? Like lc_messages=de_DE, for example?

Comment by Frank [ 2020-01-30 ]

Yes, I have found this setting in one of the config files, present under /etc/my.cnf.d/.
Was here something changed, that will break it?
If yes, then it will be very bad when such changes will be done in stable release stream like 10.1 or 10.2.

Comment by Sergei Golubchik [ 2020-01-30 ]

This bug was introduced in MDEV-11345. Sorry for this, it'll be fixed.

Comment by Dominique Ottello [ 2020-01-30 ]

Hi,
In the my.ini of versions 10.2.31, 10.3.22 and 10.4.12 in 32 and 64 bit, I removed the lc-messages and lc-messages-dir lines before compiling the InnoSetup installers.
Now, there are no more problems and it works the first time after installation.
As a result, it simplifies my task, no more need to manage the error language !
Also think about fixing the 10.5.0 versions that have the same problem.

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