"ClusterControl is only compatible with x86_64 systems"
root@mariadb-cluster-1:~# uname -a
Linux mariadb-cluster-1 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u1 x86_64 GNU/Linux
root@mariadb-cluster-1:~# ./install-cc
ClusterControl is only compatible with x86_64 systems
root@mariadb-cluster-1:~# uname -i
unknown
-
Apparently the Debian developers know that uname -i outputs unknown and simply don't care.
I commented that section out as I know my platforms are 64 bit.[ ok ] Stopping MySQL database server: mysqld.
[....] Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . [FAIL. . . failed!
=> Failed to start the MySQL Server. Bye...151025 22:30:46 InnoDB: 5.5.46 started; log sequence number 1595675
ERROR: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ALTER TABLE user ADD column Show_view_priv enum('N','Y') C$
151025 22:30:46 [ERROR] Aborting151025 22:30:46 InnoDB: Starting shutdown...
151025 22:30:47 InnoDB: Shutdown completed; log sequence number 1595675
151025 22:30:47 [Note] /usr/sbin/mysqld: Shutdown complete -
Hi
We've changed uname to use -m instead in the script. That should fix the "unknown" check.
The error
...
ERROR: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ALTER TABLE user ADD column Show_view_priv enum('N','Y') C$
...
Seems to be similar to this bug report, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708176
Are you able to update your debian 7 to the latest?
I couldn't re-produce it on
$ uname -a
Linux n2 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u5 x86_64 GNU/Linux
And can you try to uninstall and then re-install everything again
# purge the packages first
$ apt-get purge apache2 mysql-server mysql-server-5.5 mysql-server-core-5.5$ apt-get purge clustercontrol clustercontrol-cmonapi clustercontrol-controller
Thanks,Alex
-
I went a different direction. I was going via: http://www.severalnines.com/getting-started. I had purged everything I could find in the install script, but it still messed up. My debian is the latest as of today. I went a different direction that had me at a web site filling out information and then it downloaded a tar.gz for me instead of a script. That has been going much better. I'm not out of the woods yet.
-
I have hit a few bumps along the way, but I've been able to overcome them so far. I haven't had the opportunity to look into the last bump yet.
10.0.254.22: Executing 'MYSQLD_STARTUP_TIMEOUT=180 nohup /etc/init.d/mysql restart > /tmp/mysql.out 2> /tmp/mysql.err < /dev/null ' [failed]
Not asking for help on it yet as I haven't even looked at the log file, just giving you an update as to where I'm at. -
WSREP_SST: [INFO] Evaluating socat -u TCP-LISTEN:4444,reuseaddr stdio | xbstream -x; RC=( ${PIPESTATUS[@]} ) (20151027 08:11:44.476)
151027 8:11:44 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') turning message relay requesting off
151027 8:16:44 [Note] WSREP: 0.0 (10.1.8.48): State transfer to 2.0 (10.0.254.22) complete.
151027 8:16:44 [Note] WSREP: Member 0.0 (10.1.8.48) synced with group.
WSREP_SST: [INFO] Preparing the backup at /var/lib/mysql/ (20151027 08:16:46.579)
WSREP_SST: [INFO] Evaluating innobackupex --no-version-check --apply-log $rebuildcmd ${DATA} &>${DATA}/innobackup.prepare.log (20151027 08:16:46.589)
WSREP_SST: [INFO] Total time on joiner: 0 seconds (20151027 08:17:16.151)
WSREP_SST: [INFO] Removing the sst_in_progress file (20151027 08:17:16.163)
151027 8:17:16 [Note] WSREP: SST complete, seqno: 1
151027 8:17:16 [Note] InnoDB: Using mutexes to ref count buffer pool pages
151027 8:17:16 [Note] InnoDB: The InnoDB memory heap is disabled
151027 8:17:16 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
151027 8:17:16 [Note] InnoDB: Memory barrier is not used
151027 8:17:16 [Note] InnoDB: Compressed tables use zlib 1.2.8
151027 8:17:16 [Note] InnoDB: Using Linux native AIO
151027 8:17:16 [Note] InnoDB: Not using CPU crc32 instructions
151027 8:17:16 [Note] InnoDB: Initializing buffer pool, size = 2.6G
151027 8:17:16 [Note] InnoDB: Completed initialization of buffer pool
151027 8:17:16 [Note] InnoDB: Highest supported file format is Barracuda.
151027 8:17:17 [Note] InnoDB: 128 rollback segment(s) are active.
151027 8:17:17 [Note] InnoDB: Waiting for purge to start
151027 8:17:17 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.25-73.1 started; log sequence number 1617430
151027 8:17:17 [Note] Plugin 'FEEDBACK' is disabled.
151027 8:17:17 [Note] Server socket created on IP: '::'.
151027 8:17:17 [Warning] 'user' entry 'root@mariadb-cluster-1' ignored in --skip-name-resolve mode.
151027 8:17:17 [Warning] 'proxies_priv' entry '@% root@mariadb-cluster-1' ignored in --skip-name-resolve mode.
151027 8:17:17 [Note] Event Scheduler: Loaded 0 events
151027 8:17:17 [Note] WSREP: Signalling provider to continue.
151027 8:17:17 [Note] WSREP: SST received: 26716605-7ca3-11e5-a1eb-1b14cc849b3c:1
151027 8:17:17 [Note] Reading of all Master_info entries succeded
151027 8:17:17 [Note] Added new Master_info '' to hash table
151027 8:17:17 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.21-MariaDB-1~jessie-wsrep' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution, wsrep_25.10.r4144151027 8:17:17 [Note] WSREP: 2.0 (10.0.254.22): State transfer from 0.0 (10.1.8.48) complete.
151027 8:17:17 [Note] WSREP: Shifting JOINER -> JOINED (TO: 1)
151027 8:17:17 [Note] WSREP: Member 2.0 (10.0.254.22) synced with group.
151027 8:17:17 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 1)
151027 8:17:17 [Note] WSREP: Synchronized with group, ready for connections
151027 8:17:17 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
151027 11:31:40 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 11:31:40 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') turning message relay requesting on, nonlive peers: tcp://10.1.8.47:4567 tcp://10.1.8.48:4567
151027 11:31:41 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') reconnecting to 722a9b82 (tcp://10.1.8.47:4567), attempt 0
151027 11:31:41 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') reconnecting to 2670855d (tcp://10.1.8.48:4567), attempt 0
151027 11:31:41 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 11:31:41 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 11:31:41 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 11:31:41 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 11:31:41 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 11:31:41 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 11:31:41 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 11:31:41 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 11:31:44 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') turning message relay requesting off
151027 20:26:48 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 20:26:48 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') turning message relay requesting on, nonlive peers: tcp://10.1.8.47:4567 tcp://10.1.8.48:4567
151027 20:26:49 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') reconnecting to 722a9b82 (tcp://10.1.8.47:4567), attempt 0
151027 20:26:49 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') reconnecting to 2670855d (tcp://10.1.8.48:4567), attempt 0
151027 20:26:52 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 20:26:52 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 20:26:53 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 20:26:54 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 20:26:56 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 20:26:57 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 20:26:59 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 20:26:59 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 20:26:59 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 20:26:59 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 20:27:03 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') turning message relay requesting off
151027 21:33:39 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:39 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') turning message relay requesting on, nonlive peers: tcp://10.1.8.47:4567 tcp://10.1.8.48:4567
151027 21:33:40 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') reconnecting to 722a9b82 (tcp://10.1.8.47:4567), attempt 0
151027 21:33:40 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') reconnecting to 2670855d (tcp://10.1.8.48:4567), attempt 0
151027 21:33:52 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:55 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:56 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:57 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:57 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:57 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:57 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:57 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:57 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:57 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:57 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:58 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:58 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') address 'tcp://10.0.254.22:4567' pointing to uuid e1b535e1 is blacklisted, skipping
151027 21:33:59 [Note] WSREP: (e1b535e1, 'tcp://0.0.0.0:4567') reconnecting to 722a9b82 (tcp://10.1.8.47:4567), attempt 0 -
Hi
Looks like you might have network issues or need to increase some timeout settings. .22 stops seeing keep alive pings from the other nodes. "blacklisted" here means .22 will not attempt to connect to itself.
Are your nodes deployed across a WAN? Then you should play with these settings, http://galeracluster.com/documentation-webpages/configurationtips.html
===When running the cluster over WAN, you may frequently experience transient network connectivity failures. To prevent this from partitioning the cluster, you may want to increase the keepalive timeouts.
The following parameters can tolerate 30 second connectivity outages.
wsrep_provider_options = "evs.keepalive_period = PT3S; evs.suspect_timeout = PT30S; evs.inactive_timeout = PT1M; evs.install_timeout = PT1M"Add these changes to the my.cnf file and restart your nodes.
-
Can you let me know where I originally found that configuration web page?
Also, I assume my setup is not complete due to it failing. How can I modify the initial setup to be more tolerant?
In conducting pings across the network during the setup, nothing is dropped and nothing is excessive, yet it still fails. -
Hi
If the deployment script ran to completion without any errors then you should have a database cluster setup properly for a LAN env as default.
Do you have something that pings/scans your ports on the node(s) perhaps? What are the issues that you experience exactly?
Galera ports: http://galeracluster.com/documentation-webpages/firewallsettings.html
Try this link, http://www.severalnines.com/New-Galera-Configurator/index.html to create a new DB configuration package (http://www.severalnines.com/clusterconfigurator).
There is WAN on/off switch there which you can enable that will increase these timeouts mentioned previously for the generated db package.
If you deploy for a WAN env then set also the "gmcast.segment" value to be identical for the nodes that are in the same datacenter. For example set gmcast.segment=1 for nodes in DC1 and gmcast.segment=2 for nodes in DC2.
Best Regards,
Alex
-
The issue I'm experiencing is an aborted install.
10.0.254.22: Executing ' /usr/sbin/mysqld --bootstrap --user=mysql --skip-grant-tables --default-storage-engine=myisam < /tmp/s9s_init.sql' [ok]
10.0.254.22: Executing 'rm /tmp/s9s_init.sql' [ok]
10.0.254.22: Executing 'sed -i.bak 's#password =.*#password = s9sdebianmaint2014#g' /etc/mysql/debian.cnf' [ok]
10.0.254.22: Executing 'MYSQLD_STARTUP_TIMEOUT=180 nohup /etc/init.d/mysql restart > /tmp/mysql.out 2> /tmp/mysql.err < /dev/null ' [failed]
root@clustercontrol:~/s9s-galera-mariadb-3.5.0/mysql/scripts/install#
From my own research, it aborts during after line 115 of bootstrap.sh on the final host.
Please sign in to leave a comment.
Comments
14 comments