[MDEV-9054] Logged InnoDB Notes have Syslog Priority 3 (Error) Created: 2015-11-01  Updated: 2022-09-12  Resolved: 2022-09-12

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: 10.0.22
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Michael Herold Assignee: Sergei Golubchik
Resolution: Won't Fix Votes: 0
Labels: logging
Environment:

Debian Jessie


 Description   

Only observed on startup. Messages seem irrelevant but have priority error. Extract:

[Note] InnoDB: Using mutexes to ref count buffer pool pages
 
[Note] InnoDB: The InnoDB memory heap is disabled
 
[Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
 
[Note] InnoDB: Memory barrier is not used



 Comments   
Comment by Elena Stepanova [ 2015-11-02 ]

It's not just these 4 lines, and not just InnoDB, but apparently the whole MySQL/MariaDB error log. "3 err" below are "syslogseverity syslogseverity-text". 

Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] /usr/sbin/mysqld (mysqld 10.0.22-MariaDB-1~jessie) starting as process 7391 ...
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] InnoDB: Using mutexes to ref count buffer pool pages
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] InnoDB: The InnoDB memory heap is disabled
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] InnoDB: Memory barrier is not used
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] InnoDB: Compressed tables use zlib 1.2.8
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] InnoDB: Using Linux native AIO
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] InnoDB: Not using CPU crc32 instructions
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] InnoDB: Initializing buffer pool, size = 128.0M
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] InnoDB: Completed initialization of buffer pool
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] InnoDB: Highest supported file format is Barracuda.
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] InnoDB: 128 rollback segment(s) are active.
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] InnoDB: Waiting for purge to start
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1616787
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] Plugin 'FEEDBACK' is disabled.
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] Server socket created on IP: '127.0.0.1'.
 
Nov  2 01:23:01 3 err debian8 mysqld: 151102  1:23:01 [Note] /usr/sbin/mysqld: ready for connections.
 
Nov  2 01:23:01 3 err debian8 mysqld: Version: '10.0.22-MariaDB-1~jessie'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution

I would assume that's just because it's the error log, so whatever goes there is considered the error level for syslog; but I cannot judge whether it's acceptable or not conceptually.
otto, serg, can you advise on this?

Comment by Otto Kekäläinen [ 2015-11-02 ]

I don't know what to advice. To syslog you can log whatever you want. Currently at least on Debian mysqld logs quite a lot to syslog and that should be OK.

The file /etc/init.d/mysql defines:
ERR_LOGGER="logger -p daemon.err -t /etc/init.d/mysql -i"

and later on when mysql starts:
noformat
/usr/bin/mysqld_safe "${@:2}" 2>&1 >/dev/null | $ERR_LOGGER &
noformat

The logger priority daemon.err seems to be used then for all error messages.

With this structure there is not directly any mechanism built in to vary the log message priority level. If this is changes, then at least please focus on writing a good systemd file so that the systemd facilities would get messages with varying severity level.

There is also a separate /var/log/mysql/error.log which is mostly empty and that indeed gets contents only if there are errors. Current status for that seems OK to me too.

Comment by Sergei Golubchik [ 2022-09-12 ]

10.0 was EOLed in March 2019

Generated at Thu Feb 08 07:31:47 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.