MariaDB 10.1 stable GA released

D

ditto

Verified User
Joined
Apr 27, 2009
Messages
2,354
MariaDB 10.1 stable GA is now released, and the new version 10.1.8 is already available in custombuild. Please note that it is not tested so much yet, so be careful if upgrading production servers. To upgrade you can use mariadb=10.1 in options.conf - if you test it, please post reply if there is any problems.

Here is the official blog post: MariaDB 10.1 is stable GA: https://blog.mariadb.org/mariadb-10-1-is-stable-ga/

Here is the release notes: https://mariadb.com/kb/en/mariadb/mariadb-1018-release-notes/
 
Last edited:
I just updated from MariaDB 10.0 to 10.1 and everything went smooth. :cool:
 
Last edited:
That didn't go well here on my server:
Code: 
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.1.8-centos6-x86_64-client.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.1.8-centos6-x86_64-devel.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.1.8-centos6-x86_64-server.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.1.8-centos6-x86_64-shared.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.1.8-centos6-x86_64-common.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.1.8-centos6-x86_64-compat.rpm
Stopping mysqld ...
Shutting down MySQL.............................. SUCCESS! 
Upgrading MariaDB 10.0.21 to 10.1.8
warning: /etc/my.cnf saved as /etc/my.cnf.rpmsave
warning: MariaDB-10.1.8-centos6-x86_64-client.rpm: Header V4 DSA/SHA1 Signature, key ID 1bb943db: NOKEY
Preparing...                ########################################### [100%]
   1:MariaDB-compat         ########################################### [ 17%]
   2:MariaDB-common         ########################################### [ 33%]
   3:MariaDB-client         ########################################### [ 50%]
   4:MariaDB-server         ########################################### [ 67%]
   5:MariaDB-devel          ########################################### [ 83%]
   6:MariaDB-shared         ########################################### [100%]
Starting MySQL. ERROR! 
Giving mysqld a few seconds to start up...
Version check failed. Got the following error when calling the 'mysql' command line client
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2 "No such file or directory")
FATAL ERROR: Upgrade failed
/usr/bin/mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2 "No such file or directory") when trying to connect
cp: `/usr/lib/libmysqlclient.so' and `/usr/lib/mysql/libmysqlclient.so' are the same file
Restarting MySQL.
 ERROR! MySQL server PID file could not be found!
Starting MySQL. ERROR! 
 ERROR! Failed to restart server.

When manually trying to start married the following error shows up:
mysqld: error while loading shared libraries: libjemalloc.so.1: cannot open shared object file: No such file or directory

Could it be that since 'Jemalloc' is no longer bundled with MariaDB 10.1 that the upgrade fails? can it be installed with yum to solve the issue?
 
Last edited:
smtalk said:
Try:
Code: 
yum -y install jemalloc
Click to expand...

Code: 
> yum -y install jemalloc
Loaded plugins: fastestmirror, security
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: mirrors.prometeus.net
 * extras: mirrors.prometeus.net
 * updates: mirrors.prometeus.net
No package jemalloc available.
Error: Nothing to do

how to
Code: 
rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
warning: /var/tmp/rpm-tmp.7y2ZC2: Header V3 RSA/SHA256 Signature, key ID 0608b895: NOKEY
Retrieving http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
Preparing...                ##################################################
epel-release                ##################################################
> yum -y install jemalloc
Loaded plugins: fastestmirror, security
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: mirrors.prometeus.net
 * epel: ftp.uni-bayreuth.de
 * extras: mirrors.prometeus.net
 * updates: mirrors.prometeus.net
Resolving Dependencies
--> Running transaction check
---> Package jemalloc.i686 0:3.6.0-1.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package            Arch           Version                 Repository      Size
================================================================================
Installing:
 jemalloc           i686           3.6.0-1.el6             epel            97 k

Transaction Summary
================================================================================
Install       1 Package(s)

Total download size: 97 k
Installed size: 307 k
Downloading Packages:
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 0608b895: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6
Importing GPG key 0x0608B895:
 Userid : EPEL (6) <[email protected]>
 Package: epel-release-6-8.noarch (installed)
 From   : /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.

  Installing : jemalloc-3.6.0-1.el6.i686                                    1/1 

  Verifying  : jemalloc-3.6.0-1.el6.i686                                    1/1 

Installed:
  jemalloc.i686 0:3.6.0-1.el6                                                   

Complete!
 
