We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From what happened in the user environment, after accelerating status hooks, mysql charm started to fail to log rotate
Having faster status hook should not fail the
Charm fails again and again to logrotate
mysql-k8s: 8.0/stable 180
Juju CLI: 3.6.0
Juju debug log:
unit-mysql-0: 13:43:13 ERROR unit.mysql/0.juju-log Failed command: commands=logrotate -f /etc/logrotate.d/flush_mysql_logs, user=None, group=None unit-mysql-0: 13:43:13 WARNING unit.mysql/0.juju-log Failed to rotate MySQL logs
juju ssh -m openstack --container mysql mysql/0 bash root@mysql-0:/# logrotate -f /etc/logrotate.d/flush_mysql_logs error: destination /var/log/mysql/archive_error/error.log-20241205_1344 already exists, skipping rotation error: destination /var/log/mysql/archive_general/general.log-20241205_1344 already exists, skipping rotation error: destination /var/log/mysql/archive_audit/audit.log-20241205_1344 already exists, skipping rotation
^C
Deleting the files (log lost then) allowed the charm to resume operations.
The text was updated successfully, but these errors were encountered:
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-6156.
This message was autogenerated
Sorry, something went wrong.
No branches or pull requests
Steps to reproduce
From what happened in the user environment, after accelerating status hooks, mysql charm started to fail to log rotate
Expected behavior
Having faster status hook should not fail the
Actual behavior
Charm fails again and again to logrotate
Versions
mysql-k8s: 8.0/stable 180
Juju CLI: 3.6.0
Log output
Juju debug log:
^C
Additional context
Deleting the files (log lost then) allowed the charm to resume operations.
The text was updated successfully, but these errors were encountered: