cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hugo Trippaers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2440) MS fails to start after upgrade to 4.1
Date Mon, 13 May 2013 14:13:15 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655989#comment-13655989
] 

Hugo Trippaers commented on CLOUDSTACK-2440:
--------------------------------------------

1) /var/log/cloudstack-management/initd.log

Fixed by creating this directory in the spec file. (commit c2118180d5e2e4442f6744e83089295060eba73e
on master)
                
> MS fails to start after upgrade to 4.1
> --------------------------------------
>
>                 Key: CLOUDSTACK-2440
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2440
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Packaging
>    Affects Versions: 4.1.0
>            Reporter: Kishan Kavala
>            Assignee: Hugo Trippaers
>            Priority: Blocker
>
> After upgrading to 4.1 from 3.0, MS failed to start with below error.
> Starting cloudstack-management: sed: can't read /usr/share/cloudstack-management/conf/server.xml:
No such file or directory
> /etc/rc.d/init.d/tomcat6: line 191: /var/log/cloudstack-management/initd.log: No such
file or directory
> Error code 4                                               [FAILED]
> Manually copying server.xml and creating directory /var/log/cloudstack-managemen solved
the issue.

--
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

Mime
View raw message