Sample Header Ad - 728x90

Database Administrators

Q&A for database professionals who wish to improve their database skills

Latest Questions

0 votes
0 answers
20 views
I'm trying to run mysqld to Purge Binary Logs, but it fails with "Permission Denied"
When I run mysqld it fails as follows:- > 2025-07-31 14:47:29 0 [Warning] Can't create test file 'C:\Program > Files\MariaDB 11.4\data\AcerVero.lower-test' (Errcode: 13 "Permission > denied") C:\Program Files\MariaDB 11.4\bin\mysqld: Can't create file > 'C:\Program Files\MariaDB 11.4\data\AcerVero.e...
When I run mysqld it fails as follows:- > 2025-07-31 14:47:29 0 [Warning] Can't create test file 'C:\Program > Files\MariaDB 11.4\data\AcerVero.lower-test' (Errcode: 13 "Permission > denied") C:\Program Files\MariaDB 11.4\bin\mysqld: Can't create file > 'C:\Program Files\MariaDB 11.4\data\AcerVero.err' (errno: 13 > "Permission denied") > >2025-07-31 14:47:29 0 [Note] Starting MariaDB > 11.4.5-MariaDB source revision 0771110266ff5c04216af4bf1243c65f8c67ccf4 server_uid > MhQsFfBB48q7y378l6y8KZMY7gs= as process 29644 > >2025-07-31 14:47:29 0 > [ERROR] mysqld: Can't create/write to file '.\ddl_recovery.log' > (Errcode: 13 "Permission denied") > >2025-07-31 14:47:29 0 [ERROR] > DDL_LOG: Failed to create ddl log file: .\ddl_recovery.log > >2025-07-31 14:47:29 0 [ERROR] Aborting I've tried running it from a different drive, but that made no difference. I am logged into Windows 11 as an administrator. What am I doing wrong? Thanks in advance, Steve
Steve Franks (1 rep)
Jul 31, 2025, 01:51 PM • Last activity: Aug 1, 2025, 12:08 AM
3 votes
1 answers
1835 views
mysqld node not connecting to cluster
I'm trying to set up a basic NDB cluster, the data nodes register correctly but the mysqld API node doesn't accept Connected to Management Server at: 174.138.80.168:1186 Cluster Configuration --------------------- [ndbd(NDB)] 2 node(s) id=2 @104.131.16.252 (mysql-5.6.37 ndb-7.4.16, Nodegroup: 0, *)...
I'm trying to set up a basic NDB cluster, the data nodes register correctly but the mysqld API node doesn't accept Connected to Management Server at: 174.138.80.168:1186 Cluster Configuration --------------------- [ndbd(NDB)] 2 node(s) id=2 @104.131.16.252 (mysql-5.6.37 ndb-7.4.16, Nodegroup: 0, *) id=3 @174.138.80.126 (mysql-5.6.37 ndb-7.4.16, Nodegroup: 0) [ndb_mgmd(MGM)] 1 node(s) id=1 @174.138.80.168 (mysql-5.6.37 ndb-7.4.16) [mysqld(API)] 1 node(s) id=4 (not connected, accepting connect from manager.mysql.cluster) Manager Node's my.cnf [ndb_mgmd] config-dir=/usr/local/mysql/mysql-cluster config-file=/usr/local/mysql/mysql-cluster/config.ini # MySQL Config [mysqld] datadir=/usr/local/mysql/data socket=/tmp/mysql.sock user=mysql # Run ndb storage engine ndbcluster # IP address management node ndb-connectstring=174.138.80.168 # MySQL Pid and Log [mysqld_safe] log-error=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid Management Node's /var/lib/mysql-cluster/config.ini file [ndb_mgmd] # Management process options: hostname=manager.mysql.cluster # Hostname of the manager [ndbd] hostname=node1.mysql.cluster # Hostname of the first data node datadir=/var/lib/mysql-cluster # Remote directory for the data files [ndbd] hostname=node2.mysql.cluster # Hostname of the second data node datadir=/var/lib/mysql-cluster # Remote directory for the data files [mysqld] # SQL node options: hostname=manager.mysql.cluster Each of the data node's /etc/my.cnf files: # MySQL Config [mysqld] datadir=/usr/local/mysql/data socket=/tmp/mysql.sock user=mysql # Run ndb storage engine ndbcluster # IP address management node ndb-connectstring=174.138.80.168 [mysql_cluster] # IP address management node ndb-connectstring=174.138.80.168 # MySQL Pid and Log [mysqld_safe] log-error=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid Thanks
user133385 (31 rep)
Aug 25, 2017, 08:36 PM • Last activity: Jun 16, 2025, 08:07 PM
0 votes
1 answers
304 views
Creating MariaDB database on network drive
I'm working with **confidential data** stored on a network drive, and I need to ensure that this data never leaves the network drive. The data is a **300GB** **.mysql** file that I need to import into a MariaDB database. My setup involves a remote machine where I have mounted this network drive with...
I'm working with **confidential data** stored on a network drive, and I need to ensure that this data never leaves the network drive. The data is a **300GB** **.mysql** file that I need to import into a MariaDB database. My setup involves a remote machine where I have mounted this network drive with uid, gid set to ubuntu. My goal is to create the MariaDB database directly on the network drive due to the confidentiality requirements. I tried to change the datadir in the 50-server.cnf configuration file to a new directory located on the network drive. However, when I restart the MariaDB service, I encounter the following errors related to InnoDB:
Aug 13 06:11:15  mariadbd: 2024-08-13  6:11:15 0 [ERROR] InnoDB: The data file './ibdata1' must be writable

Aug 13 06:11:15  mariadbd: 2024-08-13  6:11:15 0 [ERROR] InnoDB: The data file './ibdata1' must be writable

Aug 13 06:11:15  mariadbd: 2024-08-13  6:11:15 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

Aug 13 06:11:15  mariadbd: 2024-08-13  6:11:15 0 [Note] Plugin 'FEEDBACK' is disabled.

Aug 13 06:11:15  mariadbd: 2024-08-13  6:11:15 0 [Note] Zerofilling moved table:  './mysql/plugin'

Aug 13 06:11:15  mariadbd: 2024-08-13  6:11:15 0 [ERROR] Unknown/unsupported storage engine: InnoDB

Aug 13 06:11:15  mariadbd: 2024-08-13  6:11:15 0 [ERROR] Aborting

Aug 13 06:11:15  systemd: mariadb.service: Main process exited, code=exited, status=1/FAILURE

