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

Saurav Lahiri commented on CLOUDSTACK-6258:
-------------------------------------------

The problem appears to be the start function in the /etc/init.d/cloud service 
for console proxy. 
More specifically the following line also writes to /var/log/cloud.out

----------------------------------------------------------------------------------------------------------------------------------
(cd $CLOUD_COM_HOME/systemvm; nohup ./run.sh > /var/log/cloud/cloud.out 2>&1 & )
----------------------------------------------------------------------------------------------------------------------------------

since run.sh calls _run.sh and both has "set -x" enabled, in certain situations 
they can keep
logging messages to cloud.out without being aware of the settings in 
log4j-cloud.xml


One way to fix that could be that run.sh and _run.sh would log to cloud.out 
only if a debug flag 
was set to true, otherwise only the java process would write to cloud.out and 
log4j would 
respect the settings in log4j-cloud.xml

> console proxy log files in /var/log/cloud are larger than 10MB
> --------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6258
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6258
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: SystemVM
>    Affects Versions: 4.3.0
>            Reporter: Saurav Lahiri
>            Assignee: Saurav Lahiri
>
> We have seen that very often on console proxy, the root filesystem goes full 
> with the cloud.out.* occupying all the space. To resolve this issue it is 
> required to recycle the CPVM.
> As seen below, cloud.out.2 should not have exceeded 10MB but it stands at 
> 217MB now.
> root@v-zzzz-VM:/var/log/cloud# ls -alh
> drwxr-xr-x 2 root root 4.0K Mar 17 14:57 .
> drwxr-xr-x 8 root root 4.0K Mar 17 15:01 ..
> -rw-r--r-- 1 root root    0 Mar 12 18:18 api-server.log
> -rw-r--r-- 1 root root 357K Mar 17 15:06 cloud.out
> -rw-r--r-- 1 root root 2.1M Mar 17 14:56 cloud.out.1
> -rw-r--r-- 1 root root 217M Mar 17 15:06 cloud.out.2
> root@v-zzzz-VM:/var/log/cloud# lsof | grep cloud.out
> sleep       649 root    1w      REG      202,1 226122291     181737 
> /var/log/cloud/cloud.out.2
> sleep       649 root    2w      REG      202,1 226122291     181737 
> /var/log/cloud/cloud.out.2
> bash       2312 root    1w      REG      202,1 226122291     181737 
> /var/log/cloud/cloud.out.2
> bash       2312 root    2w      REG      202,1 226122291     181737 
> /var/log/cloud/cloud.out.2
> bash       2339 root    1w      REG      202,1 226122291     181737 
> /var/log/cloud/cloud.out.2
> bash       2339 root    2w      REG      202,1 226122291     181737 
> /var/log/cloud/cloud.out.2
> bash       2786 root    1w      REG      202,1 226122291     181737 
> /var/log/cloud/cloud.out.2
> bash       2786 root    2w      REG      202,1 226122291     181737 
> /var/log/cloud/cloud.out.2
> java       2805 root    1w      REG      202,1 226122291     181737 
> /var/log/cloud/cloud.out.2
> java       2805 root    2w      REG      202,1 226122291     181737 
> /var/log/cloud/cloud.out.2
> java       2805 root  116w      REG      202,1    319382     181769 
> /var/log/cloud/cloud.out



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to