Restarting MySQL Server failed and slow restarting.

Samet Chan

Well-Known Member
Jun 24, 2016
359
32
103
cPanel Access Level
Root Administrator
Twitter
Dear,

I've restarted MySQL got failed and error, But unsuccessfully well.

Restarting MySQL Server said:
Waiting for “mysql” to restart ……Job for mariadb.service failed because a timeout was exceeded. See "systemctl status mariadb.service" and "journalctl -xe" for details. ………finished.

Service Status
mysql (/usr/sbin/mysqld) is running as mysql with PID 18679 (systemd+/proc check method).

Startup Log
Aug 28 17:26:02
AnimeServer
systemd[1]: Starting MariaDB database server...
Aug 28 17:26:02
AnimeServer
mysqld[18679]: 2017-08-28 17:26:02 140438937245824 [Note] /usr/sbin/mysqld (mysqld 10.2.8-MariaDB) starting as process 18679 ...
Aug 28 17:26:03
AnimeServer
systemd[1]: Started MariaDB database server.

Log Messages
2017-08-28 17:26:03 140438937245824 [Note] /usr/sbin/mysqld: ready for connections.
2017-08-28 17:25:56 139833284470528 [Note] /usr/sbin/mysqld: Shutdown complete
2017-08-28 17:25:55 139833756801152 [Note] /usr/sbin/mysqld: ready for connections.
2017-08-28 17:24:10 140006407264000 [Note] /usr/sbin/mysqld: Shutdown complete
Aug 28 17:26:02 AnimeServer mysqld: 2017-08-28 17:26:02 140438937245824 [Note] /usr/sbin/mysqld (mysqld 10.2.8-MariaDB) starting as process 18679 ...

MySQL restarted successfully.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,904
2,218
463
Hello,

Could you let us know of any specific output to /var/lib/mysql/$hostname.err log file when attempting to start the MySQL server?

Thank you.
 

Samet Chan

Well-Known Member
Jun 24, 2016
359
32
103
cPanel Access Level
Root Administrator
Twitter
Hello,

Could you let us know of any specific output to /var/lib/mysql/$hostname.err log file when attempting to start the MySQL server?

Thank you.
Code:
2017-08-28  2:07:20 140006442956544 [Note] InnoDB: page_cleaner: 1000ms intended loop took 4059ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
2017-08-28  2:11:52 140006409385728 [Warning] IP address '23.245.248.32' has been resolved to the host name '32.248-245-23.rdns.scalabledns.com', which resembles IPv4-address itself.
2017-08-28  4:07:10 140006442956544 [Note] InnoDB: page_cleaner: 1000ms intended loop took 4137ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
2017-08-28  6:03:39 140006405445376 [Warning] IP address '61.158.163.73' has been resolved to the host name '73.163.158.61.ha.cnc', which resembles IPv4-address itself.
2017-08-28  8:11:14 140006442956544 [Note] InnoDB: page_cleaner: 1000ms intended loop took 6652ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
2017-08-28 13:50:09 140006442956544 [Note] InnoDB: page_cleaner: 1000ms intended loop took 5044ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
2017-08-28 14:17:39 140006442956544 [Note] InnoDB: page_cleaner: 1000ms intended loop took 5408ms. The settings might not be optimal. (flushed=1 and evicted=0, during the time.)
2017-08-28 14:21:19 140006442956544 [Note] InnoDB: page_cleaner: 1000ms intended loop took 4164ms. The settings might not be optimal. (flushed=4 and evicted=0, during the time.)
2017-08-28 17:24:03 140006407264000 [Note] /usr/sbin/mysqld (root[root] @ localhost []): Normal shutdown

