• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Resolved mysql in logrotate.d wrong path?

Azurel

Silver Pleskian
‪CentOS Linux 7.5.1804 (Core)‬ Product Plesk Onyx Version 17.8.11 Update #32

#1

I see that /etc/logrotate.d/mysql was created 31.10.2018, so its must created/changed with a plesk update?
Code:
/var/lib/mysql/mysqld.log {
        # create 600 mysql mysql
        notifempty
    daily
        rotate 3
        missingok
        compress
    postrotate
    # just if mysqld is really running
    if test -x /usr/bin/mysqladmin && \
       /usr/bin/mysqladmin ping &>/dev/null
    then
       /usr/bin/mysqladmin --local flush-error-log \
              flush-engine-log flush-general-log flush-slow-log
    fi
    endscript
}
with /var/lib/mysql/mysqld.log, but this file not exists. The right path in my.cnf is:
Code:
[mysqld_safe]
log-error=/var/log/mariadb/mariadb.log


#2
I missing a rotation for /var/log/mysql-slow.log, because this file is (for me) 400MB big.
 
I see /etc/logrotate.d/mariadb file with your path /var/log/mariadb/mariadb.log instead of /etc/logrotate.d/mysql on my Plesk Onyx 17.8 server installed on CentOS7.
What is output of

# rpm -qf /etc/logrotate.d/mysql

?
 
Back
Top