This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
daily_issues [2016/05/13 14:45] k2patel [Reading Binlog] |
daily_issues [2018/08/19 05:13] k2patel |
||
---|---|---|---|
Line 14: | Line 14: | ||
</code> | </code> | ||
+ | ===== Mysql Generate hash for password ===== | ||
+ | <code mysql> | ||
+ | SELECT PASSWORD('mypass'); | ||
+ | </code> | ||
+ | OR | ||
+ | |||
+ | <code mysql> | ||
+ | SELECT OLD_PASSWORD('mypass'); | ||
+ | </code> | ||
==== MySQL Cluster information gathering ==== | ==== MySQL Cluster information gathering ==== | ||
Line 142: | Line 151: | ||
I've started seeing following error in my log.\\ | 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 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> |