Why does MySQL fail to start with a custom `log_error` location?

dmitrii_fediuk · June 15, 2024, 2:43pm

dmitrii_fediuk · June 15, 2024, 11:10pm

Step 1

Adjust AppArmor settings for MySQL:

thehcginstitute-com/167.71.186.128/blob/2024-06-16/etc/apparmor.d/usr.sbin.mysqld#L72-L81


      
          # 2024-06-16 Dmitrii Fediuk https://upwork.com/fl/mage2pro
          # 1.1) "MySQL fails to start with a custom `log_error` location":
          # https://github.com/thehcginstitute-com/167.71.186.128/issues/20
          # 1.2) "Why does MySQL fail to start with a custom `log_error` location?": https://df.tips/t/2223
          # 2.1) "«Status: "Server shutdown complete"» / «Error: 9 (Bad file descriptor)» in MySQL for a custom `log_error` location":
          # https://github.com/thehcginstitute-com/167.71.186.128/issues/17
          # 2.2) "How did I fix «Status: "Server shutdown complete"» / «Error: 9 (Bad file descriptor)»
          # in MySQL for a custom `log_error` location?": https://df.tips/t/2222
            /var/log/_mage2pro/ r,
            /var/log/_mage2pro/** rw,

Step 2

Reload AppArmor security profiles