Aug 13 06:11:15  systemd: mariadb.service: Failed with result 'exit-code'.
I'm not very experienced with MariaDB or setting up databases on network drives, and I'm unsure how to resolve these errors. Any help would be greatly appreciated!
Sarandeep Singh (1 rep)
Aug 13, 2024, 05:25 PM • Last activity: May 29, 2025, 12:04 AM
0 votes
0 answers
50 views
Why does removing `skip-grant-tables` cause resource conflict error for mysqld?
After hours of searching, I have managed to narrow a mysqld issue down to a point, which I cannot find reason for. I am attempting to launch multiple instances of mysqld on my Ubuntu server. When running a single instance, my process is as follows: 1) Run mysqld with an options file containing `skip...
After hours of searching, I have managed to narrow a mysqld issue down to a point, which I cannot find reason for. I am attempting to launch multiple instances of mysqld on my Ubuntu server. When running a single instance, my process is as follows: 1) Run mysqld with an options file containing skip-grant-tables 2) Use the mysql client to FLUSH PRIVILEGES; and allow root@localhost to access the server. 3) Kill the mysqld process 4) Remove the line skip-grant-tables from the options file 5) Relaunch mysqld when desired This works without issue. When I attempt to launch a second instance of mysqld, the above steps work fine also - except I cannot include step (4). If I include skip-grant-tables in my options file, mysqld launches without issue. If I remove skip-grant-tables, I get several errors:
2024-04-16T19:31:36.478828Z 0 [ERROR] [MY-011292] [Server] Plugin mysqlx reported: 'Preparation of I/O interfaces failed, X Protocol won't be accessible'
2024-04-16T19:31:36.478932Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx reported: 'Setup of bind-address: '*' port: 33060 failed, bind() failed with error: Address already in use (98). Do you already have another mysqld server running with Mysqlx ?'
2024-04-16T19:31:36.478966Z 0 [ERROR] [MY-013597] [Server] Plugin mysqlx reported: 'Value '*' set to Mysqlx_bind_address, X Plugin can't bind to it. Skipping this value.
2024-04-16T19:31:36.479059Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx reported: 'Setup of socket: '/tmp/mysqlx.sock' failed, another process with PID 419201 is using UNIX socket file'
2024-04-16T19:31:36.636815Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-04-16T19:31:36.636894Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-04-16T19:31:36.644131Z 0 [ERROR] [MY-010262] [Server] Can't start server: Bind on TCP/IP port: Address already in use
2024-04-16T19:31:36.644151Z 0 [ERROR] [MY-010257] [Server] Do you already have another mysqld server running on port: 3306 ?
2024-04-16T19:31:36.644169Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-04-16T19:31:38.237950Z 0 [System] [MY-010910] [Server] /rootInstallDir/mysql/bin/mysqld: Shutdown
2024-04-16T19:31:38.237978Z 0 [System] [MY-015016] [Server] MySQL Server - end.
I am using UNIX socket files, not ports, so I'm not sure why ports are being mentioned. Excluding log settings, my options file is:
[mysqld]
socket=/tmp/unique.sock
pid_file=/unique/path.pid
datadir=/unique/path
After many hours searching, advice, guidance or an explanation of what is causing this issue is greatly appreciated. Update ------ After further testing, I am confident the error is due to the presence of skip-grant-tables as I execute the following steps: 1) Run mysqld with options file containing skip-grant-tables. mysqld runs successfully 2) I start a second instance with skip-grant-tables. mysqld runs successfully 3) I kill the second instance 4) I start a second instance without skip-grant-tables. mysqld exits soon after starting with the error detailed above. 5) I add skip-grant-tables to the options file and start a second instance. mysqld runs successfully. Why will mysqld not start without skip-grant-tables ?
user10709800 (21 rep)
Apr 16, 2024, 08:10 PM • Last activity: Apr 17, 2024, 08:31 AM
0 votes
0 answers
29 views
I need to install MySQL 5.0.9 on a CentOS
I need to install MySQL 5.0.9 on a CentOS. But I'm failing. I realize that the installation is different from MySQL 5.7. Some help?
I need to install MySQL 5.0.9 on a CentOS. But I'm failing. I realize that the installation is different from MySQL 5.7. Some help?
f8neto (1 rep)
Jan 12, 2024, 07:06 PM
2 votes
2 answers
341 views
Mysqld process not showing all options on command line in CentOs 7
Mysqld process showed all config file options on command line in CentOs 5 and CentOs 6. But it's not showing the same in CentOs 7. I am using mysql 5.7.21 on CentOs 7 example stated below and 5.7.19 on CentOs 6 example stated below. centos 6: mysql@xxxxxxxx ==> ps -ef | grep 3306 mysql 23084 1 0 Jan...
Mysqld process showed all config file options on command line in CentOs 5 and CentOs 6. But it's not showing the same in CentOs 7. I am using mysql 5.7.21 on CentOs 7 example stated below and 5.7.19 on CentOs 6 example stated below. centos 6: mysql@xxxxxxxx ==> ps -ef | grep 3306 mysql 23084 1 0 Jan16 ? 00:00:00 /bin/sh /usr/bin/mysqld_safe --socket=/datadata/mysql.sock --port=3306 --max_allowed_packet=100M --datadir=/datadata --pid-file=/datadata/mysqld-qa.pid --max_connections=500 --open-files-limit=8192 --thread_cache_size=64 --delayed_insert_limit=4096 --query_cache_limit=1M --query_cache_size=32M --query_cache_type=1 --log_queries_not_using_indexes=off --log-error=/datalogs/mysql-error.log --expire_logs_days=3 --sort_buffer_size=2M --join_buffer_size=4M --read_buffer_size=2M --read_rnd_buffer_size=2M --tmp_table_size=64M --max_heap_table_size=64M --lower_case_table_names=0 --myisam_sort_buffer_size=16M --innodb_file_per_table --innodb_buffer_pool_size=1G --innodb_open_files=600 --innodb_max_dirty_pages_pct=10 --innodb_flush_log_at_trx_commit=0 --innodb_log_file_size=64M --innodb_log_buffer_size=4M --innodb_log_files_in_group=3 --innodb_flush_method=O_DIRECT --binlog_cache_size=64K --transaction_isolation=REPEATABLE-READ --server-id=3664 --log-bin=mysqldb01.bin --log-slave-updates --binlog_format=statement --sysdate-is-now=1 --sync-binlog=1 --sync-master-info=1 --log-queries-not-using-indexes=1 --innodb_buffer_pool_instances=5 --innodb_concurrency_tickets=1000000 --auto_increment_increment=10 --auto_increment_offset=2 --binlog_checksum=none --sql_mode=STRICT_ALL_TABLES --explicit_defaults_for_timestamp --open_files_limit=10000 --max_connections=4000 --table_open_cache=400 --binlog_format=statement --log_timestamps=SYSTEM --explicit_defaults_for_timestamp --master_info_repository=table --relay_log_info_repository=table --relay-log=dbtemp02-relay-bin --mysqld_safe_log_timestamps=SYSTEM --slave_net_timeout=3600 --default_password_lifetime=0 --relay_log_recovery=ON mysql 27230 23084 0 Jan16 ? 00:32:37 /usr/sbin/mysqld --basedir=/usr --datadir=/datadata --plugin-dir=/usr/lib64/mysql/plugin --max-allowed-packet=100M --max-connections=500 --thread-cache-size=64 --delayed-insert-limit=4096 --query-cache-limit=1M --query-cache-size=32M --query-cache-type=1 --log-queries-not-using-indexes=off --expire-logs-days=3 --sort-buffer-size=2M --join-buffer-size=4M --read-buffer-size=2M --read-rnd-buffer-size=2M --tmp-table-size=64M --max-heap-table-size=64M --lower-case-table-names=0 --myisam-sort-buffer-size=16M --innodb-file-per-table --innodb-buffer-pool-size=1G --innodb-open-files=600 --innodb-max-dirty-pages-pct=10 --innodb-flush-log-at-trx-commit=0 --innodb-log-file-size=64M --innodb-log-buffer-size=4M --innodb-log-files-in-group=3 --innodb-flush-method=O_DIRECT --binlog-cache-size=64K --transaction-isolation=REPEATABLE-READ --server-id=3664 --log-bin=mysqldb01.bin --log-slave-updates --binlog-format=statement --sysdate-is-now=1 --sync-binlog=1 --sync-master-info=1 --log-queries-not-using-indexes=1 --innodb-buffer-pool-instances=5 --innodb-concurrency-tickets=1000000 --auto-increment-increment=10 --auto-increment-offset=2 --binlog-checksum=none --sql-mode=STRICT_ALL_TABLES --explicit-defaults-for-timestamp --max-connections=4000 --table-open-cache=400 --binlog-format=statement --log-timestamps=SYSTEM --explicit-defaults-for-timestamp --master-info-repository=table --relay-log-info-repository=table --relay-log=dbtemp02-relay-bin --slave-net-timeout=3600 --default-password-lifetime=0 --relay-log-recovery=ON --log-error=/datalogs/mysql-error.log --open-files-limit=10000 --pid-file=/datadata/mysqld-qa.pid --socket=/datadata/mysql.sock --port=3306 centos 7: [mysql@xxxxxx binlogs]$ ps -ef | grep mysql mysql 16343 1 44 00:42 ? 00:53:00 /usr/sbin/mysqld --defaults-group-suffix=@0 --daemonize --pid-file=/var/run/mysqld/mysqld-0.pid Any idea how to display all variables in CentOs 7.
kasi (419 rep)
Feb 2, 2018, 08:46 AM • Last activity: Jul 20, 2023, 05:06 AM
-2 votes
1 answers
1024 views
Cannot start mysql server. Error
I'm on Ubuntu 20.4 and did some apt update/upgrade. Not sure what package was changed, but I'm unable to start my mysql server due to these error: === 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. 2022...
I'm on Ubuntu 20.4 and did some apt update/upgrade. Not sure what package was changed, but I'm unable to start my mysql server due to these error: === 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. 2022-06-09T04:05:14.093531Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead. 2022-06-09T04:05:14.093553Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.29-0ubuntu0.20.04.3) starting as process 1974 2022-06-09T04:05:14.097652Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2022-06-09T04:05:14.895737Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended. 2022-06-09T04:05:15.184723Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed. 2022-06-09T04:05:15.184755Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel. 2022-06-09T04:05:15.208172Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock 2022-06-09T04:05:15.208213Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.29-0ubuntu0.20.04.3' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu). 04:05:15 UTC - mysqld got signal 11 ; Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware. Thread pointer: 0x7f854c000b60 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 = 7f85667fbc10 thread_stack 0x78000 /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x5632646f8ad1] /usr/sbin/mysqld(print_fatal_signal(int)+0x2fb) [0x5632635997db] /usr/sbin/mysqld(handle_fatal_signal+0xa5) [0x563263599895] /lib/x86_64-linux-gnu/libpthread.so.0(+0x14420) [0x7f85e376e420] /usr/sbin/mysqld(page_cur_search_with_match_bytes(buf_block_t const*, dict_index_t const*, dtuple_t const*, page_cur_mode_t, unsigned long*, unsigned long*, unsigned long*, unsigned long*, page_cur_t*)+0x1c2) [0x56326484f482] /usr/sbin/mysqld(btr_cur_search_to_nth_level(dict_index_t*, unsigned long, dtuple_t const*, page_cur_mode_t, unsigned long, btr_cur_t*, unsigned long, char const*, unsigned long, mtr_t*)+0x1f62) [0x5632649c0c82] /usr/sbin/mysqld(row_search_on_row_ref(btr_pcur_t*, unsigned long, dict_table_t*, dtuple_t const*, mtr_t*)+0xd3) [0x5632648c40b3] /usr/sbin/mysqld(+0x2452899) [0x5632648ba899] /usr/sbin/mysqld(+0x24532d1) [0x5632648bb2d1] /usr/sbin/mysqld(row_purge_step(que_thr_t*)+0x92a) [0x5632648bf33a] /usr/sbin/mysqld(que_run_threads(que_thr_t*)+0xe28) [0x563264870348] /usr/sbin/mysqld(srv_worker_thread()+0x580) [0x5632648fc400] /usr/sbin/mysqld(std::thread::_State_impl > >::_M_run()+0xbc) [0x56326480208c] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xd6de4) [0x7f85e2cc5de4] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8609) [0x7f85e3762609] /lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7f85e29b2133] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0): is an invalid pointer Connection ID (thread ID): 0 Status: NOT_KILLED === Stuck and my web sites are down. Any help regarding the bug or reverting all the update the last hours appreciated.
user42124 (1 rep)
Jun 9, 2022, 04:15 AM • Last activity: Jun 9, 2022, 07:23 PM
1 votes
1 answers
7287 views
Wordpress causes high CPU usage (mysqld)
I have a **wordpress** site with 500k posts in MYSQL database running on debian dedicated server: **Server OS**: Debian 8 "Jesssie)" - Linux version 4.9.58-xxxx-std-ipv6-64 (kernel@kernel.ovh.net) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Mon Oct 23 11:35:59 CEST 2017 (Ispconfig) **Web...
I have a **wordpress** site with 500k posts in MYSQL database running on debian dedicated server: **Server OS**: Debian 8 "Jesssie)" - Linux version 4.9.58-xxxx-std-ipv6-64 (kernel@kernel.ovh.net) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Mon Oct 23 11:35:59 CEST 2017 (Ispconfig) **Web server**: Server version: Apache/2.4.10 (Debian) **PHP**: PHP Version 7.1.8 **Procesor**: Intel 2x Xeon E5-2630v3 - 16/32t - 2.4GHz /3.2GHz **RAM**: 128GB DDR4 ECC 1866 MHz **Disks**: SoftRaid 2x450GB SSD NVMe Today I noticed that MySQL is causing a high CPU usage: > 2383 mysql 20 0 68.666g 7.596g 11152 S **2435%** 6.0 108:43.00 > mysqld **top**: top - 18:05:42 up 6 min, 1 user, load average: 23.29, 14.22, 6.09 Tasks: 548 total, 4 running, 544 sleeping, 0 stopped, 0 zombie %Cpu0 : 25.8 us, 61.0 sy, 0.0 ni, 13.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu1 : 25.2 us, 57.7 sy, 0.0 ni, 17.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu2 : 24.7 us, 49.3 sy, 0.0 ni, 26.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu3 : 53.6 us, 15.9 sy, 0.0 ni, 30.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu4 : 27.0 us, 43.0 sy, 0.0 ni, 30.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu5 : 24.8 us, 41.3 sy, 0.0 ni, 33.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu6 : 59.3 us, 31.8 sy, 0.0 ni, 8.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu7 : 21.6 us, 63.2 sy, 0.0 ni, 15.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu8 : 41.5 us, 40.5 sy, 0.0 ni, 18.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu9 : 51.5 us, 35.6 sy, 0.0 ni, 12.5 id, 0.3 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu10 : 41.0 us, 39.2 sy, 0.0 ni, 19.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu11 : 55.4 us, 33.2 sy, 0.0 ni, 11.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu12 : 76.9 us, 10.0 sy, 0.0 ni, 13.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu13 : 81.7 us, 3.0 sy, 0.0 ni, 15.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu14 : 31.8 us, 43.2 sy, 0.0 ni, 25.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu15 : 35.3 us, 58.7 sy, 0.0 ni, 6.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu16 : 24.4 us, 52.5 sy, 0.0 ni, 23.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu17 : 26.0 us, 64.3 sy, 0.0 ni, 9.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu18 : 34.9 us, 36.6 sy, 0.0 ni, 28.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu19 : 20.0 us, 46.7 sy, 0.0 ni, 33.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu20 : 86.3 us, 1.0 sy, 0.0 ni, 12.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu21 : 36.2 us, 51.2 sy, 0.0 ni, 12.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu22 : 25.5 us, 46.0 sy, 0.0 ni, 28.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu23 : 19.7 us, 41.5 sy, 0.0 ni, 38.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu24 : 62.3 us, 4.6 sy, 0.0 ni, 33.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu25 : 26.3 us, 60.9 sy, 0.0 ni, 12.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu26 : 57.3 us, 24.7 sy, 0.0 ni, 18.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu27 : 73.6 us, 7.9 sy, 0.0 ni, 18.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu28 : 21.7 us, 42.8 sy, 0.0 ni, 35.1 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st %Cpu29 : 43.3 us, 37.0 sy, 0.0 ni, 19.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu30 : 26.2 us, 57.8 sy, 0.0 ni, 15.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu31 : 28.2 us, 65.8 sy, 0.0 ni, 5.7 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st KiB Mem: 13198007+total, 16391500 used, 11558857+free, 86084 buffers KiB Swap: 1046520 total, 0 used, 1046520 free. 5456440 cached Mem **show full processlist;** mysql> show full processlist; +------+---------------+-----------+---------------+---------+------+----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Id | User | Host | db | Command | Time | State | Info | +------+---------------+-----------+---------------+---------+------+----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 1541 | root | localhost | NULL | Query | 0 | NULL | show full processlist | | 1604 | c1database | localhost | c1database | Query | 2 | Sending data | SELECT post_id FROM wp_postmeta WHERE meta_key = '_wp_attached_file' AND meta_value = '2018/01/amp.jpg' | | 1605 | c1database | localhost | c1database | Query | 1 | Sending data | SELECT post_id FROM wp_postmeta WHERE meta_key = '_wp_attached_file' AND meta_value = '2018/01/amp.jpg' | | 1610 | c1database | localhost | c1database | Query | 0 | Sorting result | SELECT t.*, tt.* FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id WHERE tt.taxonomy IN ('post_tag') AND tt.count > 0 ORDER BY tt.count DESC LIMIT 45 | | 1611 | c1database | localhost | c1database | Query | 6 | Sorting result | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1613 | c1database | localhost | c1database | Query | 5 | Sorting result | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1614 | c1database | localhost | c1database | Query | 4 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1615 | c1database | localhost | c1database | Query | 3 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1616 | c1database | localhost | c1database | Query | 3 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1617 | c1database | localhost | c1database | Query | 2 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1618 | c1database | localhost | c1database | Query | 2 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1619 | c1database | localhost | c1database | Query | 2 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1620 | c1database | localhost | c1database | Query | 2 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1621 | c1database | localhost | c1database | Query | 2 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1622 | c1database | localhost | c1database | Query | 2 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1623 | c1database | localhost | c1database | Query | 1 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1624 | c1database | localhost | c1database | Query | 1 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1625 | c1database | localhost | c1database | Query | 1 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1626 | c1database | localhost | c1database | Query | 1 | Sending data | SELECT post_id FROM wp_postmeta WHERE meta_key = '_wp_attached_file' AND meta_value = '2018/01/amp.jpg' | | 1627 | c1database | localhost | c1database | Query | 1 | Sending data | SELECT post_id FROM wp_postmeta WHERE meta_key = '_wp_attached_file' AND meta_value = '2018/01/amp.jpg' | | 1628 | c1database | localhost | c1database | Query | 1 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1629 | c1database | localhost | c1database | Query | 1 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1630 | c1database | localhost | c1database | Query | 0 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY RAND() LIMIT 0, 10 | | 1631 | c1database | localhost | c1database | Query | 0 | Sending data | SELECT post_id FROM wp_postmeta WHERE meta_key = '_wp_attached_file' AND meta_value = '2018/01/amp.jpg' | | 1632 | c1database | localhost | c1database | Query | 0 | Sending data | SELECT post_id FROM wp_postmeta WHERE meta_key = '_wp_attached_file' AND meta_value = '2018/01/amp.jpg' | +------+---------------+-----------+---------------+---------+------+----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 25 rows in set (0.00 sec) mysql> **my.cnf (MySQL):** innodb_buffer_pool_size = 61440M innodb_file_per_table=1 innodb_log_file_size = 1024M innodb_buffer_pool_instances=60 key_buffer = 2048M max_allowed_packet = 16M thread_stack = 192K thread_cache_size = 8 # This replaces the startup script and checks MyISAM tables if needed # the first time they are touched myisam-recover = BACKUP #max_connections = 100 #table_cache = 64 #thread_concurrency = 10 # # * Query Cache Configuration # query_cache_limit = 1M query_cache_size = 0 query_cache_type = 0 #query_cache_size = 8192M **25 queries** have caused my MySQL to generate over **2435% CPU usage**. Any advice? Thank you!
Martin Smith (13 rep)
Jan 31, 2018, 11:23 PM • Last activity: Sep 9, 2021, 03:04 PM
3 votes
1 answers
1502 views
mysqld not starting up
I installed mysql on ubuntu. mysqld does not startup with the following errors - 2017-04-16T00:22:35.320639Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2017-04-16T00:22:35.321014Z 0 [Note] InnoDB: Buffer pool(s) load completed at 170415 19:22:35 2017-04-16T00:22:35.32...
I installed mysql on ubuntu. mysqld does not startup with the following errors - 2017-04-16T00:22:35.320639Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2017-04-16T00:22:35.321014Z 0 [Note] InnoDB: Buffer pool(s) load completed at 170415 19:22:35 2017-04-16T00:22:35.321036Z 0 [Note] Plugin 'FEDERATED' is disabled. mysqld: Table 'mysql.plugin' doesn't exist 2017-04-16T00:22:35.321354Z 0 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 2017-04-16T00:22:35.322301Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened. 2017-04-16T00:22:35.322490Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key 2017-04-16T00:22:35.323247Z 0 [Note] Server hostname (bind-address): '*'; port: 3306 2017-04-16T00:22:35.323361Z 0 [Note] IPv6 is available. 2017-04-16T00:22:35.323379Z 0 [Note] - '::' resolves to '::'; 2017-04-16T00:22:35.323411Z 0 [Note] Server socket created on IP: '::'. 2017-04-16T00:22:35.323450Z 0 [ERROR] Could not create unix socket lock file /var/run/mysqld/mysqld.sock.lock. 2017-04-16T00:22:35.323464Z 0 [ERROR] Unable to setup unix socket lock file. 2017-04-16T00:22:35.323476Z 0 [ERROR] Aborting 2017-04-16T00:22:35.323497Z 0 [Note] Binlog end 2017-04-16T00:22:35.323545Z 0 [Note] Shutting down plugin 'ngram' Please help. Thanks
user122918 (31 rep)
Apr 16, 2017, 12:35 AM • Last activity: Sep 1, 2021, 03:08 PM
0 votes
5 answers
579 views
mysqld process performance
I'm running in problems that I can't solve by myself. Mysqld process go over 100%, sometimes over 500% in web peaks. Idk why mysql running only one process, websites works fast without any problem with db, but the server is on fire :) Thanks for help. **Glances screenshot** [![enter image descriptio...
I'm running in problems that I can't solve by myself. Mysqld process go over 100%, sometimes over 500% in web peaks. Idk why mysql running only one process, websites works fast without any problem with db, but the server is on fire :) Thanks for help. **Glances screenshot** enter image description here **PMA stats** enter image description here **Mysql conf** # # These groups are read by MariaDB server. # Use it for options that only the server (but not clients) should see # # See the examples of server my.cnf files in /usr/share/mysql # this is read by the standalone daemon and embedded servers [server] # this is only for the mysqld standalone daemon [mysqld] # # * Basic Settings # user = mysql pid-file = /run/mysqld/mysqld.pid socket = /run/mysqld/mysqld.sock #port = 3306 basedir = /usr datadir = /var/lib/mysql tmpdir = /tmp lc-messages-dir = /usr/share/mysql #skip-external-locking # Instead of skip-networking the default is now to listen only on # localhost which is more compatible and is not less secure. #bind-address = 127.0.0.1 # # * Fine Tuning # #key_buffer_size = 16M #max_allowed_packet = 16M #thread_stack = 192K #thread_cache_size = 8 # This replaces the startup script and checks MyISAM tables if needed # the first time they are touched #myisam_recover_options = BACKUP #max_connections = 100 #table_cache = 64 #thread_concurrency = 10 # # * Query Cache Configuration # query_cache_limit = 3M query_cache_size = 512M # # * Logging and Replication # # Both location gets rotated by the cronjob. # Be aware that this log type is a performance killer. # As of 5.1 you can enable the log at runtime! #general_log_file = /var/log/mysql/mysql.log #general_log = 1 # # Error log - should be very few entries. # log_error = /var/log/mysql/error.log # # Enable the slow query log to see queries with especially long duration slow_query_log_file = /var/log/mysql/mariadb-slow.log long_query_time = 10 log_slow_rate_limit = 1000 log_slow_verbosity = query_plan #log-queries-not-using-indexes # # The following can be used as easy to replay backup logs or for replication. # note: if you are setting up a replication slave, see README.Debian about # other settings you may need to change. #server-id = 1 #log_bin = /var/log/mysql/mysql-bin.log expire_logs_days = 10 #max_binlog_size = 100M #binlog_do_db = include_database_name #binlog_ignore_db = exclude_database_name # # * Security Features # # Read the manual, too, if you want chroot! #chroot = /var/lib/mysql/ # # For generating SSL certificates you can use for example the GUI tool "tinyca". # #ssl-ca = /etc/mysql/cacert.pem #ssl-cert = /etc/mysql/server-cert.pem #ssl-key = /etc/mysql/server-key.pem # # Accept only connections using the latest and most secure TLS protocol version. # ..when MariaDB is compiled with OpenSSL: #ssl-cipher = TLSv1.2 # ..when MariaDB is compiled with YaSSL (default in Debian): #ssl = on # # * Character sets # # MySQL/MariaDB default is Latin1, but in Debian we rather default to the full # utf8 4-byte character set. See also client.cnf # character-set-server = utf8mb4 collation-server = utf8mb4_general_ci # # * InnoDB # # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/. # Read the manual for more InnoDB related options. There are many! # # * Unix socket authentication plugin is built-in since 10.0.22-6 # # Needed so the root database user can authenticate without a password but # only when running as the unix root user. # # Also available for other users if required. # See https://mariadb.com/kb/en/unix_socket-authentication-plugin/ # this is only for embedded server [embedded] # This group is only read by MariaDB servers, not by MySQL. # If you use the same .cnf file for MySQL and MariaDB, # you can put MariaDB-only options here [mariadb] # This group is only read by MariaDB-10.3 servers. # If you use the same .cnf file for MariaDB of different versions, # use this group for options that older servers don't understand [mariadb-10.3] **innodb status** ===================================== 2021-05-18 07:28:40 0x7fa254ae1700 INNODB MONITOR OUTPUT ===================================== Per second averages calculated from the last 20 seconds ----------------- BACKGROUND THREAD ----------------- srv_master_thread loops: 0 srv_active, 0 srv_shutdown, 2071 srv_idle srv_master_thread log flush and writes: 2071 ---------- SEMAPHORES ---------- OS WAIT ARRAY INFO: reservation count 91905 OS WAIT ARRAY INFO: signal count 308896 RW-shared spins 30399106, rounds 62424994, OS waits 24849 RW-excl spins 70580, rounds 75923, OS waits 1236 RW-sx spins 2, rounds 31, OS waits 1 Spin rounds per wait: 2.05 RW-shared, 1.08 RW-excl, 15.50 RW-sx ------------ TRANSACTIONS ------------ Trx id counter 702288838 Purge done for trx's n:o = 702288838, sees < 702288838 ---TRANSACTION 421810504253824, not started 0 lock struct(s), heap size 1128, 0 row lock(s) ---TRANSACTION 421810504245392, not started 0 lock struct(s), heap size 1128, 0 row lock(s) -------- FILE I/O -------- I/O thread 0 state: waiting for completed aio requests (insert buffer thread) I/O thread 1 state: waiting for completed aio requests (log thread) I/O thread 2 state: waiting for completed aio requests (read thread) I/O thread 3 state: waiting for completed aio requests (read thread) I/O thread 4 state: waiting for completed aio requests (read thread) I/O thread 5 state: waiting for completed aio requests (read thread) I/O thread 6 state: waiting for completed aio requests (write thread) I/O thread 7 state: waiting for completed aio requests (write thread) I/O thread 8 state: waiting for completed aio requests (write thread) I/O thread 9 state: waiting for completed aio requests (write thread) Pending normal aio reads: [0, 0, 0, 0] , aio writes: [0, 0, 0, 0] , ibuf aio reads:, log i/o's:, sync i/o's: Pending flushes (fsync) log: 0; buffer pool: 0 112634734 OS file reads, 21796 OS file writes, 13046 OS fsyncs 1 pending reads, 0 pending writes 38857.36 reads/s, 16384 avg bytes/read, 9.55 writes/s, 4.55 fsyncs/s ------------------------------------- INSERT BUFFER AND ADAPTIVE HASH INDEX ------------------------------------- Ibuf: size 1, free list len 20, seg size 22, 3 merges merged operations: insert 3, delete mark 0, delete 0 discarded operations: insert 0, delete mark 0, delete 0 Hash table size 34679, node heap has 1 buffer(s) Hash table size 34679, node heap has 16 buffer(s) Hash table size 34679, node heap has 1 buffer(s) Hash table size 34679, node heap has 1 buffer(s) Hash table size 34679, node heap has 2 buffer(s) Hash table size 34679, node heap has 1 buffer(s) Hash table size 34679, node heap has 1 buffer(s) Hash table size 34679, node heap has 1 buffer(s) 0.50 hash searches/s, 5.45 non-hash searches/s --- LOG --- Log sequence number 18286288975 Log flushed up to 18286288953 Pages flushed up to 18286288408 Last checkpoint at 18286288339 0 pending log flushes, 0 pending chkp writes 6692 log i/o's done, 2.70 log i/o's/second ---------------------- BUFFER POOL AND MEMORY ---------------------- Total large memory allocated 170655744 Dictionary memory allocated 274160 Buffer pool size 8192 Free buffers 0 Database pages 8168 Old database pages 3003 Modified db pages 4 Percent of dirty pages(LRU & free pages): 0.049 Max dirty pages percent: 75.000 Pending reads 1 Pending writes: LRU 0, flush list 0, single page 0 Pages made young 1447105, not young 960198976 0.00 youngs/s, 371282.29 non-youngs/s Pages read 112634979, created 220, written 12713 38857.26 reads/s, 0.00 creates/s, 6.30 writes/s Buffer pool hit rate 928 / 1000, young-making rate 0 / 1000 not 685 / 1000 Pages read ahead 2432.43/s, evicted without access 182.74/s, Random read ahead 0.00/s LRU len: 8168, unzip_LRU len: 0 I/O sum:cur, unzip sum:cur -------------- ROW OPERATIONS -------------- 0 queries inside InnoDB, 0 queries in queue 1 read views open inside InnoDB Process ID=15562, Main thread ID=140334759667456, state: sleeping Number of rows inserted 1556, updated 704, deleted 113, read 2705916905 0.70 inserts/s, 0.00 updates/s, 0.00 deletes/s, 1027711.31 reads/s Number of system rows inserted 0, updated 0, deleted 0, read 0 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s ---------------------------- END OF INNODB MONITOR OUTPUT ============================ **Global status** Aborted_clients 0 Aborted_connects 7 Access_denied_errors 6 Acl_column_grants 0 Acl_database_grants 16 Acl_function_grants 0 Acl_procedure_grants 0 Acl_package_spec_grants 0 Acl_package_body_grants 0 Acl_proxy_users 1 Acl_role_grants 0 Acl_roles 0 Acl_table_grants 0 Acl_users 17 Aria_pagecache_blocks_not_flushed 0 Aria_pagecache_blocks_unused 15706 Aria_pagecache_blocks_used 1755 Aria_pagecache_read_requests 328323 Aria_pagecache_reads 5310 Aria_pagecache_write_requests 108520 Aria_pagecache_writes 108520 Aria_transaction_log_syncs 49 Binlog_commits 0 Binlog_group_commits 0 Binlog_group_commit_trigger_count 0 Binlog_group_commit_trigger_lock_wait 0 Binlog_group_commit_trigger_timeout 0 Binlog_snapshot_file Binlog_snapshot_position 0 Binlog_bytes_written 0 Binlog_cache_disk_use 0 Binlog_cache_use 0 Binlog_stmt_cache_disk_use 0 Binlog_stmt_cache_use 0 Busy_time 0.000000 Bytes_received 32955992 Bytes_sent 2811242294 Column_compressions 0 Column_decompressions 0 Com_admin_commands 0 Com_alter_db 0 Com_alter_db_upgrade 0 Com_alter_event 0 Com_alter_function 0 Com_alter_procedure 0 Com_alter_server 0 Com_alter_sequence 0 Com_alter_table 0 Com_alter_tablespace 0 Com_alter_user 0 Com_analyze 0 Com_assign_to_keycache 0 Com_begin 0 Com_binlog 0 Com_call_procedure 0 Com_change_db 2377 Com_change_master 0 Com_check 0 Com_checksum 0 Com_commit 0 Com_compound_sql 0 Com_create_db 0 Com_create_event 0 Com_create_function 0 Com_create_index 0 Com_create_package 0 Com_create_package_body 0 Com_create_procedure 0 Com_create_role 0 Com_create_sequence 0 Com_create_server 0 Com_create_table 0 Com_create_temporary_table 0 Com_create_trigger 0 Com_create_udf 0 Com_create_user 0 Com_create_view 0 Com_dealloc_sql 0 Com_delete 102 Com_delete_multi 0 Com_do 0 Com_drop_db 0 Com_drop_event 0 Com_drop_function 0 Com_drop_index 0 Com_drop_procedure 0 Com_drop_package 0 Com_drop_package_body 0 Com_drop_role 0 Com_drop_server 0 Com_drop_sequence 0 Com_drop_table 0 Com_drop_temporary_table 0 Com_drop_trigger 0 Com_drop_user 0 Com_drop_view 0 Com_empty_query 0 Com_execute_immediate 0 Com_execute_sql 0 Com_flush 0 Com_get_diagnostics 0 Com_grant 0 Com_grant_role 0 Com_ha_close 0 Com_ha_open 0 Com_ha_read 0 Com_help 0 Com_insert 1445 Com_insert_select 0 Com_install_plugin 0 Com_kill 0 Com_load 0 Com_lock_tables 0 Com_multi 0 Com_optimize 0 Com_preload_keys 0 Com_prepare_sql 0 Com_purge 0 Com_purge_before_date 0 Com_release_savepoint 0 Com_rename_table 0 Com_rename_user 0 Com_repair 0 Com_replace 0 Com_replace_select 0 Com_reset 0 Com_resignal 0 Com_revoke 0 Com_revoke_all 0 Com_revoke_role 0 Com_rollback 0 Com_rollback_to_savepoint 0 Com_savepoint 0 Com_select 130176 Com_set_option 7437 Com_show_authors 0 Com_show_binlog_events 0 Com_show_binlogs 0 Com_show_charsets 0 Com_show_collations 0 Com_show_contributors 0 Com_show_create_db 0 Com_show_create_event 0 Com_show_create_func 0 Com_show_create_package 0 Com_show_create_package_body 0 Com_show_create_proc 0 Com_show_create_table 0 Com_show_create_trigger 0 Com_show_create_user 0 Com_show_databases 0 Com_show_engine_logs 0 Com_show_engine_mutex 0 Com_show_engine_status 1 Com_show_errors 0 Com_show_events 0 Com_show_explain 0 Com_show_fields 3706 Com_show_function_status 0 Com_show_generic 0 Com_show_grants 0 Com_show_keys 48 Com_show_master_status 126 Com_show_open_tables 0 Com_show_package_status 0 Com_show_package_body_status 0 Com_show_plugins 0 Com_show_privileges 0 Com_show_procedure_status 0 Com_show_processlist 91 Com_show_profile 0 Com_show_profiles 0 Com_show_relaylog_events 0 Com_show_slave_hosts 0 Com_show_slave_status 126 Com_show_status 170 Com_show_storage_engines 0 Com_show_table_status 0 Com_show_tables 1 Com_show_triggers 0 Com_show_variables 149 Com_show_warnings 2 Com_shutdown 0 Com_signal 0 Com_start_all_slaves 0 Com_start_slave 0 Com_stmt_close 0 Com_stmt_execute 0 Com_stmt_fetch 0 Com_stmt_prepare 0 Com_stmt_reprepare 0 Com_stmt_reset 0 Com_stmt_send_long_data 0 Com_stop_all_slaves 0 Com_stop_slave 0 Com_truncate 0 Com_uninstall_plugin 0 Com_unlock_tables 0 Com_update 79463 Com_update_multi 0 Com_xa_commit 0 Com_xa_end 0 Com_xa_prepare 0 Com_xa_recover 0 Com_xa_rollback 0 Com_xa_start 0 Compression OFF Connection_errors_accept 0 Connection_errors_internal 0 Connection_errors_max_connections 0 Connection_errors_peer_address 0 Connection_errors_select 0 Connection_errors_tcpwrap 0 Connections 3702 Cpu_time 0.000000 Created_tmp_disk_tables 5310 Created_tmp_files 5 Created_tmp_tables 6267 Delayed_errors 0 Delayed_insert_threads 0 Delayed_writes 0 Delete_scan 34 Empty_queries 22185 Executed_events 0 Executed_triggers 0 Feature_check_constraint 0 Feature_custom_aggregate_functions 0 Feature_delay_key_write 0 Feature_dynamic_columns 0 Feature_fulltext 0 Feature_gis 0 Feature_invisible_columns 0 Feature_json 0 Feature_locale 142 Feature_subquery 139 Feature_system_versioning 0 Feature_timezone 0 Feature_trigger 0 Feature_window_functions 0 Feature_xml 0 Flush_commands 1 Handler_commit 108826 Handler_delete 103 Handler_discover 0 Handler_external_lock 0 Handler_icp_attempts 14767 Handler_icp_match 14764 Handler_mrr_init 0 Handler_mrr_key_refills 0 Handler_mrr_rowid_refills 0 Handler_prepare 0 Handler_read_first 1899 Handler_read_key 90853 Handler_read_last 587 Handler_read_next 196570228 Handler_read_prev 5958699 Handler_read_retry 0 Handler_read_rnd 23321 Handler_read_rnd_deleted 2 Handler_read_rnd_next 2320508904 Handler_rollback 27 Handler_savepoint 0 Handler_savepoint_rollback 0 Handler_tmp_delete 0 Handler_tmp_update 6 Handler_tmp_write 452577 Handler_update 79571 Handler_write 1445 Innodb_buffer_pool_dump_status Innodb_buffer_pool_load_status Buffer pool(s) load completed at 210518  6:54:02 Innodb_buffer_pool_resize_status Innodb_buffer_pool_load_incomplete OFF Innodb_buffer_pool_pages_data 8169 Innodb_buffer_pool_bytes_data 133840896 Innodb_buffer_pool_pages_dirty 4 Innodb_buffer_pool_bytes_dirty 65536 Innodb_buffer_pool_pages_flushed 10792 Innodb_buffer_pool_pages_free 0 Innodb_buffer_pool_pages_misc 23 Innodb_buffer_pool_pages_total 8192 Innodb_buffer_pool_read_ahead_rnd 0 Innodb_buffer_pool_read_ahead 5192384 Innodb_buffer_pool_read_ahead_evicted 673851 Innodb_buffer_pool_read_requests 1304826605 Innodb_buffer_pool_reads 100447238 Innodb_buffer_pool_wait_free 174313 Innodb_buffer_pool_write_requests 20725 Innodb_data_fsyncs 12305 Innodb_data_pending_fsyncs 0 Innodb_data_pending_reads 0 Innodb_data_pending_writes 0 Innodb_data_read 1730815887872 Innodb_data_reads 105640389 Innodb_data_writes 20461 Innodb_data_written 395168256 Innodb_dblwr_pages_written 11792 Innodb_dblwr_writes 2306 Innodb_log_waits 0 Innodb_log_write_requests 4286 Innodb_log_writes 4620 Innodb_os_log_fsyncs 6228 Innodb_os_log_pending_fsyncs 0 Innodb_os_log_pending_writes 0 Innodb_os_log_written 5798400 Innodb_page_size 16384 Innodb_pages_created 215 Innodb_pages_read 105640616 Innodb_pages0_read 106 Innodb_pages_written 11923 Innodb_row_lock_current_waits 0 Innodb_row_lock_time 7 Innodb_row_lock_time_avg 3 Innodb_row_lock_time_max 6 Innodb_row_lock_waits 2 Innodb_rows_deleted 103 Innodb_rows_inserted 1445 Innodb_rows_read 2522664847 Innodb_rows_updated 689 Innodb_system_rows_deleted 0 Innodb_system_rows_inserted 0 Innodb_system_rows_read 0 Innodb_system_rows_updated 0 Innodb_num_open_files 109 Innodb_truncated_status_writes 0 Innodb_available_undo_logs 128 Innodb_undo_truncations 0 Innodb_page_compression_saved 0 Innodb_num_index_pages_written 0 Innodb_num_non_index_pages_written 0 Innodb_num_pages_page_compressed 0 Innodb_num_page_compressed_trim_op 0 Innodb_num_pages_page_decompressed 0 Innodb_num_pages_page_compression_error 0 Innodb_num_pages_encrypted 0 Innodb_num_pages_decrypted 0 Innodb_have_lz4 ON Innodb_have_lzo OFF Innodb_have_lzma OFF Innodb_have_bzip2 OFF Innodb_have_snappy ON Innodb_have_punch_hole ON Innodb_defragment_compression_failures 0 Innodb_defragment_failures 0 Innodb_defragment_count 0 Innodb_instant_alter_column 0 Innodb_onlineddl_rowlog_rows 0 Innodb_onlineddl_rowlog_pct_used 0 Innodb_onlineddl_pct_progress 0 Innodb_secondary_index_triggered_cluster_reads 17047 Innodb_secondary_index_triggered_cluster_reads_avo... 0 Innodb_encryption_rotation_pages_read_from_cache 0 Innodb_encryption_rotation_pages_read_from_disk 0 Innodb_encryption_rotation_pages_modified 0 Innodb_encryption_rotation_pages_flushed 0 Innodb_encryption_rotation_estimated_iops 0 Innodb_encryption_key_rotation_list_length 0 Innodb_encryption_n_merge_blocks_encrypted 0 Innodb_encryption_n_merge_blocks_decrypted 0 Innodb_encryption_n_rowlog_blocks_encrypted 0 Innodb_encryption_n_rowlog_blocks_decrypted 0 Innodb_encryption_n_temp_blocks_encrypted 0 Innodb_encryption_n_temp_blocks_decrypted 0 Innodb_scrub_background_page_reorganizations 0 Innodb_scrub_background_page_splits 0 Innodb_scrub_background_page_split_failures_underf... 0 Innodb_scrub_background_page_split_failures_out_of... 0 Innodb_scrub_background_page_split_failures_missin... 0 Innodb_scrub_background_page_split_failures_unknow... 0 Innodb_scrub_log 0 Innodb_encryption_num_key_requests 0 Key_blocks_not_flushed 0 Key_blocks_unused 107162 Key_blocks_used 1 Key_blocks_warm 0 Key_read_requests 18 Key_reads 1 Key_write_requests 0 Key_writes 0 Last_query_cost 0.000000 Master_gtid_wait_count 0 Master_gtid_wait_time 0 Master_gtid_wait_timeouts 0 Max_statement_time_exceeded 0 Max_used_connections 24 Memory_used 817596480 Memory_used_initial 809934208 Not_flushed_delayed_rows 0 Open_files 27 Open_streams 0 Open_table_definitions 120 Open_tables 165 Opened_files 21443 Opened_plugin_libraries 0 Opened_table_definitions 119 Opened_tables 171 Opened_views 0 Performance_schema_accounts_lost 0 Performance_schema_cond_classes_lost 0 Performance_schema_cond_instances_lost 0 Performance_schema_digest_lost 0 Performance_schema_file_classes_lost 0 Performance_schema_file_handles_lost 0 Performance_schema_file_instances_lost 0 Performance_schema_hosts_lost 0 Performance_schema_locker_lost 0 Performance_schema_mutex_classes_lost 0 Performance_schema_mutex_instances_lost 0 Performance_schema_rwlock_classes_lost 0 Performance_schema_rwlock_instances_lost 0 Performance_schema_session_connect_attrs_lost 0 Performance_schema_socket_classes_lost 0 Performance_schema_socket_instances_lost 0 Performance_schema_stage_classes_lost 0 Performance_schema_statement_classes_lost 0 Performance_schema_table_handles_lost 0 Performance_schema_table_instances_lost 0 Performance_schema_thread_classes_lost 0 Performance_schema_thread_instances_lost 0 Performance_schema_users_lost 0 Prepared_stmt_count 0 Qcache_free_blocks 903 Qcache_free_memory 489504208 Qcache_hits 98707 Qcache_inserts 25058 Qcache_lowmem_prunes 0 Qcache_not_cached 6619 Qcache_queries_in_cache 13668 Qcache_total_blocks 28525 Queries 229107 Questions 229107 Rows_read 2522113042 Rows_sent 14378120 Rows_tmp_read 458710 Rpl_semi_sync_master_clients 0 Rpl_semi_sync_master_get_ack 0 Rpl_semi_sync_master_net_avg_wait_time 0 Rpl_semi_sync_master_net_wait_time 0 Rpl_semi_sync_master_net_waits 0 Rpl_semi_sync_master_no_times 0 Rpl_semi_sync_master_no_tx 0 Rpl_semi_sync_master_request_ack 0 Rpl_semi_sync_master_status OFF Rpl_semi_sync_master_timefunc_failures 0 Rpl_semi_sync_master_tx_avg_wait_time 0 Rpl_semi_sync_master_tx_wait_time 0 Rpl_semi_sync_master_tx_waits 0 Rpl_semi_sync_master_wait_pos_backtraverse 0 Rpl_semi_sync_master_wait_sessions 0 Rpl_semi_sync_master_yes_tx 0 Rpl_semi_sync_slave_send_ack 0 Rpl_semi_sync_slave_status OFF Rpl_status AUTH_MASTER Rpl_transactions_multi_engine 0 Select_full_join 180 Select_full_range_join 0 Select_range 1662 Select_range_check 0 Select_scan 23758 Slave_connections 0 Slave_heartbeat_period 0.000 Slave_open_temp_tables 0 Slave_received_heartbeats 0 Slave_retried_transactions 0 Slave_running OFF Slave_skipped_errors 0 Slaves_connected 0 Slaves_running 0 Slow_launch_threads 0 Slow_queries 0 Sort_merge_passes 0 Sort_priority_queue_sorts 1627 Sort_range 339 Sort_rows 23495 Sort_scan 3369 Ssl_accept_renegotiates 0 Ssl_accepts 0 Ssl_callback_cache_hits 0 Ssl_cipher Ssl_cipher_list Ssl_client_connects 0 Ssl_connect_renegotiates 0 Ssl_ctx_verify_depth 0 Ssl_ctx_verify_mode 0 Ssl_default_timeout 0 Ssl_finished_accepts 0 Ssl_finished_connects 0 Ssl_server_not_after Ssl_server_not_before Ssl_session_cache_hits 0 Ssl_session_cache_misses 0 Ssl_session_cache_mode NONE Ssl_session_cache_overflows 0 Ssl_session_cache_size 0 Ssl_session_cache_timeouts 0 Ssl_sessions_reused 0 Ssl_used_session_cache_entries 0 Ssl_verify_depth 0 Ssl_verify_mode 0 Ssl_version Subquery_cache_hit 0 Subquery_cache_miss 0 Syncs 100 Table_locks_immediate 132 Table_locks_waited 0 Table_open_cache_active_instances 1 Table_open_cache_hits 114847 Table_open_cache_misses 371 Table_open_cache_overflows 0 Tc_log_max_pages_used 0 Tc_log_page_size 4096 Tc_log_page_waits 0 Threadpool_idle_threads 0 Threadpool_threads 0 Threads_cached 19 Threads_connected 5 Threads_created 24 Threads_running 8 Transactions_gtid_foreign_engine 0 Transactions_multi_engine 0 Update_scan 441 Uptime 1918 Uptime_since_flush_status 1918 wsrep_applier_thread_count 0 wsrep_cluster_conf_id 18446744073709551615 wsrep_cluster_size 0 wsrep_cluster_state_uuid wsrep_cluster_status Disconnected wsrep_connected OFF wsrep_local_bf_aborts 0 wsrep_local_index 18446744073709551615 wsrep_provider_name wsrep_provider_vendor wsrep_provider_version wsrep_ready OFF wsrep_rollbacker_thread_count 0 wsrep_thread_count 0 **Server info** - Debian 10 - 6 core CPU - 16 Gb ram
Michal Čern&#253; (3 rep)
May 18, 2021, 07:38 AM • Last activity: May 22, 2021, 11:55 AM
5 votes
1 answers
24772 views
How can I check the path of my.ini, through the command line?
I would like to know, if possible, how to display (using the command line) the path to `my.ini` used by the server. I am using MySQL 5.6 inside a windows IIS. I have the following: - `Program Files\MySQL\MySQL Server 5.6\my-default.ini` - `C:\ProgramData\MySQL\MySQL Server 5.6\my.ini`. For sure, the...
I would like to know, if possible, how to display (using the command line) the path to my.ini used by the server. I am using MySQL 5.6 inside a windows IIS. I have the following: - Program Files\MySQL\MySQL Server 5.6\my-default.ini - C:\ProgramData\MySQL\MySQL Server 5.6\my.ini. For sure, the server is using the second one. Is the path stored in any variable inside mysql server variables? I was checking some system variables but I couldn't find it. Any ideas? ------------------------------------------------------------------------------- UPDATE After Ronaldo's post I ran a --help and this is what I found: ... Default options are read from the following files in the given order: C:\Windows\my.ini C:\Windows\my.cnf C:\my.ini C:\my.cnf C:\Program Files\MySQL\MySQL Server 5.6\my.ini C:\Program Files\MySQL\MySQL Server 5.6\my.cnf The following groups are read: mysql client The following options may be given as the first argument: --print-defaults Print the program argument list and exit. ... The strange thing is that I don't have none of these files. I sit to display hided files on each folder. So, I took a look to this post and I followed the steps. Finally I arrived at the window **MySQL56 Properties(Local Computer)**. I could read: Path to executable: "C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe" --defaults-file BUT, if we click over it with the mouse's right button and choose Select All, this is what we have: "C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe" --defaults-file="C:\ProgramData\MySQL\MySQL Server 5.6\my.ini" MySQL56 So that replies my question.
IgorAlves (337 rep)
Mar 29, 2016, 01:42 PM • Last activity: Apr 22, 2021, 07:20 PM
1 votes
0 answers
426 views
MariaDB service fails to start with InnoDB Space id error
I've been running MariaDB on a Raspberry Pi 4 (Raspbian 10 / buster) as the database server for my Webtrees and Owncloud sites. Recently, I noticed that the server wasn't looking right, and after a reboot, I can see that the MariaDB service is failing to start. Contents of /var/log/mysql/error.log:...
I've been running MariaDB on a Raspberry Pi 4 (Raspbian 10 / buster) as the database server for my Webtrees and Owncloud sites. Recently, I noticed that the server wasn't looking right, and after a reboot, I can see that the MariaDB service is failing to start. Contents of /var/log/mysql/error.log:
2021-03-26 14:45:06 0 [Note] InnoDB: Using Linux native AIO
2021-03-26 14:45:06 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-03-26 14:45:06 0 [Note] InnoDB: Uses event mutexes
2021-03-26 14:45:06 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-03-26 14:45:06 0 [Note] InnoDB: Number of pools: 1
2021-03-26 14:45:06 0 [Note] InnoDB: Using generic crc32 instructions
2021-03-26 14:45:06 0 [Note] InnoDB: Disabling background log and ibuf IO write threads.
2021-03-26 14:45:06 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-03-26 14:45:06 0 [Note] InnoDB: Completed initialization of buffer pool
2021-03-26 14:45:06 0 [Note] InnoDB: innodb_force_recovery=6 skips redo log apply
2021-03-26 14:45:06 0 [ERROR] InnoDB: Space id and page no stored in the page, read in are [page id: space=0, page number=399], should be [page id: space=0, page number=394]
210326 14:45:06 [ERROR] mysqld got signal 11 ;
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.3.27-MariaDB-0+deb10u1
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466214 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
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/  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             12860                12860                processes
Max open files            16384                16384                files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       12860                12860                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
Here's the terminal output from trying to start fro the terminal:
$ sudo systemctl restart mariadb.service
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
Libraries:
$ ldd /usr/sbin/mysqld
        linux-vdso.so.1 (0xbefe7000)
        /usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so => /usr/lib/arm-li                      nux-gnueabihf/libarmmem-v7l.so (0xb562e000)
        libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb5604000)
        liblz4.so.1 => /usr/lib/arm-linux-gnueabihf/liblz4.so.1 (0xb55d8000)
        libsnappy.so.1 => /usr/lib/arm-linux-gnueabihf/libsnappy.so.1 (0xb55c100                      0)
        libaio.so.1 => /usr/lib/arm-linux-gnueabihf/libaio.so.1 (0xb55af000)
        libz.so.1 => /lib/arm-linux-gnueabihf/libz.so.1 (0xb5584000)
        libpcre.so.3 => /lib/arm-linux-gnueabihf/libpcre.so.3 (0xb550d000)
        libcrypt.so.1 => /lib/arm-linux-gnueabihf/libcrypt.so.1 (0xb54cd000)
        libsystemd.so.0 => /lib/arm-linux-gnueabihf/libsystemd.so.0 (0xb5430000)
        libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb541d000)
        libatomic.so.1 => /usr/lib/arm-linux-gnueabihf/libatomic.so.1 (0xb540400                      0)
        libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0xb52bd00                      0)
        libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb523b000)
        libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb50ed000)
        /lib/ld-linux-armhf.so.3 (0xb6ed4000)
        libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xb50c0000)
        librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0xb50a9000)
        liblzma.so.5 => /lib/arm-linux-gnueabihf/liblzma.so.5 (0xb5078000)
        libgcrypt.so.20 => /lib/arm-linux-gnueabihf/libgcrypt.so.20 (0xb4f9e000)
        libgpg-error.so.0 => /lib/arm-linux-gnueabihf/libgpg-error.so.0 (0xb4f74                      000)
Googling hasn't turned up too much, though I've tried
innodb_force_recovery = 1 (and all the way up to 6!)
innodb_purge_threads=0
In /etc/mysql/my.cnf, which didn't seem to change anything. Any thoughts before I attempt to restore from backup?
Charlie (11 rep)
Mar 27, 2021, 10:51 AM • Last activity: Mar 27, 2021, 05:15 PM
0 votes
1 answers
6703 views
The innodb_system data file 'ibdata1' must be writable even with full permissions set
i'm trying to change the datadir in mysql, i created a new directory with the user mysql as a owner, i know am not supposed to set the permission to 777. but even with this full permission still getting the same error in the log file whenever i try to start the mysql service. ```[InnoDB] The innodb_...
i'm trying to change the datadir in mysql, i created a new directory with the user mysql as a owner, i know am not supposed to set the permission to 777. but even with this full permission still getting the same error in the log file whenever i try to start the mysql service.
[InnoDB] The innodb_system data file 'ibdata1' must be writable
user@user:~$ ls -l /database2/mysql | grep ibdata1 
-rwxrwxrwx 1 mysql mysql 12582912 Jan 15 15:24 ibdata1
any solution ?
Someone (1 rep)
Jan 15, 2021, 03:56 PM • Last activity: Jan 17, 2021, 07:44 PM
6 votes
3 answers
7881 views
Something in MySQL is causing progressively high load which consumes almost all memory
I have this server that has only one site with one database on it. And yet, I cannot tweak it to make the load go back down to normal. If I restart mysql service, memory and load go down to normal, but a few days later, memory and load are progressively increasing. ## Server specs - Centos 7 - total...
I have this server that has only one site with one database on it. And yet, I cannot tweak it to make the load go back down to normal. If I restart mysql service, memory and load go down to normal, but a few days later, memory and load are progressively increasing. ## Server specs - Centos 7 - total memory 7.8G - swap 1G ## htop output htop output ## MySQL version mysql Ver 14.14 Distrib 5.7.28, for Linux (x86_64) using EditLine wrapper ## my.cnf
-none
# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html 

