Hello I need help for this problem. I have not connected to the ISPConfig panel and the Wordpress panel of the web for more than 1 month After 1 month when I go to connect, I can't establish connection 1- If I try to connect to the ISPConfig panel by its address https://51.75.254.67:8080/ the screen stays thinking and blank, it does not connect, it does not show any message, just a white screen 2- If the connection is made by wordpress to the web at the address https://caminseivissa.org/wp-admin/, it gives me an error Error establishing a database connection. Nothing has been modified, for 1 month I had not connected The server is an OVH VPS I have sent a ticket to OVH and they answer me that the server responds with the following data # ping -c 4 vps622713.ovh.net PING vps622713.ovh.net (51.75.254.67) 56(84) bytes of data. 64 bytes from 67.ip-51-75-254.eu (51.75.254.67): icmp_seq=1 ttl=55 time=0.659 ms 64 bytes from 67.ip-51-75-254.eu (51.75.254.67): icmp_seq=2 ttl=55 time=0.761 ms 64 bytes from 67.ip-51-75-254.eu (51.75.254.67): icmp_seq=3 ttl=55 time=0.782 ms 64 bytes from 67.ip-51-75-254.eu (51.75.254.67): icmp_seq=4 ttl=55 time=0.629 ms nmap vps622713.ovh.net Starting Nmap 7.80 ( https://nmap.org ) at 2022-11-15 08:45 UTC Nmap scan report for vps622713.ovh.net (51.75.254.67) Host is up (0.00093s latency). rDNS record for 51.75.254.67: 67.ip-51-75-254.eu Not shown: 985 closed ports PORT STATE SERVICE 21/tcp open ftp 22/tcp open ssh 25/tcp open smtp 53/tcp open domain 80/tcp open http 110/tcp open pop3 143/tcp open imap 443/tcp open https 465/tcp open smtps 587/tcp open submission 993/tcp open imaps 995/tcp open pop3s 3306/tcp open mysql 8080/tcp open http-proxy 8081/tcp open blackice-icecap Nmap done: 1 IP address (1 host up) scanned in 0.33 seconds can someone help me with this problem Thanks for your help Enric
Please run the test script as root user and post the result: https://forum.howtoforge.com/threads/please-read-before-posting.58408/
script the result PHP Warning: mysqli_connect(): (HY000/2002): No such file or directory in /root/htf-common-issues.php on line 288 ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory") ##### SCRIPT FINISHED ##### Results can be found in htf_report.txt To view results use your favourite text editor or type 'cat htf_report.txt | more' on the server console. If you want to see the non-anonymized output start the script with --debug as parameter (php -q htf-common-issues.php --debug).
Ok, so MySQL/MariaDB server is not started. Start it and try again. And please post the content of the htf_report.txt file.
ok this is the result ##### SERVER ##### IP-address (as per hostname): ***.***.***.*** [WARN] could not determine server's ip address by ifconfig [INFO] OS version is Debian GNU/Linux 9.13 (stretch) [INFO] uptime: 19:08:06 up 2:12, 1 user, load average: 0.06, 0.10, 0.09 [INFO] memory: total used free shared buff/cache available Mem: 1.9G 1.5G 92M 55M 368M 264M Swap: 0B 0B 0B [INFO] ISPConfig is installed. ##### ISPCONFIG ##### ISPConfig version is 3.2.8p1 [WARN] Could not connect to mysql with given user data. [WARN] Could not use mysql command line to connect to the database. Check your mysql config! ##### VERSION CHECK ##### [INFO] php (cli) version is 7.0.33-57+0~20211119.61+debian9~1.gbp5d8ba5 [INFO] php-cgi (used for cgi php in default vhost!) is version 7.0.33 [WARN] Your php-cgi in ' . /usr/bin/php-cgi . ' seems to be outdated and might contain known exploits. ##### PORT CHECK ##### ##### MAIL SERVER CHECK #### ##### RUNNING SERVER PROCESSES ##### [INFO] I found the following web server(s): Apache 2 (PID 16329) [INFO] I found the following mail server(s): Postfix (PID 7724) [INFO] I found the following pop3 server(s): Dovecot (PID 1027) [INFO] I found the following imap server(s): Dovecot (PID 1027) [INFO] I found the following ftp server(s): PureFTP (PID 8414) ##### LISTENING PORTS ##### (only () Local (Address) [anywhere]:25 (7724/master) [localhost]:953 (909/named) [anywhere]:4190 (1027/dovecot) [anywhere]:993 (1027/dovecot) [anywhere]:995 (1027/dovecot) [localhost]:10025 (7724/master) [localhost]:10027 (7724/master) [anywhere]:587 (7724/master) [localhost]:11211 (947/memcached) [anywhere]:110 (1027/dovecot) [anywhere]:143 (1027/dovecot) [anywhere]:465 (7724/master) [anywhere]:21 (8414/pure-ftpd) ***.***.***.***:53 (909/named) [localhost]:53 (909/named) [anywhere]:22 (962/sshd) *:*:*:*::*:25 (7724/master) *:*:*:*::*:953 (909/named) *:*:*:*::*:443 (16329/apache2) *:*:*:*::*:4190 (1027/dovecot) *:*:*:*::*:993 (1027/dovecot) *:*:*:*::*:995 (1027/dovecot) *:*:*:*::*:587 (7724/master) [localhost]10 (1027/dovecot) [localhost]43 (1027/dovecot) *:*:*:*::*:80 (16329/apache2) *:*:*:*::*:8080 (16329/apache2) *:*:*:*::*:465 (7724/master) *:*:*:*::*:8081 (16329/apache2) *:*:*:*::*:21 (8414/pure-ftpd) *:*:*:*::*:53 (909/named) *:*:*:*::*:22 (962/sshd) ##### IPTABLES ##### Chain INPUT (policy ACCEPT) target prot opt source destination f2b-pureftpd tcp -- [anywhere]/0 [anywhere]/0 multiport dports 21 f2b-postfix-sasl tcp -- [anywhere]/0 [anywhere]/0 multiport dports 25 f2b-sshd tcp -- [anywhere]/0 [anywhere]/0 multiport dports 22 Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain f2b-postfix-sasl (1 references) target prot opt source destination RETURN all -- [anywhere]/0 [anywhere]/0 Chain f2b-pureftpd (1 references) target prot opt source destination RETURN all -- [anywhere]/0 [anywhere]/0 Chain f2b-sshd (1 references) target prot opt source destination REJECT all -- ***.***.***.*** [anywhere]/0 reject-with icmp-port-unreachable REJECT all -- ***.***.***.*** [anywhere]/0 reject-with icmp-port-unreachable RETURN all -- [anywhere]/0 [anywhere]/0 ##### LET'S ENCRYPT ##### Certbot is installed in /usr/bin/letsencrypt
I have already tried what you say and it presents this error <<Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.>> the mysqld.sock file seems to have disappeared from the var/run/mysqld/ path
The error message tells you what to do next. I don't understand I don't know how the database works and I can lose the web data. Is there somewhere that explains what to do?
Here is the error message you posted: It tells you to run two commands to find out why MySQL or MariaDB fails: systemctl status mariadb.service journalctl -xe and that's what you should do next. It is important to run these right after you tried to start MySQL. So try starting MySQL again and then run these commands and post what they show you on the screen. In addition to these commands, also run the command: df -h and post the output as well. Makes not much sense as you have not found out why it fails yet, so there is a good chance that a reinstall will not fix things but make things worse.
Ok following your instructions I post what you ask me << systemctl status mariadb.service >> ● mariadb.service - MariaDB 10.1.48 database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: Active: failed (Result: exit-code) since Wed 2022-11-16 00:33:53 CET; 10h ago Docs: man:mysqld(8) https://mariadb.com/kb/en/library/systemd/ Process: 21098 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_W Process: 21018 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VA Process: 21013 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_STAR Process: 21012 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/r Main PID: 21098 (code=exited, status=1/FAILURE) Status: "MariaDB server is down" Nov 16 00:33:50 vps622713 systemd[1]: Starting MariaDB 10.1.48 database server.. Nov 16 00:33:50 vps622713 mysqld[21098]: 2022-11-16 0:33:50 140499980205440 [No Nov 16 00:33:53 vps622713 systemd[1]: mariadb.service: Main process exited, code Nov 16 00:33:53 vps622713 systemd[1]: Failed to start MariaDB 10.1.48 database s Nov 16 00:33:53 vps622713 systemd[1]: mariadb.service: Unit entered failed state Nov 16 00:33:53 vps622713 systemd[1]: mariadb.service: Failed with result 'exit- << journalctl -xe >> Nov 16 10:49:52 vps622713 sshd[18165]: Received disconnect from 202.46.29.76 por Nov 16 10:49:52 vps622713 sshd[18165]: Disconnected from 202.46.29.76 port 50666 Nov 16 10:50:01 vps622713 CRON[18172]: pam_unix(cron:session): session opened fo Nov 16 10:50:01 vps622713 CRON[18171]: pam_unix(cron:session): session opened fo Nov 16 10:50:01 vps622713 CRON[18170]: pam_unix(cron:session): session opened fo Nov 16 10:50:01 vps622713 CRON[18173]: (root) CMD (/usr/local/ispconfig/server/c Nov 16 10:50:01 vps622713 CRON[18174]: (root) CMD (/usr/local/ispconfig/server/s Nov 16 10:50:01 vps622713 CRON[18175]: (getmail) CMD (/usr/local/bin/run-getmail Nov 16 10:50:01 vps622713 CRON[18170]: pam_unix(cron:session): session closed fo Nov 16 10:50:11 vps622713 CRON[18171]: pam_unix(cron:session): session closed fo Nov 16 10:50:22 vps622713 CRON[18172]: pam_unix(cron:session): session closed fo Nov 16 10:51:01 vps622713 CRON[18262]: pam_unix(cron:session): session opened fo Nov 16 10:51:01 vps622713 CRON[18261]: pam_unix(cron:session): session opened fo Nov 16 10:51:01 vps622713 CRON[18263]: (root) CMD (/usr/local/ispconfig/server/s Nov 16 10:51:01 vps622713 CRON[18264]: (root) CMD (/usr/local/ispconfig/server/c Nov 16 10:51:11 vps622713 CRON[18261]: pam_unix(cron:session): session closed fo Nov 16 10:51:21 vps622713 CRON[18262]: pam_unix(cron:session): session closed fo Nov 16 10:52:01 vps622713 CRON[18347]: pam_unix(cron:session): session opened fo Nov 16 10:52:01 vps622713 CRON[18348]: pam_unix(cron:session): session opened fo Nov 16 10:52:01 vps622713 CRON[18349]: (root) CMD (/usr/local/ispconfig/server/s Nov 16 10:52:01 vps622713 CRON[18350]: (root) CMD (/usr/local/ispconfig/server/c Nov 16 10:52:11 vps622713 CRON[18347]: pam_unix(cron:session): session closed fo Nov 16 10:52:21 vps622713 CRON[18348]: pam_unix(cron:session): session closed fo lines 1015-1037/1037 (END) << df -h >> Filesystem Size Used Avail Use% Mounted on udev 967M 0 967M 0% /dev tmpfs 196M 21M 176M 11% /run /dev/sda1 20G 14G 5.1G 73% / tmpfs 979M 0 979M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 979M 0 979M 0% /sys/fs/cgroup /dev/loop0 64M 64M 0 100% /snap/core20/1634 /dev/loop1 115M 115M 0 100% /snap/core/13741 /dev/loop2 45M 45M 0 100% /snap/certbot/2511 /dev/loop3 64M 64M 0 100% /snap/core20/1695 /dev/loop4 45M 45M 0 100% /snap/certbot/2414 /dev/loop5 115M 115M 0 100% /snap/core/13886 Waiting to find the solution, I have put a static html page Thanks Enric
We need some more info on the cause of the mariadb crash here. You can check if there is a error.log set see: Code: mysqld --help --verbose | grep 'log-error' | tail -1 This will either output "log-error /var/log/...." or "log-error ", if there is no file specified after log-error it is not set. You can add the following line to the mariadb config to enable error logging: Code: log_error=/var/log/mysql/mariadb.err After that restart the service and post the output of /var/log/mysql/mariadb.err And please, post your Output in CODE Tags in the forum, and make sure to not cut them off as it seems like that happened in your last post.
Hello This is the result of what you request mysqld --help --verbose | grep 'log-error' | tail -1 Code: 2022-11-16 12:13:44 140005519871360 [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. 2022-11-16 12:13:44 140005519871360 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2022-11-16 12:13:44 140005519871360 [Note] InnoDB: The InnoDB memory heap is disabled 2022-11-16 12:13:44 140005519871360 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-11-16 12:13:44 140005519871360 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2022-11-16 12:13:44 140005519871360 [Note] InnoDB: Compressed tables use zlib 1.2.8 2022-11-16 12:13:44 140005519871360 [Note] InnoDB: Using Linux native AIO 2022-11-16 12:13:44 140005519871360 [Note] InnoDB: Using SSE crc32 instructions 2022-11-16 12:13:44 140005519871360 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2022-11-16 12:13:44 140005519871360 [Note] InnoDB: Completed initialization of buffer pool 2022-11-16 12:13:44 140005519871360 [Note] InnoDB: Highest supported file format is Barracuda. 2022-11-16 12:13:44 140005519871360 [Note] InnoDB: 128 rollback segment(s) are active. 2022-11-16 12:13:44 140005519871360 [Note] InnoDB: Waiting for purge to start 2022-11-16 12:13:44 140005519871360 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.49-89.0 started; log sequence number 27294131853 2022-11-16 12:13:44 140004898596608 [Note] InnoDB: Dumping buffer pool(s) not yet started 2022-11-16 12:13:45 140005519871360 [Note] Plugin 'FEEDBACK' is disabled. 2022-11-16 12:13:45 140005519871360 [Note] Recovering after a crash using tc.log 2022-11-16 12:13:45 140005519871360 [ERROR] Can't init tc log 2022-11-16 12:13:45 140005519871360 [ERROR] Aborting 2022-11-16 12:36:37 139686576160128 [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. 2022-11-16 12:36:37 139686576160128 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2022-11-16 12:36:37 139686576160128 [Note] InnoDB: The InnoDB memory heap is disabled 2022-11-16 12:36:37 139686576160128 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-11-16 12:36:37 139686576160128 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2022-11-16 12:36:37 139686576160128 [Note] InnoDB: Compressed tables use zlib 1.2.8 2022-11-16 12:36:37 139686576160128 [Note] InnoDB: Using Linux native AIO 2022-11-16 12:36:37 139686576160128 [Note] InnoDB: Using SSE crc32 instructions 2022-11-16 12:36:37 139686576160128 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2022-11-16 12:36:38 139686576160128 [Note] InnoDB: Completed initialization of buffer pool 2022-11-16 12:36:39 139686576160128 [Note] InnoDB: Highest supported file format is Barracuda. 2022-11-16 12:36:39 139686576160128 [Note] InnoDB: 128 rollback segment(s) are active. 2022-11-16 12:36:40 139686576160128 [Note] InnoDB: Waiting for purge to start 2022-11-16 12:36:40 139686576160128 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.49-89.0 started; log sequence number 27294131863 2022-11-16 12:36:40 139686022473472 [Note] InnoDB: Dumping buffer pool(s) not yet started 2022-11-16 12:36:40 139686576160128 [Note] Plugin 'FEEDBACK' is disabled. 2022-11-16 12:36:40 139686576160128 [Note] Recovering after a crash using tc.log 2022-11-16 12:36:40 139686576160128 [ERROR] Can't init tc log 2022-11-16 12:36:40 139686576160128 [ERROR] Aborting 2022-11-16 16:15:44 139887806762368 [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. 2022-11-16 16:15:44 139887806762368 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2022-11-16 16:15:44 139887806762368 [Note] InnoDB: The InnoDB memory heap is disabled 2022-11-16 16:15:44 139887806762368 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-11-16 16:15:44 139887806762368 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2022-11-16 16:15:44 139887806762368 [Note] InnoDB: Compressed tables use zlib 1.2.8 2022-11-16 16:15:44 139887806762368 [Note] InnoDB: Using Linux native AIO 2022-11-16 16:15:44 139887806762368 [Note] InnoDB: Using SSE crc32 instructions 2022-11-16 16:15:44 139887806762368 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2022-11-16 16:15:44 139887806762368 [Note] InnoDB: Completed initialization of buffer pool 2022-11-16 16:15:44 139887806762368 [Note] InnoDB: Highest supported file format is Barracuda. 2022-11-16 16:15:45 139887806762368 [Note] InnoDB: 128 rollback segment(s) are active. 2022-11-16 16:15:45 139887806762368 [Note] InnoDB: Waiting for purge to start 2022-11-16 16:15:45 139887806762368 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.49-89.0 started; log sequence number 27294131873 2022-11-16 16:15:45 139887189649152 [Note] InnoDB: Dumping buffer pool(s) not yet started 2022-11-16 16:15:45 139887806762368 [Note] Plugin 'FEEDBACK' is disabled. 2022-11-16 16:15:45 139887806762368 [Note] Recovering after a crash using tc.log 2022-11-16 16:15:45 139887806762368 [ERROR] Can't init tc log 2022-11-16 16:15:45 139887806762368 [ERROR] Aborting 2022-11-16 16:16:56 140701933608320 [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. 2022-11-16 16:16:56 140701933608320 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2022-11-16 16:16:56 140701933608320 [Note] InnoDB: The InnoDB memory heap is disabled 2022-11-16 16:16:56 140701933608320 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-11-16 16:16:56 140701933608320 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2022-11-16 16:16:56 140701933608320 [Note] InnoDB: Compressed tables use zlib 1.2.8 2022-11-16 16:16:56 140701933608320 [Note] InnoDB: Using Linux native AIO 2022-11-16 16:16:56 140701933608320 [Note] InnoDB: Using SSE crc32 instructions 2022-11-16 16:16:56 140701933608320 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2022-11-16 16:16:56 140701933608320 [Note] InnoDB: Completed initialization of buffer pool 2022-11-16 16:16:56 140701933608320 [Note] InnoDB: Highest supported file format is Barracuda. 2022-11-16 16:16:56 140701933608320 [Note] InnoDB: 128 rollback segment(s) are active. 2022-11-16 16:16:56 140701933608320 [Note] InnoDB: Waiting for purge to start 2022-11-16 16:16:56 140701933608320 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.49-89.0 started; log sequence number 27294131883 2022-11-16 16:16:56 140701933608320 [Note] Plugin 'FEEDBACK' is disabled. 2022-11-16 16:16:56 140701933608320 [Note] Recovering after a crash using tc.log 2022-11-16 16:16:56 140701933608320 [ERROR] Can't init tc log 2022-11-16 16:16:56 140701933608320 [ERROR] Aborting 2022-11-16 16:21:40 139876627705216 [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. 2022-11-16 16:21:40 139876627705216 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2022-11-16 16:21:40 139876627705216 [Note] InnoDB: The InnoDB memory heap is disabled 2022-11-16 16:21:40 139876627705216 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-11-16 16:21:40 139876627705216 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2022-11-16 16:21:40 139876627705216 [Note] InnoDB: Compressed tables use zlib 1.2.8 2022-11-16 16:21:40 139876627705216 [Note] InnoDB: Using Linux native AIO 2022-11-16 16:21:40 139876627705216 [Note] InnoDB: Using SSE crc32 instructions 2022-11-16 16:21:40 139876627705216 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2022-11-16 16:21:40 139876627705216 [Note] InnoDB: Completed initialization of buffer pool 2022-11-16 16:21:40 139876627705216 [Note] InnoDB: Highest supported file format is Barracuda. 2022-11-16 16:21:40 139876627705216 [Note] InnoDB: 128 rollback segment(s) are active. 2022-11-16 16:21:40 139876627705216 [Note] InnoDB: Waiting for purge to start 2022-11-16 16:21:40 139876627705216 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.49-89.0 started; log sequence number 27294131893 2022-11-16 16:21:40 139876627705216 [Note] Plugin 'FEEDBACK' is disabled. 2022-11-16 16:21:40 139876627705216 [Note] Recovering after a crash using tc.log 2022-11-16 16:21:40 139876627705216 [ERROR] Can't init tc log 2022-11-16 16:21:40 139876627705216 [ERROR] Aborting 2022-11-16 16:27:13 140331696151936 [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. 2022-11-16 16:27:13 140331696151936 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2022-11-16 16:27:13 140331696151936 [Note] InnoDB: The InnoDB memory heap is disabled 2022-11-16 16:27:13 140331696151936 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-11-16 16:27:13 140331696151936 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2022-11-16 16:27:13 140331696151936 [Note] InnoDB: Compressed tables use zlib 1.2.8 2022-11-16 16:27:13 140331696151936 [Note] InnoDB: Using Linux native AIO 2022-11-16 16:27:13 140331696151936 [Note] InnoDB: Using SSE crc32 instructions 2022-11-16 16:27:13 140331696151936 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2022-11-16 16:27:15 140331696151936 [Note] InnoDB: Completed initialization of buffer pool 2022-11-16 16:27:16 140331696151936 [Note] InnoDB: Highest supported file format is Barracuda. 2022-11-16 16:27:17 140331696151936 [Note] InnoDB: 128 rollback segment(s) are active. 2022-11-16 16:27:17 140331696151936 [Note] InnoDB: Waiting for purge to start 2022-11-16 16:27:17 140331696151936 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.49-89.0 started; log sequence number 27294131903 2022-11-16 16:27:17 140331696151936 [Note] Plugin 'FEEDBACK' is disabled. 2022-11-16 16:27:17 140331696151936 [Note] Recovering after a crash using tc.log 2022-11-16 16:27:17 140331696151936 [ERROR] Can't init tc log 2022-11-16 16:27:17 140331696151936 [ERROR] Aborting
A classic Just move tc.log and restart the DB: Code: mv /var/lib/mysql/tc.log /var/lib/mysql/tc.log.old systemctl restart mariadb
hi It was already configured since 2019 Now since the error in mariadb does not access phpmyadmin When I click on the database icon it directs me to it but shows blank screen https:/xx.xx.xx.xx:8080/phpmyadmin/
Ok, so the issue is not related to ISPConfig. Your problem is that phpmyadmin does not work at all. Have a look at the error.log of the webserver to see which error messages appear there when you access phpmyadmin.