2017-08-28 17:24:03 140006407264000 [Note] Event Scheduler: Purging the queue. 0 events
2017-08-28 17:24:03 140006320494336 [Note] InnoDB: FTS optimize thread exiting.
2017-08-28 17:24:05 140006407264000 [Note] InnoDB: Starting shutdown...
2017-08-28 17:24:05 140005867517696 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2017-08-28 17:24:05 140005867517696 [Note] InnoDB: Instance 0, restricted to 2048 pages due to innodb_buf_pool_dump_pct=25
2017-08-28 17:24:05 140005867517696 [Note] InnoDB: Buffer pool(s) dump completed at 170828 17:24:05
2017-08-28 17:24:10 140006407264000 [Note] InnoDB: Shutdown completed; log sequence number 86282439851
2017-08-28 17:24:10 140006407264000 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2017-08-28 17:24:10 140006407264000 [Note] /usr/sbin/mysqld: Shutdown complete

2017-08-28 17:24:12 139833756801152 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-08-28 17:24:12 139833756801152 [Note] InnoDB: Uses event mutexes
2017-08-28 17:24:12 139833756801152 [Note] InnoDB: Compressed tables use zlib 1.2.7
2017-08-28 17:24:12 139833756801152 [Note] InnoDB: Using Linux native AIO
2017-08-28 17:24:12 139833756801152 [Note] InnoDB: Number of pools: 1
2017-08-28 17:24:12 139833756801152 [Note] InnoDB: Using SSE2 crc32 instructions
2017-08-28 17:24:12 139833756801152 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-08-28 17:24:12 139833756801152 [Note] InnoDB: Completed initialization of buffer pool
2017-08-28 17:24:12 139832991708928 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-08-28 17:24:12 139833756801152 [Note] InnoDB: Highest supported file format is Barracuda.
2017-08-28 17:25:54 139833756801152 [Note] InnoDB: 128 out of 128 rollback segments are active.
2017-08-28 17:25:54 139833756801152 [Note] InnoDB: Creating shared tablespace for temporary tables
2017-08-28 17:25:54 139833756801152 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2017-08-28 17:25:54 139833756801152 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2017-08-28 17:25:54 139833756801152 [Note] InnoDB: Waiting for purge to start
2017-08-28 17:25:54 139833756801152 [Note] InnoDB: 5.7.19 started; log sequence number 86282439851
2017-08-28 17:25:54 139832693077760 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2017-08-28 17:25:54 139833756801152 [Note] Plugin 'FEEDBACK' is disabled.
2017-08-28 17:25:54 139833756801152 [Note] Server socket created on IP: '::'.
2017-08-28 17:25:54 139833284470528 [Note] /usr/sbin/mysqld (unknown): Normal shutdown

2017-08-28 17:25:55 139833756801152 [Note] Reading of all Master_info entries succeded
2017-08-28 17:25:55 139833756801152 [Note] Added new Master_info '' to hash table
2017-08-28 17:25:55 139833756801152 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.2.8-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
2017-08-28 17:25:55 139833284470528 [Note] Event Scheduler: Purging the queue. 0 events
2017-08-28 17:25:55 139832939235072 [Note] InnoDB: FTS optimize thread exiting.
2017-08-28 17:25:55 139833284470528 [Note] InnoDB: Starting shutdown...
2017-08-28 17:25:55 139832693077760 [Note] InnoDB: Buffer pool(s) load completed at 170828 17:25:55
2017-08-28 17:25:55 139832693077760 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2017-08-28 17:25:55 139832693077760 [Note] InnoDB: Instance 0, restricted to 2048 pages due to innodb_buf_pool_dump_pct=25
2017-08-28 17:25:55 139832693077760 [Note] InnoDB: Buffer pool(s) dump completed at 170828 17:25:55
2017-08-28 17:25:56 139833284470528 [Note] InnoDB: Shutdown completed; log sequence number 86282439879
2017-08-28 17:25:56 139833284470528 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2017-08-28 17:25:56 139833284470528 [Note] /usr/sbin/mysqld: Shutdown complete

