Ask Your Question

rcgelber's profile - activity

2018-06-29 11:01:30 -0500 received badge  Famous Question (source)
2017-11-13 15:02:28 -0500 received badge  Popular Question (source)
2017-11-13 15:02:28 -0500 received badge  Notable Question (source)
2017-07-16 19:02:33 -0500 asked a question Cannot cluster MySQL Database when try to make my stack highly available

So I'm trying to make my openstack configuration at our data center highly available. When I follow the openstack HA guide I get stuck on making the stack on service mysql start --wsrep-new-cluster and i get the following error.

Any Ideas on how to solve this???

Error:

journalctl -xe

Jul 16 16:51:08 rno-a1-r2-u41 mysqld[31763]: 170716 16:51:08 [Note] InnoDB: Starting shutdown... Jul 16 16:51:09 rno-a1-r2-u41 mysqld[31763]: 170716 16:51:09 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool Jul 16 16:51:10 rno-a1-r2-u41 mysqld[31763]: 170716 16:51:10 [Note] InnoDB: Shutdown completed; log sequence number 1616787 Jul 16 16:51:10 rno-a1-r2-u41 mysqld[31763]: 170716 16:51:10 [Note] /usr/sbin/mysqld: Shutdown complete Jul 16 16:51:10 rno-a1-r2-u41 mysqld[31763]: Jul 16 16:51:10 rno-a1-r2-u41 mysqld_safe[31815]: mysqld from pid file /var/run/mysqld/mysqld.pid ended Jul 16 16:51:38 rno-a1-r2-u41 /etc/init.d/mysql[32073]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in Jul 16 16:51:38 rno-a1-r2-u41 /etc/init.d/mysql[32073]: [61B blob data] Jul 16 16:51:38 rno-a1-r2-u41 /etc/init.d/mysql[32073]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")' Jul 16 16:51:38 rno-a1-r2-u41 /etc/init.d/mysql[32073]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists! Jul 16 16:51:38 rno-a1-r2-u41 mysql[31539]: ...fail! Jul 16 16:51:38 rno-a1-r2-u41 /etc/init.d/mysql[32073]: Jul 16 16:51:38 rno-a1-r2-u41 systemd[1]: mysql.service: Control process exited, code=exited status=1 Jul 16 16:51:38 rno-a1-r2-u41 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon. Jul 16 16:51:38 rno-a1-r2-u41 systemd[1]: mysql.service: Unit entered failed state. Jul 16 16:51:38 rno-a1-r2-u41 systemd[1]: mysql.service: Failed with result 'exit-code'.

Config: /etc/mysql/conf.d/galera.cnf

[mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock user=mysql binlog_format=ROW bind-address=10.11.2.3

InnoDB Configuration default_storage_engine=innodb innodb_autoinc_lock_mode=2 innodb_flush_log_at_trx_commit=0 innodb_buffer_pool_size=122M

Galera Cluster Configuration wsrep_provider=/usr/lib/libgalera_smm.so wsrep_provider_options='pc.recovery=TRUE;gcache.size=300M' wsrep_cluster_name='rno-sql' wsrep_cluster_address='gcomm://192.168.10.1,192.168.10.2' wsrep_sst_method=rsync

Galera Node Configuration wsrep_node_address=192.168.1.1 wsrep_node_name=rno-a1-r2-u41

Hosts

localhost 127.0.0.1 localhost rno-a1-r2-u41

Openstack Host File 10.11.2.2 controller 10.11.2.3 controller-u41 10.11.2.4 controller-u38 10.11.2.5 compute-u36 10.11.2.6 compute-u34 10.11.2.7 compute-u32 10.11.2.8 compute-u30 10.11.2.9 compute-u19 10.11.2.10 compute-u17 10.11.2.11 compute-u15 10.11.2.12 compute-u13 10.11.2.13 compute-u11

2017-07-12 11:59:24 -0500 received badge  Teacher (source)
2017-07-09 13:28:34 -0500 received badge  Editor (source)
2017-07-09 12:05:54 -0500 answered a question Unable to log into Horizon in Ocata. Previous solution doesn't work

Is that dashboard on the same node as the controller? If so make sure change this and make sure memcached is binding to the management interface (aka the private side of the network) of the controller.

Local_Setting.py

    'LOCATION': '127.0.0.1:11211', <<<<<------------- To  'controller:11211'

Also, move into apache /etc/apache2/apache2.conf and make sure the the following looks like this.

Directory /

    Options FollowSymLinks
    AllowOverride all
    Require all granted

</directory>

Directory /usr/share

    AllowOverride all
    Require all granted

</directory>

Directory /var/www/

    Options Indexes FollowSymLinks
    AllowOverride None
    Require all granted

</directory>

2017-07-02 22:42:47 -0500 answered a question Dashboard cannot access identity tab

After several hours of troubleshooting I found the simple solution to this issue. The solution is to edit /etc/openstack-dashboard/local_settings.py and uncomment LOGIN_REDIRECT_URL = WEBROOT. I hope this will help anyone having the same issue.