April 2014 - discuss - lists.mariadb.org

[Maria-discuss] New Question: Circular Dependency on 5.5.36
by AskMonty KB 03 Apr '14

03 Apr '14

Hello, A new question has been asked in "Installing MariaDB RPM Files" by peter-mclarty: -------------------------------- Does anyone have a clever solution to installing 5.5.36 when compat and common rpms have a circular dependency, Since the contents appear to be needed do we need them packaged separately? [root@faws01_dbs itadmin]# yum install MariaDB-5.5.36-centos6-x86_64-compat.rpm Loaded plugins: product-id, subscription-manager Updating certificate-based repositories. Setting up Install Process Examining MariaDB-5.5.36-centos6-x86_64-compat.rpm: MariaDB-compat-5.5.36-1.el6.x86_64 Marking MariaDB-5.5.36-centos6-x86_64-compat.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package MariaDB-compat.x86_64 0:5.5.36-1.el6 will be installed --> Processing Dependency: MariaDB-common for package: MariaDB-compat-5.5.36-1.el6.x86_64 --> Finished Dependency Resolution Error: Package: MariaDB-compat-5.5.36-1.el6.x86_64 (/MariaDB-5.5.36-centos6-x86_64-compat) Requires: MariaDB-common You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@faws01_dbs itadmin]# yum install MariaDB-5.5.36-centos6-x86_64-common.rpm Loaded plugins: product-id, subscription-manager Updating certificate-based repositories. Setting up Install Process Examining MariaDB-5.5.36-centos6-x86_64-common.rpm: MariaDB-common-5.5.36-1.el6.x86_64 Marking MariaDB-5.5.36-centos6-x86_64-common.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package MariaDB-common.x86_64 0:5.5.36-1.el6 will be installed --> Processing Dependency: MariaDB-compat for package: MariaDB-common-5.5.36-1.el6.x86_64 --> Finished Dependency Resolution Error: Package: MariaDB-common-5.5.36-1.el6.x86_64 (/MariaDB-5.5.36-centos6-x86_64-common) Requires: MariaDB-compat You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest As you can see one is dependent on the other, that is not a smart approach Any thoughts Peter -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/circular-dependency-on-5536/

1 0

[Maria-discuss] New Question: unable to upgrade from MariaDB 5.5 to MariaDB 10.0 using YUM
by AskMonty KB 01 Apr '14

01 Apr '14

Hello, A new question has been asked in "MariaDB community" by cyberdomecyberdome: -------------------------------- I created a file mariadb.repo and put in info for mariadb 10.0, when I run the command yum -y update or yum -y upgrade mariadb-server mariadb-client, Loaded plugins: langpacks, refresh-packagekit Resolving Dependencies --> Running transaction check ---> Package MariaDB-server.x86_64 0:10.0.10-1.fc20 will be obsoleting ---> Package mariadb-server.x86_64 1:5.5.36-1.fc20 will be obsoleted --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: MariaDB-server x86_64 10.0.10-1.fc20 mariadb 49 M replacing mariadb-server.x86_64 1:5.5.36-1.fc20 Transaction Summary ================================================================================ Install 1 Package Total download size: 49 M Downloading packages: MariaDB-10.0.10-fedora20-x86_64-server.rpm | 49 MB 00:00:10 Running transaction check Running transaction test Transaction test succeeded Running transaction sed: invalid option -- '1' Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]... -n, --quiet, --silent suppress automatic printing of pattern space -e script, --expression=script add the script to the commands to be executed -f script-file, --file=script-file add the contents of script-file to the commands to be executed --follow-symlinks follow symlinks when processing in place -i[SUFFIX], --in-place[=SUFFIX] edit files in place (makes backup if SUFFIX supplied) -c, --copy use copy instead of rename when shuffling files in -i mode -b, --binary does nothing; for compatibility with WIN32/CYGWIN/MSDOS/EMX ( open files in binary mode (CR+LFs are not treated specially)) -l N, --line-length=N specify the desired line-wrap length for the `l' command --posix disable all GNU extensions. -r, --regexp-extended use extended regular expressions in the script. -s, --separate consider files as separate rather than as a single continuous long stream. -u, --unbuffered load minimal amounts of data from the input files and flush the output buffers more often -z, --null-data separate lines by NUL characters --help display this help and exit --version output version information and exit If no -e, --expression, -f, or --file option is given, then the first non-option argument is taken as the sed script to interpret. All remaining arguments are names of input files; if no input files are specified, then the standard input is read. GNU sed home page: <http://www.gnu.org/software/sed/>. General help using GNU software: <http://www.gnu.org/gethelp/>. ****************************************************************** A MySQL or MariaDB server package () is installed. The current MariaDB server package is provided by a different vendor (package is not installed) than Monty Program AB. Some files may be installed to different locations, including log files and the service startup script in /etc/init.d/. Upgrading directly from MySQL <unrecognized version package is not installed> to MariaDB 10.0 may not be safe in all cases. A manual dump and restore using mysqldump is recommended. It is important to review the MariaDB manual's Upgrading section for version-specific incompatibilities. A manual upgrade is required. - Ensure that you have a complete, working backup of your data and my.cnf files - Shut down the MySQL server cleanly - Remove the existing MySQL packages. Usually this command will list the packages you should remove: rpm -qa | grep -i '^mysql-' You may choose to use 'rpm --nodeps -ev <package-name>' to remove the package which contains the mysqlclient shared library. The library will be reinstalled by the MariaDB-shared package. - Install the new MariaDB packages supplied by Monty Program AB - Ensure that the MariaDB server is started - Run the 'mysql_upgrade' program This is a brief description of the upgrade process. Important details can be found in the MariaDB manual, in the Upgrading section. ****************************************************************** error: %pre(MariaDB-server-10.0.10-1.fc20.x86_64) scriptlet failed, exit status 1 Error in PREIN scriptlet in rpm package MariaDB-server-10.0.10-1.fc20.x86_64 Verifying : MariaDB-server-10.0.10-1.fc20.x86_64 1/2 1:mariadb-server-5.5.36-1.fc20.x86_64 was supposed to be removed but is not! Verifying : 1:mariadb-server-5.5.36-1.fc20.x86_64 2/2 Failed: MariaDB-server.x86_64 0:10.0.10-1.fc20 -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/unable-to-upgrade-from-mariadb-55-to-mariadb-100-u…

1 0

[Maria-discuss] New Question: crash recovery
by AskMonty KB 01 Apr '14

01 Apr '14

Hello, A new question has been asked in "Backing Up and Restoring" by joemurray: -------------------------------- An XtraDB database running in MariaDB - no cluster, no replication - has been crashing about 15 x per day for 3 days and we suspect it may be corrupt. We don't see any reason in the log files for the crashes. We have taken a mysqldump and restored into a new db and run mysqlcheck on the new db and not fond any errors, but I suspect that the dumping and restoring has hidden them. After testing a staging site with this new database we are planning to repeat the process of dumping and restoring into a new db and then making it live. I intend to run mysqlcheck on the production database once it is no longer in production. Any other suggestions from DBAs to this developer? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/crash-recovery/

1 0