daily_issues
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
daily_issues [2016/05/18 18:26] – [Easy Command List] k2patel | daily_issues [2020/08/10 02:35] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 14: | Line 14: | ||
</ | </ | ||
- | ==== Mysql Generate hash for password ==== | + | ===== Mysql Generate hash for password |
<code mysql> | <code mysql> | ||
SELECT PASSWORD(' | SELECT PASSWORD(' | ||
Line 189: | 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 / | ||
+ | for i in `find . -name ' | ||
+ | systemctl start mariadb | ||
+ | </ |
daily_issues.1463595978.txt.gz · Last modified: 2020/08/10 02:28 (external edit)