Hello Steve, Many thanks for your reply.
My problem was that I had made a mess of setting up passwords. Now that
is sorted logging in can now be done safely. It sure is tricky to get right.
Barry
-----------------------------------
On 09/02/16 08:34, steve wrote:
Hi Barry,
Obviously this isn't the best way to run mysql, as you've removed the
security layer! Mysql is very touchy ( and rightly so! ) about
fileownership.
sudo chown -R mysql:mysql /var/lib/mysql
will ensure it's not going to trip up on any of that.
Once you've got mysql running,
mysqlcheck --all-databases --auto-repair
and
mysql_upgrade
may help ensure that your database is both healthy and fully compatible
with the installed software version.
Good luck!
Steve
On 02/05/2016 09:55 PM, Barry wrote:
On 04/02/16 23:02, Eliot Blennerhassett wrote:
lsof /var/lib/mysql/aria_log_control
Thanks for your reply. this is result, 1st command after reboot....
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
mysqld 2147 mysql 3uW REG 8,8 52 1270518
/var/lib/mysql/aria_log_control
As root tried 'kill xxxx', it does not seam to work every time. Then I
tried other juggling around.
I seem to have it starting ok now - by using mysqld_safe
--skip-grant-tables so I think there is an error in my setup
somewhere, but thats enough for tonight. Will try it in the morning.
Ta, Barry.
_______________________________________________
Linux-users mailing list
[email protected]
http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
_______________________________________________
Linux-users mailing list
[email protected]
http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
