You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rayees Namathponnan (JIRA)" <ji...@apache.org> on 2013/07/23 01:08:51 UTC
[jira] [Comment Edited] (CLOUDSTACK-3718) [Automation] MS and API
logs failed to generate due to wrong permissions
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715828#comment-13715828 ]
Rayees Namathponnan edited comment on CLOUDSTACK-3718 at 7/22/13 11:08 PM:
---------------------------------------------------------------------------
If you perfrom about steps, logs are not writing to "management-server.log" and "api log", these files are always blank
Also you can see the owner of these files are root, it should suppose to be "cloud"
This need to be handled in packaging
was (Author: rayeesn):
If you perfrom about steps, logs are not writing to "management-server.log" and "api log", these files are always blank
Also you can see the owner of these files are root, it should suppose to be "cloud"
if need to be handled in packaging
> [Automation] MS and API logs failed to generate due to wrong permissions
> ------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3718
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3718
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: API, Automation, Install and Setup
> Affects Versions: 4.2.0
> Environment: 4.2
> Reporter: Rayees Namathponnan
> Priority: Blocker
> Fix For: 4.2.0
>
>
> Steps to reproduce
> Step 1 : Install Cloudstack management server
> Step 2 : Stop MS and Cleanup /var/log/cloudstack/management/
> Step 3: Remove cloudstack
> Step 4 : Re-install MS and run setup scripts
> Actual Result
> Failed to add log in "management-server.log and api-server.log" and both the files owners are not cloud,
> [root@auto_ms2 management]# ll
> total 64576
> -rw-rw-r--. 1 cloud cloud 67867 Jul 21 23:59 access_log.2013-07-21.txt
> -rw-rw-r--. 1 cloud cloud 13931049 Jul 22 10:51 access_log.2013-07-22.txt
> -rw-rw-r--. 1 cloud cloud 45285780 Jul 22 10:51 apilog.log
> -rw-rw-r--. 1 cloud cloud 15488 Jul 22 00:00 apilog.log.2013-07-21.gz
> -rw-r--r--. 1 root root 0 Jul 21 23:24 api-server.log
> -rw-rw-r--. 1 cloud cloud 0 Jul 21 23:24 catalina.2013-07-21.log
> -rw-r--r--. 1 cloud cloud 6785324 Jul 22 10:51 catalina.out
> -rw-rw-r--. 1 cloud cloud 0 Jul 21 23:24 host-manager.2013-07-21.log
> -rw-rw-r--. 1 cloud cloud 437 Jul 21 23:28 localhost.2013-07-21.log
> -rw-r--r--. 1 root root 0 Jul 21 23:24 management-server.log
> -rw-rw-r--. 1 cloud cloud 0 Jul 21 23:24 manager.2013-07-21.log
> -rw-r--r--. 1 root root 5811 Jul 21 23:24 setupManagement.log
--
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