Hi ! I've got a problem which already occurred twice in a few days (ISPConfig 3.1.13 on Debian 9 Stretch from perfect setup guide). At first sight looks problem connecting to mariadb (10.1.37-MariaDB-0+deb9u1). However, mariadb seems to be running OK from ps aux except: Code: 2019-01-21 23:57:24 140551975178688 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB. .... 2019-01-22 0:00:02 140551928416000 [ERROR] mysqld: Table './dbispconfig/mail_traffic' is marked as crashed and should be repaired 2019-01-22 0:00:02 140551928416000 [Warning] Checking table: './dbispconfig/mail_traffic' Which was automatically repaired (checked table status from command line). What could be cause of such strange behavior? Everything worked fine for very long time. Thanks in advance. Code: Jan 21 23:17:10 mail dovecot: lda([email protected]): Error: userdb lookup([email protected]): Request timed out Jan 21 23:17:10 mail dovecot: lda: Fatal: Internal error occurred. Refer to server log for more information. Jan 21 23:17:10 mail dovecot: lda([email protected]): Error: userdb lookup([email protected]): Request timed out Jan 21 23:17:10 mail dovecot: lda: Fatal: Internal error occurred. Refer to server log for more information. an 21 23:46:59 mail postfix/trivial-rewrite[1694]: warning: virtual_mailbox_domains lookup failure Jan 21 23:47:00 mail postfix/error[1707]: warning: connect to mysql server 127.0.0.1: Can't connect to MySQL server on '127.0.0.1' (111 "Connection refused") Jan 21 23:47:00 mail postfix/error[1707]: warning: fast_flush_domains: mysql:/etc/postfix/mysql-virtual_relaydomains.cf: table lookup problem Jan 21 23:47:00 mail postfix/error[1707]: warning: D9C3D3C5172: flush service failure Jan 21 23:47:01 mail postfix/error[1707]: warning: fast_flush_domains: mysql:/etc/postfix/mysql-virtual_relaydomains.cf: table lookup problem Jan 21 23:47:01 mail postfix/error[1707]: warning: F007E3C4DC6: flush service failure
Created "/etc/cron.d/mysql_autorestart" with Code: * * * * * root test -x /usr/sbin/service mysql status || /usr/sbin/service mysql restart Really strange, never had any issue with mysql for many years of ISPConfig usage.
As mentioned in your other post, I would try to rais max_connections and max_suer_connections values first. Do you have any harddisk errors? Checking the smart value of the harddisks and doing a filesystem check might be good too.