#[mysqld]
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M
#
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
#datadir=/var/lib/mysql
#socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
#symbolic-links=0

#log-error=/var/log/mysqld.log
#pid-file=/var/run/mysqld/mysqld.pid

#max_allowed_packet=1024M


##################

# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html 

[mysqld]
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M
#
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

plugin-load-add=validate_password.so


max_allowed_packet=100M

#------------------| query cach config
# https://easyengine.io/tutorials/mysql/query-cache 
#------------------|
query_cache_type = 1
query_cache_size = 256M
query_cache_limit = 2M
#query_cache_strip_comments =1



port            = 3306
#socket         = /var/lib/mysql/mysql.sock
#skip-external-locking
key_buffer_size = 512M
max_allowed_packet=268435456
table_open_cache = 256
sort_buffer_size = 256
read_buffer_size = 256
read_rnd_buffer_size = 40
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size= 16M
# Try number of CPU's x 2 for thread_concurrency
#thread_concurrency = 2

# Point the following paths to different dedicated disks
#tmpdir         = /tmp/

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
# 
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
#log-bin=mysql-bin

# binary logging format - mixed recommended
binlog_format=mixed

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
#server-id      = 1



# ============================================================ #
# =============== Custom server tweaks [start] =============== #
# ============================================================ #

