Thats for that link to the bug, Ive changed the paths on both configuration
files(server and tomcat) for the keystone, even created my own keystore, and I
still see the issue with the SSVM not being able to communicate to the
management server with SSL. Do we have a valid fix in place?
On M
Seems to be a known issue
https://issues.apache.org/jira/browse/CLOUDSTACK-2024
On 8/19/13 3:28 PM, "Edward Valencia" wrote:
>When you run cloudstack-setup-management
> it creates this:
>
>[root@cstack-411 management]# cloudstack-setup-management --https
>
>lrwxrwxrwx. 1 root root 44 Aug 19 22
When you run cloudstack-setup-management
it creates this:
[root@cstack-411 management]# cloudstack-setup-management --https
lrwxrwxrwx. 1 root root 44 Aug 19 22:22 server.xml ->
/etc/cloudstack/management/server-nonssl.xml
lrwxrwxrwx. 1 root root 46 Aug 19 22:22 tomcat6.conf ->
/etc/cloudsta
Isn't there a /etc/cloudstack/management/tomcat6-ssl.conf ? I think
cloudstack-setup-management creates a symlink to this one.
On 8/19/13 2:19 PM, "Edward Valencia" wrote:
>Hi All,
>
>The following error keeps showing up on my ssvm instance, I've set the
>api port in global settings to 8250, re
Hi All,
The following error keeps showing up on my ssvm instance, I've set the api port
in global settings to 8250, restarted the management service and still see this
error:
root@s-21-VM:/var/log/cloud# tail -f /var/log/cloud/cloud.out
21:09:23,162 ERROR NioConnection:113 - Unable to initiali
