maria-discuss team mailing list archive
Mailing list archive
Re: why stdout? -> [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096
Mailing-List mariadb <maria-discuss@xxxxxxxxxxxxxxxxxxx>
Reindl Harald <h.reindl@xxxxxxxxxxxxx>
Thu, 6 Aug 2015 12:59:31 +0200
the lounge interactive design
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
Am 06.08.2015 um 12:53 schrieb Guillaume Lefranc:
You don't give any meaningful context at all to solve this issue.
what is so hard to understand in "why is only this one message not
written to the mysqld log but goes ot stdout with recent releases?"
if you know what stdout means that's pretty clear
if you don't know you are hardly a developer who could change it
What's the distribution you using?
self built as all the years befor
What commands do you use to start
the same as always
surely, did you see the mysqld 10.0.20-MariaDB?
Where do you see this message?
in /var/log/messages as said *because* it's thrown to stdout which is
catched by systemd-journald while anything else goes to "log-error" from
2015-08-06 12:27 GMT+02:00 Reindl Harald <h.reindl@xxxxxxxxxxxxx
Aug 6 12:24:24 testserver mysqld: 150806 12:24:24 [Note]
/usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process
why is this now stdout instead mysql logs?
on systemd based distributions that spits now to the global syslog
and finally on machines restarting 2 instances every hour for backup
reasons it annoys
until 10.0.19 or 10.0.20 that was not this way
Description: OpenPGP digital signature