default_storage_engine = InnoDB
innodb_buffer_pool_size =  2G #4G # 8G # Use up to 70-80% of RAM & optionally check if /proc/sys/vm/swappiness is set to 0. Use Tuning Primer or MySQL Tuner to adjust accordingly.
innodb_file_per_table = 1
#--------------------------| 
# 2 means log buffer is flushed to OS file cache on every transaction commit. 
# The implication of 2 is optimal and improve performance 
# if you are not concerning ACID and can lose transactions for last second or two in case of OS crashes
# -------------------------|
innodb_flush_log_at_trx_commit = 2
innodb_flush_method = O_DIRECT
innodb_log_buffer_size = 16M

#---------------------------| 
# Delete the ib_logfile0 & ib_logfile1 files in /var/lib/mysql whenever you change this, 
# even the first time you set it up, as the default value is 8M. 
# Don't go above 256M.
# ref: https://gist.github.com/wh4u/1fafe2bf98f630d7753717b5a8835bca 
#---------------------------|
innodb_log_file_size = 256M


innodb_file_per_table=ON
innodb_stats_on_metadata = OFF
innodb_buffer_pool_instances = 8  #(or 1 if innodb_buffer_pool_size < 1GB)
#query_cache_type = 0
#query_cache_size = 0 #(disabling mutex)

