[MDEV-20287] Have the server process print a "starting mysql" message before first actual log message Created: 2019-08-08 Updated: 2023-04-27 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Server |
| Affects Version/s: | 10.2.26, 10.1.41, 10.3.17, 10.4.7 |
| Fix Version/s: | 10.4 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Hartmut Holzgraefe | Assignee: | Oleksandr Byelkin |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Description |
|
Right now server log output just starts with whatever log message comes out first. Depending on configuration typically the first startup message you'll see will be
But that's nothing you can rely on. Especially in cases where mysqld was killed hard (kill -9, OOM kill, machine failure), there's no clear "old instance messages end here, new instance log starts" distinction that can easily be searched for. |
| Comments |
| Comment by Hartmut Holzgraefe [ 2019-10-21 ] |
|
Would also be nice to have the version number in the very first and very last message, to make it more easy to spot where a version change happened in a larger error log ... |
| Comment by Geoff Montee (Inactive) [ 2020-02-12 ] |
|
MDEV-21046 is related to this as well. |
| Comment by Daniel Black [ 2022-10-26 ] |
|
Corrected in https://github.com/MariaDB/server/pull/1979 |