Here is what our team found in that ticket:
"I appreciate your patience while I look into this issue. It seems at some point, the mysql_config_editor program led to the creation of the "/root/.mylogin.cnf" file, which is essentially an encoded .my.cnf file that will take precedence over an existing .my.cnf file if it exists.
[20:53:29 [email protected] ~]cPs# cat /root/.mylogin.cnf
[20:53:42 [email protected] ~]cPs# stat /root/.mylogin.cnf
Size: 24 Blocks: 8 IO Block: 4096 regular file
Device: fd01h/64769d Inode: 12731 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 27/ mysql) Gid: ( 27/ mysql)
Access: 2022-03-26 20:53:42.098070493 -0400
Modify: 2020-11-02 04:15:48.716250029 -0500
Change: 2022-03-26 20:53:14.599820255 -0400
I went ahead and moved this file to the directory you see in the output below:
[20:59:13 [email protected] ~]cPs# mkdir -vp /root/cptechs/94429335
mkdir: created directory ‘/root/cptechs’
mkdir: created directory ‘/root/cptechs/94429335’
[21:12:27 [email protected] ~]cPs# mv -v /root/.mylogin.cnf /root/cptechs/94429335/
‘/root/.mylogin.cnf’ -> ‘/root/cptechs/94429335/.mylogin.cnf’
I believe this will fix the issue; if you keep receiving emails regarding database corruption, feel free to reach out to us. If you have any other questions or concerns, cPanel support is always here to help. It was my pleasure working on this issue with you, and I hope you are satisfied with the experience."
At this point we haven't seen any additional emails sent from the server.