#---------------|
# ref: http://techinfobest.com/optimize-mysql-table_open_cache/ 
# --------------|
#open_files_limit=10000
open_files_limit=19107
table_open_cache=39390

slow-query-log=1
long_query_time = 1
log-queries-not-using-indexes = 1


[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[myisamchk]
key_buffer_size = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout
## htop output after a couple of days If I don't restart MySQL, this is what happens after 3-4 days htop output Can someone point me to the right direction please? ## Additional details MySQL crashed a little later with following messages in the log:
-none
2020-01-03T12:59:51.514413Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 4887ms. The settings might not be optimal. (flushed=142 and evicted=0, during the time.)
2020-01-03T13:00:35.061257Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 11874ms. The settings might not be optimal. (flushed=89 and evicted=0, during the time.)
2020-01-03T13:01:13.857771Z 0 [Warning] Could not increase number of max_open_files to more than 5000 (request: 78941)
2020-01-03T13:01:13.858498Z 0 [Warning] Changed limits: table_open_cache: 2419 (requested 39390)
2020-01-03T13:01:14.177515Z 0 [Warning] option 'sort_buffer_size': unsigned value 256 adjusted to 32768
2020-01-03T13:01:14.177549Z 0 [Warning] option 'read_buffer_size': unsigned value 256 adjusted to 8192
2020-01-03T13:01:14.177630Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-01-03T13:01:14.420855Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.28-log) starting as process 15029 ...
2020-01-03T13:01:15.607997Z 0 [Warning] You need to use --log-bin to make --binlog-format work.
2020-01-03T13:01:15.758435Z 0 [Note] InnoDB: PUNCH HOLE support available
2020-01-03T13:01:15.758521Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-01-03T13:01:15.758535Z 0 [Note] InnoDB: Uses event mutexes
2020-01-03T13:01:15.758552Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-01-03T13:01:15.758563Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-01-03T13:01:15.758574Z 0 [Note] InnoDB: Using Linux native AIO
2020-01-03T13:01:15.759295Z 0 [Note] InnoDB: Number of pools: 1
2020-01-03T13:01:15.759589Z 0 [Note] InnoDB: Using CPU crc32 instructions
2020-01-03T13:01:15.773538Z 0 [Note] InnoDB: Initializing buffer pool, total size = 2G, instances = 8, chunk size = 128M
2020-01-03T13:01:16.072379Z 0 [Note] InnoDB: Completed initialization of buffer pool
2020-01-03T13:01:16.142472Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-01-03T13:01:16.237526Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2020-01-03T13:01:16.349890Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 82179195773
2020-01-03T13:01:16.349986Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 82179207508
2020-01-03T13:01:16.471207Z 0 [Note] InnoDB: Database was not shutdown normally!
I tried the solution that was provided in the duplicate question suggestion , but this has made things worse. The server runs out of memory within minutes. **UPDATE**
BUFFER POOL AND MEMORY
----------------------
Total large memory allocated 2198863872
Dictionary memory allocated 1654382
Buffer pool size   131072
Free buffers       1
Database pages     128972
Old database pages 47448
Modified db pages  1578
Pending reads      1
Pending writes: LRU 0, flush list 163, single page 0
Pages made young 17903348, not young 602752081
0.00 youngs/s, 0.00 non-youngs/s
Pages read 75403666, created 44758503, written 47149356
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
Buffer pool hit rate 997 / 1000, young-making rate 0 / 1000 not 67 / 1000
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
LRU len: 128972, unzip_LRU len: 0
I/O sum:cur, unzip sum:cur
Are Old database pages too many? What issues do you see? **UPDATE #2** Here is what my.cnf looks like at the moment
# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html 

