- discuss - lists.mariadb.org

Re: [Maria-discuss] noinstall package for MariaDB
by Vineet Deodhar 25 Jan '13

25 Jan '13

Thank you. I really appreciate the fast & helpful response on this mailing list. --- Vineet --- On Fri, 25/1/13, Vladislav Vaintroub <wlad(a)montyprogram.com> wrote: From: Vladislav Vaintroub <wlad(a)montyprogram.com> Subject: RE: [Maria-discuss] noinstall package for MariaDB To: "'Vineet Deodhar'" <d_vineet(a)yahoo.com> Date: Friday, 25 January, 2013, 15:10 >Thanks Vladislav. >If I get you right, I should copy & paste the directories EXCEPT the data directory. >Is that correct? This is correct, and this is what you also should normally do when updating zips, even if you are not switching MySQL variants. >I am using Windows at present, but going to switch over to Ubuntu 12.04 LTS soon. :-) >Can you pl. share the mariadb download url for linux? Everything is on https://downloads.mariadb.org/mariadb . For example https://downloads.mariadb.org/mariadb/5.5.28a/#os_group=linux_generic would be tar.gz (if you favor non-install packages, like on Windows, those are the right ones)

1 0

[Maria-discuss] noinstall package for MariaDB
by Vineet Deodhar 25 Jan '13

25 Jan '13

