Hi Keerthi,
Did you clear the MySQL cloud db in between attempts?
I’m a bit confused. Are you using CentOS 6 or 7? First I thought CentOS 7, but
now you show an CentOS 6 MariaDB package?
If you’re on CentOS 6 I’d recommend using the MySQL version that ships with it.
Otherwise, the fix as described works, as long as you start clean.
Regards, Remi
On 13/09/15 17:32, "Keerthiraja SJ" <sjkeer...@gmail.com> wrote:
>Even After I commented this line on MariaDB-server-10.0.21-1.el6.x86_64.
>
>
>#realhostip changes, before changing table and adding default value
>#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";
>#UPDATE `cloud`.`configuration` SET `value` = CONCAT("*.",(SELECT
>`temptable`.`value` FROM (SELECT * FROM `cloud`.`configuration` WHERE
>`name`="secstorage.ssl.cert.domain") AS `temptable` WHERE
>`temptable`.`name`="secstorage.ssl.cert.domain")) WHERE
>`name`="secstorage.ssl.cert.domain";
>
>
>Still could see error during the start up with below error on catalina.out
>
>ERROR
>ERROR [c.c.u.d.ScriptRunner] (main:null) Error executing: alter table
>vm_template add size bigint unsigned
>ERROR [c.c.u.d.ScriptRunner] (main:null)
>com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column
>name 'size'
>ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to execute upgrade
>script: /usr/share/cloudstack-management/setup/db/schema-40to410.sql
>com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column
>name 'size'
> at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:185)
>
>
>ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to upgrade the
>database
>com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade
>script: /usr/share/cloudstack-management/setup/db/schema-40to410.sql
>
>Thanks,
>Keerthi
>
>
>
>On Sat, Sep 12, 2015 at 1:13 PM, Remi Bergsma <rberg...@schubergphilis.com>
>wrote:
>
>> Hi,
>>
>> The root cause was recently fixed here:
>> https://github.com/apache/cloudstack/pull/757/files
>>
>> As a workaround you can either alter the query (as mentioned below) or
>> downgrade mariadb:
>>
>> systemctl stop mariadb
>> yum -y remove mariadb-libs
>> yum -y install mariadb-1:5.5.41-2.el7_0.x86_64
>> mariadb-server-1:5.5.41-2.el7_0.x86_64
>> systemctl start mariadb
>>
>> Regards, Remi
>>
>> Sent from my iPhone
>>
>> On 12 Sep 2015, at 00:59, giraffeg forestg <giraffefore...@gmail.com
>> <mailto:giraffefore...@gmail.com>> wrote:
>>
>> Hi
>>
>>
>> CLOUDSTACK-8212 might become your help.
>>
>> https://issues.apache.org/jira/browse/CLOUDSTACK-8212
>>
>>
>> 1. This is resolved by commenting out:
>> ---
>> [root@acs ~]# vi
>> /usr/share/cloudstack-management/setup/db/schema-421to430.sql
>>
>> :
>>
>> #realhostip changes, before changing table and adding default value
>> # UPDATE `cloud`.`configuration` SET value = CONCAT("*.",(SELECT
>> `temptable`.`value` FROM (SELECT * FROM `cloud`.`configuration` WHERE
>> `name`="consoleproxy.u
>> rl.domain") AS `temptable` WHERE
>> `temptable`.`name`="consoleproxy.url.domain")) WHERE
>> `name`="consoleproxy.url.domain";
>> # UPDATE `cloud`.`configuration` SET `value` = CONCAT("*.",(SELECT
>> `temptable`.`value` FROM (SELECT * FROM `cloud`.`configuration` WHERE
>> `name`="secstorage.ssl.cert.domain") AS `temptable` WHERE
>> `temptable`.`name`="secstorage.ssl.cert.domain")) WHERE
>> `name`="secstorage.ssl.cert.domain";
>> ---
>>
>> and,
>>
>> 2. stop cloudsack-management & cloudsack-usage & mariadb
>> 3. initialize database
>> 4. cloudstack-setup-databases
>> 5. cloudstack-setup-management
>>
>>
>> I also the same problem has occurred.
>>
>> My environment:
>> CloudStack 4.5.2 (
>> http://packages.shapeblue.com/cloudstack/upstream/centos7/4.5)
>> CentOS 7.1.1503
>> mariadb-5.5.44-1
>>
>>
>>
>> ---
>> Satoru Nakaya
>>
>> Japan CloudStack User Group
>> http://cloudstack.jp/
>>
>>
>> 2015-09-11 23:11 GMT+09:00 Keerthiraja SJ <sjkeer...@gmail.com<mailto:
>> sjkeer...@gmail.com>>:
>>
>> I really face this issue when I install on MariaDB. If I do the same on
>> MySQL this pass it.
>>
>> On Fri, Sep 11, 2015 at 7:09 PM, Keerthiraja SJ <sjkeer...@gmail.com
>> <mailto:sjkeer...@gmail.com>>
>> wrote:
>>
>> Hi All,
>>
>> Today I tried to install the CS 4.5.2 on fresh box where I could able to
>> successfully deploy
>> the cloudstack-setup-databases.
>>
>> After I tried number of times the fresh installation I could see the same
>> issue been reproducing it.
>>
>> While stating the cloudstack servers I could see below error constantly.
>>
>>
>>
>>
>> *ERROR*ERROR [c.c.u.d.ScriptRunner] (main: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] (main:null)
>> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications
>> link failure
>>
>> The last packet successfully received from the server was 25 milliseconds
>> ago. The last packet sent successfully to the server was 25 milliseconds
>> ago.
>> ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to execute
>> upgrade
>> script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
>> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications
>> link failure
>>
>>
>> Caused by: java.net.SocketException: Broken pipe
>> ... 61 more
>> ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to upgrade the
>> database
>> com.cloud.utils.exception.CloudRuntimeException: Unable to execute
>> upgrade
>> script: /usr/share/cloudstack-management/setup/db/schema-421to430.sql
>> at
>>
>>
>> com.cloud.upgrade.DatabaseUpgradeChecker.runScript(DatabaseUpgradeChecker.java:311)
>>
>> ERROR [c.c.u.d.DbUtil] (main:null) RELEASE_LOCK() throws exception
>> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications
>> link failure
>>
>>
>> I did this test number of times by allocating fresh box.
>>
>> Thanks,
>> Keerthi
>>
>>
>>
