Obsolete Releases > SME 8.x Contribs

[Announce] Moodle 2.5 for SME 8.0

<< < (5/5)

LANMonkey:
I did a little research on the error I get when running mysql-dump-tables in SME 9.0 Beta 2 and made some progress


--- Quote ---mysqldump: Couldn't execute 'SELECT /*!40001 SQL_NO_CACHE */ * FROM `PARAMETERS`': Cannot load from mysql.proc. The table is probably corrupted (1548)
--- End quote ---

and found this tip here:

http://dba.stackexchange.com/questions/956/resolving-issue-with-mysql-proc-after-upgrading-mysql-from-5-0-to-5-1

On SME 9.0 Beta 2, I tried running,


--- Code: ---mysql_upgrade --force
/usr/bin/sv t mysqld
--- End code ---

And now I get no errors back when I run, " /etc/e-smith/events/actions/mysql-dump-tables"

On SME 8.0, I tried doing the same thing, but continue to get the same errors back when I run mysql-dump-tables:


--- Quote ---mysqldump: Got error: 1044: Access denied for user 'root'@'localhost' to database 'information_schema' when using LOCK TABLES
--- End quote ---

So since I am getting no errors back when I run mysql-dump-tables in SME 9.0 Beta 2, I assume the problem is solved there.  I wanted to try running a scheduled backup, but for some reason, I cannot access my user share on my Windows Home Server from this Beta machine.

LANMonkey:

--- Quote from: mmccarn on December 24, 2013, 01:59:52 AM ---Try adding the "-x" option to mysqldump:
--- Code: ---for db in $(mysql -BNre "show databases;"); do mysqldump -x --add-drop-table -QB "$db" -r /home/e-smith/db/mysql/"$db".dump || exit 1; done

--- End code ---

I had to do this when adapting /etc/e-smith/events/actions/mysql-dump-tables to backup mariadb:
http://wiki.contribs.org/User_talk:Mmccarn#.2Fetc.2Fe-smith.2Fevents.2Factions.2Fmariadb-dump-tables

--- End quote ---

I completely misunderstood this instruction.  I thought the poster was recommending a command line to test the installation.  No, the poster was talking about actually altering the file /etc/e-smith/events/actions/mysql-dump-tables.  I did this as instructed and ran that script - which is what I had been doing - /etc/e-smith/events/actions/mysql-dump-tables and only got the following error message:


--- Quote ----- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.

--- End quote ---

I tried scheduling a backup and the backups are working.

[PROBLEM SOLVED]

LANMonkey:
I'm back again for this fix.  An update or something has replaced the mysqldump script with one without the "-x".

LANMonkey:
I have tried all of the above fixes, but I am still having problems.  To review, I've done the following,

Added the "-x" in the code below in mysqldump:


--- Code: ---for db in $(mysql -BNre "show databases;"); do mysqldump -x --add-drop-table -QB "$db" -r /home/e-smith/db/mysql/"$db".dump || exit 1; done
--- End code ---

Tried restoring the password as outlined here:

http://wiki.contribs.org/MySQL#Resetting_the_MySQL_root_password


--- Code: ---cd /var/service/mysqld
sv d .
expand-template /root/.my.cnf
expand-template /var/service/mysqld/set.password
/usr/libexec/mysqld --bootstrap --user=mysql --skip-grant-tables < ./set.password
sv u .
--- End code ---

I also have tried enabling and disabling the InnoDB tables as described above.

I am now getting this error when running the /etc/e-smith/events/actions/mysql-dump-tables script:

"mysqldump: Couldn't execute 'show create table `atkin_relations_reord_vw_2`': View 'connectivity.atkin_relations_reord_vw_2' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them (1356)"

There appears to be another problem with root again.

Any ideas, anyone?

LANMonkey:
I assumed this was another problem with root.  It is not, I deleted the offending views and this problem is gone.

Navigation

[0] Message Index

[*] Previous page