Note that cloudstack RPMs don't ship with a tomcat6.conf, only: /etc/cloudstack/management/tomcat6-nonssl.conf /etc/cloudstack/management/tomcat6-ssl.conf
I believe it's the cloudstack-setup-management that creates a symlink to the correct one of the two. On Wed, Jul 10, 2013 at 5:48 PM, Marcus Sorensen <shadow...@gmail.com> wrote: > The user, on installation of the cloudstack-management RPM, should have seen: > > "Unable to determine ssl settings for tomcat.conf, please run > cloudstack-setup-management manually" > > If there was a previous install, the existing tomcat6.conf would have > been used. Since there is none, the user needs to configure their > management server via 'cloudstack-setup-management' to create the > tomcat6.conf. If it is not created, then there's a new bug there. > > On Wed, Jul 10, 2013 at 5:12 PM, Sebastien Goasguen <run...@gmail.com> wrote: >> >> On Jul 8, 2013, at 11:58 PM, Maurice Lawler <maurice.law...@me.com> wrote: >> >> Hello, >> >> Fresh install /setup, I am getting error: >> >> [root@cloud ~]# /etc/init.d/cloudstack-management start >> /etc/sysconfig/cloudstack-management: line 21: >> /etc/cloudstack/management/tomcat6.conf: No such file or directory >> Starting cloudstack-management: awk: cmd. line:1: fatal: cannot open file >> `/etc/cloudstack/management/tomcat6.conf' for reading (No such file or >> directory) >> Error code 4 [FAILED] >> >> However, I read of a work around, copy tomcat6-nonssl.conf to tomcat6.conf >> and that allowed me to start the management server. >> >> Why is this error on going? >> >> https://issues.apache.org/jira/browse/CLOUDSTACK-1802 >> >> >> I am copying Marcus since 180 points to : >> https://issues.apache.org/jira/browse/CLOUDSTACK-1694 >> >> Which he is listed as "assignee" and bugs seems fixed. >> >> Marcus, any thoughts ? >> >> -sebastien >> >> >> >> >> >>
