MariaDB fails to update from 10.0.27 to 10.0.29
Need help, seems when I ran updates on mariadb it tried to update from 10.0.27 to 10.0.29 and mysql hung on shut down.
now it says 10.0.27 is not fully configured. When I try apt-get upgrade it just hangs on shutting DB down..
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Bobby Yakovich
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
What is the output of:
lsb_release -a; uname -a; apt-cache policy `dpkg -l | grep -i maria | awk ('print $2'}`
Thanks
Revision history for this message
|
#2 |
Sorry for delay was away, here is the output you requested.
http://
Revision history for this message
|
#3 |
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty
Linux cwtrdb001 3.13.0-107-generic #154-Ubuntu SMP Tue Dec 20 09:57:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
-bash: command substitution: line 1: syntax error near unexpected token `'print $2'}'
-bash: command substitution: line 1: `dpkg -l | grep -i maria | awk ('print $2'}'
Package files:
100 /var/lib/
release a=now
500 http://
release o=MariaDB,
origin ftp.osuosl.org
500 http://
release o=MariaDB,
origin ftp.osuosl.org
500 http://
release o=MariaDB,
origin mirrors.
500 http://
release o=MariaDB,
origin mirrors.
500 http://
500 http://
500 http://
500 http://
500 http://
release v=14.04,
origin security.ubuntu.com
500 http://
release v=14.04,
origin security.ubuntu.com
500 http://
release v=14.04,
origin security.ubuntu.com
500 http://
release v=14.04,
origin security.ubuntu.com
500 http://
release v=14.04,
origin security.ubuntu.com
500 http://
release v=14.04,
origin security.ubuntu.com
500 http://
release v=14.04,
origin security.ubuntu.com
500 http://
release v=14.04,
origin security.ubuntu.com
500 http://
500 http://
500 http://
500 http://
100 http://
release v=14.04,
origin us.archive.
100 http://
release v=14.04,
origin us.archive.
100 http://
release v=14.04,
origin us.archive.
100 http://
release v=14.04,
origin us.archive.
100 http://
release v=14.04,
origin us.archive.
100 http://
release v=14.04,
origin us.archive.
100 http://
release v=14.04,
origin us.archive.
100 http://
release v=14.04,
origin us.archive.
500 http://
500 http://
500 http://
500 http://
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
500 http://
500 http://
500 http://
500 http://
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
500 http://
release v=14.04,
origin us.archive.
Pinned packages:
Revision history for this message
|
#4 |
That is the output, are you asking a question?
Side note, I was able to clean up the install and reinstall mariaDB and got this node working.
The issue I am seeing now is that the second node is showing wsrep_local_
Should show wsrep_local_
Any idea why? Seems the cluster is not synced.
Revision history for this message
|
#5 |
When in a state of Joined indicates that node lost connection to cluster. Takes very long time to re-sync