Last edited:
Just updated to 10.1 on one CentOS 7.1 server. I also needed to install jemalloc because i got the same error as above.
After building MariaDB the second time i got this error:

Code: 
Updating / installing...
   1:MariaDB-common-10.1.8-1.el7.cento################################# [ 17%]
   2:MariaDB-client-10.1.8-1.el7.cento################################# [ 33%]
   3:MariaDB-server-10.1.8-1.el7.cento################################# [ 50%]
   4:MariaDB-devel-10.1.8-1.el7.centos################################# [ 67%]
   5:MariaDB-shared-10.1.8-1.el7.cento################################# [ 83%]
   6:MariaDB-compat-10.1.8-1.el7.cento################################# [100%]
Failed to issue method call: No such file or directory
Giving mysqld a few seconds to start up...
Phase 1/6: Checking and upgrading mysql database
Processing databases

Failed to issue method call

But everything is running fine as i can see and test. No error messages or logs. Does anyone know what this error means and if it need a fix?
 
Be careful when updating:

In my previous post everything was fine. I updated another production server to 10.1.8 and now mysql crashed and won't come up. Some error logs:

Code: 
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: The InnoDB memory heap is disabled
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: Memory barrier is not used
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: Compressed tables use zlib 1.2.7
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: Using Linux native AIO
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: Using CPU crc32 instructions
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: Completed initialization of buffer pool
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: Highest supported file format is Barracuda.
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1891117338
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: Database was not shutdown normally!
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: Starting crash recovery.
Oct 21 14:50:32 vps01 mysqld: 2015-10-21 14:50:32 140053752678528 [Note] InnoDB: Reading tablespace information from the .ibd files...
Oct 21 14:50:33 vps01 mysqld: 2015-10-21 14:50:33 140053752678528 [Note] InnoDB: Restoring possible half-written data pages
Oct 21 14:50:33 vps01 mysqld: 2015-10-21 14:50:33 140053752678528 [Note] InnoDB: from the doublewrite buffer...
Oct 21 14:50:33 vps01 mysqld: InnoDB: Doing recovery: scanned up to log sequence number 1891120787
Oct 21 14:50:33 vps01 mysqld: 2015-10-21 14:50:33 140053752678528 [Note] InnoDB: 128 rollback segment(s) are active.
Oct 21 14:50:33 vps01 mysqld: 2015-10-21 14:50:33 140053752678528 [Note] InnoDB: Waiting for purge to start
Oct 21 14:50:33 vps01 mysqld: 2015-10-21 14:50:33 7f60a53fa700  InnoDB: Assertion failure in thread 140053066000128 in file btr0cur.cc line 5341
Oct 21 14:50:33 vps01 mysqld: InnoDB: Failing assertion: rb_ctx != RB_NONE
Oct 21 14:50:33 vps01 mysqld: InnoDB: We intentionally generate a memory trap.
Oct 21 14:50:33 vps01 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Oct 21 14:50:33 vps01 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
Oct 21 14:50:33 vps01 mysqld: InnoDB: immediately after the mysqld startup, there may be
Oct 21 14:50:33 vps01 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
Oct 21 14:50:33 vps01 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
Oct 21 14:50:33 vps01 mysqld: InnoDB: about forcing recovery.
Oct 21 14:50:33 vps01 mysqld: 151021 14:50:33 [ERROR] mysqld got signal 6 ;
Oct 21 14:50:33 vps01 mysqld: This could be because you hit a bug. It is also possible that this binary
Oct 21 14:50:33 vps01 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Oct 21 14:50:33 vps01 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Oct 21 14:50:33 vps01 mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs
Oct 21 14:50:33 vps01 mysqld: We will try our best to scrape up some info that will hopefully help
Oct 21 14:50:33 vps01 mysqld: diagnose the problem, but since we have already crashed,
Oct 21 14:50:33 vps01 mysqld: something is definitely wrong and this may fail.
Oct 21 14:50:33 vps01 mysqld: Server version: 10.1.8-MariaDB
Oct 21 14:50:33 vps01 mysqld: key_buffer_size=134217728
Oct 21 14:50:33 vps01 mysqld: read_buffer_size=131072
Oct 21 14:50:33 vps01 mysqld: max_used_connections=0
Oct 21 14:50:33 vps01 mysqld: max_threads=153
Oct 21 14:50:33 vps01 mysqld: thread_count=0
Oct 21 14:50:33 vps01 mysqld: It is possible that mysqld could use up to
Oct 21 14:50:33 vps01 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467104 K  bytes of memory
Oct 21 14:50:33 vps01 mysqld: Hope that's ok; if not, decrease some variables in the equation.
Oct 21 14:50:33 vps01 mysqld: Thread pointer: 0x0x0
Oct 21 14:50:33 vps01 mysqld: Attempting backtrace. You can use the following information to find out
Oct 21 14:50:33 vps01 mysqld: where mysqld died. If you see no messages after this, something went
Oct 21 14:50:33 vps01 mysqld: terribly wrong...
Oct 21 14:50:33 vps01 mysqld: stack_bottom = 0x0 thread_stack 0x48000
Oct 21 14:50:33 vps01 mysqld: 2015-10-21 14:50:33 140053752678528 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1891120787
Oct 21 14:50:33 vps01 mysqld: mysys/stacktrace.c:247(my_print_stacktrace)[0x7f60ced688be]
Oct 21 14:50:33 vps01 mysqld: sql/signal_handler.cc:160(handle_fatal_signal)[0x7f60ce898d0d]
Oct 21 14:50:33 vps01 mysqld: /lib64/libpthread.so.0(+0xf130)[0x7f60cdec1130]
Oct 21 14:50:33 vps01 mysqld: /lib64/libc.so.6(gsignal+0x37)[0x7f60cc0195d7]
Oct 21 14:50:33 vps01 mysqld: /lib64/libc.so.6(abort+0x148)[0x7f60cc01acc8]
Oct 21 14:50:33 vps01 mysqld: btr/btr0cur.cc:5341(btr_free_externally_stored_field(dict_index_t*, unsigned char*, unsigned char const*, unsigned long const*, page_zip_des_t*, unsigned long, trx_rb_ctx, mtr_t*))[0x7f60ceb48a7e]
Oct 21 14:50:33 vps01 mysqld: row/row0purge.cc:712(row_purge_upd_exist_or_extern_func)[0x7f60cead3879]
Oct 21 14:50:33 vps01 mysqld: row/row0purge.cc:869(row_purge_record_func)[0x7f60cead44f8]
Oct 21 14:50:33 vps01 mysqld: que/que0que.cc:1089(que_thr_step)[0x7f60cea9b707]
Oct 21 14:50:33 vps01 mysqld: trx/trx0purge.cc:1254(trx_purge(unsigned long, unsigned long, bool))[0x7f60ceb01d4e]
Oct 21 14:50:33 vps01 mysqld: srv/srv0srv.cc:3432(srv_do_purge)[0x7f60ceaefc9f]
Oct 21 14:50:33 vps01 mysqld: /lib64/libpthread.so.0(+0x7df5)[0x7f60cdeb9df5]
Oct 21 14:50:33 vps01 mysqld: /lib64/libc.so.6(clone+0x6d)[0x7f60cc0da1ad]

