mohammadreza

Active Member
Jan 7, 2018
32
0
6
Teh
cPanel Access Level
Root Administrator
This indicates that you've set the max_open_files and max_connections in the mysql conf at /etc/my.cnf but it does not indicate the issue with it starting. Can you please include the log messages when you attempt to restart the service. If you're unsure where the log file is you can find it listed in the mysql configuration file.
When i run this command:

Code:
systemctl restart mysql
output is :

Code:
restart mysqlJob for mariadb.service failed because a fatal signal was delivered to the control process. See "systemctl status mariadb.service" and "journalctl -xe" for details.
and output of this command systemctl status mariadb.service is :

Code:
systemctl status mariadb.service

● mariadb.service - MariaDB database server

   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)

  Drop-In: /etc/systemd/system/mariadb.service.d

           └─migrated-from-my.cnf-settings.conf, tokudb.conf

   Active: activating (start) since Fri 2020-03-20 21:07:43 +0330; 2s ago

  Process: 1135623 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)

  Process: 1135620 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)

 Main PID: 1135704 (mysqld)

   CGroup: /system.slice/mariadb.service

           └─1135704 /usr/sbin/mysqld



Mar 20 21:07:43 sv8 systemd[1]: Starting MariaDB database server...

Mar 20 21:07:44 sv8 mysqld[1135704]: 2020-03-20 21:07:44 140517118224640 [Note] libgovernor.so found

Mar 20 21:07:44 sv8 mysqld[1135704]: 2020-03-20 21:07:44 140517118224640 [Note] All governors functions found too

Mar 20 21:07:44 sv8 mysqld[1135704]: 2020-03-20 21:07:44 140517118224640 [ERROR] Governor not connected

Mar 20 21:07:44 sv8 mysqld[1135704]: 2020-03-20 21:07:44 140517118224640 [Note] All governors lve functions found too

Mar 20 21:07:44 sv8 mysqld[1135704]: 2020-03-20 21:07:44 140517118224640 [Note] /usr/sbin/mysqld (mysqld 10.2.27-MariaDB-cll-lv...704 ...

Mar 20 21:07:44 sv8 mysqld[1135704]: 2020-03-20 21:07:44 140517118224640 [Warning] Could not increase number of max_open_files ...050715)

Mar 20 21:07:44 sv8 mysqld[1135704]: 2020-03-20 21:07:44 140517118224640 [Warning] Changed limits: max_open_files: 1048576  max...524288)

Hint: Some lines were ellipsized, use -l to show in full.


output of journalctl -xe :

Code:
journalctl -xe

-- Subject: Unit mariadb.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit mariadb.service has failed.

--

-- The result is failed.

Mar 20 21:08:27 sv8 systemd[1]: Unit mariadb.service entered failed state.

Mar 20 21:08:27 sv8 systemd[1]: mariadb.service failed.

Mar 20 21:08:27 sv8 systemd[1]: Starting MySQL watcher service...

-- Subject: Unit db_governor.service has begun start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit db_governor.service has begun starting up.

Mar 20 21:08:27 sv8 systemd[1]: Started MySQL watcher service.

-- Subject: Unit db_governor.service has finished start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit db_governor.service has finished starting up.

--

-- The start-up result is done.

Mar 20 21:08:27 sv8 systemd[1]: db_governor.service: main process exited, code=exited, status=1/FAILURE

Mar 20 21:08:27 sv8 systemd[1]: Unit db_governor.service entered failed state.

Mar 20 21:08:27 sv8 systemd[1]: db_governor.service failed.
If you need other information please help me for run any command

Thank you
 

cPanelLauren

Forums Analyst II
Staff member
Nov 14, 2017
10,088
877
313
Houston
Again, this is not what I requested, I see this information as was requested previously.

I asked specifically for log data that is present when you attempt to restart the mysql server.

1. If you don't know where the log file is located you can look at /etc/my.cnf for the directory location.
2. If you don't know how to get this information I'd suggest you open a ticket so that our analysts can look at the issue for you.
 

mohammadreza

Active Member
Jan 7, 2018
32
0
6
Teh
cPanel Access Level
Root Administrator
Again, this is not what I requested, I see this information as was requested previously.

I asked specifically for log data that is present when you attempt to restart the mysql server.

