| Bug #84074 | Wrong binary path in Apparmor profile | ||
|---|---|---|---|
| Submitted: | 6 Dec 2016 9:16 | Modified: | 17 Jul 2017 22:38 |
| Reporter: | Mihaly Arva-Toth | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Router | Severity: | S3 (Non-critical) |
| Version: | 2.0.4 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | apparmor | ||
[14 Dec 2016 11:56]
MySQL Verification Team
Hello Mihaly Arva-Toth, Thank you for the report and feedback! Thanks, Umesh
[17 Jul 2017 22:38]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL Router 2.1.4 release, and here's the changelog entry: The commercial version of MySQL Router did not have the correct setting for the AppArmor profile configuration file /etc/apparmor.d/usr.sbin.mysqlrouter. Thank you for the bug report.
Description: $ head -5 /etc/apparmor.d/usr.sbin.mysqlrouter # vim:syntax=apparmor #include <tunables/global> /usr/sbin/mysqld { . . . Path of mysqlrouter is invalid. How to repeat: If you have a real running mysqld instance on the server, this apparmor profile will totaly unavailable mysqld process. Suggested fix: Use /usr/sbin/mysqlrouter in Apparmor profile config file.