#[mysqld]
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M
#
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
#datadir=/var/lib/mysql
#socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
#symbolic-links=0

#log-error=/var/log/mysqld.log
#pid-file=/var/run/mysqld/mysqld.pid

#max_allowed_packet=1024M


##################

# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html 

[mysqld]
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M
#
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

plugin-load-add=validate_password.so


max_allowed_packet=100M

#------------------| query cach config
# https://easyengine.io/tutorials/mysql/query-cache 
#------------------|
query_cache_type = 1
query_cache_size = 256M
query_cache_limit = 2M
#query_cache_strip_comments =1



port            = 3306
#socket         = /var/lib/mysql/mysql.sock
#skip-external-locking
key_buffer_size = 512M
max_allowed_packet=268435456
#table_open_cache = 256
sort_buffer_size = 256
read_buffer_size = 256
read_rnd_buffer_size = 40
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size= 16M
# Try number of CPU's x 2 for thread_concurrency
#thread_concurrency = 2

# Point the following paths to different dedicated disks
#tmpdir         = /tmp/

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
# 
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
#log-bin=mysql-bin

# binary logging format - mixed recommended
binlog_format=mixed

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
#server-id      = 1



# ============================================================ #
# =============== Custom server tweaks [start] =============== #
# ============================================================ #

