Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Sun, 14 Oct 2012 05:22:03 +0000 (UTC)
From: "edison su (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <2022317050.42694.1350192123641.JavaMail.jiratomcat@arcas>
In-Reply-To: <146558396.42549.1350182283097.JavaMail.jiratomcat@arcas>
Subject: [jira] [Closed] (CLOUDSTACK-340) Tomcat config files broken after
 ant deploy-server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

edison su closed CLOUDSTACK-340.
--------------------------------

    Resolution: Fixed
    
> Tomcat config files broken after ant deploy-server
> --------------------------------------------------
>
>                 Key: CLOUDSTACK-340
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-340
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Install and Setup
>    Affects Versions: pre-4.0.0
>         Environment: Centos 5.6
>            Reporter: John Kinsella
>              Labels: ant, wscript
>             Fix For: pre-4.0.0
>
>
> Looks like something should be performing substitution before config files are deployed, but this isn't happening:
> # ant deploy-server
> (completes without error)
> # /etc/init.d/cloud-management restart
> Stopping cloud-management:                                 [  OK  ]
> /etc/cloud/management/tomcat6.conf: line 73: @MSCONF@/classpath.conf: No such file or directory
> Starting cloud-management: chown: `@MSUSER@:@MSUSER@': invalid user
> touch: cannot touch `@MSLOGDIR@/catalina.out': No such file or directory
> chown: `@MSUSER@:@MSUSER@': invalid user
> /etc/rc.d/init.d/tomcat6: line 179: @MSLOGDIR@/catalina.out: No such file or directory
>                                                            [FAILED]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira