MariaDB 10.0.0.8 RC

Hello,
I wanted to share on AUR mariadb 10.0.0.8 but i can't submit it as it's a split package.
If anyone is interested, you can find the PKGBUILD or source package here: http://fabienwang.fr/aur/mariadb/
I also let the binaries for myself because it took 3 hours to compile.
NB: i needed the mariadb 10 branch as some fixes are missing in the old 5.5 branch
(ie. default value to CURRENT_TIMESTAMP on datetime fields, which was fixed in original mysql 5.6 branch.
I hope you enjoy it.
Regards,
fabienwang
edited after karol's remark
Last edited by fabienwang (2014-02-28 15:29:56)

karol wrote:AUR is for PKGBUILDs, if you want to share a prebuilt binary, create an unofficial repository.
Read my post again. I can't submit the package to AUR as it's a «split package» and that's not my fault coz the official mariadb PKGBUILD is the exact same in extra repository.
I'm not trying to share the compiled binaries and won't create a repo for that.
If you want to save 3 hours of compilation it's your choice but people can also get the source package and compile it themselves.

Similar Messages

MariaDB, PHP, and mysql_connect() issue on Installation scripts

I searched for this issue and turned out nothing..
I am using an installation script on my web server and i get this error:
function mysql_connect() not found:
Your system does not appear to have mysql available within php
I followed the wiki and have uncommented the following lines
extension=pdo_mysql.so
extension=mysqli.so
extension=mysql.so
I have also restarted the httpd daemon several times. I am using MariaDB because I know arch is dropping mysql. I followed the MariaDB wiki too and have it set-up properly.
Here is my "mysqli" section of phpinfo()
MysqlI Support enabled
Client API library version mysqlnd 5.0.10 - 20111026 - $Id: e707c415db32080b3752b232487a435ee0372157 $
Active Persistent Links 0
Inactive Persistent Links 0
Active Links 0
Directive Local Value Master Value
mysqli.allow_local_infile On On
mysqli.allow_persistent On On
mysqli.default_host no value no value
mysqli.default_port 3306 3306
mysqli.default_pw no value no value
mysqli.default_socket /var/run/mysqld/mysqld.sock /var/run/mysqld/mysqld.sock
mysqli.default_user no value no value
mysqli.max_links Unlimited Unlimited
mysqli.max_persistent Unlimited Unlimited
mysqli.reconnect Off Off
and here is "mysqlnd" in phpinfo()
mysqlnd
mysqlnd enabled
Version mysqlnd 5.0.10 - 20111026 - $Id: e707c415db32080b3752b232487a435ee0372157 $
Compression supported
SSL supported
Command buffer size 4096
Read buffer size 32768
Read timeout 31536000
Collecting statistics Yes
Collecting memory statistics No
Tracing n/a
Loaded plugins mysqlnd,example,debug_trace,auth_plugin_mysql_native_password,auth_plugin_mysql_clear_password
API Extensions mysqli
MySQL is running as I have set-up a database and user for this installation script.

I dropped to the command line and tried to run php and realized that mysql.so was named mssql.so..
so for anyone that has this issue, when you install php, unless they change it next release, that's a typo you have to fix when uncommented the mysql extension
Last edited by evil (2013-03-31 19:34:12)

New installation of MariaDB does not start with systemctl

Just installed MariaDB, and I get this:
# systemctl start mariadb.service
Failed to issue method call: Unit mariadb.service failed to load: No such file or directory.
Is there something I'm missing?

pacman -Ql mariadb | grep service

MariaDB allowing login without command line password

Hi,
Today I have upgraded to MariaDB as recommended. I am currently in configuration process and didn't want my cronjobs to run with a command line password for MySQL. Thus I searched and came up with three different solutions (found on SO). None of these options work for me.
Note: I did not try thins on native MySQL so this issue might not strictly be with MariaDB, but I cannot know.
The methods described in the answers where:
- Placing a users ".my.cnf" in his home dir and inserting this:
[client]
password = my_secret_pass
- Setting the MYSQL_PWD variable:
MYSQL_PWD="my_secret_pass" mysql -u username -p
- Changing the default searched file ".my.cnf" to something different.
mysql --defaults-file=my_user_login.cnf -u username -p
I also tried a fourth method: Just editing the global "my.cnf" in "/etc/mysql/". There was already a line like this:
#password = your_password
I changed that and restarted the mysql service. Stil running
mysql -u username -p
asks for a password.
When running
mysql --defaults-file
it complains
mysql: unknown option '--defaults-file'
But when running
mysql --help
it says this:
Default options are read from the following files in the given order:
/etc/my.cnf /etc/mysql/my.cnf ~/.my.cnf
The following groups are read: mysql client client-server client-mariadb
The following options may be given as the first argument:
--print-defaults Print the program argument list and exit.
--no-defaults Don't read default options from any option file.
--defaults-file=# Only read default options from the given file #.
--defaults-extra-file=# Read this file after the global files are read.
I have tried those options, with and without the "=" but it complains that they are not present.
Google on this only spit out that MariaDB behaves on this like MySQL does (they link to the MySQL docs).
The last fallback idea would now be that Arch has disabled this behaviour during compile time (but why is the doc then there?). Is anyone able to help me on this issue? Thanks in adavnce.

Post to the appropriate forum under OS X Technologies. That's where the Unix, Terminal, and developer gurus hang out.

Why Arch Linux official repository provide MariaDB instead of MySQL?

First, I want to say I'm not an expert in MySQL or any other RDBMS. I just started to learn mysql a month ago. So didn't know exactly what is the practical difference between MariaDB and MySQL. Both are looks the same (except for the prompt as far as I know). But oracle MySQL is still the majority RDBMS that is being used in comparision with MariaDB. Since I just started to learn, I wanna use the most used. So I choose MySQL.
My curiosity is why Arch choose MariaDB? Is MySQL going against "The Arch Way" or something like that? I read somewhere when googling that one of the reason why MariaDB is created is because Oracle purchased Sun Microsystems. Or maybe there're some bug issues or something if using MySQL on Arch Linux?

Search back through the arch news items. We switched over a fews ago I think.
EDIT: https://lists.archlinux.org/pipermail/a … 24478.html
Last edited by graysky (2015-04-13 10:30:28)

Mariadb failed to start again [solved]

mariadb is not starting, or restarting.
i have poured over topics, tried a few things, but not really sure where to go next.
$ journalctl -xn
-- Logs begin at Fri 2014-09-19 23:05:01 PDT, end at Sun 2014-10-26 15:07:23 PDT. --
Oct 26 15:05:53 falcon systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
Oct 26 15:05:53 falcon mysqld[971]: 141026 15:05:53 [ERROR] Aborting
Oct 26 15:07:23 falcon systemd[1]: mysqld.service start-post operation timed out. Stopping.
Oct 26 15:07:23 falcon systemd[1]: Failed to start MariaDB database server.
-- Subject: Unit mysqld.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit mysqld.service has failed.
-- The result is failed.
Oct 26 15:07:23 falcon systemd[1]: Unit mysqld.service entered failed state.
Oct 26 15:07:23 falcon systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: No such file or directory.
Oct 26 15:07:23 falcon systemd[1]: Cannot add dependency job for unit swat.socket, ignoring: Unit swat.socket failed to load: No such file or directory.
Oct 26 15:07:23 falcon mysqld[1606]: 141026 15:07:23 [ERROR] /usr/bin/mysqld: ambiguous option '--u' (user, use_stat_tables)
Oct 26 15:07:23 falcon mysqld[1606]: 141026 15:07:23 [ERROR] Aborting
Oct 26 15:07:23 falcon systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
$ systemctl status mysqld.service
* mysqld.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled)
Active: activating (start-post) (Result: exit-code) since Sun 2014-10-26 14:58:07 PDT; 15s ago
Process: 9807 ExecStart=/usr/bin/mysqld --pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE)
Main PID: 9807 (code=exited, status=1/FAILURE); : 9808 (mysqld-post)
CGroup: /system.slice/mysqld.service
`-control
|-9808 /bin/sh /usr/bin/mysqld-post
`-9920 sleep 1
Oct 26 14:58:07 falcon mysqld[9807]: 141026 14:58:07 [ERROR] /usr/bin/mysqld: ambiguous option '--u' (user, use_stat_tables)
Oct 26 14:58:07 falcon mysqld[9807]: 141026 14:58:07 [ERROR] Aborting
Oct 26 14:58:07 falcon systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
$ mysql -u root -p
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2 "No such file or directory")
$ mysql_install_db --user=mysql --ldata=/var/lib/mysql/
FATAL ERROR: Could not find ./share/mysql/fill_help_tables.sql
If you compiled from source, you need to run 'make install' to
copy the software into the correct location ready for operation.
If you are using a binary release, you must either be at the top
level of the extracted archive, or pass the --basedir option
pointing to that location.
The latest information about mysql_install_db is available at
https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
i looked in /var/log and im not seeing anything related to mysql, no file with the name mysql, and no folder either... so i looked in my.cnf, saw it was pointing to /var/log/mysqld.log, so i created this file, chowned it to mysql:mysql, chmod 770, and i still cant restart it. (i havent rebooted since i created the log file, do i need to?)
i do see it saying something about
ambiguous option '--u'
, is that the problem?
any suggestions on how to dig out more info here so i can figure out whats going on?
Last edited by wolfdogg (2014-10-26 22:22:12)

