1.In 4.1,cloud service run before cloud-early-config,that could be an issue. 2.In 4.2,new template,the issue does not exist
2013/9/27, John Beredimas (JIRA) <j...@apache.org>: > John Beredimas created CLOUDSTACK-4753: > ------------------------------------------ > > Summary: Console proxy disk space fills up > Key: CLOUDSTACK-4753 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4753 > Project: CloudStack > Issue Type: Bug > Security Level: Public (Anyone can view this level - this is the > default.) > Components: SystemVM > Affects Versions: 4.1.0 > Reporter: John Beredimas > > > I run into this when I restarted the console proxy as part of upgrading to > Cloudstack 4.2. It seems that the console proxy is filling up the cloud.out > files and can potentially exhaust disk space. > > root@v-1011-VM:~# df -h > Filesystem Size Used Avail Use% Mounted on > /dev/xvda1 2.0G 1.1G 873M 55% / > <snip> > root@v-1011-VM:~# du -sh /var/log/cloud/cloud.out* > 3.2M /var/log/cloud/cloud.out > 9.8M /var/log/cloud/cloud.out.1 > 502M /var/log/cloud/cloud.out.2 > > This can cause the console proxy to become non-available on a reboot, due to > no disk left on device. > > -- > 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 >
