cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Tripathi (JIRA)" <>
Subject [jira] [Updated] (CLOUDSTACK-4450) Possibility of /tmp/xapilog filling up the Root disk on Xenserver
Date Thu, 22 Aug 2013 12:49:52 GMT


Sanjay Tripathi updated CLOUDSTACK-4450:

    Status: Ready To Review  (was: In Progress)
> Possibility of /tmp/xapilog filling up the Root disk on Xenserver 
> ------------------------------------------------------------------
>                 Key: CLOUDSTACK-4450
>                 URL:
>             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.2.1
> CloudStack installs "/opt/xensource/sm/" 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/ 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message