cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Phillips <>
Subject cloudmanagementserver.keystore
Date Tue, 08 Apr 2014 03:57:20 GMT
I know this was a problem in 4.2.1 in which the system would endlessly log the following error:
014-04-07 22:29:29,715 WARN  [c.c.u.n.Link] (AgentManager-Selector:null) SSL: Fail to find
the generated keystore. Loading fail-safe one to continue.
The fix was to rename /etc/cloudstack/management/cloudmanagementserver.keystore, to cloud.keystore
then restart cloudstack.
I just installed 4.3.0 fresh, and it seems like this problem persists with a twist. The system
now does not create any keystore file and logs the following 3 errors.
Executing: sudo keytool -genkey -keystore /etc/cloudstack/management/cloudmanagementserver.keystore
-storepass -keypass -keyalg RSA -validity 3650 -dname cn="Cloudstack User",ou="ustxdalcstackwebp1.cloudagy.local",o="ustxdalcstackwebp1.cloudagy.local",c="Unknown"
2014-04-07 21:31:53,610 DEBUG [c.c.u.s.Script] (main:null) Exit value is 12014-04-07 21:31:53,610
DEBUG [c.c.u.s.Script] (main:null) sudo: no tty present and no askpass program specified
My fix was to run the above command "keytool..." from the command line, then rename the file
to cloud.keystore. Once I did that it stopped logging the "SSL: Fail to find the generated
keystore" errors. Can anyone else confirm they saw this behavior in 4.3.0? If so I can make
a bug report in JIRA..
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message