← Back to team overview

maria-discuss team mailing list archive

Re: why stdout? -> [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096

 


Am 06.08.2015 um 14:25 schrieb Sergei Golubchik:
Hi, Reindl!

On Aug 06, Reindl Harald wrote:

Am 06.08.2015 um 13:56 schrieb Sergei Golubchik:
Hi, Reindl!

On Aug 06, Reindl Harald wrote:
Aug  6 12:24:24 testserver mysqld: 150806 12:24:24 [Note]
/usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096 ...

why is this now stdout instead mysql logs?

I cannot repeat it.
Here:

$ ./mysqld >out 2>err &
$ grep starting err out
err:150806 13:53:24 [Note] /home/serg/maria/sql/mysqld (mysqld 10.0.21-MariaDB-debug) starting as process 22001 ...
^^^
[root@rh:~]$ > /var/log/messages
[root@rh:~]$ > /var/log/mysql_error.log
[root@rh:~]$ systemctl restart mysqld
[root@rh:~]$ cat /var/log/mysql_error.log
[root@rh:~]$ cat /usr/lib/systemd/system/mysqld.service
[builduser@buildserver:~]$ cat /rpmbuild/SPECS/mariadb.spec

Well, I've shown you a minimal test. It proves that mysqld does not
write that line into stdout. You're using your own packaging and systemd
service scripts. Perhaps something's wrong with them? I don't know
what and where is wrong, I can only state with certainty that mysqld
does *not* prints "starting as process" line to stdout.

then it's maybe stderr, journald catchs all stderr and stdout stuff and forwards it to syslog, but why only *that one* message don't end in "log-error = /var/log/mysql_error.log" as specified in "my.cnf"

the point is that echo something to stdout/stderr in case of a background service burries the lines and the only reason they appear at all is journald collecting that stuff and forwards it to syslog

they should go to "log-error" as all other messages



Attachment: signature.asc
Description: OpenPGP digital signature


Follow ups

References