Does anybody has an idea how to solve this? Starting mysql within DA gives this error:

Code: 
Cannot find the script in /etc/systemd/system or /usr/lib/systemd/system

Details

/usr/lib/systemd/system/mysqld.service

Reverting back to latest 10.x also doesn't work.
 
Last edited:
Couldn't there be a dependencies check in custom build that checks if jemalloc is installed?

And after installing jemalloc, upgrade fails with this error:
Code: 
Stopping mysqld ...
 ERROR! MySQL server PID file could not be found!
Updating MariaDB 10.1.8 to 10.1.8
warning: MariaDB-10.1.8-centos6-x86_64-client.rpm: Header V4 DSA/SHA1 Signature, key ID 1bb943db: NOKEY
Preparing...                ########################################### [100%]
   1:MariaDB-compat         ########################################### [ 17%]
   2:MariaDB-common         ########################################### [ 33%]
   3:MariaDB-client         ########################################### [ 50%]
   4:MariaDB-server         ########################################### [ 67%]
   5:MariaDB-devel          ########################################### [ 83%]
   6:MariaDB-shared         ########################################### [100%]
Starting MySQL................. SUCCESS! 
Giving mysqld a few seconds to start up...
Version check failed. Got the following error when calling the 'mysql' command line client
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111 "Connection refused")
FATAL ERROR: Upgrade failed
/usr/bin/mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111 "Connection refused") when trying to connect
cp: `/usr/lib/libmysqlclient.so' and `/usr/lib/mysql/libmysqlclient.so' are the same file
Restarting MySQL.
 ERROR! MySQL server PID file could not be found!
Starting MySQL............. SUCCESS!
 
What does your error log say?

// I really don't recommend upgrading right now:p Messed up my whole day schedule. I am now re-installing and using backups from a couple hours earlier. Quicker then sorting out this error because i can't find a solution. The errors i am getting are from a InnoDB crash.
 
Last edited:
Finally i know what the error message is but still don't know how to resolve :s
Code: 
2015-10-21 17:26:34 140712553408544 [Note] InnoDB: Waiting for purge to start
InnoDB: Error: trying to access update undo rec field 58 in index "cache_key" of table "core_cache"
InnoDB: but index has only 5 fields
InnoDB: Submit a detailed bug report to http://bugs.mysql.com
InnoDB: Run also CHECK TABLE "core_cache"
InnoDB: n_fields = 2, i = 1, ptr 0x7ffa09026a63
151021 17:26:34 [ERROR] mysqld got signal 11 ;
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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 10.1.8-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467104 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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 = 0x0 thread_stack 0x48000
2015-10-21 17:26:34 140712553408544 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 242933384519
mysys/stacktrace.c:247(my_print_stacktrace)[0x7ffa326936cb]
sql/signal_handler.cc:160(handle_fatal_signal)[0x7ffa321f50d5]
/lib64/libpthread.so.0(+0xf790)[0x7ffa3180e790]
include/mach0data.ic:172(mach_read_from_2)[0x7ffa324454b9]
row/row0purge.cc:850(row_purge_record_func)[0x7ffa324145d5]
que/que0que.cc:1089(que_thr_step)[0x7ffa323da84f]
trx/trx0purge.cc:1254(trx_purge(unsigned long, unsigned long, bool))[0x7ffa324421e1]
srv/srv0srv.cc:3432(srv_do_purge)[0x7ffa3242fdc5]
/lib64/libpthread.so.0(+0x7a51)[0x7ffa31806a51]
/lib64/libc.so.6(clone+0x6d)[0x7ffa2fcec93d]
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.
151021 17:26:34 mysqld_safe mysqld from pid file /var/lib/mysql/server.domain.com.pid ended

Bug reports that are similar:
https://mariadb.atlassian.net/browse/MDEV-8163
https://mariadb.atlassian.net/browse/MDEV-8992
 
Last edited:
Seems that jemalloc is only part of FreeBSD 10+. So if you run an earlier version you have to upgrade. MariaDB 10.0 runs well but 10.1 won't build without the jemalloc.

Working on my upgrade right now. Will update this once it's working.

EDIT: Still didn't work. Found this:
https://mariadb.atlassian.net/browse/MDEV-8973

Building this include/mysql/service_encryption.h fails because it requires alloca.h and with FreeBSD it's included in stdlib.h.
 
Last edited:
I just updated from MariaDB 10.1.8 to MariaDB 10.1.9 on CentOS 7 but it failed

It, still seems to run. :confused:

Code: 
Downloading		mysql/jemalloc-3.6.0-1.el7.x86_64.rpm...
--2015-11-25 04:31:05--  http://files6.directadmin.com/services/custombuild/all/mariadb/jemalloc/3.6.0/jemalloc-3.6.0-1.el7.x86_64.rpm
Resolving files6.directadmin.com (files6.directadmin.com)... 62.148.181.110, 2001:16e8:1:4:62:148:181:110
Connecting to files6.directadmin.com (files6.directadmin.com)|62.148.181.110|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 106112 (104K) [application/x-rpm]
Saving to: '/usr/local/directadmin/custombuild/mysql/jemalloc-3.6.0-1.el7.x86_64.rpm'

100%[======================================>] 106,112     --.-K/s   in 0.02s   

2015-11-25 04:31:05 (5.44 MB/s) - '/usr/local/directadmin/custombuild/mysql/jemalloc-3.6.0-1.el7.x86_64.rpm' saved [106112/106112]

Downloading		mysql/jemalloc-devel-3.6.0-1.el7.x86_64.rpm...
--2015-11-25 04:31:05--  http://files6.directadmin.com/services/custombuild/all/mariadb/jemalloc/3.6.0/jemalloc-devel-3.6.0-1.el7.x86_64.rpm
Resolving files6.directadmin.com (files6.directadmin.com)... 62.148.181.110, 2001:16e8:1:4:62:148:181:110
Connecting to files6.directadmin.com (files6.directadmin.com)|62.148.181.110|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 22876 (22K) [application/x-rpm]
Saving to: '/usr/local/directadmin/custombuild/mysql/jemalloc-devel-3.6.0-1.el7.x86_64.rpm'

