[jira] [Commented] (CLOUDSTACK-9209) Database HA not working on a fresh install on Ubuntu 12.04

[Tom Wood (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353641#comment-15353641
 ] 

Tom Wood commented on CLOUDSTACK-9209:
--

I get the same error on CloudStack 4.8.0.1 with CentOS 7 and Maria 10.1 setup 
when HA is set to true.  When i set HA to false the bootstrap runs no problem.  
I am installing CloudStack through the offical yum repositories.  Anyway to fix 
this after CloudStack install?

> Database HA not working on a fresh install on Ubuntu 12.04
> --
>
> Key: CLOUDSTACK-9209
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9209
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.7.0
> Environment: Two Ubuntu 12.04 Management Servers, Mysql Master Master 
> Replication, Official community repository: 
> http://cloudstack.apt-get.eu/ubuntu/dists/precise/4.7/
>Reporter: Thomas
>Priority: Blocker
>
> The cloudstack-management service will not come up because of this error:
> 2016-01-05 16:15:00,899 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) Is 
> Data Base High Availiability enabled? Ans : true
> 2016-01-05 16:15:00,924 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) 
> The slaves configured for Cloud Data base is/are : 192.168.0.90
> 2016-01-05 16:15:00,974 ERROR [c.c.u.d.Merovingian2] (main:null) (logid:) 
> Unable to get a new db connection
> java.sql.SQLException: Invalid load balancing strategy 
> 'com.cloud.utils.db.StaticStrategy'.
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:934)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:931)
> at com.mysql.jdbc.Util.loadExtensions(Util.java:588)
> at 
> com.mysql.jdbc.LoadBalancingConnectionProxy.(LoadBalancingConnectionProxy.java:279)
> at 
> com.mysql.jdbc.FailoverConnectionProxy.(FailoverConnectionProxy.java:66)
> at 
> com.mysql.jdbc.NonRegisteringDriver.connectFailover(NonRegisteringDriver.java:382)
> at 
> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:301)
> at java.sql.DriverManager.getConnection(DriverManager.java:571)
> at java.sql.DriverManager.getConnection(DriverManager.java:215)
> at 
> org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75)
> at 
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
> at 
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)
> at 
> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
> at 
> com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:202)
> at com.cloud.utils.db.Merovingian2.(Merovingian2.java:68)
> at 
> com.cloud.utils.db.Merovingian2.createLockMaster(Merovingian2.java:88)
> at 
> com.cloud.server.LockMasterListener.(LockMasterListener.java:33)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at 
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148)
> at 
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121)
> at 
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:277)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1077)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:981)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
> at 
> org.springframework.beans.fa

[jira] [Commented] (CLOUDSTACK-8212) database upgrade failed for fresh install of 4.5.0-SNAPSHOT

[Tom Wood (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617337#comment-14617337
 ] 

Tom Wood commented on CLOUDSTACK-8212:
--

I was able to reproduce this problem using CentOS 7 and CloudStack 4.5.1 using 
the following databases all on one VM:
MariaDB 5.5.44 (pulled from MariaDB repo)
MariaDB 10.0.20 (pulled from MariaDB repo)
I was able to resolve this problem using the recommendation above.  Or at least 
everything seemed to work.  Not sure if commenting out those two lines is a 
"fix".

Also when I used the default CentOS repo for the database "MariaDB 5.5.41" 
would installed instead of the latest from MariaDB which worked fine with no 
problems.  This may be why some people are running into the problem and some 
people are not.

> database upgrade failed for fresh install of 4.5.0-SNAPSHOT
> ---
>
> Key: CLOUDSTACK-8212
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8212
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.5.0
> Environment: RedHat 7, external MariaDB on custom port.
>Reporter: Andreas Stenius
> Attachments: cloudstack-4.5.0-SNAPSHOT-logs.tar.gz
>
>
> During installation of a new system, when first starting the MS, it logs that 
> the db needs upgrading from 4.0.0, but fails to do so (see attached logs).
> The culprit would seem to be due to these error messages (my guess from 
> screening the logs...):
> ERROR [c.c.u.d.ScriptRunner] (localhost-startStop-1:null) Error executing: 
> UPDATE `cloud`.`configuration` SET value = CONCAT("*.",(SELECT 
> `temptable`.`value` FROM (SELECT * FROM `cloud`.`configuration` WHERE 
> `name`="consoleproxy.url.domain") AS `temptable` WHERE 
> `temptable`.`name`="consoleproxy.url.domain")) WHERE 
> `name`="consoleproxy.url.domain" 
> ERROR [c.c.u.d.ScriptRunner] (localhost-startStop-1:null) 
> java.sql.SQLException: You can't specify target table 'configuration' for 
> update in FROM clause
> ERROR [c.c.u.DatabaseUpgradeChecker] (localhost-startStop-1:null) Unable to 
> execute upgrade script: 
> /usr/share/cloudstack-management/setup/db/schema-421to430.sql



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)