1. If you don't know where the log file is located you can look at /etc/my.cnf for the directory location.
2. If you don't know how to get this information I'd suggest you open a ticket so that our analysts can look at the issue for you.
Code:
2020-03-20 22:08:33 139926287259904 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-03-20 22:08:33 139926287259904 [Note] InnoDB: Uses event mutexes
2020-03-20 22:08:33 139926287259904 [Note] InnoDB: Compressed tables use zlib 1.2.7
2020-03-20 22:08:33 139926287259904 [Note] InnoDB: Using Linux native AIO
2020-03-20 22:08:33 139926287259904 [Note] InnoDB: Number of pools: 1
2020-03-20 22:08:33 139926287259904 [Note] InnoDB: Using SSE2 crc32 instructions
2020-03-20 22:08:33 139926287259904 [Note] InnoDB: Initializing buffer pool, total size = 10G, instances = 10, chunk size = 128M
2020-03-20 22:08:33 139926287259904 [Note] InnoDB: Completed initialization of buffer pool
2020-03-20 22:08:33 139911910872832 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-03-20 22:08:36 139926287259904 [Warning] InnoDB: 1048576 bytes should have been read. Only 503808 bytes read. Retrying for the remaining bytes.
2020-03-20 22:08:39 139926287259904 [Warning] InnoDB: Retry attempts for reading partial data failed.
2020-03-20 22:08:39 139926287259904 [ERROR] InnoDB: Tried to read 1048576 bytes at offset 2097152, but was only able to read 503808
2020-03-20 22:08:39 139926287259904 [ERROR] InnoDB: Operating system error number 5 in a file operation.
2020-03-20 22:08:39 139926287259904 [ERROR] InnoDB: Error number 5 means 'Input/output error'
2020-03-20 22:08:39 139926287259904 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2020-03-20 22:08:39 139926287259904 [ERROR] InnoDB: File (unknown): 'read' returned OS error 205. Cannot continue operation
200320 22:08: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 https://mariadb.com/kb/en/reporting-bugs

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.27-MariaDB-cll-lve
key_buffer_size=2147483648
read_buffer_size=131072
max_used_connections=0
max_threads=2102
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6716127 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
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55b98e80733e]
/usr/sbin/mysqld(handle_fatal_signal+0x30d)[0x55b98e28b0fd]
sigaction.c:0(__restore_rt)[0x7f4320416630]
:0(__GI_raise)[0x7f431e90c377]
:0(__GI_abort)[0x7f431e90da68]
/usr/sbin/mysqld(+0x96e2f5)[0x55b98e5752f5]
/usr/sbin/mysqld(+0x96e7c3)[0x55b98e5757c3]
/usr/sbin/mysqld(+0x9737a7)[0x55b98e57a7a7]
/usr/sbin/mysqld(+0xaacd3a)[0x55b98e6b3d3a]
/usr/sbin/mysqld(+0xb33bf0)[0x55b98e73abf0]
/usr/sbin/mysqld(+0xb34bcf)[0x55b98e73bbcf]
/usr/sbin/mysqld(+0xa13b6d)[0x55b98e61ab6d]
/usr/sbin/mysqld(+0x8fa9d8)[0x55b98e5019d8]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x55b98e28d7a4]
/usr/sbin/mysqld(+0x4fc5f0)[0x55b98e1035f0]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x9a2)[0x55b98e104ec2]
/usr/sbin/mysqld(+0x456211)[0x55b98e05d211]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x1d19)[0x55b98e0626d9]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f431e8f8545]
/usr/sbin/mysqld(+0x44f12d)[0x55b98e05612d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        0                    unlimited            bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             127548               127548               processes
Max open files            1048576              1048576              files     
Max locked memory         unlimited            unlimited            bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       127548               127548               signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                   
Max realtime priority     0                    0                   
Max realtime timeout      unlimited            unlimited            us       
Core pattern: core

2020-03-20 22:08:45 140253352085760 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-03-20 22:08:45 140253352085760 [Note] InnoDB: Uses event mutexes
2020-03-20 22:08:45 140253352085760 [Note] InnoDB: Compressed tables use zlib 1.2.7
2020-03-20 22:08:45 140253352085760 [Note] InnoDB: Using Linux native AIO
2020-03-20 22:08:45 140253352085760 [Note] InnoDB: Number of pools: 1
2020-03-20 22:08:45 140253352085760 [Note] InnoDB: Using SSE2 crc32 instructions
2020-03-20 22:08:45 140253352085760 [Note] InnoDB: Initializing buffer pool, total size = 10G, instances = 10, chunk size = 128M
2020-03-20 22:08:45 140253352085760 [Note] InnoDB: Completed initialization of buffer pool
2020-03-20 22:08:45 140238974310144 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
 

cPanelLauren

Forums Analyst II
Staff member
Nov 14, 2017
10,088
877
313
Houston
Code:
2020-03-20 22:08:36 139926287259904 [Warning] InnoDB: 1048576 bytes should have been read. Only 503808 bytes read. Retrying for the remaining bytes.
2020-03-20 22:08:39 139926287259904 [Warning] InnoDB: Retry attempts for reading partial data failed.
2020-03-20 22:08:39 139926287259904 [ERROR] InnoDB: Tried to read 1048576 bytes at offset 2097152, but was only able to read 503808
2020-03-20 22:08:39 139926287259904 [ERROR] InnoDB: Operating system error number 5 in a file operation.
2020-03-20 22:08:39 139926287259904 [ERROR] InnoDB: Error number 5 means 'Input/output error'
2020-03-20 22:08:39 139926287259904 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2020-03-20 22:08:39 139926287259904 [ERROR] InnoDB: File (unknown): 'read' returned OS error 205. Cannot continue operation
Is the specific issue you're hitting. I can see matching this with the error reading earlier it's related specifically to the max_open_files limit:
Code:
Mar 20 21:07:44 sv8 mysqld[1135704]: 2020-03-20 21:07:44 140517118224640 [Warning] Could not increase number of max_open_files ...050715)