2017-08-28 17:26:02 140438937245824 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-08-28 17:26:02 140438937245824 [Note] InnoDB: Uses event mutexes
2017-08-28 17:26:02 140438937245824 [Note] InnoDB: Compressed tables use zlib 1.2.7
2017-08-28 17:26:02 140438937245824 [Note] InnoDB: Using Linux native AIO
2017-08-28 17:26:02 140438937245824 [Note] InnoDB: Number of pools: 1
2017-08-28 17:26:02 140438937245824 [Note] InnoDB: Using SSE2 crc32 instructions
2017-08-28 17:26:02 140438937245824 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-08-28 17:26:02 140438937245824 [Note] InnoDB: Completed initialization of buffer pool
2017-08-28 17:26:02 140438162671360 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-08-28 17:26:02 140438937245824 [Note] InnoDB: Highest supported file format is Barracuda.
2017-08-28 17:26:02 140438937245824 [Note] InnoDB: 128 out of 128 rollback segments are active.
2017-08-28 17:26:02 140438937245824 [Note] InnoDB: Creating shared tablespace for temporary tables
2017-08-28 17:26:02 140438937245824 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2017-08-28 17:26:02 140438937245824 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2017-08-28 17:26:02 140438937245824 [Note] InnoDB: 5.7.19 started; log sequence number 86282439879
2017-08-28 17:26:02 140437998245632 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2017-08-28 17:26:02 140437998245632 [Note] InnoDB: Buffer pool(s) load completed at 170828 17:26:02
2017-08-28 17:26:03 140438937245824 [Note] Plugin 'FEEDBACK' is disabled.
2017-08-28 17:26:03 140438937245824 [Note] Server socket created on IP: '::'.
2017-08-28 17:26:03 140438937245824 [Note] Reading of all Master_info entries succeded
2017-08-28 17:26:03 140438937245824 [Note] Added new Master_info '' to hash table
2017-08-28 17:26:03 140438937245824 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.2.8-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
2017-08-28 17:26:05 140438791714560 [Note] Detected table cache mutex contention at instance 1: 38% waits. Additional table cache instance activated. Number of instances after activation: 2.
2017-08-28 17:26:06 140438792017664 [Note] Detected table cache mutex contention at instance 2: 23% waits. Additional table cache instance activated. Number of instances after activation: 3.
2017-08-28 17:26:06 140438792017664 [Note] Detected table cache mutex contention at instance 2: 22% waits. Additional table cache instance activated. Number of instances after activation: 4.
2017-08-28 18:35:59 140438788986624 [Note] /usr/sbin/mysqld (root[root] @ localhost []): Normal shutdown

2017-08-28 18:35:59 140438788986624 [Note] Event Scheduler: Purging the queue. 0 events
2017-08-28 18:35:59 140438040209152 [Note] InnoDB: FTS optimize thread exiting.
2017-08-28 18:35:59 140438788986624 [Note] InnoDB: Starting shutdown...
2017-08-28 18:35:59 140437998245632 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2017-08-28 18:35:59 140437998245632 [Note] InnoDB: Instance 0, restricted to 2048 pages due to innodb_buf_pool_dump_pct=25
2017-08-28 18:35:59 140437998245632 [Note] InnoDB: Buffer pool(s) dump completed at 170828 18:35:59
2017-08-28 18:36:09 140438788986624 [Note] InnoDB: Shutdown completed; log sequence number 86306814602
2017-08-28 18:36:09 140438788986624 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2017-08-28 18:36:09 140438788986624 [Note] /usr/sbin/mysqld: Shutdown complete

