Details
Description
this annoying message don't belog to stdout and i have pointed this out years ago on the mailing list after the update which introduced it with a heatet discussion because most people spoke up didn't gasp what i am talking about
we have maraidb logfiles and so there is no point to spit out anything ond stdout which on other init systems won't be seen at all
Aug 14 04:02:41 backup-dbmail systemd[1]: Stopping MariaDB Replication...
Aug 14 04:02:43 backup-dbmail systemd[1]: Stopped MariaDB Replication.
Aug 14 04:10:18 backup-dbmail systemd[1]: Starting MariaDB Replication...
Aug 14 04:10:18 backup-dbmail mysqld[496132]: 2019-08-14 4:10:18 140369542626816 [Note] /usr/libexec/mysqld (mysqld 10.2.26-MariaDB) starting as process 496132 ...
Aug 14 04:10:20 backup-dbmail systemd[1]: Started MariaDB Replication.
Attachments
Issue Links
- is caused by
-
MDEV-9593 Print the real version in the error log
- Closed
- relates to
-
MDEV-6873 On startup please make MariaDB report it's version number
- Closed
-
MDEV-9593 Print the real version in the error log
- Closed
-
MDEV-10967 Print the real version in the error log #2
- Closed
-
MDEV-17093 Print version_source_revision in the error log upon server startup
- Closed
-
MDEV-20287 Have the server process print a "starting mysql" message before first actual log message
- Closed
-
MDEV-21711 Log: "Server Version xx.xx.xx starting" as very first thing when an instance is starting
- Open
-
MDEV-10648 mysqld --log-error prints on stdout at start
- Confirmed
-
MDEV-21046 Print server version to error log instead of stderr during startup process
- Open