100%[======================================>] 22,876      --.-K/s   in 0.004s  

2015-11-25 04:31:05 (5.53 MB/s) - '/usr/local/directadmin/custombuild/mysql/jemalloc-devel-3.6.0-1.el7.x86_64.rpm' saved [22876/22876]

Downloading		mysql/MariaDB-10.1.9-centos7-x86_64-client.rpm...
--2015-11-25 04:31:05--  http://files6.directadmin.com/services/custombuild/all/mariadb/10.1/10.1.9/MariaDB-10.1.9-centos7-x86_64-client.rpm
Resolving files6.directadmin.com (files6.directadmin.com)... 62.148.181.110, 2001:16e8:1:4:62:148:181:110
Connecting to files6.directadmin.com (files6.directadmin.com)|62.148.181.110|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 40421316 (39M) [application/x-rpm]
Saving to: '/usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-client.rpm'

100%[======================================>] 40,421,316  26.3MB/s   in 1.5s   

2015-11-25 04:31:07 (26.3 MB/s) - '/usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-client.rpm' saved [40421316/40421316]

Downloading		mysql/MariaDB-10.1.9-centos7-x86_64-devel.rpm...
--2015-11-25 04:31:07--  http://files6.directadmin.com/services/custombuild/all/mariadb/10.1/10.1.9/MariaDB-10.1.9-centos7-x86_64-devel.rpm
Resolving files6.directadmin.com (files6.directadmin.com)... 62.148.181.110, 2001:16e8:1:4:62:148:181:110
Connecting to files6.directadmin.com (files6.directadmin.com)|62.148.181.110|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6860264 (6.5M) [application/x-rpm]
Saving to: '/usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-devel.rpm'

100%[======================================>] 6,860,264   29.4MB/s   in 0.2s   

2015-11-25 04:31:07 (29.4 MB/s) - '/usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-devel.rpm' saved [6860264/6860264]

Downloading		mysql/MariaDB-10.1.9-centos7-x86_64-server.rpm...
--2015-11-25 04:31:07--  http://files6.directadmin.com/services/custombuild/all/mariadb/10.1/10.1.9/MariaDB-10.1.9-centos7-x86_64-server.rpm
Resolving files6.directadmin.com (files6.directadmin.com)... 62.148.181.110, 2001:16e8:1:4:62:148:181:110
Connecting to files6.directadmin.com (files6.directadmin.com)|62.148.181.110|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 103453884 (99M) [application/x-rpm]
Saving to: '/usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-server.rpm'

100%[======================================>] 103,453,884 26.9MB/s   in 3.6s   

2015-11-25 04:31:11 (27.6 MB/s) - '/usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-server.rpm' saved [103453884/103453884]

Downloading		mysql/MariaDB-10.1.9-centos7-x86_64-shared.rpm...
--2015-11-25 04:31:11--  http://files6.directadmin.com/services/custombuild/all/mariadb/10.1/10.1.9/MariaDB-10.1.9-centos7-x86_64-shared.rpm
Resolving files6.directadmin.com (files6.directadmin.com)... 62.148.181.110, 2001:16e8:1:4:62:148:181:110
Connecting to files6.directadmin.com (files6.directadmin.com)|62.148.181.110|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1311080 (1.2M) [application/x-rpm]
Saving to: '/usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-shared.rpm'

100%[======================================>] 1,311,080   --.-K/s   in 0.09s   

2015-11-25 04:31:11 (13.2 MB/s) - '/usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-shared.rpm' saved [1311080/1311080]

Downloading		mysql/MariaDB-10.1.9-centos7-x86_64-common.rpm...
--2015-11-25 04:31:11--  http://files6.directadmin.com/services/custombuild/all/mariadb/10.1/10.1.9/MariaDB-10.1.9-centos7-x86_64-common.rpm
Resolving files6.directadmin.com (files6.directadmin.com)... 62.148.181.110, 2001:16e8:1:4:62:148:181:110
Connecting to files6.directadmin.com (files6.directadmin.com)|62.148.181.110|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 44152 (43K) [application/x-rpm]
Saving to: '/usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-common.rpm'