Mar 20 21:07:44 sv8 mysqld[1135704]: 2020-03-20 21:07:44 140517118224640 [Warning] Changed limits: max_open_files: 1048576  max...524288)
Somewhere that limit is set to lower than the systems max_open_files limit.

You can view the current limit by doing the following on the mysql commandline:

Code:
[[email protected] ~]# mysql
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 50156
Server version: 10.3.22-MariaDB MariaDB Server

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> show variables like 'open_files_limit';
+------------------+-------+
| Variable_name    | Value |
+------------------+-------+
| open_files_limit | 10000 |
+------------------+-------+
1 row in set (0.001 sec)

MariaDB [(none)]>
This will be handy later on.

Typically this is a result of omewhere in one or multiple of these files, this has been modified to the number being shown:


/etc/systemd/system/mariadb.service.d/migrated-from-my.cnf-settings.conf
/etc/systemd/system/mysqld.service.d/limits.conf
/usr/lib/systemd/system/mariadb.service
/usr/lib/systemd/system/mariadb.service
/etc/systemd/system/mysql.service
/etc/systemd/system/mysqld.service


You're going to look for LimitNOFILE and LimitMEMLOCK lines - these need to be set to your specified limit.

Once you're done you need to reload systemd which can be done with the following:

Code:
systemctl daemon-reload
Once systemd is restarted you can attempt to restart mysql/mariadb again.

You can confirm the open files limit has changed with the command I showed previously using the mysql command line

MariaDB also has a kb on this here: Could not increase number of max_open_files to more than 1024 (request: 1835)
 

mohammadreza

Active Member
Jan 7, 2018
32
0
6
Teh
cPanel Access Level
Root Administrator
Thanks for
Code:
2020-03-20 22:08:36 139926287259904 [Warning] InnoDB: 1048576 bytes should have been read. Only 503808 bytes read. Retrying for the remaining bytes.
2020-03-20 22:08:39 139926287259904 [Warning] InnoDB: Retry attempts for reading partial data failed.
2020-03-20 22:08:39 139926287259904 [ERROR] InnoDB: Tried to read 1048576 bytes at offset 2097152, but was only able to read 503808
2020-03-20 22:08:39 139926287259904 [ERROR] InnoDB: Operating system error number 5 in a file operation.
2020-03-20 22:08:39 139926287259904 [ERROR] InnoDB: Error number 5 means 'Input/output error'
2020-03-20 22:08:39 139926287259904 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2020-03-20 22:08:39 139926287259904 [ERROR] InnoDB: File (unknown): 'read' returned OS error 205. Cannot continue operation
Is the specific issue you're hitting. I can see matching this with the error reading earlier it's related specifically to the max_open_files limit:
Code:
Mar 20 21:07:44 sv8 mysqld[1135704]: 2020-03-20 21:07:44 140517118224640 [Warning] Could not increase number of max_open_files ...050715)