crap, in my mysql conf file, i found the
u
, it was here
u# table_open_cache = 64
where that came from i have no idea. it restarted RIGHT away just after that
$ systemctl start mysqld
$ systemctl status mysqld.service
* mysqld.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled)
Active: active (running) since Sun 2014-10-26 15:19:33 PDT; 1min 47s ago
Process: 6659 ExecStartPost=/usr/bin/mysqld-post (code=exited, status=0/SUCCESS)
Main PID: 6658 (mysqld)
CGroup: /system.slice/mysqld.service
`-6658 /usr/bin/mysqld --pid-file=/run/mysqld/mysqld.pid
Oct 26 15:19:27 falcon mysqld[6658]: 141026 15:19:27 [Warning] /usr/bin/mysqld: ignoring option '--character-set-client-handshake' due to invalid value 'utf8'
Oct 26 15:19:27 falcon mysqld[6658]: 141026 15:19:27 [Warning] option 'max_heap_table_size': unsigned value 0 adjusted to 16384
Oct 26 15:19:27 falcon mysqld[6658]: 141026 15:19:27 [Warning] Changed limits: max_open_files: 1024 max_connections: 214 table_cache: 400

MariaDB installed again and can't run mysqld.service

Hi,
It started when I dropped root user in mysql. I panicked and removed mariadb by yaourt, and any of files "mysql" name(manually).
Later I installed mariadb again. While install i get this output:
Installing MariaDB/MySQL system tables in './data' ...
141113 22:41:22 [Note] InnoDB: Using mutexes to ref count buffer pool pages
141113 22:41:22 [Note] InnoDB: The InnoDB memory heap is disabled
141113 22:41:22 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
141113 22:41:22 [Note] InnoDB: Memory barrier is not used
141113 22:41:22 [Note] InnoDB: Compressed tables use zlib 1.2.8
141113 22:41:22 [Note] InnoDB: Using Linux native AIO
141113 22:41:22 [Note] InnoDB: Using CPU crc32 instructions
141113 22:41:22 [Note] InnoDB: Initializing buffer pool, size = 128.0M
141113 22:41:22 [Note] InnoDB: Completed initialization of buffer pool
141113 22:41:22 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
141113 22:41:22 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
141113 22:41:22 [Note] InnoDB: Database physically writes the file full: wait...
141113 22:41:22 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
141113 22:41:23 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
141113 22:41:24 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
141113 22:41:24 [Warning] InnoDB: New log files created, LSN=45781
141113 22:41:24 [Note] InnoDB: Doublewrite buffer not found: creating new
141113 22:41:24 [Note] InnoDB: Doublewrite buffer created
141113 22:41:24 [Note] InnoDB: 128 rollback segment(s) are active.
141113 22:41:24 [Warning] InnoDB: Creating foreign key constraint system tables.
141113 22:41:24 [Note] InnoDB: Foreign key constraint system tables created
141113 22:41:24 [Note] InnoDB: Creating tablespace and datafile system tables.
141113 22:41:24 [Note] InnoDB: Tablespace and datafile system tables created.
141113 22:41:24 [Note] InnoDB: Waiting for purge to start
141113 22:41:24 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.20-68.0 started; log sequence number 0
141113 22:41:24 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
141113 22:41:28 [Note] InnoDB: FTS optimize thread exiting.
141113 22:41:28 [Note] InnoDB: Starting shutdown...
141113 22:41:30 [Note] InnoDB: Shutdown completed; log sequence number 1616697
OK
Filling help tables...
141113 22:41:31 [Note] InnoDB: Using mutexes to ref count buffer pool pages
141113 22:41:31 [Note] InnoDB: The InnoDB memory heap is disabled
141113 22:41:31 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
141113 22:41:31 [Note] InnoDB: Memory barrier is not used
141113 22:41:31 [Note] InnoDB: Compressed tables use zlib 1.2.8
141113 22:41:31 [Note] InnoDB: Using Linux native AIO
141113 22:41:31 [Note] InnoDB: Using CPU crc32 instructions
141113 22:41:31 [Note] InnoDB: Initializing buffer pool, size = 128.0M
141113 22:41:31 [Note] InnoDB: Completed initialization of buffer pool
141113 22:41:31 [Note] InnoDB: Highest supported file format is Barracuda.
141113 22:41:31 [Note] InnoDB: 128 rollback segment(s) are active.
141113 22:41:31 [Note] InnoDB: Waiting for purge to start
141113 22:41:31 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.20-68.0 started; log sequence number 1616697
141113 22:41:31 [Note] InnoDB: FTS optimize thread exiting.
141113 22:41:31 [Note] InnoDB: Starting shutdown...
141113 22:41:33 [Note] InnoDB: Shutdown completed; log sequence number 1616707
OK
To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system
PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
To do so, start the server, then issue the following commands:
'/usr/bin/mysqladmin' -u root password 'new-password'
'/usr/bin/mysqladmin' -u root -h laptop password 'new-password'
Alternatively you can run:
'/usr/bin/mysql_secure_installation'
which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.
See the MariaDB Knowledgebase at http://mariadb.com/kb or the
MySQL manual for more instructions.
You can start the MariaDB daemon with:
cd '/usr' ; /usr/bin/mysqld_safe --datadir='./data'
You can test the MariaDB daemon with mysql-test-run.pl
cd '/usr/mysql-test' ; perl mysql-test-run.pl
Please report any problems at http://mariadb.org/jira
The latest information about MariaDB is available at http://mariadb.org/.
You can find additional information about the MySQL part at:
http://dev.mysql.com
Support MariaDB development by buying support/new features from
SkySQL Ab. You can contact us about this at [email protected].
Alternatively consider joining our community based development effort:
http://mariadb.com/kb/en/contributing-to-the-mariadb-project/
here are 2 warnings, but i ignored them.
next step(following wiki) is running mysqld.service. I try, and the output is:
Job for mysqld.service failed. See "systemctl status mysqld.service" and "journalctl -xe" for details.
next:
systemctl status mysqld.service
● mysqld.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled)
Active: activating (start-post) since Thu 2014-11-13 22:48:14 CET; 57s ago
Main PID: 6692 (mysqld); : 6693 (mysqld-post)
CGroup: /system.slice/mysqld.service
├─6692 /usr/bin/mysqld --pid-file=/run/mysqld/mysqld.pid
└─control
├─6693 /bin/sh /usr/bin/mysqld-post
└─7119 sleep 1
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Completed initialization of buffer pool
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Highest supported file format is Barracuda.
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: 128 rollback segment(s) are active.
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Waiting for purge to start
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.20-68.0 started; log sequence number 1616857
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] Plugin 'FEEDBACK' is disabled.
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] Server socket created on IP: '::'.
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] Event Scheduler: Loaded 0 events
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] /usr/bin/mysqld: ready for connections.
Nov 13 22:48:14 laptop mysqld[6692]: Version: '10.0.14-MariaDB-log' socket: '/run/mysqld/mysqld.sock' port: 3306 MariaDB Server
more:
journalctl -xe
-- Unit mysqld.service has failed.
-- The result is failed.
Nov 13 22:48:13 laptop systemd[1]: Unit mysqld.service entered failed state.
Nov 13 22:48:13 laptop systemd[1]: mysqld.service failed.
Nov 13 22:48:13 laptop sudo[6328]: pam_unix(sudo:session): session closed for user root
Nov 13 22:48:14 laptop systemd[1]: mysqld.service holdoff time over, scheduling restart.
Nov 13 22:48:14 laptop systemd[1]: Stopping MariaDB database server...
-- Subject: Unit mysqld.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit mysqld.service has begun shutting down.
Nov 13 22:48:14 laptop systemd[1]: Starting MariaDB database server...
-- Subject: Unit mysqld.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit mysqld.service has begun starting up.
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: The InnoDB memory heap is disabled
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Memory barrier is not used
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Compressed tables use zlib 1.2.8
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Using Linux native AIO
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Using CPU crc32 instructions
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Completed initialization of buffer pool
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Highest supported file format is Barracuda.
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: 128 rollback segment(s) are active.
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Waiting for purge to start
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.20-68.0 started; log sequence number 1616857
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] Plugin 'FEEDBACK' is disabled.
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] Server socket created on IP: '::'.
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] Event Scheduler: Loaded 0 events
Nov 13 22:48:14 laptop mysqld[6692]: 141113 22:48:14 [Note] /usr/bin/mysqld: ready for connections.
Nov 13 22:48:14 laptop mysqld[6692]: Version: '10.0.14-MariaDB-log' socket: '/run/mysqld/mysqld.sock' port: 3306 MariaDB Server
Nov 13 22:48:58 laptop sudo[7027]: rlk120 : TTY=pts/0 ; PWD=/home/rlk120 ; USER=root ; COMMAND=/usr/bin/systemctl status mysqld.service
Nov 13 22:48:58 laptop sudo[7027]: pam_unix(sudo:session): session opened for user root by rlk120(uid=0)
Nov 13 22:48:58 laptop sudo[7027]: pam_unix(sudo:session): session closed for user root
Nov 13 22:49:03 laptop kernel: perf interrupt took too long (2515 > 2495), lowering kernel.perf_event_max_sample_rate to 50100
Nov 13 22:49:11 laptop sudo[7120]: rlk120 : TTY=pts/0 ; PWD=/home/rlk120 ; USER=root ; COMMAND=/usr/bin/systemctl status mysqld.service
Nov 13 22:49:11 laptop sudo[7120]: pam_unix(sudo:session): session opened for user root by rlk120(uid=0)
Nov 13 22:49:11 laptop sudo[7120]: pam_unix(sudo:session): session closed for user root
Anybody can help? I considered even reinstall Arch because of this, i really need fast fix this database.

MlchaelLAX wrote:
If you are unable to upgrade your Microsoft Office products consider installing Snow Leopard (and Rosetta) into Parallels 7 in Lion and run Microsoft Office 2004 concurrently:
Some people have expressed compatibility problems with data files from 2004 when opened in MS Office 2008 or 2011.
For example, I have an important spreadsheet with a chart created in Excel 2004 that when opened in Excel 2011, the chart is completely unusable. I continue to use this file weekly and I do so with Excel 2004 in my Parallels 7 Snow Leopard Environment with ease.
Full Snow Leopard installation instructions here:
http://forums.macrumors.com/showthread.php?t=1365439
Whooa! Here we go! Never heard of this hack before!! Most simply update their programs.
Marvellous.
Thank you Mr. Lax (ative)
Pete

CentOS/ MariaDB and Amazon S3

Hello all,
Currently I am running a CentOS 6.6 server on a VPS. I am looking to expand the storage utilizing the Amazon S3 service. The main purpose of this server is Mailpiler, the open source email archive program. My local storage is filling up fast which is why I want to expand.
My question is, can I move my MariaDB onto Amazon S3 and continue running my program just by altering the file paths in the mailpiler config? For those who are not familiar MariaDB (MYSQL) is a database. My main goal here is to keep running the program utilizing offsite storage with Amazon S3. I know it is possible to mount Amazon S3 on the server but not sure if I can do anything with my existing database.
This topic first appeared in the Spiceworks Community

Hello all,
Currently I am running a CentOS 6.6 server on a VPS. I am looking to expand the storage utilizing the Amazon S3 service. The main purpose of this server is Mailpiler, the open source email archive program. My local storage is filling up fast which is why I want to expand.
My question is, can I move my MariaDB onto Amazon S3 and continue running my program just by altering the file paths in the mailpiler config? For those who are not familiar MariaDB (MYSQL) is a database. My main goal here is to keep running the program utilizing offsite storage with Amazon S3. I know it is possible to mount Amazon S3 on the server but not sure if I can do anything with my existing database.
This topic first appeared in the Spiceworks Community

[Solved] Connecting Webmin to mariadb

Hi everyone,
I hope this is the right subforum for my question ...
I am trying to setup a Webmin interface to experiment with my newly setup LAMP on a Raspberry Pi (running all the latest from the repositories in Arch-ARM). I have Arch running and just installed Apache, Mariadb and Php, i secured the mysql-installation from the command line, apache and php are running as well. Now I'm trying to setup webmin for easier administration.
I'm stuck where Webmin expects me to point it to multiple MySQL commands to control it. I stumbled through various guides that told me to exchange the default
/etc/rc.d/mysql start
for
/etc/init.d/mysql start
and point webmin to
/var/lib/mysql/my.cnf
for a config file, however I keep getting error messages like
The MySQL startup script /etc/init.d/mysql was not found on your system. Maybe MySQL is not installed, or your module configuration is incorrect.
Since I'm a beginner concerning all but the L-part in LAMP, I do not know where to start looking for the right commands. Any help is greatly appreciated.
Cheers,
jds
Last edited by jds (2014-11-11 18:49:39)

I kind of feared it would be that simple. Thank you sir.

MariaDB not starting due to missing /run/mysqld directory

Hi everyone,
this is my first strike in the Forums, so please do not hurt me if I'm doing something wrong
I already used the forum's search (using "mariadb /run" ad buzzwords), but didn't find a thing.
I just installed MariaDB like described ion the wiki. But when I start it, I get these:
Mar 26 14:04:19 alarmpi systemd[1]: Starting MariaDB database server...
Mar 26 14:04:20 alarmpi mysqld[6626]: 130326 14:04:20 InnoDB: The InnoDB memory heap is disabled
Mar 26 14:04:20 alarmpi mysqld[6626]: 130326 14:04:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins
Mar 26 14:04:20 alarmpi mysqld[6626]: 130326 14:04:20 InnoDB: Compressed tables use zlib 1.2.7
Mar 26 14:04:20 alarmpi mysqld[6626]: 130326 14:04:20 InnoDB: Initializing buffer pool, size = 16.0M
Mar 26 14:04:20 alarmpi mysqld[6626]: 130326 14:04:20 InnoDB: Completed initialization of buffer pool
Mar 26 14:04:20 alarmpi mysqld[6626]: 130326 14:04:20 InnoDB: highest supported file format is Barracuda.
Mar 26 14:04:20 alarmpi mysqld[6626]: 130326 14:04:20 InnoDB: Waiting for the background threads to start
Mar 26 14:04:21 alarmpi mysqld[6626]: 130326 14:04:21 Percona XtraDB (http://www.percona.com) 5.5.30-MariaDB-30.1 started; log sequence number 1597945
Mar 26 14:04:26 alarmpi mysqld[6626]: 130326 14:04:26 [ERROR] Can't start server : Bind on unix socket: No such file or directory
Mar 26 14:04:26 alarmpi mysqld[6626]: 130326 14:04:26 [ERROR] Do you already have another mysqld server running on socket: /run/mysqld/mysqld.sock ?
Mar 26 14:04:26 alarmpi mysqld[6626]: 130326 14:04:26 [ERROR] Aborting
I already figured out that this happens due to a missing directory /run/mysqld ; once this is created, it works like a charm. But just creating it manually won't fix this, since /run is a tmpfs . So next boot, this will happen again.
I tried to edit /usr/lib/systemd/system/mysqld.service and added 'ExecStartPre=mkdir -p /run/mysqld' to it, but this didn't work. Also, it looks like a little bit weird solution even if it works, don't it?
Could someone more familiar with MariaDB/Systemd/ArchLinux please assist ?
Thank you !

You actually found a bug in the mariadb package there. The package is supposed to run "systemd-tmpfiles --create mysql.conf" to make sure this directory exists after installing.
Looking at the .install file, it runs "systemd-tmpfiles --create mysqld.conf" instead which fails (I wonder why there is no error message on installing). Please file a bug report about this.
edit: to clarify, the directory will automatically be created on every boot by the systemd-tmpfiles-setup service, so everything should just work after a reboot. The problem is that currently the directory isn't created after installing the package so it won't work unless you create the directory manually or reboot.
Last edited by 65kid (2013-03-26 14:34:10)

New install of mariadb and mysql-workbench - some questions

So I've installed mariadb along with mysql-workbench. These were fresh installs on a system which has never had mariadb/mysql installed previously. Per the Wiki, I installed mariadb and mysql-workbench, started and enabled the service, and ran the mysql_secure_installation script. I then added a non-root user and even imported a database into it. Everything seems fine, though I have never used either MySQL, mariadb, or mysql-workbench before.
I have a couple of questions:
Question 1:
When I run mysql-workbench, I have to run it with the command “gksudo mysql-workbench” or it comes up in a locked form that doesn't give me (user) access. I am presuming that this is simply because my user account is not a member of the mysql group and that if I changed that, I'd be able to run it with a simple “mysql-workbench” command.
The question is: Should I do that, or is there a good security reason to not have the user be a member of the mysql group? (Would the current setup (having to run “gksudo” be a problem if I installed the mariadb on my server (rather than locally) and mysql-workbench locally?)
The Wiki doesn't say anything about adding the user to the mysql group, so I don't know if that's just an implied standard practice, or if there is good reason not to do so.
Question 2:
When I try to connect to the database with mysql-workbench, it presents me with a password prompt, as expected, then I get a message box that says:
Incompatible/nonstandard server version or connection protocol detected (10.0.17).
A connection to this database can be established but some MySQL Workbench
features may not work properly since the database is not fully compatible
with the supported versions of MySQL.
MySQL Workbench is developed and tested for MySQL Server versions 5.1, 5.5, 5.6 and 5.7
Clicking “Continue Anyway” lets me in and connects everything up and seems to work fine. However, the tab at the top says “Local Instance 33061 - Warning - not supported”.
I presume this has something to do with the fact that I am running mysql-workbench as the front end not to MySQL, but mariadb - and functionality that I've tried seems to work fine.
So my question is: Is there more to this warning (should I be changing some default setting to make everything play nice), or is this just one of those warnings that mean nothing really, and everything IS playing nice already?
Thanks,
Andre

presume this has something to do with the fact that I am running mysql-workbench as the front end not to MySQL, but mariadb - and functionality that I've tried seems to work fine.
I think its probably as you say.
If everything is working fine don't worry.
I'm using php admin to control mariadb but i think there is not much difference between maradb and MySQL.
If problems appear you can always change to MySQL.

MariaDB - Cannot find OQGRAPH package

I am in need of OQGRAPH, however I cannot find this package for Arch. Where abouts may I find this?

You probably have to recompile mariadb with boost and judy added to depends and makedepends. Maybe suggest that in a bugreport. I believe it should be possible to split the compiled plugin out of the main package, so that mariadb itself doesn't have to depend on these packages.
Last edited by progandy (2014-09-02 21:19:23)

[SOLVED] Replacing mariadb with aur/mysql

Hi,
I use KDE and therefore have akonadi as dependency of mariadb.
I need the original mysql community for development.
How do I replace mariadb with aur/mysql?
Thanks for help
Silberling
Last edited by Silberling (2015-01-16 09:30:59)

@fsckd Thanks for moving my post to the right location
==> Finished making: mysql 5.6.22-1 (Thu Jan 15 20:24:17 CET 2015)
==> Continue installing mysql ? [Y/n]
==> [v]iew package contents [c]heck package with namcap
==> ---------------------------------------------------
==>
loading packages...
resolving dependencies...
looking for conflicting packages...
:: libmysqlclient and libmariadbclient are in conflict. Remove libmariadbclient? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: libmysqlclient and libmariadbclient are in conflict
==> WARNING: Your packages are saved in /tmp/yaourt-tmp-kai
These are the last lines. The conflict is:
root@luna /home/kai> pacman -R mariadb
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: akonadi: requires mariadb
root@luna /home/kai> pacman -R libmariadbclient
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: gdal: requires libmariadbclient
:: mariadb-clients: requires libmariadbclient
:: mysql-connector-c++: requires libmysqlclient
:: mysql-python: requires libmariadbclient
:: mysql-workbench: requires libmariadbclient
The dependencies meet at mariadb, which I can not remove because of akonadi.
Is it possible to enforce removal and the akonadi package detects aur/mysql as alternative?
The connector and workbench might just need recompilation
Last edited by Silberling (2015-01-15 19:46:40)

[SOLVED] Cannot start mysqld after switching to MariaDB

Hey guys,
I just switched to MariaDB as recommended.
After installing MariaDB and running
systemctl start mysqld
, I get this error message:
Job for mysqld.service failed.
journal:
systemd[1]: Starting MariaDB database server...
mysqld[9358]: 130326 0:27:17 InnoDB: The InnoDB memory heap is disabled
mysqld[9358]: 130326 0:27:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysqld[9358]: 130326 0:27:17 InnoDB: Compressed tables use zlib 1.2.7
mysqld[9358]: 130326 0:27:17 InnoDB: Initializing buffer pool, size = 128.0M
mysqld[9358]: 130326 0:27:17 InnoDB: Completed initialization of buffer pool
mysqld[9358]: 130326 0:27:17 InnoDB: highest supported file format is Barracuda.
mysqld[9358]: 130326 0:27:17 InnoDB: Waiting for the background threads to start
mysqld[9358]: 130326 0:27:18 Percona XtraDB (http://www.percona.com) 5.5.30-MariaDB-30.1 started; log sequence number 46580545
mysqld[9358]: 130326 0:27:18 [ERROR] mysqld: Got error 'Size of control file is smaller than expected' when trying to use aria control file '/var/lib/mysql/aria_log_control'
mysqld[9358]: 130326 0:27:18 [ERROR] Plugin 'Aria' init function returned error.
mysqld[9358]: 130326 0:27:18 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
mysqld[9358]: 130326 0:27:18 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables
mysqld[9358]: 130326 0:27:18 [ERROR] Aborting
mysqld[9358]: 130326 0:27:18 InnoDB: Starting shutdown...
mysqld[9358]: 130326 0:27:19 InnoDB: Shutdown completed; log sequence number 46580545
mysqld[9358]: 130326 0:27:19 [Note] /usr/bin/mysqld: Shutdown complete
systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
Last edited by lonaowna (2013-03-26 01:23:20)

Hi ! I come here because I have a trouble since the last update of Mysqld :
I cannot start the daemon with
sudo systemctl start mysqld
I have these problems when i look in journalctl -xn :
mars 26 00:22:14 server mysqld[11593]: InnoDB: Error: log file ./ib_logfile0 is of different size 0 3174400 bytes
mars 26 00:22:14 server mysqld[11593]: InnoDB: than specified in the .cnf file 0 5242880 bytes!
mars 26 00:22:14 server mysqld[11593]: 130326 0:22:14 [ERROR] Plugin 'InnoDB' init function returned error.
mars 26 00:22:14 server mysqld[11593]: 130326 0:22:14 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
mars 26 00:22:14 server mysqld[11593]: 130326 0:22:14 [ERROR] Unknown/unsupported storage engine: InnoDB
mars 26 00:22:14 server mysqld[11593]: 130326 0:22:14 [ERROR] Aborting
mars 26 00:22:14 server mysqld[11593]: 130326 0:22:14 [Note] /usr/bin/mysqld: Shutdown complete
mars 26 00:22:14 server systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE
When I try with mysqld, I have
130326 0:23:21 [Warning] Can't create test file /var/lib/mysql/server.lower-test
130326 0:23:21 [Warning] Can't create test file /var/lib/mysql/server.lower-test
mysqld: Can't change dir to '/var/lib/mysql/' (Errcode: 13)
130326 0:23:21 [ERROR] Aborting
130326 0:23:21 [Note] mysqld: Shutdown complete
And when I look in /var/lib/mysql/server.err I have these lines
130207 23:32:56 mysqld_safe mysqld from pid file /var/lib/mysql/server.pid ended
130322 00:25:27 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130322 0:25:27 InnoDB: The InnoDB memory heap is disabled
130322 0:25:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130322 0:25:27 InnoDB: Compressed tables use zlib 1.2.7
130322 0:25:27 InnoDB: Initializing buffer pool, size = 128.0M
130322 0:25:27 InnoDB: Completed initialization of buffer pool
130322 0:25:27 InnoDB: highest supported file format is Barracuda.
InnoDB: Error: tried to read 65536 bytes at offset 0 3173376.
InnoDB: Was only able to read 1024.
InnoDB: Fatal error: cannot read from file. OS error number 17.
130322 0:25:30 InnoDB: Assertion failure in thread 139785666135872 in file os0file.c line 2538
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
23:25:30 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 134074 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/bin/mysqld(my_print_stacktrace+0x29)[0x78ae99]
/usr/bin/mysqld(handle_fatal_signal+0x471)[0x67ad71]
/usr/lib/libpthread.so.0(+0xf1e0)[0x7f226299a1e0]
/usr/lib/libc.so.6(gsignal+0x35)[0x7f22615612c5]
/usr/lib/libc.so.6(abort+0x148)[0x7f2261562748]
/usr/bin/mysqld[0x8f2ac0]
/usr/bin/mysqld[0x8af1a0]
/usr/bin/mysqld[0x8e187c]
/usr/bin/mysqld[0x8e75ef]
/usr/bin/mysqld[0x834204]
/usr/bin/mysqld[0x7fe61f]
/usr/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x67ccf1]
/usr/bin/mysqld[0x59ad94]
/usr/bin/mysqld(_Z11plugin_initPiPPci+0xa42)[0x59f342]
/usr/bin/mysqld[0x524328]
/usr/bin/mysqld(_Z11mysqld_mainiPPc+0x447)[0x529187]
/usr/lib/libc.so.6(__libc_start_main+0xf5)[0x7f226154da15]
/usr/bin/mysqld[0x51ff89]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
130322 00:25:30 mysqld_safe mysqld from pid file /var/lib/mysql/server.pid ended
130326 00:24:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130326 0:24:58 InnoDB: The InnoDB memory heap is disabled
130326 0:24:58 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130326 0:24:58 InnoDB: Compressed tables use zlib 1.2.7
130326 0:24:58 InnoDB: Initializing buffer pool, size = 128.0M
130326 0:24:58 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 3174400 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
130326 0:24:58 [ERROR] Plugin 'InnoDB' init function returned error.
130326 0:24:58 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130326 0:24:58 [ERROR] Unknown/unsupported storage engine: InnoDB
130326 0:24:58 [ERROR] Aborting
130326 0:24:58 [Note] /usr/bin/mysqld: Shutdown complete
130326 00:24:58 mysqld_safe mysqld from pid file /var/lib/mysql/server.pid ended
130326 00:25:33 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/
130326 0:25:33 InnoDB: The InnoDB memory heap is disabled
130326 0:25:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130326 0:25:33 InnoDB: Compressed tables use zlib 1.2.7
130326 0:25:33 InnoDB: Initializing buffer pool, size = 128.0M
130326 0:25:33 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 3174400 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
130326 0:25:33 [ERROR] Plugin 'InnoDB' init function returned error.
130326 0:25:33 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130326 0:25:33 [ERROR] Unknown/unsupported storage engine: InnoDB
130326 0:25:33 [ERROR] Aborting
130326 0:25:33 [Note] /usr/bin/mysqld: Shutdown complete
130326 00:25:33 mysqld_safe mysqld from pid file /var/lib/mysql//server.pid ended
When I try mysqld_safe, here is what I get
130326 00:24:58 mysqld_safe Logging to '/var/lib/mysql/server.err'.
130326 00:24:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130326 00:24:58 mysqld_safe mysqld from pid file /var/lib/mysql/server.pid ended
Resolution
===== It's a good thing to make a post :
It allows me to order my ideas and I find the solution here http://serverfault.com/questions/104014 … erent-size
I juste deleted the files /var/lib/mysqld/ib_logfile0 and /var/lib/mysql/ib_logfile1
First, I had a problem about the file who is in the future (WTF ?:p) But after, it worked !
Thanks Anyway !
Last edited by shox (2013-03-25 23:51:43)

How to append linux shell command output to MariaDB?

That link gave me an idea, I can create an .sql template file with the "insert" query, dump the shell command output to a text file (>), then use "grep" and "sed" to append the desired parts of the command's output file to that .sql file and then execute the .sql file. What do you think?

I haven't done this myself, but it is probably something along the lines of the answer provided in this link:
http://stackoverflow.com/questions/3900496/using-shell-script-to-insert-data-into-remote-mysql-datab...

MariaDB 10.0.0.8 RC

Similar Messages

Maybe you are looking for