MySQL service going down regularly

I keep getting notification emails for failed mysql service or mysql service down. This is happening like a couple of times a week. The email includes messages like these: [QUOTE]The subprocess "/usr/local/cpanel/scripts/restartsrv_mysql" reported error number 2 when it ended.
The email indicates serveral tables marked as crashed like this message: [QUOTE][ERROR] mysqld: Table 'Logs' is marked as crashed and should be repaired
The service seems to automatically recover immediately. We haven't noticed any significant disruption to the websites. I get a "recovered" email notification with these messages: [QUOTE]The 'mysql' service passed the check: mariadb (/usr/sbin/mysqld --basedir=/usr) is running as mysql with PID 5430 (systemd+/proc check method).
[QUOTE][Warning] Could not increase number of max_open_files to more than 40000 (request: 81671)
When I go and check the tables that were initially marked as crashed, their status is now shown as OK. When I check the log file in /var/lib/mysql/mysql_error.log, I don't see anything significant other than the tables marked as crashed as mentioned above. I would like to know why 'mysql' service keeps going down almost every week. Is this due to the max_open_files limit? Do I need to increase this?