Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Logrotate not working with proxy protocol

Description

Description: The log rotation functionality ceases to operate correctly when the proxy_protocol_networks=* option is enabled in the XtraDBCluster Custom Resource configuration. This issue manifests as an error during the execution of the postrotate-mysql.sh script, subsequently preventing logs from being collected. Additionally, this results in the deletion of the /var/lib/mysql/mysqld-error.log file, halting the logcollector's ability to forward logs to stdout.

Temporary Solution: Removing the proxy_protocol_networks option from the configuration restores log rotation functionality. However, a permanent fix is required to support the proxy protocol without impacting log rotation.

Environment

None

Activity

Show:

Julio Pasinatto August 12, 2024 at 6:13 PM

Verified fix is working.
Reproduced with:

configuration: | [mysqld] proxy_protocol_networks=*

And by forcing log rotation, to trigger postrotate-mysql.sh with:

kubectl exec -it cluster1-pxc-1 -c logrotate -n test -- logrotate -f -s /opt/percona/logrotate/logrotate.status /opt/percona/logrotate/logrotate-mysql.conf

does not produce the error anymore, as 1.14.0:

error: error running shared postrotate script for '/var/lib/mysql/[!G]*.log '

Slava Sarzhan March 7, 2024 at 8:31 AM

The issue was fixed.

Done

Details

Assignee

Reporter

Labels

Needs QA

Yes

Fix versions

Affects versions

Priority

Smart Checklist

Created March 6, 2024 at 9:55 PM
Updated August 21, 2024 at 8:03 AM
Resolved August 12, 2024 at 6:14 PM

Flag notifications