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

Keerthiraja commented on CLOUDSTACK-8836:
-----------------------------------------

This issue been identified and able to resolve this by below method.

stop cloud-management 
stop MariaDB

Need to comment the query and update the new one mention below.

/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.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";

UPDATE `cloud`.`configuration` SET value=CONCAT("*.",value) WHERE 
`name`="consoleproxy.url.domain" OR `name`="consoleproxy.url.domain";
UPDATE `cloud`.`configuration` SET value=CONCAT("*.",value) WHERE 
`name`="secstorage.ssl.cert.domain" OR `name`="secstorage.ssl.cert.domain";

Then redeploy the cloudstack-database
Then start the service all seems to be working fine without any issue.

Not sure will this be patched very soon no the version 4.5.3 and 4.6.



> Cloudstack 4.5.2 Not starting on Fresh install on MariaDB-server-10.0.21-1
> --------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8836
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8836
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Install and Setup
>    Affects Versions: 4.5.2
>         Environment: CentOS 6.7 with MariaDB-server-10.0.21-1.el6.x86_64.
>            Reporter: Keerthiraja
>            Priority: Blocker
>             Fix For: 4.5.3
>
>
> After the successful installation along with cloudstack-setup-database.
> I tried to start the cloudstack services. During the time I could see the 
> tomcat fails to start. Pasted the ERROR below.
> Kindly can someone help me out on this as soon as possible. I am right now in 
> client place to implement for production setup.
> Error
> ====
> 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



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

Reply via email to