2017-08-28 18:36:12 140591771121792 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-08-28 18:36:12 140591771121792 [Note] InnoDB: Uses event mutexes
2017-08-28 18:36:12 140591771121792 [Note] InnoDB: Compressed tables use zlib 1.2.7
2017-08-28 18:36:12 140591771121792 [Note] InnoDB: Using Linux native AIO
2017-08-28 18:36:12 140591771121792 [Note] InnoDB: Number of pools: 1
2017-08-28 18:36:12 140591771121792 [Note] InnoDB: Using SSE2 crc32 instructions
2017-08-28 18:36:12 140591771121792 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-08-28 18:36:12 140591771121792 [Note] InnoDB: Completed initialization of buffer pool
2017-08-28 18:36:12 140591003092736 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-08-28 18:36:12 140591771121792 [Note] InnoDB: Highest supported file format is Barracuda.
2017-08-28 18:38:04 140591771121792 [Note] InnoDB: 128 out of 128 rollback segments are active.
2017-08-28 18:38:04 140591771121792 [Note] InnoDB: Creating shared tablespace for temporary tables
2017-08-28 18:38:04 140591771121792 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2017-08-28 18:38:04 140591771121792 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2017-08-28 18:38:04 140591771121792 [Note] InnoDB: Waiting for purge to start
2017-08-28 18:38:04 140591771121792 [Note] InnoDB: 5.7.19 started; log sequence number 86306814602
2017-08-28 18:38:04 140590628980480 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2017-08-28 18:38:04 140591771121792 [Note] Plugin 'FEEDBACK' is disabled.
2017-08-28 18:38:04 140591771121792 [Note] Server socket created on IP: '::'.
2017-08-28 18:38:04 140591662540544 [Note] /usr/sbin/mysqld (unknown): Normal shutdown

2017-08-28 18:38:04 140591771121792 [Note] Reading of all Master_info entries succeded
2017-08-28 18:38:04 140591771121792 [Note] Added new Master_info '' to hash table
2017-08-28 18:38:04 140591771121792 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.2.8-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
2017-08-28 18:38:04 140591662540544 [Note] Event Scheduler: Purging the queue. 0 events
2017-08-28 18:38:04 140590880630528 [Note] InnoDB: FTS optimize thread exiting.
2017-08-28 18:38:04 140591662540544 [Note] InnoDB: Starting shutdown...
2017-08-28 18:38:04 140590628980480 [Note] InnoDB: Buffer pool(s) load completed at 170828 18:38:04
2017-08-28 18:38:04 140590628980480 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2017-08-28 18:38:04 140590628980480 [Note] InnoDB: Instance 0, restricted to 2048 pages due to innodb_buf_pool_dump_pct=25
2017-08-28 18:38:04 140590628980480 [Note] InnoDB: Buffer pool(s) dump completed at 170828 18:38:04
2017-08-28 18:38:05 140591662540544 [Note] InnoDB: Shutdown completed; log sequence number 86306814630
2017-08-28 18:38:05 140591662540544 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2017-08-28 18:38:05 140591662540544 [Note] /usr/sbin/mysqld: Shutdown complete

2017-08-28 18:38:11 140523539851392 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-08-28 18:38:11 140523539851392 [Note] InnoDB: Uses event mutexes
2017-08-28 18:38:11 140523539851392 [Note] InnoDB: Compressed tables use zlib 1.2.7
2017-08-28 18:38:11 140523539851392 [Note] InnoDB: Using Linux native AIO
2017-08-28 18:38:11 140523539851392 [Note] InnoDB: Number of pools: 1
2017-08-28 18:38:11 140523539851392 [Note] InnoDB: Using SSE2 crc32 instructions
2017-08-28 18:38:11 140523539851392 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-08-28 18:38:11 140523539851392 [Note] InnoDB: Completed initialization of buffer pool
2017-08-28 18:38:11 140522770163456 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-08-28 18:38:11 140523539851392 [Note] InnoDB: Highest supported file format is Barracuda.
2017-08-28 18:38:12 140523539851392 [Note] InnoDB: 128 out of 128 rollback segments are active.
2017-08-28 18:38:12 140523539851392 [Note] InnoDB: Creating shared tablespace for temporary tables
2017-08-28 18:38:12 140523539851392 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2017-08-28 18:38:12 140523539851392 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2017-08-28 18:38:12 140523539851392 [Note] InnoDB: 5.7.19 started; log sequence number 86306814630
2017-08-28 18:38:12 140522328942336 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2017-08-28 18:38:12 140522328942336 [Note] InnoDB: Buffer pool(s) load completed at 170828 18:38:12
2017-08-28 18:38:12 140523539851392 [Note] Plugin 'FEEDBACK' is disabled.
2017-08-28 18:38:12 140523539851392 [Note] Server socket created on IP: '::'.
2017-08-28 18:38:12 140523539851392 [Note] Reading of all Master_info entries succeded
2017-08-28 18:38:12 140523539851392 [Note] Added new Master_info '' to hash table
2017-08-28 18:38:12 140523539851392 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.2.8-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
2017-08-28 19:15:12 140523080247040 [Warning] IP address '222.186.xx.xx' could not be resolved: Name or service not known
2017-08-28 20:39:20 140523100153600 [Warning] IP address '218.66.xx.xx' has been resolved to the host name '129.43.xx.xxx.broad.example.com.cn', which resembles IPv4-address itself.
2017-08-28 20:41:56 140523079640832 [Warning] IP address '42.7.xx.xx' could not be resolved: Name or service not known
 
