Hi guys,
After installing the newest Freepbx15 distro on VMware ESXI Hypervisor, it was taking a very long time to reboot or shutdown the system.
I figured out that the reason is MariaDB server, which hangs during the stopping process and, actually, it stops only after 5 minutes, when it reaches the timeout.
Here is what I can see in /var/log/mariadb/mariadb.log when executing “systemctl stop mariadb” :
200129 11:21:21 [Note] /usr/libexec/mysqld: Normal shutdown
200129 11:21:21 [Note] Event Scheduler: Purging the queue. 0 events
200129 11:21:21 InnoDB: Starting shutdown…
200129 11:22:21 InnoDB: Waiting for worker threads to be suspended
200129 11:23:22 InnoDB: Waiting for worker threads to be suspended
200129 11:24:22 InnoDB: Waiting for worker threads to be suspended
200129 11:25:22 InnoDB: Waiting for worker threads to be suspended
Than, after executing “systemctl start mariadb” I get this output in /var/log/mariadb/mariadb.log :
200129 11:45:36 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200129 11:45:36 [Note] /usr/libexec/mysqld (mysqld 5.5.60-MariaDB) starting as process 28309 …
200129 11:45:36 InnoDB: The InnoDB memory heap is disabled
200129 11:45:36 InnoDB: Mutexes and rw_locks use GCC atomic builtins
200129 11:45:36 InnoDB: Compressed tables use zlib 1.2.7
200129 11:45:36 InnoDB: Using Linux native AIO
200129 11:45:36 InnoDB: Initializing buffer pool, size = 128.0M
200129 11:45:36 InnoDB: Completed initialization of buffer pool
200129 11:45:36 InnoDB: highest supported file format is Barracuda.
200129 11:45:36 InnoDB: Starting crash recovery from checkpoint LSN=32237726
InnoDB: Restoring possible half-written data pages from the doublewrite buffer…
200129 11:45:36 InnoDB: Starting final batch to recover 40 pages from redo log
200129 11:45:36 InnoDB: Waiting for the background threads to start
200129 11:45:37 Percona XtraDB (http://www.percona.com) 5.5.59-MariaDB-38.11 started; log sequence number 32575033
200129 11:45:37 [Note] Plugin ‘FEEDBACK’ is disabled.
200129 11:45:37 [Note] Server socket created on IP: ‘0.0.0.0’.
200129 11:45:37 [Note] Event Scheduler: Loaded 0 events
200129 11:45:37 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.60-MariaDB’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 MariaDB Server.
I found some info, that it can be related with the time settings, so have made the appropriate changes, but no luck. Time and date settings seems correct.
The output of “timedatectl” is:
Local time: Wed 2020-01-29 12:01:08 +04
Universal time: Wed 2020-01-29 08:01:08 UTC
RTC time: Wed 2020-01-29 12:01:08
Time zone: Asia/Yerevan (+04, +0400)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: yes
DST active: n/a
One interesting moment, when I shut down the virtual machine and disable the Ethernet from the Hypervisor settings and power on the VM again, MariaDB starts working great.
I even tried to clone the virtual machine, with malfunctioning MariaDB server to my Desktop PC and run it in VMware Workstation Pro, and it worked just awesome, even with enabled Ethernet.
Also, I can decrease the timeout time from 300 sec to, let’s say, 30 sec, but the main issue will not be resolved.
I couldn’t find any useful info about the possible reasons of the described issue.
Additional info:
ESXI Version: 6.7.0 Update 3 (Build 15160138)
Guest OS: Other 3.x Linux (64-bit)
Compatibility: ESXi 6.7 virtual machine
VMware Tools: Yes
CPUs: 4
Memory: 12 GB
Any help would be highly appreciated. Thanks!
Best.