cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sadhu suresh (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-6498) [Automation] unable to start management server after restart
Date Mon, 21 Jul 2014 10:40:39 GMT


sadhu suresh commented on CLOUDSTACK-6498:

my MS is up  now by following the workaround,just now kishan pushed a fix 
and for those who don't want recreate the setup again or want to reuse  exiting setup then
follow the below work around:

identify for which field it fail to decrypt in the log , take the value and search in the
database for relevant table.

Once  you identify the table(in my case its ocnfiguration  table) and update the exiting value
with encrypted value

1. take the value displayed in the log "sc20X2B-SzHp1nU3FYc-AA"
2.encrypt the value
java -classpath /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/jasypt-1.9.0.jar
org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI input=sc20X2B-SzHp1nU3FYc-AA password=password

it will generate the encrypted value
3. update in the db 
 update configuration set value="V3cfEEk54oFq/EAa3VFN8p9M/CCx6/wIhYiwxID7t+U=" where name
like "security.encryption.key"\G;
4. restart the ms 

5.repeat step 1 to 4 (same procedure)  for other  decrypt failures

> [Automation] unable to start management server after restart
> ------------------------------------------------------------
>                 Key: CLOUDSTACK-6498
>                 URL:
>             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: advanced zone
> xenserer 6.2
>            Reporter: Srikanteswararao Talluri
>            Assignee: Harikrishna Patnala
>            Priority: Blocker
>             Fix For: 4.5.0
>         Attachments: CLOUDSTACK-6498.rar, cloud.sql, log.tar.gz
> on the daily automation environment, After the zone is deployed , system VMs came up
fine. After setting few global settings, I tried to restart management server, it never came
up again. I could see some db exceptions related to duplicate keys.
> I will attach management server logs to this bug for your reference.
> Caught SQLException when inserting system account
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate
entry '1' for key 'PRIMARY'
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance(
>         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
>         at java.lang.reflect.Constructor.newInstance(
>         at com.mysql.jdbc.Util.handleNewInstance(
>         at com.mysql.jdbc.Util.getInstance(
>         at com.mysql.jdbc.SQLError.createSQLException(
>         at com.mysql.jdbc.MysqlIO.checkErrorPacket(
>         at com.mysql.jdbc.MysqlIO.checkErrorPacket(
>         at com.mysql.jdbc.MysqlIO.sendCommand(
>         at com.mysql.jdbc.MysqlIO.sqlQueryDirect(
>         at com.mysql.jdbc.ConnectionImpl.execSQL(
>         at com.mysql.jdbc.PreparedStatement.executeInternal(
>         at com.mysql.jdbc.PreparedStatement.executeUpdate(
>         at com.mysql.jdbc.PreparedStatement.executeUpdate(
>         at com.mysql.jdbc.PreparedStatement.executeUpdate(
>         at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(
>         at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(
                                                                     14761,2-9     96%

This message was sent by Atlassian JIRA

View raw message