Hi ! At present, I am using MySQL noinstall version (which doesn't require ANY installation). Just copy & paste the folder & start. Is there any way to use MariaDB without installing? (Maybe replace MySQL folder containing the binaries with MariaDB folder? If yes, from where to get the noinstall folder for MariaDB?) Thanks, Vineet

2 2

[Maria-discuss] Compatibility problems switching Glassfish application from MySQL to MariaDB
by Guido Winkelmann 24 Jan '13

24 Jan '13

Hi, I'm having some problems switching one of our Java/Glassfish-based web applications over from MySQL to to MariaDB. Since the MariaDB project advertises the software as a fully compatible drop- in replacement for MySQL, the first thing I did was simply stop the MySQL server, uninstall it, and then install and start MariaDB (5.5.28a, from Gentoo portage). We have got several C/C++ based application that access our MySQL databases. Those took a recompile, but afterwards continued to work as if nothing had happened. I didn't have as much luck with our glassfish-based web frontend though. The first problem was that the existing MySQL connector is apparently unable to connect to MariaDB, so I deleted the existing JDBC Connection Pools and replaced them with new ones using the MariaDB Java Client instead. This worked on the surface, however now I'm getting a lot of exceptions whenever I'm accessing parts of the application that make use of BINARY type columns. According to the developer (of the web application on question), this is because either MariaDB itself or the connector are returning binary columns as type string, causing the persistance layer to attempt to convert them to a string object. Since the binary columns in question contain various unprintable characters, including zero-bytes, this fails. Can someone please help me with these problems? Guido

2 2

[Maria-discuss] 10.0.0 msi pack fails first start
by Federico Razzoli 24 Jan '13

24 Jan '13

Hi I tried to install MariaDB 10.0.0 on Windows XP, MSI package. Apparently the installation worked, but the server fails to start. I paste here the log until the first shutdown, just in case you don't know about this problem. Federico 130124 10:49:47 InnoDB: The InnoDB memory heap is disabled 130124 10:49:47 InnoDB: Mutexes and rw_locks use Windows interlocked functions 130124 10:49:47 InnoDB: Compressed tables use zlib 1.2.3 130124 10:49:47 InnoDB: CPU does not support crc32 instructions 130124 10:49:47 InnoDB: Initializing buffer pool, size = 128.0M 130124 10:49:47 InnoDB: Completed initialization of buffer pool InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 130124 10:49:47 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 130124 10:49:47 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 130124 10:49:48 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file .\ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... 130124 10:49:48 InnoDB: Doublewrite buffer not found: creating new 130124 10:49:48 InnoDB: Doublewrite buffer created 130124 10:49:49 InnoDB: 128 rollback segment(s) are active. InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 130124 10:49:49 InnoDB: Waiting for the background threads to start 130124 10:49:49 InnoDB: 1.2.0 started; log sequence number 0 130124 10:49:49 [Note] Plugin 'FEEDBACK' is disabled. 130124 10:49:56 InnoDB: FTS optimize thread exiting. 130124 10:49:56 InnoDB: Starting shutdown... 130124 10:49:58 InnoDB: Shutdown completed; log sequence number 1602824 130124 10:50:00 InnoDB: The InnoDB memory heap is disabled 130124 10:50:00 InnoDB: Mutexes and rw_locks use Windows interlocked functions 130124 10:50:00 InnoDB: Compressed tables use zlib 1.2.3 130124 10:50:00 InnoDB: CPU does not support crc32 instructions 130124 10:50:01 InnoDB: Initializing buffer pool, size = 31.0M 130124 10:50:01 InnoDB: Completed initialization of buffer pool 130124 10:50:01 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 31 MB InnoDB: Database physically writes the file full: wait... 130124 10:50:02 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file .\ib_logfile1 size to 31 MB InnoDB: Database physically writes the file full: wait... 130124 10:50:03 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 130124 10:50:03 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 130124 10:50:03 InnoDB: 128 rollback segment(s) are active. 130124 10:50:03 InnoDB: Waiting for the background threads to start 130124 10:50:03 InnoDB: 1.2.0 started; log sequence number 1603084 130124 10:50:03 [Note] Plugin 'FEEDBACK' is disabled. 130124 10:50:03 [Note] Event Scheduler: Loaded 0 events 130124 10:50:03 [Note] C:\Programmi\MariaDB 10.0\bin\mysqld.exe: ready for connections. Version: '10.0.0-MariaDB' socket: '' port: 3306 Source distribution 130124 11:03:13 InnoDB: The InnoDB memory heap is disabled 130124 11:03:13 InnoDB: Mutexes and rw_locks use Windows interlocked functions 130124 11:03:13 InnoDB: Compressed tables use zlib 1.2.3 130124 11:03:13 InnoDB: CPU does not support crc32 instructions 130124 11:03:13 InnoDB: Initializing buffer pool, size = 128.0M 130124 11:03:13 InnoDB: Completed initialization of buffer pool InnoDB: Error: log file .\ib_logfile0 is of different size 32505856 bytes InnoDB: than specified in the .cnf file 5242880 bytes! 130124 11:03:14 [ERROR] Plugin 'InnoDB' init function returned error. 130124 11:03:14 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 130124 11:03:15 [Note] Plugin 'FEEDBACK' is disabled. 130124 11:03:16 [ERROR] Unknown/unsupported storage engine: InnoDB 130124 11:03:16 [ERROR] Aborting 130124 11:03:17 [Note] C:/Programmi/MariaDB 10.0/bin/mysqldd: Shutdown complete

1 1

[Maria-discuss] Trouble installing MariaDB 5.5 on Ubuntu 12.04 (& 12.10)
by Aaron Anderson 23 Jan '13

23 Jan '13

Gang, I've installed MariaDB on several Debian/Ubuntu systems in the past few months, without any issues. ~2 days ago on an Unbuntu 12.10 system did an apt-get update/upgrade/dist-upgrade. I believe that MariaDB was updated in that process. After the updates, mysql was "gone" My apps couldn't find it, it wasn't running, etc. I was in a hurry so I had to fall back to the standard mysql package so not a lot of into there. I built a new Ubuntu 12.04 LTS server, added the Maria repo, did an apt-get update/ugprade/dist-upgrade. Rebooted. Here's some output... I'm stuck in this loop. root@nn01:~# apt-get install mariadb-server Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mariadb-server : Depends: mariadb-server-5.5 but it is not going to be installed E: Unable to correct problems, you have held broken packages. root@nn01:~# apt-get install mariadb-server-5.5 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mariadb-server-5.5 : Depends: mariadb-client-5.5 (>= 5.5.28-mariadb-a1~precise) but it is not going to be installed Depends: mariadb-server-core-5.5 (>= 5.5.28-mariadb-a1~precise) but it is not going to be installed E: Unable to correct problems, you have held broken packages. root@nn01:~# apt-get install mariadb-client-5.5 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mariadb-client-5.5 : Depends: libdbd-mysql-perl (>= 1.2202) but it is not going to be installed Depends: mariadb-common but it is not going to be installed Depends: libmariadbclient18 (>= 5.5.28-mariadb-a1~precise) but it is not going to be installed Depends: mariadb-client-core-5.5 (>= 5.5.28-mariadb-a1~precise) but it is not going to be installed E: Unable to correct problems, you have held broken packages. root@nn01:~#

2 2

[Maria-discuss] KB Question: Issues with ignore-db-dir
by Daniel Bartholomew 23 Jan '13

23 Jan '13

The following question has been posted to the Knowledgebase: https://kb.askmonty.org/en/issues-with-ignore-db-dir/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Issues with ignore-db-dir Hello, I see that the ignore-db-dir option has been available since Maria 5.3.9 ( https://kb.askmonty.org/en/mariadb-539-changelog/ ) , however I am finding that MariaDB 5.5.27 is not recognizing the option. When I put "ignore-db-dir=lost+found" in the mysqld section of the my.cnf file or when I attempt to start mysqld with "/etc/init.d/mysql start --ignore-db-dir=lost+found", both times mysql fails to start with the following message: 130111 17:08:57 [ERROR] /usr/sbin/mysqld: unknown variable 'ignore-db-dir=lost+found' 130111 17:08:57 [ERROR] Aborting Is there a patch that I was supposed to apply but haven't ? Or maybe I am misunderstanding how or where to specify the ignore-db-dir option. For reference, the full version as reported by mysqld is: $ mysqld --version mysqld Ver 5.5.27-MariaDB for Linux on x86_64 (MariaDB Server) Thanks, -Said - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- Daniel Bartholomew Google+ - http://gplus.to/dbart Twitter - http://twitter.com/daniel_bart MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledgebase - http://kb.askmonty.org Monty Program - http://montyprogram.com

1 0

[Maria-discuss] Fwd: [debian-mysql] Bug#688505: MariaDB packaging.
by Colin Charles 19 Jan '13

19 Jan '13

A good wishlist. I think more should vote for this, quite clearly! cheers, -colin Begin forwarded message: > Resent-From: Robert de Bath <robert$(a)debath.co.uk> > From: Robert de Bath <robert$(a)debath.co.uk> > Subject: [debian-mysql] Bug#688505: MariaDB packaging. > Date: 23 September 2012 16:25:39 GMT+08:00 > Resent-To: debian-bugs-dist(a)lists.debian.org > To: submit(a)bugs.debian.org > Resent-Cc: Debian MySQL Maintainers <pkg-mysql-maint(a)lists.alioth.debian.org> > Reply-To: Robert de Bath <robert$(a)debath.co.uk>, 688505(a)bugs.debian.org > > Package: mysql-server > Version: 5.5.24+dfsg-8 > Severity: wishlist > > My very technically savvy webhost has recently switched from MySQL to > MariaDB and claim it's for both technical and political reasons. > > Both of these reasons (better performance and better licensing) appear > to be good reasons for the software to be packaged as a Debian package > and I expect it's getting to the point that someone will do it themselves. > > BUT the software is technically still not a forked variant of MySQL > but a patched version where the maintainers continually resync to the > Oracle releases. For this reason I would like to see it treated as just > a simple MySQL version within Debian. This way the users (ie: me) can > simply switch by prodding apt in the right way. > > For this to work seamlessly (unlike, for example, the recent multimedia > troubles) the MariaDB package should be packaged identically to MySQL, > which IMO is best done by the same Debian maintainers. > > So my request is that you package the MariaDB as a secondary version of > MySQL in such a way that the two packages can be seamlessly switched within the Debian system. > > -- > Rob. (Robert de Bath <robert$ @ debath.co.uk>) > <http://www.debath.co.uk/> > > _______________________________________________ > pkg-mysql-maint mailing list > pkg-mysql-maint(a)lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/

3 3

[Maria-discuss] MariaDB Java Client 1.1.0 Released
by Daniel Bartholomew 16 Jan '13

16 Jan '13

The MariaDB Java Client 1.1.0 has been released. You can download it here: https://downloads.mariadb.org/client-java/1.1.0/ This version focused on fixing all known database metadata bugs and ConnnectorJ incompatibilities. Specific fixes include: - Consistent, compatible with ConnectorJ handling of JDBC catalogs vs schemas vs databases - Implementation of several missing methods in DatabaseMetaData - Better handling of statement timeouts - OSGi-specific entries have been added to MANIFEST.MF so it can be used in OSGi environments - Added support for dumpQueriesOnException=true in the JDBC URL - Added support for IPv6 addresses in the connector - Added SSL support - and more... See the Release Notes and Changelog for more information: - https://kb.askmonty.org/en/mariadb-java-client-110-release-notes - https://kb.askmonty.org/en/mariadb-java-client-110-changelog See also the "About the MariaDB Java Client" page: - https://kb.askmonty.org/en/about-the-mariadb-java-client -- MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledgebase - http://kb.askmonty.org Monty Program - http://montyprogram.com

1 0

[Maria-discuss] MariaDB installation failed in fedora17, No more mirrors to try!!!
by Haseena L. 14 Jan '13

14 Jan '13

Hi all, Iam trying to install mariadb in fedora17 using the following link : https://kb.askmonty.org/en/installing-mariadb-with-yum/#manually-importi ng-the-mariadb-signing-key It shows an error, there is no mirror for downloading mariadb. Please see the error log : $ sudo yum install MariaDB-server MariaDB-client Loaded plugins: langpacks, presto, refresh-packagekit fedora/metalink | 8.3 kB 00:00 fedora | 4.2 kB 00:00 fedora/primary_db | 12 MB 00:02 fedora/group_gz | 434 kB 00:00 mariadb | 1.9 kB 00:00 mariadb/primary_db | 15 kB 00:00 updates/metalink | 3.7 kB 00:00 updates | 4.7 kB 00:00 updates/primary_db | 5.9 MB 00:44 updates/group_gz | 439 kB 00:00 Resolving Dependencies --> Running transaction check ---> Package MariaDB-client.i686 0:5.5.28a-1 will be installed --> Processing Dependency: MariaDB-common for package: MariaDB-client-5.5.28a-1.i686 ---> Package MariaDB-server.i686 0:5.5.28a-1 will be obsoleting ---> Package mysql.i686 0:5.5.23-1.fc17 will be obsoleted ---> Package mysql-server.i686 0:5.5.23-1.fc17 will be obsoleted --> Running transaction check ---> Package MariaDB-common.i686 0:5.5.28a-1 will be installed --> Finished Dependency Resolution Dependencies Resolved ======================================================================== ======== Package Arch Version Repository Size ======================================================================== ======== Installing: MariaDB-client i686 5.5.28a-1 mariadb 8.4 M MariaDB-server i686 5.5.28a-1 mariadb 32 M replacing mysql.i686 5.5.23-1.fc17 replacing mysql-server.i686 5.5.23-1.fc17 Installing for dependencies: MariaDB-common i686 5.5.28a-1 mariadb 23 k Transaction Summary ======================================================================== ======== Install 2 Packages (+1 Dependent package) Total size: 41 M Total download size: 41 M Is this ok [y/N]: y Downloading Packages: http://yum.mariadb.org/5.5/fedora17-x86/rpms/MariaDB-5.5.28a-fedora17-i6 86-client.rpm: [Errno 12] Timeout on http://yum.mariadb.org/5.5/fedora17-x86/rpms/MariaDB-5.5.28a-fedora17-i6 86-client.rpm: (28, '') Trying other mirror. http://yum.mariadb.org/5.5/fedora17-x86/rpms/MariaDB-5.5.28a-fedora17-i6 86-server.rpm: [Errno 12] Timeout on http://yum.mariadb.org/5.5/fedora17-x86/rpms/MariaDB-5.5.28a-fedora17-i6 86-server.rpm: (28, '') Trying other mirror. Error Downloading Packages: MariaDB-server-5.5.28a-1.i686: failure: rpms/MariaDB-5.5.28a-fedora17-i686-server.rpm from mariadb: [Errno 256] No more mirrors to try. MariaDB-client-5.5.28a-1.i686: failure: rpms/MariaDB-5.5.28a-fedora17-i686-client.rpm from mariadb: [Errno 256] No more mirrors to try. Please help me... Give me the appropriate mirror for downloading mariadb Regards, Haseena ***** Confidentiality Statement/Disclaimer ***** This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt. The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message.

1 0

[Maria-discuss] Reporting upstream bugs
by Federico Razzoli 10 Jan '13

10 Jan '13

Hi all. I reported a bug in JIRA - I hit it in MariaDB but it was tagged as "upstream". This brings us to the question: is it ok to report upstream bugs in MariaDB's JIRA? There are 2 reasons why I didn't report it to Oracle. Let me explain. 1) MySQL Ab and Sun never had a lot of data about me or the companies where I worked. They only had my email and my full name, plus some optional info, if I remember correctly. But my old account doesn't work anymore, and the new Oracle's sign up page REQUIRES a lot of data - including a physical address and a work phone. I don't want to provide them too much info about me and my company. 2) I tried to sign up with fake data, but after 2 days I didn't receive a confirm email and my account still doesn't work. They are very slow, or something doesn't work fine in their website, or they detected that some data I wrote is fake (but I got no error message). I think that a company which develops open source software should be glad that people reports bugs, and should make the process easier. If the process is hard, I would prefer to report bugs to MariaDB. But, what does MariaDB think about it? Is it ok to report the bugs to you? Federico Razzoli

3 3