This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
daily_issues [2016/05/13 14:54] k2patel [Can't open file] |
daily_issues [2020/08/10 02:35] (current) |
||
---|---|---|---|
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 180: | Line 189: | ||
restart mysql and check again it should represent new value. | 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> |