default_storage_engine = InnoDB
innodb_buffer_pool_size =  2G #4G # 8G # Use up to 70-80% of RAM & optionally check if /proc/sys/vm/swappiness is set to 0. Use Tuning Primer or MySQL Tuner to adjust accordingly.
innodb_file_per_table = 1
#--------------------------| 
# 2 means log buffer is flushed to OS file cache on every transaction commit. 
# The implication of 2 is optimal and improve performance 
# if you are not concerning ACID and can lose transactions for last second or two in case of OS crashes
# -------------------------|
innodb_flush_log_at_trx_commit = 2
innodb_flush_method = O_DIRECT
innodb_log_buffer_size = 16M

#---------------------------| 
# Delete the ib_logfile0 & ib_logfile1 files in /var/lib/mysql whenever you change this, 
# even the first time you set it up, as the default value is 8M. 
# Don't go above 256M.
# ref: https://gist.github.com/wh4u/1fafe2bf98f630d7753717b5a8835bca 
#---------------------------|
innodb_log_file_size = 256M


innodb_file_per_table=ON
innodb_stats_on_metadata = OFF
innodb_buffer_pool_instances = 8  #(or 1 if innodb_buffer_pool_size < 1GB)
#query_cache_type = 0
#query_cache_size = 0 #(disabling mutex)

#---------------|
# ref: http://techinfobest.com/optimize-mysql-table_open_cache/ 
# --------------|
table_open_cache=1501
#table_open_cache=30000
open_files_limit=3003
#open_files_limit=19107
#table_open_cache=39390

slow-query-log=0
long_query_time = 1
log-queries-not-using-indexes = 1


[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[myisamchk]
key_buffer_size = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout
I noticed some parameters were double in the file so I commented out the duplicates. e.g. table_open_cache was in two places under mysqld, one with value 256 and the other with value 39390.
Vasiliki (181 rep)
Jan 3, 2020, 10:16 AM • Last activity: Feb 3, 2020, 03:10 PM
0 votes
1 answers
565 views
How do correct mysqld.log error messages on start up?
I'm running Plesk and CentOS 6.7 Following is the excerpt of the log file `mysqld.log` when I restart mysqld service. I normally don't check this log file, but I just noticed some errors messages. It could have been there for a long time already. This is a live production server up and running for a...
I'm running Plesk and CentOS 6.7 Following is the excerpt of the log file mysqld.log when I restart mysqld service. I normally don't check this log file, but I just noticed some errors messages. It could have been there for a long time already. This is a live production server up and running for a couple of months, and I don't want to run anything destructive that can potentially jeopardize the stability and data integrity of the server. 170207 13:29:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 170207 13:29:52 [Note] libgovernor.so not found 170207 13:29:52 [Note] /usr/libexec/mysqld (mysqld 5.5.44-cll-lve) starting as process 20524 ... 170207 13:29:52 [Note] Plugin 'FEDERATED' is disabled. 170207 13:29:52 InnoDB: The InnoDB memory heap is disabled 170207 13:29:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins 170207 13:29:52 InnoDB: Compressed tables use zlib 1.2.3 170207 13:29:52 InnoDB: Using Linux native AIO 170207 13:29:52 InnoDB: Initializing buffer pool, size = 16.0G 170207 13:29:53 InnoDB: Completed initialization of buffer pool 170207 13:29:53 InnoDB: highest supported file format is Barracuda. 170207 13:29:54 InnoDB: Waiting for the background threads to start 170207 13:29:55 InnoDB: 5.5.44 started; log sequence number 408971509487 170207 13:29:55 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306 170207 13:29:55 [Note] - '127.0.0.1' resolves to '127.0.0.1'; 170207 13:29:55 [Note] Server socket created on IP: '127.0.0.1'. 170207 13:29:55 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it 170207 13:29:55 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure 170207 13:29:55 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure 170207 13:29:55 [Note] Event Scheduler: Loaded 0 events 170207 13:29:55 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.44-cll-lve' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Atomicorp **Questions:** 1. Even with all these startup errors, MySQL is still up and running well. Is this going to cause any performance impact on current MySQL server performance? 2. Regarding to missing system table mysql.proxies_priv, is this critical? and can I safely run the suggested mysql_upgrade without damaging the existing database? 3. If I were to run mysql_upgrade, do I need to stop mysqld first? 4. How do I correct/repair all the performance_schema wrong structure error messages?
KDX (133 rep)
Feb 7, 2017, 02:20 PM • Last activity: Jul 11, 2019, 09:02 PM
0 votes
1 answers
673 views
After Update Mysql 8.0.13 to 8.0.15 MySql Server Fails with error code = 1265
After Upgrading from MySql 8.0.13 (compiled from sourcecode) to MySql 8.0.15, the MySql Server can not start. Log: 2019-02-12T10:09:52.275336Z 1 [ERROR] [MY-013178] [Server] Execution of server-side SQL statement 'INSERT INTO routines SELECT * FROM mysql.routines' failed with error code = 1265, erro...
After Upgrading from MySql 8.0.13 (compiled from sourcecode) to MySql 8.0.15, the MySql Server can not start. Log: 2019-02-12T10:09:52.275336Z 1 [ERROR] [MY-013178] [Server] Execution of server-side SQL statement 'INSERT INTO routines SELECT * FROM mysql.routines' failed with error code = 1265, error message = 'Daten abgeschnitten für Feld 'sql_mode' in Zeile 7'. 2019-02-12T10:09:52.302630Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2019-02-12T10:09:52.302856Z 0 [ERROR] [MY-010119] [Server] Aborting "Daten abgeschnitten für Feld" means "Data truncated for field" - its a german version ... table checker does not find any errors - how can I solve this problem ? yours sincerely Robert
bitranox (121 rep)
Feb 12, 2019, 12:08 PM • Last activity: Feb 12, 2019, 01:12 PM
5 votes
3 answers
19658 views
Cant initialize MySQL. "mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended"
I am doing a fresh install of MySQL on Fedora 22. After I run mysql_install_db I try to start the daemon using mysqld_safe but it does not work. The system says: mysqld_safe Logging to '/var/log/mariadb/mariadb.log'. mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql mysqld_safe m...
I am doing a fresh install of MySQL on Fedora 22. After I run mysql_install_db I try to start the daemon using mysqld_safe but it does not work. The system says: mysqld_safe Logging to '/var/log/mariadb/mariadb.log'. mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended How do I get this to work? Here are the mariadb.log contents: mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql [Note] /usr/libexec/mysqld (mysqld 10.0.23-MariaDB) starting as process 20443 ... [Note] InnoDB: Using mutexes to ref count buffer pool pages [Note] InnoDB: The InnoDB memory heap is disabled [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins [Note] InnoDB: Memory barrier is not used [Note] InnoDB: Compressed tables use zlib 1.2.8 [Note] InnoDB: Using Linux native AIO [Note] InnoDB: Using CPU crc32 instructions [Note] InnoDB: Initializing buffer pool, size = 128.0M [Note] InnoDB: Completed initialization of buffer pool [ERROR] InnoDB: ./ibdata1 can't be opened in read-write mode [ERROR] InnoDB: The system tablespace must be writable! [ERROR] Plugin 'InnoDB' init function returned error. [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. [ERROR] mysqld: File '/var/lib/mysql/aria_log_control' not found (Errcode: 13 "Permission denied") [ERROR] mysqld: Got error 'Can't open file' when trying to use aria control file '/var/lib/mysql/aria_log_control' [ERROR] Plugin 'Aria' init function returned error. [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. [Note] Plugin 'FEEDBACK' is disabled. [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. [ERROR] Unknown/unsupported storage engine: InnoDB [ERROR] Aborting [Note] /usr/libexec/mysqld: Shutdown complete mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
user93897
May 5, 2016, 08:48 AM • Last activity: Oct 28, 2018, 09:59 PM
2 votes
1 answers
3090 views
MySQL fails to start after editing my.cnf
I am trying to optimize memory usage (eating up more than 500MB by default) of MySQL using my.cnf, but I am having some trouble. The service is not starting after placing my custom my.cnf. It goes back to working state if I fallback to default my.cnf. MySQL version: > mysql Ver 14.14 Distrib 5.7.19,...
I am trying to optimize memory usage (eating up more than 500MB by default) of MySQL using my.cnf, but I am having some trouble. The service is not starting after placing my custom my.cnf. It goes back to working state if I fallback to default my.cnf. MySQL version: > mysql Ver 14.14 Distrib 5.7.19, for Linux (x86_64) using EditLine > wrapper OS Version: > DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.04 DISTRIB_CODENAME=zesty > DISTRIB_DESCRIPTION="Ubuntu 17.04" > > Linux 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 > UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Here is my /etc/mysql/my.cnf ( generated using myconfgen with memory size parameter 0.25): [mysql] # CLIENT # port = 3306 socket = /var/lib/mysql/mysql.sock [mysqld] # GENERAL # user = mysql default-storage-engine = InnoDB socket = /var/lib/mysql/mysql.sock pid-file = /var/run/mysqld/mysqld.pid # MyISAM # # key-buffer-size = 32M # myisam-recover = FORCE,BACKUP # SAFETY # max-allowed-packet = 16M max-connect-errors = 1000000 skip-name-resolve sql-mode = NO_ENGINE_SUBSTITUTION,NO_AUTO_CREATE_USER sysdate-is-now = 1 innodb-strict-mode = 1 # DATA STORAGE # datadir = /var/lib/mysql # SERVER ID # server-id = 968898 # BINARY LOGGING # log-bin # CACHES AND LIMITS # max-connections = 500 tmp-table-size = 32M max-heap-table-size = 32M query-cache-type = 0 query-cache-size = 0 thread-cache-size = 50 open-files-limit = 65535 table-definition-cache = 1024 table-open-cache = 2048 # INNODB # innodb-flush-method = O_DIRECT innodb-log-files-in-group = 2 innodb-log-file-size = 768M innodb-flush-log-at-trx-commit = 1 innodb-file-per-table = 1 innodb-buffer-pool-size = 192M # LOGGING # log-error = /var/log/mysqld.log slow-query-log = 1 slow-query-log-file = /var/log/mysqld-slow.log log-queries-not-using-indexes = OFF long_query_time = 30 [mysqldump] max-allowed-packet = 16M When I try to start MySQL, this is what I get: ● mysql.service - MySQL Community Server Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled) Active: activating (start-post) (Result: exit-code) since Mon 2017-08-21 12:09:51 UTC; 1s ago Process: 14659 ExecStart=/usr/sbin/mysqld (code=exited, status=1/FAILURE) Process: 14643 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS) Main PID: 14659 (code=exited, status=1/FAILURE); Control PID: 14660 (mysql-systemd-s) Tasks: 2 (limit: 4915) Memory: 760.0K CPU: 223ms CGroup: /system.slice/mysql.service └─control ├─14660 /bin/bash /usr/share/mysql/mysql-systemd-start post └─14669 sleep 1 **There is nothing in /var/log/mysql.log**. I don't know where else to look for error log. Can you please help? Edit: I ran journalcl and found more error logs: -- Unit mysql.service has begun starting up. Aug 21 13:04:46 www.####.com kernel: audit: type=1400 audit(1503320686.962:1051): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/18169/status" pid=18169 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=112 ouid=112 Aug 21 13:04:46 www.####.com audit: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/18169/status" pid=18169 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=112 ouid=112 Aug 21 13:04:46 www.####.com audit: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=18169 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=112 ouid=0 Aug 21 13:04:46 www.####.com kernel: audit: type=1400 audit(1503320686.974:1052): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=18169 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=112 ouid=0 Aug 21 13:04:46 www.####.com audit: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/18169/status" pid=18169 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=112 ouid=112 Aug 21 13:04:46 www.####.com kernel: audit: type=1400 audit(1503320686.978:1053): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/18169/status" pid=18169 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=112 ouid=112 Aug 21 13:04:47 www.####.com audit: AVC apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/log/mysqld.log" pid=18169 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=112 ouid=112 Aug 21 13:04:47 www.####.com audit: AVC apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/log/mysqld.log" pid=18169 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=112 ouid=112 Aug 21 13:04:47 www.####.com audit: AVC apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/log/mysqld.log" pid=18169 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=112 ouid=112 Aug 21 13:04:47 www.####.com audit: AVC apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/log/mysqld.log" pid=18169 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=112 ouid=112 Aug 21 13:04:47 www.####.com audit: AVC apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/log/mysqld.log" pid=18169 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=112 ouid=112 Aug 21 13:04:47 www.####.com audit: AVC apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/log/mysqld.log" pid=18169 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=112 ouid=112 Aug 21 13:04:47 www.####.com kernel: audit: type=1400 audit(1503320687.182:1054): apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/log/mysqld.log" pid=18169 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=112 ouid=112 Aug 21 13:04:47 www.####.com kernel: audit: type=1400 audit(1503320687.182:1055): apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/log/mysqld.log" pid=18169 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=112 ouid=112 Aug 21 13:04:47 www.####.com kernel: audit: type=1400 audit(1503320687.182:1056): apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/log/mysqld.log" pid=18169 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=112 ouid=112 Aug 21 13:04:47 www.####.com kernel: audit: type=1400 audit(1503320687.182:1057): apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/log/mysqld.log" pid=18169 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=112 ouid=112 Aug 21 13:04:47 www.####.com kernel: audit: type=1400 audit(1503320687.182:1058): apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/log/mysqld.log" pid=18169 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=112 ouid=112 Aug 21 13:04:47 www.####.com kernel: audit: type=1400 audit(1503320687.182:1059): apparmor="DENIED" operation="mknod" profile="/usr/sbin/mysqld" name="/var/log/mysqld.log" pid=18169 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=112 ouid=112 Aug 21 13:04:47 www.####.com systemd[1] : mysql.service: Main process exited, code=exited, status=1/FAILUREl.service: Main process exited, code=exited, status=1/FAILURE
Spero (121 rep)
Aug 21, 2017, 12:21 PM • Last activity: Sep 17, 2018, 05:00 AM
1 votes
1 answers
3844 views
Unable to start mysqld service after enabling log_bin
Hi I am unable to start mysqld service after I make changes in my.cnf to enable log-bin. After making changes the file looks like below: # For advice on how to change settings please see # http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html [mysqld] # # Remove leading # and set...
Hi I am unable to start mysqld service after I make changes in my.cnf to enable log-bin. After making changes the file looks like below: # For advice on how to change settings please see # http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html [mysqld] # # Remove leading # and set to the amount of RAM for the most important data # cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%. # innodb_buffer_pool_size = 128M # # Remove leading # to turn on a very important data integrity option: logging # changes to the binary log between backups. # log_bin #This is what I added to enable log-bin log-bin=/var/log/mysql/ log-bin-index=bin-log.index max_binlog_size=100M binlog_format=row socket=mysql.sock #That was what I added to enable log-bin # # Remove leading # to set options mainly useful for reporting servers. # The server defaults are faster for transactions and fast SELECTs. # Adjust sizes as needed, experiment to find the optimal values. # join_buffer_size = 128M # sort_buffer_size = 2M # read_rnd_buffer_size = 2M datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock # Disabling symbolic-links is recommended to prevent assorted security risks symbolic-links=0 log-error=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid I am using: [ec2-user@pip my.cnf.d]$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.3 (Maipo) Following is the ownership and permissions: d]$ ls -ld /var/log/mysql drwxrwxrwx. 2 mysql mysql 23 Sep 8 09:01 /var/log/mysql Following is the error that I get: [ec2-user@i.d]$ sudo service mysqld start Redirecting to /bin/systemctl start mysqld.service Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details. MySQL version is: Server version: 5.7.19 MySQL Community Server (GPL) Please let me know if any other detail is required
Kitty (11 rep)
Sep 8, 2017, 04:01 PM • Last activity: Sep 12, 2018, 02:01 AM
3 votes
2 answers
10176 views
mysqld dead but subsys locked
I'm executing the following command in a shell script and I'm executing this on an RHEL-6 server and MySQL version 5.1.47- mysqld_safe --defaults-extra-file=/custom/path/of/my.cnf The path of my.cnf can be anything. (If I am not wrong, as a developer we cannot determine where mysql could be installe...
I'm executing the following command in a shell script and I'm executing this on an RHEL-6 server and MySQL version 5.1.47- mysqld_safe --defaults-extra-file=/custom/path/of/my.cnf The path of my.cnf can be anything. (If I am not wrong, as a developer we cannot determine where mysql could be installed.) After the above command in the script, there are a few mysql commands to be executed. When the script executes the above command, the output console displays that the mysql service has successfully started. But when the control comes to the part where the mysql commands are to be executed, the following error message comes up- mysqld dead but subsys locked Any idea where I am going wrong? This is what my my.cnf contains- [mysqld] innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 innodb_file_io_threads=4 max_binlog_size=20M max_allowed_packet=16M max_connections=500 log_bin=logFile.log binlog-do-db=test server-id=1 datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock user=mysql binlog-format=ROW log_warnings=1 # Disabling symbolic-links is recommended to prevent assorted security risks symbolic-links=0
AlwaysALearner (151 rep)
Apr 29, 2013, 02:40 PM • Last activity: Jun 20, 2018, 05:59 PM
Showing page 1 of 20 total questions