Linux vlmmk644 2.6.18-308.8.1.0.1.el5 #1 SMP Tue May 29 20:48:54 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

Hi,

We have 2 sets of binary tarballs in downloads ( https://downloads.mariadb.org/mariadb/10.0.0/ ):

mariadb-10.0.0-linux-x86_64.tar.gz (GLIBC_2.14) 292.4 MB
mariadb-10.0.0-linux-x86_64.tar.gz 242.2 MB
mariadb-10.0.0-linux-i686.tar.gz 233.7 MB
mariadb-10.0.0-linux-i686.tar.gz (GLIBC_2.14) 282.2 MB

It looks like you are using the first one, while you actually need the second. Please try it out.

can you please name the exact tarball which i can use on my server.

Here is the link which, with some luck, will get you directly to the download

https://downloads.mariadb.org/f/mariadb-10.0.0/kvm-bintar-hardy-amd64/mariadb-10.0.0-linux-x86_64.tar.gz/from/http:/ftp.igh.cnrs.fr/pub/mariadb/

but if it doesn't, please go to the downloads page and pick

mariadb-10.0.0-linux-x86_64.tar.gz

without "(GLIBC_2.14)" in the file name column.

md5sum: d7477d3241888c11d3a2bc1a2394e9c5

Please let us know if it works for you.

I am downloading it.

I am working on this for the first time,so could you please share db installation steps.
Should i create any configuration file?

Please check documentation provided at https://kb.askmonty.org , there is a lot of information out there.
Particularly, you might be interested in "Installing MariaDB Binary Tarballs": https://kb.askmonty.org/en/installing-mariadb-binary-tarballs/

it says
MariaDB searches for the configuration files '/etc/my.cnf' (on some systems '/etc/mysql/my.cnf') and '~/.my.cnf'. If you have an old my.cnf file (maybe from a system installation of MariaDB or MySQL) you need to take care that you don't accidentally use the old one with your new binary .tar installation.

I dont have any my.cnf file.
Can i create a file my.cnf under my own directory where i am copying the tarfile ?
what can we have in my.cnf file?

You don't have to create my.cnf file if you are just trying the product and don't have any specific configuration you want it to start with. If you don't have my.cnf on your machine, bin/mysqld_safe will start MariaDB server with the default configuration, which is quite all right for a trial run.

If you choose to create my.cnf file, you can place it anywhere you have access to, as long as you provide the correct path to it on mysqld_safe command line
./bin/mysqld_safe --defaults-file=<path to my.cnf>

In general, in my.cnf you can have various startup options. For quick reference and overall view of general MySQL options, you can use MySQL manual: http://dev.mysql.com/doc/refman/5.5/en/mysqld-option-tables.html
specifically, you are interested in those that have 'Yes' in the options file column.
You can also find most of those and some MariaDB-specific options in here: https://kb.askmonty.org/en/mysqld-options-full-list/

But which options you choose to tune, and which values you use, depends on your installation, environment, requirements, business needs and personal preferences.

I presume the problem with GLIBC_2.14 has been solved by using another binary tarball; closing the report.