Hi
We noticed something strange on one of our cpanel servers. We increased memory on the server even though it does not seem to really be the cause. We installed litespeed and upgrade the licence to a higher one and we even installed LSCache. Still no lock.
%wa is very low around under 1 normally 0.8
CPu is low aswell around 1.2%
Enough diskspace as we use RAID 10 Enterprise HDD disks but as stated above it;s not %wa issue
Now looking at top we don't see really problematic or overusage activity on any process. Mysql does use over 22% of the memory and sometimes 50% but there a;ways seems to be more memory available left.
I however noticed the following now after I noticed mysql crashed:
160123 17:08:46 [Warning] Checking table: './crazystu_wp/ahc_recent_visitors'
160123 17:08:46 [ERROR] mysqld: Table './crazystu_wp/ahc_hits' is marked as crashed and should be repaired
160123 17:08:46 [Warning] Checking table: './crazystu_wp/ahc_hits'
160123 17:08:46 [ERROR] mysqld: Table './crazystu_wp/ahc_visitors' is marked as crashed and should be repaired
160123 17:08:46 [Warning] Checking table: './crazystu_wp/ahc_visitors'
160123 17:08:46 [ERROR] mysqld: Table './crazystu_wp/ahc_visits_time' is marked as crashed and should be repaired
160123 17:08:46 [Warning] Checking table: './crazystu_wp/ahc_visits_time'
160123 17:08:46 [ERROR] mysqld: Table './crazystu_wp/ahc_browsers' is marked as crashed and should be repaired
160123 17:08:46 [Warning] Checking table: './crazystu_wp/ahc_browsers'
160123 17:08:51 [ERROR] Error in accept: Too many open files
That link in bold is what amazes me. Running a SQL query this is what is set:
MariaDB [(none)]> show variables like '%open%';
+-------------------+---------+
| Variable_name | Value |
+-------------------+---------+
| have_openssl | YES |
| innodb_open_files | 4096 |
| open_files_limit | 1024000 |
| table_open_cache | 4096 |
+-------------------+---------+
4 rows in set (0.00 sec)
As you can see we increased the open files limit to a very high a mount already so its not that.
Could it be the innodb_open_files and table_open_files that returns this error aswell? Should we increase that aswell.
We noticed something strange on one of our cpanel servers. We increased memory on the server even though it does not seem to really be the cause. We installed litespeed and upgrade the licence to a higher one and we even installed LSCache. Still no lock.
%wa is very low around under 1 normally 0.8
CPu is low aswell around 1.2%
Enough diskspace as we use RAID 10 Enterprise HDD disks but as stated above it;s not %wa issue
Now looking at top we don't see really problematic or overusage activity on any process. Mysql does use over 22% of the memory and sometimes 50% but there a;ways seems to be more memory available left.
I however noticed the following now after I noticed mysql crashed:
160123 17:08:46 [Warning] Checking table: './crazystu_wp/ahc_recent_visitors'
160123 17:08:46 [ERROR] mysqld: Table './crazystu_wp/ahc_hits' is marked as crashed and should be repaired
160123 17:08:46 [Warning] Checking table: './crazystu_wp/ahc_hits'
160123 17:08:46 [ERROR] mysqld: Table './crazystu_wp/ahc_visitors' is marked as crashed and should be repaired
160123 17:08:46 [Warning] Checking table: './crazystu_wp/ahc_visitors'
160123 17:08:46 [ERROR] mysqld: Table './crazystu_wp/ahc_visits_time' is marked as crashed and should be repaired
160123 17:08:46 [Warning] Checking table: './crazystu_wp/ahc_visits_time'
160123 17:08:46 [ERROR] mysqld: Table './crazystu_wp/ahc_browsers' is marked as crashed and should be repaired
160123 17:08:46 [Warning] Checking table: './crazystu_wp/ahc_browsers'
160123 17:08:51 [ERROR] Error in accept: Too many open files
That link in bold is what amazes me. Running a SQL query this is what is set:
MariaDB [(none)]> show variables like '%open%';
+-------------------+---------+
| Variable_name | Value |
+-------------------+---------+
| have_openssl | YES |
| innodb_open_files | 4096 |
| open_files_limit | 1024000 |
| table_open_cache | 4096 |
+-------------------+---------+
4 rows in set (0.00 sec)
As you can see we increased the open files limit to a very high a mount already so its not that.
Could it be the innodb_open_files and table_open_files that returns this error aswell? Should we increase that aswell.