On 16/10/16 09:26, Alex Evonosky wrote:
> Hello team-
>
> Quick question-
>
> I recently just installed mariaDB 10.1.18 (via apt-get) and all went
> well, no issues.. Here is my galera.cnf file:
>
> cat galera.cnf
> [mysqld]
> binlog_format = ROW
> default_storage_engine = InnoDB
> innodb_autoinc_lock_mode = 2
> innodb_locks_unsafe_for_binlog = 1
>
> wsrep_on = ON
> wsrep_causal_reads = ON
> wsrep_cluster_address = gcomm://10.10.10.104
> <http://10.10.10.104>,10.10.13.2
> wsrep_cluster_name = soho_cluster
> wsrep_node_address = 10.10.10.104
> wsrep_provider = /usr/lib/galera/libgalera_smm.so show *GLOBAL* status like 'wsrep_%'
> wsrep_provider_options = "gcache.size=512M"
> wsrep_slave_threads = 4 # Should be equal to the number of
> cpu-cores.
> wsrep_sst_auth = "sstuser:r3pl1c@t3"
> #wsrep_sst_method = xtrabackup-v2
> wsrep_sst_method = rsync
>
>
>
> I started the server as: galera_new_cluster and see no errors. Syslog
> reports mariaDB has started. However, I never see any messages with WSREP.
>
>
>
> the database stat shows:
>
> mysql -u root -p -e "show status like 'wsrep%'"
> Enter password:
> +--------------------------+----------------------+ What is in the error log?
> | Variable_name | Value |
> +--------------------------+----------------------+
> | wsrep_cluster_conf_id | 18446744073709551615 |
> | wsrep_cluster_size | 0 |
> | wsrep_cluster_state_uuid | |
> | wsrep_cluster_status | Disconnected |
> | wsrep_connected | OFF |
> | wsrep_local_bf_aborts | 0 |
> | wsrep_local_index | 4294967295 |
> | wsrep_provider_name | |
> | wsrep_provider_vendor | |
> | wsrep_provider_version | |
> | wsrep_ready | OFF |
> | wsrep_thread_count | 0 |
> +--------------------------+----------------------+
>
>
> The wsrep always shows OFF. I have removed and purged any and all
> mysql, mysql-server etc three times and get the same result. Is there
> something I am missing?
Have you started one node with galera_new_cluster? (ref:
https://github.com/linux-on-ibm-power/mysql-server )
note: replies on list only.