[
https://issues.apache.org/jira/browse/CLOUDSTACK-6498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068392#comment-14068392
]
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 encrypt.sh
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: https://issues.apache.org/jira/browse/CLOUDSTACK-6498
> 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(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> at com.mysql.jdbc.Util.getInstance(Util.java:386)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625)
> at
> com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119)
> at
> com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415)
> at
> com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333)
> at
> com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318)
> at
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
> at
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
>
>
> 14761,2-9 96%
--
This message was sent by Atlassian JIRA
(v6.2#6252)
