[MDEV-12275] debian-start spams the syslog after an upgrade Created: 2017-03-15  Updated: 2022-05-05  Resolved: 2022-05-05

Status: Closed
Project: MariaDB Server
Component/s: Platform Debian, Scripts & Clients
Affects Version/s: 10.0, 10.3
Fix Version/s: 10.3.35, 10.4.25, 10.5.16, 10.6.8, 10.7.4, 10.8.3, 10.9.1

Type: Bug Priority: Minor
Reporter: Jean Weisbuch Assignee: Tuukka Pasanen
Resolution: Fixed Votes: 0
Labels: SySV, beginner-friendly, packaging
Environment:

Debian Jessie amd64

Issue Links:
Relates
relates to MDEV-12576 Upgrade MariaDB 10.0 from Distro to 1... Closed

 Description   

After upgrading MariaDB 10.0 using the MariaDB repository (even a minor upgrade), debian-start.sh executes mysql_upgrade and sends its output to the syslog.

The default behavior of mysql_upgrade is to output "database.table OK" for each tables that didnt require an upgrade.
The server i did upgrade have more than 200000 tables, which means that more than 200000 log lines are added to the syslog that does just states that nothing has been done.

Suggested fix : Add '--silent' to the call of "mysql_upgrade" which should only log tables that have been upgraded.

 Comments   
Comment by Tuukka Pasanen [ 2022-03-21 ]

Is there any down sides that you add '--silent' to upgrade? otto Can you come any downside that user can't see huge logs?

Comment by Otto Kekäläinen [ 2022-03-21 ]

I don't know. Do we have a normal output and --silent output examples to
view and compare to see what they reveal/hide?

Comment by Tuukka Pasanen [ 2022-04-04 ]

Ok I need to test what test suppress

Comment by Tuukka Pasanen [ 2022-05-03 ]

Testing this on systemd system is not easy but this should not make any harm

Comment by Tuukka Pasanen [ 2022-05-03 ]

danblack could you take look on PR.

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