100%[======================================>] 44,152      --.-K/s   in 0.009s  

2015-11-25 04:31:11 (4.83 MB/s) - '/usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-common.rpm' saved [44152/44152]

Downloading		mysql/MariaDB-10.1.9-centos7-x86_64-compat.rpm...
--2015-11-25 04:31:11--  http://files6.directadmin.com/services/custombuild/all/mariadb/10.1/10.1.9/MariaDB-10.1.9-centos7-x86_64-compat.rpm
Resolving files6.directadmin.com (files6.directadmin.com)... 62.148.181.110, 2001:16e8:1:4:62:148:181:110
Connecting to files6.directadmin.com (files6.directadmin.com)|62.148.181.110|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1499776 (1.4M) [application/x-rpm]
Saving to: '/usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-compat.rpm'

100%[======================================>] 1,499,776   --.-K/s   in 0.1s    

2015-11-25 04:31:11 (13.3 MB/s) - '/usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-compat.rpm' saved [1499776/1499776]

Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-client.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-devel.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-server.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-shared.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-common.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.1.9-centos7-x86_64-compat.rpm
Installing libjemalloc...
Found /usr/local/directadmin/custombuild/mysql/jemalloc-3.6.0-1.el7.x86_64.rpm
Found /usr/local/directadmin/custombuild/mysql/jemalloc-devel-3.6.0-1.el7.x86_64.rpm
warning: /usr/local/directadmin/custombuild/mysql/jemalloc-3.6.0-1.el7.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 1bb943db: NOKEY
Preparing...                          ################################# [100%]
Updating / installing...
   1:jemalloc-3.6.0-1.el7             ################################# [ 50%]
   2:jemalloc-devel-3.6.0-1.el7       ################################# [100%]
Stopping mysqld ...
Updating MariaDB 10.1.8 to 10.1.9
warning: MariaDB-10.1.9-centos7-x86_64-client.rpm: Header V4 DSA/SHA1 Signature, key ID 1bb943db: NOKEY
Preparing...                          ################################# [100%]
Updating / installing...
   1:MariaDB-common-10.1.9-1.el7.cento################################# [  8%]
   2:MariaDB-client-10.1.9-1.el7.cento################################# [ 17%]
   3:MariaDB-server-10.1.9-1.el7.cento################################# [ 25%]
   4:MariaDB-devel-10.1.9-1.el7.centos################################# [ 33%]
   5:MariaDB-shared-10.1.9-1.el7.cento################################# [ 42%]
   6:MariaDB-compat-10.1.9-1.el7.cento################################# [ 50%]
Cleaning up / removing...
   7:MariaDB-devel-10.1.8-1.el7.centos################################# [ 58%]
   8:MariaDB-server-10.1.8-1.el7.cento################################# [ 67%]
Restarting mysql (via systemctl):  Warning: Unit file of mysql.service changed on disk, 'systemctl daemon-reload' recommended.
                                                           [  OK  ]
   9:MariaDB-client-10.1.8-1.el7.cento################################# [ 75%]
  10:MariaDB-compat-10.1.8-1.el7.cento################################# [ 83%]
  11:MariaDB-shared-10.1.8-1.el7.cento################################# [ 92%]
  12:MariaDB-common-10.1.8-1.el7.cento################################# [100%]
Failed to issue method call: No such file or directory
Giving mysqld a few seconds to start up...
Version check failed. Got the following error when calling the 'mysql' command line client
ERROR 1193 (HY000) at line 1: Unknown system variable 'WSREP_ON'
FATAL ERROR: Upgrade failed
cp: '/usr/lib/libmysqlclient.so' and '/usr/lib/mysql/libmysqlclient.so' are the same file
Restarting MySQL.
 
So its been a long time, is all these problems fixed now? Anybody that have upgraded to MariaDB 10.1.11 without problems?

I have been trying to read all forum post about this, so far I think it is needed to install both nmap and jemalloc before upgrading to MariaDB 10.1.x, is that still correct? Anything else we should install before upgrade?
 
I am now running 10.1.11 without any problems. The upgrade to the first 10.1.8 was a disaster as i described in this topic above.

The upgrade from 10.0 to 10.1.9 went fine (this time i did make a snapshot, i learned from that mistake ;) ). Also the next upgrades (10.1.9 > 10.1.10 - 10.1.10 -> 10.1.11) went without any problems.
 
You must log in or register to reply here.
Back
Top