Last edited by a moderator:

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,904
2,218
463
Hello,

I'm not seeing anything in the output that suggests MySQL is unable to start. Could you open a support ticket using the link in my signature so we can take a closer look?

Thank you.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,904
2,218
463
To update, it looks like this issue stemmed from a potential memory, disk or hard drive failure. We recommended consulting with the hosting provider for additional assistance. Can you verify the outcome of the issue?

Thank you.
 

Samet Chan

Well-Known Member
Jun 24, 2016
359
32
103
cPanel Access Level
Root Administrator
Twitter
Sorry for late, Support ticket is solved. Contabo was solved or not. I'm confused.

Steven Sublett said:
Your server may be having some sort of hardware issue at times which is causing MySQL to crash.

==
2017-08-31 22:17:39 140259360123008 [ERROR] InnoDB: File ./ibtmp1: 'open' returned OS error 71. Cannot continue operation
170831 22:17:39 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see MariaDB Community Bug Reporting

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.2.8-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=502
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1234023 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x49000
*** buffer overflow detected ***: /usr/sbin/mysqld terminated
======= Backtrace: =========
/lib64/libc.so.6(__fortify_fail+0x37)[0x7f90ab7dc077]
/lib64/libc.so.6(+0x10d230)[0x7f90ab7da230]
/lib64/libc.so.6(+0x10efe7)[0x7f90ab7dbfe7]
/usr/sbin/mysqld(my_addr_resolve+0x48)[0x7f90ae1e1178]
/usr/sbin/mysqld(my_print_stacktrace+0x1c2)[0x7f90ae1cac12]
/usr/sbin/mysqld(handle_fatal_signal+0x30d)[0x7f90adc10dbd]
/lib64/libpthread.so.0(+0xf370)[0x7f90ad179370]
/lib64/libc.so.6(gsignal+0x37)[0x7f90ab7021d7]
/lib64/libc.so.6(abort+0x148)[0x7f90ab7038c8]
/usr/sbin/mysqld(+0x8c3b98)[0x7f90ade6cb98]
/usr/sbin/mysqld(+0xa8374c)[0x7f90ae02c74c]
/usr/sbin/mysqld(+0xa85249)[0x7f90ae02e249]
/usr/sbin/mysqld(+0xa8645f)[0x7f90ae02f45f]
/usr/sbin/mysqld(+0x9772ae)[0x7f90adf202ae]
/usr/sbin/mysqld(+0x844df1)[0x7f90addeddf1]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x7f90adc13244]
/usr/sbin/mysqld(+0x4eba50)[0x7f90ada94a50]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x9a2)[0x7f90ada96282]
/usr/sbin/mysqld(+0x447928)[0x7f90ad9f0928]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x1ce1)[0x7f90ad9f4c31]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f90ab6eeb35]
/usr/sbin/mysqld(+0x4403ed)[0x7f90ad9e93ed]
==

The above error is usually reference to a possible memory, disk or hard drive failure. Is it possible for your server provider to performing testing on your hardware for issues?

At this time the issue doesn't appear to be related to cPanel services so I would recommend consulting with your server provider or reaching out to certified administrator for further diagnosing into the issue for you.

* System Administration Services | cPanel Forums
Contabo Support Team said:
1. Your VPS XL (5.189.XXX.XXX) has been moved to another host system and the new VNC login detials have been already sent in a separate e-mail, so if you are no longer able to determine any errors at the server logfiles, everything should be fine now.