Mar 20 21:07:44 sv8 mysqld[1135704]: 2020-03-20 21:07:44 140517118224640 [Warning] Changed limits: max_open_files: 1048576  max...524288)
Somewhere that limit is set to lower than the systems max_open_files limit.

You can view the current limit by doing the following on the mysql commandline:

Code:
[[email protected] ~]# mysql
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 50156
Server version: 10.3.22-MariaDB MariaDB Server

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> show variables like 'open_files_limit';
+------------------+-------+
| Variable_name    | Value |
+------------------+-------+
| open_files_limit | 10000 |
+------------------+-------+
1 row in set (0.001 sec)

MariaDB [(none)]>
This will be handy later on.

Typically this is a result of omewhere in one or multiple of these files, this has been modified to the number being shown:


/etc/systemd/system/mariadb.service.d/migrated-from-my.cnf-settings.conf
/etc/systemd/system/mysqld.service.d/limits.conf
/usr/lib/systemd/system/mariadb.service
/usr/lib/systemd/system/mariadb.service
/etc/systemd/system/mysql.service
/etc/systemd/system/mysqld.service


You're going to look for LimitNOFILE and LimitMEMLOCK lines - these need to be set to your specified limit.

Once you're done you need to reload systemd which can be done with the following:

Code:
systemctl daemon-reload
Once systemd is restarted you can attempt to restart mysql/mariadb again.

You can confirm the open files limit has changed with the command I showed previously using the mysql command line

MariaDB also has a kb on this here: Could not increase number of max_open_files to more than 1024 (request: 1835)
Thanks for your Help
now i see my value is 500000, how many need set value for solved issues?

Thanks
 

mohammadreza

Active Member
Jan 7, 2018
32
0
6
Teh
cPanel Access Level
Root Administrator
You'd need to set it to at least what it's trying to open.
Now i set LimitNOFILE=25000000, and run this command
/scripts/restartsrv_mysql --start
output is :
Code:
 /scripts/restartsrv_mysql --start
Waiting for “mysql” to start ……info [restartsrv_mysql] systemd failed to start the service “mariadb” (The “/usr/bin/systemctl restart mariadb.service --no-ask-password” command (process 1343382) reported error number 1 when it ended.): Job for mariadb.service failed because a fatal signal was delivered to the control process. See "systemctl status mariadb.service" and "journalctl -xe" for details.

…info [restartsrv_mysql] systemd failed to start the service “mariadb” (The “/usr/bin/systemctl restart mariadb.service --no-ask-password” command (process 1343648) reported error number 1 when it ended.): Job for mariadb.service failed because a fatal signal was delivered to the control process. See "systemctl status mariadb.service" and "journalctl -xe" for details.

…info [restartsrv_mysql] systemd failed to start the service “mariadb” (The “/usr/bin/systemctl restart mariadb.service --no-ask-password” command (process 1344034) reported error number 1 when it ended.): Job for mariadb.service failed because a fatal signal was delivered to the control process. See "systemctl status mariadb.service" and "journalctl -xe" for details.

…failed.

Cpanel::Exception::Services::StartError
Service Status

Service Error
        (XID cv5ymd) The “mysql” service failed to start.

Startup Log
        Mar 20 23:41:15 sv8 systemd[1]: Starting MariaDB database server...

mysql has failed. Contact your system administrator if the service does not automagically recover.
 

mohammadreza

