Differences

This shows you the differences between two versions of the page.

--- daily_issues [2011/08/04 18:14] – jt
+++ daily_issues [2020/08/10 02:35] (current) – external edit 127.0.0.1
@@ Line 14: / Line 14: @@
 </code>
+===== Mysql Generate hash for password =====
+<code mysql>
+SELECT PASSWORD('mypass');
+</code>
+OR
+<code mysql>
+SELECT OLD_PASSWORD('mypass');
+</code>
 ==== MySQL Cluster information gathering ====
@@ Line 112: / Line 121: @@
 </code>
-== mysql dump only partition information ==
+==== mysql dump only partition information ====
 If you were planning to drop a partition, you may need to back it up. find out the range of the partition by
@@ Line 122: / Line 131: @@
 <code>
 mysqldump -S --no-create-info --where="RANGE(day) >= lowrange AND RANGE(day) < highrange" database_name table_name > /jtmp/table.sql
+</code>
+==== Reading Binlog ====
+Simple command to read binlog is
+<code bash>
+mysqlbinlog mysql-bin.000013
+</code>
+You can use following regularly used options.
+<code bash>
+--start-datetime=
+--start-position=
+--server-id=
+</code>
+==== Can't open file ====
+I've started seeing following error in my log.\\
+<code text>
+[ERROR] /usr/libexec/mysqld: Can't open file:
+</code>
+It is caused by file discriptor limit set by the system.\\
+You can check that by changing your shell to mysql user and running following command.
+<code bash>
+ulimit -a
+</code>
+In order to increase the open file limit.\\
+edit following file.\\
+<code bash /etc/security/limits.conf>
+mysql  soft  nofile  49152
+mysql  hard  nofile  65536
+</code>
+Now you can check mysql for limit seen by mysql.\\
+login to mysql as root and run following command.\\
+<code mysql>
+show GLOBAL VARIABLES LIKE "open%";
+</code>
+Now you can modify it to increased limit in limits.conf.\\
+by editing following file.
+<code bash /etc/my.cnf>
+[mysqld]
+open-files-limit=49152
+[mysqld_safe]
+open-files-limit=49152
+</code>
+restart mysql and check again it should represent new value.
+==== InnoDB: Unable to lock ./ibdata1, error: 11 ====
+I've stumble across this issue while running mariadb server in VM Guest.\\
+I believe this happens sometime when VDP is doing backup or machine is being migrated by DRS.
+In my case, i've enable innodb per tables. So i've to clear lock from all files in subfolder.\\
+In order to fix the issue, following command usually fix the issue.
+<code bash>
+systemctl stop mariadb
+cd /var/lib/mysql
+for i in `find . -name '*.ibd'`; do mv $i $i.bk; cp -a $i.bk $i ; rm $i.bk ; done
+systemctl start mariadb
 </code>