Logrotate not working with proxy protocol
General
Escalation
General
Escalation
Description
Environment
None
Activity
Show:

Julio Pasinatto August 12, 2024 at 6:13 PM
Verified fix is working.
Reproduced with:
And by forcing log rotation, to trigger postrotate-mysql.sh with:
does not produce the error anymore, as 1.14.0:

Slava Sarzhan March 7, 2024 at 8:31 AM
The issue was fixed.
Done
Details
Assignee
Julio PasinattoJulio PasinattoReporter
Philipp MalkmusPhilipp MalkmusLabels
Needs QA
YesFix versions
Affects versions
Priority
Low
Details
Details
Assignee

Reporter
Labels
Needs QA
Yes
Fix versions
Affects versions
Priority
Smart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Smart Checklist

Open 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
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 thepostrotate-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.