Active Member
Jan 7, 2018
32
0
6
Teh
cPanel Access Level
Root Administrator
What's output in the log? This gives 0 indication of what the issue is.
Output in logs:
Code:
2020-03-20 23:59:21 140021755435264 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-03-20 23:59:21 140021755435264 [Note] InnoDB: Uses event mutexes
2020-03-20 23:59:21 140021755435264 [Note] InnoDB: Compressed tables use zlib 1.2.7
2020-03-20 23:59:21 140021755435264 [Note] InnoDB: Using Linux native AIO
2020-03-20 23:59:21 140021755435264 [Note] InnoDB: Number of pools: 1
2020-03-20 23:59:21 140021755435264 [Note] InnoDB: Using SSE2 crc32 instructions
2020-03-20 23:59:21 140021755435264 [Note] InnoDB: Initializing buffer pool, total size = 10G, instances = 10, chunk size = 128M
2020-03-20 23:59:21 140021755435264 [Note] InnoDB: Completed initialization of buffer pool
2020-03-20 23:59:22 140007377426176 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-03-20 23:59:24 140021755435264 [Warning] InnoDB: 1048576 bytes should have been read. Only 503808 bytes read. Retrying for the remaining bytes.
2020-03-20 23:59:28 140021755435264 [Warning] InnoDB: Retry attempts for reading partial data failed.
2020-03-20 23:59:28 140021755435264 [ERROR] InnoDB: Tried to read 1048576 bytes at offset 2097152, but was only able to read 503808
2020-03-20 23:59:28 140021755435264 [ERROR] InnoDB: Operating system error number 5 in a file operation.
2020-03-20 23:59:28 140021755435264 [ERROR] InnoDB: Error number 5 means 'Input/output error'
2020-03-20 23:59:28 140021755435264 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2020-03-20 23:59:28 140021755435264 [ERROR] InnoDB: File (unknown): 'read' returned OS error 205. Cannot continue operation
200320 23:59:28 [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 https://mariadb.com/kb/en/reporting-bugs

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.27-MariaDB-cll-lve
key_buffer_size=2147483648
read_buffer_size=131072
max_used_connections=0
max_threads=2102
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6716127 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
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55ceb9bf733e]
/usr/sbin/mysqld(handle_fatal_signal+0x30d)[0x55ceb967b0fd]
sigaction.c:0(__restore_rt)[0x7f595a9a2630]
:0(__GI_raise)[0x7f5958e98377]
:0(__GI_abort)[0x7f5958e99a68]
/usr/sbin/mysqld(+0x96e2f5)[0x55ceb99652f5]
/usr/sbin/mysqld(+0x96e7c3)[0x55ceb99657c3]
/usr/sbin/mysqld(+0x9737a7)[0x55ceb996a7a7]
/usr/sbin/mysqld(+0xaacd3a)[0x55ceb9aa3d3a]
/usr/sbin/mysqld(+0xb33bf0)[0x55ceb9b2abf0]
/usr/sbin/mysqld(+0xb34bcf)[0x55ceb9b2bbcf]
/usr/sbin/mysqld(+0xa13b6d)[0x55ceb9a0ab6d]
/usr/sbin/mysqld(+0x8fa9d8)[0x55ceb98f19d8]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x55ceb967d7a4]
/usr/sbin/mysqld(+0x4fc5f0)[0x55ceb94f35f0]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x9a2)[0x55ceb94f4ec2]
/usr/sbin/mysqld(+0x456211)[0x55ceb944d211]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x1d19)[0x55ceb94526d9]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f5958e84545]
/usr/sbin/mysqld(+0x44f12d)[0x55ceb944612d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        0                    unlimited            bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             127548               127548               processes
Max open files            1048576              1048576              files     
Max locked memory         65536                65536                bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       127548               127548               signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                   
Max realtime priority     0                    0                   
Max realtime timeout      unlimited            unlimited            us       
Core pattern: core

2020-03-20 23:59:33 140666251254016 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-03-20 23:59:33 140666251254016 [Note] InnoDB: Uses event mutexes
2020-03-20 23:59:33 140666251254016 [Note] InnoDB: Compressed tables use zlib 1.2.7
2020-03-20 23:59:33 140666251254016 [Note] InnoDB: Using Linux native AIO
2020-03-20 23:59:33 140666251254016 [Note] InnoDB: Number of pools: 1
2020-03-20 23:59:33 140666251254016 [Note] InnoDB: Using SSE2 crc32 instructions
2020-03-20 23:59:33 140666251254016 [Note] InnoDB: Initializing buffer pool, total size = 10G, instances = 10, chunk size = 128M
2020-03-20 23:59:34 140666251254016 [Note] InnoDB: Completed initialization of buffer pool
2020-03-20 23:59:34 140651874178816 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-03-20 23:59:37 140666251254016 [Warning] InnoDB: 1048576 bytes should have been read. Only 503808 bytes read. Retrying for the remaining bytes.
2020-03-20 23:59:39 140666251254016 [Warning] InnoDB: Retry attempts for reading partial data failed.
2020-03-20 23:59:39 140666251254016 [ERROR] InnoDB: Tried to read 1048576 bytes at offset 2097152, but was only able to read 503808
2020-03-20 23:59:39 140666251254016 [ERROR] InnoDB: Operating system error number 5 in a file operation.
2020-03-20 23:59:39 140666251254016 [ERROR] InnoDB: Error number 5 means 'Input/output error'
2020-03-20 23:59:39 140666251254016 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2020-03-20 23:59:39 140666251254016 [ERROR] InnoDB: File (unknown): 'read' returned OS error 205. Cannot continue operation
200320 23:59: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 https://mariadb.com/kb/en/reporting-bugs

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.27-MariaDB-cll-lve
key_buffer_size=2147483648
read_buffer_size=131072
max_used_connections=0
max_threads=2102
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6716127 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
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x560cebf0c33e]
/usr/sbin/mysqld(handle_fatal_signal+0x30d)[0x560ceb9900fd]
sigaction.c:0(__restore_rt)[0x7fef698be630]
:0(__GI_raise)[0x7fef67db4377]
:0(__GI_abort)[0x7fef67db5a68]
/usr/sbin/mysqld(+0x96e2f5)[0x560cebc7a2f5]
/usr/sbin/mysqld(+0x96e7c3)[0x560cebc7a7c3]
/usr/sbin/mysqld(+0x9737a7)[0x560cebc7f7a7]
/usr/sbin/mysqld(+0xaacd3a)[0x560cebdb8d3a]
/usr/sbin/mysqld(+0xb33bf0)[0x560cebe3fbf0]
/usr/sbin/mysqld(+0xb34bcf)[0x560cebe40bcf]
/usr/sbin/mysqld(+0xa13b6d)[0x560cebd1fb6d]
/usr/sbin/mysqld(+0x8fa9d8)[0x560cebc069d8]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x560ceb9927a4]
/usr/sbin/mysqld(+0x4fc5f0)[0x560ceb8085f0]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x9a2)[0x560ceb809ec2]
/usr/sbin/mysqld(+0x456211)[0x560ceb762211]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x1d19)[0x560ceb7676d9]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fef67da0545]
/usr/sbin/mysqld(+0x44f12d)[0x560ceb75b12d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        0                    unlimited            bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             127548               127548               processes
Max open files            1048576              1048576              files     
Max locked memory         65536                65536                bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       127548               127548               signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                   
Max realtime priority     0                    0                   
Max realtime timeout      unlimited            unlimited            us       
Core pattern: core

2020-03-20 23:59:45 139725052094720 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-03-20 23:59:45 139725052094720 [Note] InnoDB: Uses event mutexes
2020-03-20 23:59:45 139725052094720 [Note] InnoDB: Compressed tables use zlib 1.2.7
2020-03-20 23:59:45 139725052094720 [Note] InnoDB: Using Linux native AIO
2020-03-20 23:59:45 139725052094720 [Note] InnoDB: Number of pools: 1
2020-03-20 23:59:45 139725052094720 [Note] InnoDB: Using SSE2 crc32 instructions
2020-03-20 23:59:45 139725052094720 [Note] InnoDB: Initializing buffer pool, total size = 10G, instances = 10, chunk size = 128M
2020-03-20 23:59:46 139725052094720 [Note] InnoDB: Completed initialization of buffer pool
2020-03-20 23:59:46 139710676555520 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
 

cPanelLauren

Forums Analyst II
Staff member
Nov 14, 2017
10,088
877
313
Houston
This is the same error, it doesn't look like anything has changed? To resolve this more quickly can you please open a ticket using the link in my signature as I requested initially? It's extremely difficult to troubleshoot issues of this nature without access to the server. Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved.


Thanks!
 

mohammadreza

Active Member
Jan 7, 2018
32
0
6
Teh
cPanel Access Level
Root Administrator
This indicates that you've set the max_open_files and max_connections in the mysql conf at /etc/my.cnf but it does not indicate the issue with it starting. Can you please include the log messages when you attempt to restart the service. If you're unsure where the log file is you can find it listed in the mysql configuration file.
Hello
I found the problem
One of the hard drives has a problem so i cant Start MYSQL service
How is possible move db Files on mysql/dbname/... to new server? MYD,FRM,... format