[MDEV-23555] support logging to syslog Created: 2020-08-24  Updated: 2020-09-15

Status: Open
Project: MariaDB Server
Component/s: Server
Fix Version/s: None

Type: Task Priority: Major
Reporter: Reindl Harald Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None


 Description   

don't set "log-error" on a modern system to get everything mysqld says including MDEV-20344 into a specific logfile is a dirty workaround because you spit out date/timestamp which clutters logs

MySQL supports a syslog option for years now

Aug 23 13:46:52 backupserver mysqld[489193]: 2020-08-23 13:46:52 7 [Note] Slave SQL thread exiting, replication stopped in log 'bin.000060' at position 109456465

-------------------------

https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_log_syslog
[ERROR] /usr/libexec/mysqld: unknown variable 'log-syslog=1'

https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_log_error_verbosity

2020-08-16 22:17:46 0 [ERROR] /usr/libexec/mysqld: unknown variable
'log_error_verbosity=2'



 Comments   
Comment by Sergei Golubchik [ 2020-09-15 ]

--log-warnings increases the verbosity of the error log. Apparently it was renamed in MySQL: https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_log_warnings

We should add support for --log-syslog, I agree.

Generated at Thu Feb 08 09:23:17 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.