Please get back to us as soon as you can confirm, that everything is working properly.

2. We have checked your VPS XL (5.189.XXX.XXX) and can tell you that it is online and running smooth without issues. Your websites seem to be reachable and reacting normally. Therefore we would kindly ask you to check from your side again.

Should you still encounter issues, please get back to us providing us with further details.
 
Last edited by a moderator:

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,904
2,218
463
It looks like your provider moved your VPS to another hardware node to address the slowness issue. Can you confirm if MySQL continues to fail or continues to take a long time to restart?

Thank you.
 

Samet Chan

Well-Known Member
Jun 24, 2016
359
32
103
cPanel Access Level
Root Administrator
Twitter
Little slow load, Take time to completed 18 seconds.

Restarting MySQL Server said:
Waiting for “mysql” to restart ……waiting for “mysql” to initialize ………finished.

Service Status
mysql (/usr/sbin/mysqld) is running as mysql with PID 7241 (systemd+/proc check method).

Startup Log
Sep 05 20:29:43 vmi114871.contaboserver.net systemd[1]: Starting MariaDB database server...
Sep 05 20:29:44 vmi114871.contaboserver.net mysqld[7241]: 2017-09-05 20:29:44 140007416912000 [Note] /usr/sbin/mysqld (mysqld 10.2.8-MariaDB) starting as process 7241 ...
Sep 05 20:30:24 vmi114871.contaboserver.net systemd[1]: Started MariaDB database server.

Log Messages
2017-09-05 20:30:24 140007416912000 [Note] /usr/sbin/mysqld: ready for connections.
2017-09-05 20:29:42 140350539560704 [Note] /usr/sbin/mysqld: Shutdown complete

MySQL restarted successfully.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,904
2,218
463
You may want to look into tuning your MySQL configuration to improve performance if it continues to result in access or slowness issues. You can find a list of companies offering system administration services if you need assistance with performance tuning:

System Administration Services | cPanel Forums

Thank you.
 
Last edited:

Samet Chan

Well-Known Member
Jun 24, 2016
359
32
103
cPanel Access Level
Root Administrator
Twitter
You may want to look into tuning your MySQL configuration to improve performance if it continues to result in access or slowness issues. You can find a list of companies offering system administration services if you need assistance with performance tuning:

Ioncube loader for PHP 7.1

Thank you.
My Anime Streaming doesn't support 7.0 or 7.1 will be locked to add anime and episode.

Is it available for 5.6 and 7.0 in Ioncube loader? Or it is available from EA4?
 

Samet Chan

Well-Known Member
Jun 24, 2016
359
32
103
cPanel Access Level
Root Administrator
Twitter
Hello,

I apologize, the URL I intended to post was:

System Administration Services | cPanel Forums

The Ioncube URL is unrelated to this thread.

Thank you.
Contabo said always perfectly running on my VPS Server, I really don't understand. Everyday my server again always problem.

I am getting an error again.


WHM and cPanel said error. Site is now down to 503 reached error.
Code:
Internal Server Error
500

The cPanel Server operation timed out at cpsrvd.pl line 532.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,904
2,218
463

Samet Chan

Well-Known Member
Jun 24, 2016
359
32
103
cPanel Access Level
Root Administrator
Twitter
Could you open a separate forums thread if this issue persists?



You may find the following thread helpful:

pool options for best performance

Thank you.
Sorry for late...


My VPS Server has been fixed to speed up for optimization was Contabo support did fix.

Contabo Support Team said:
Dear Samet,

Thank you very much for your reply.

We have checked the host and your VPS, some optimization was added to your VPS. However hardware messages can usually be ignored, they occur when the host system is experiencing a load peak - like a high CPU peak. Those peaks can occur but should not affect your VPS in any way - the operating system notices that something is not working properly. We are monitoring our host systems, in case of some hardware failure we will get noticed and will have enough time to plan and schedule a maintenance.
 
  • Like
Reactions: cPanelMichael