You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Sanjay Tripathi (JIRA)" <ji...@apache.org> on 2013/12/27 14:05:54 UTC

[jira] [Resolved] (CLOUDSTACK-4450) Possibility of /tmp/xapilog filling up the Root disk on Xenserver

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

Sanjay Tripathi resolved CLOUDSTACK-4450.
-----------------------------------------

    Resolution: Fixed

> Possibility of /tmp/xapilog filling up the Root disk on Xenserver 
> ------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4450
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4450
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: XenServer
>    Affects Versions: 4.2.0
>            Reporter: Sanjay Tripathi
>            Assignee: Sanjay Tripathi
>             Fix For: 4.3.0
>
>
> CloudStack installs "/opt/xensource/sm/hostvmstats.py" script into XenServer. And the script keeps outputting the log into "/tmp/xapilog." Now the log is being huge size (Almost 120MBytes) since the file has no architecture to delete/compress. 
> The info logged in /opt/xensource/sm/hostvmstats.py is not much useful. There are few cases in the past where CloudStack was contributing to Root filesystem being full on xenserver. We need to make sure either we delete/overwrite/rotate the file /tmp/xapilog in Xenserver.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)