openstack team mailing list archive

[Leander Bessa Beernaert <leanderbb@xxxxxxxxx>]

You sir a my hero! I turned out someone altered the filesystem before
installing OpenStack leaving me with 3gb partition for the operating
system.

Thanks.
Leander

On Wed, Jun 27, 2012 at 4:32 PM, Jay Pipes <jaypipes@xxxxxxxxx> wrote:

> This looks very familiar :) Make sure that you have enough space in the
> partition that houses /tmp (usually whatever partition has / mounted). The
> snapshot operation requires at least as much space in /tmp as the size of
> the snapshot to be made.
>
> If you have improperly given yourself a very small root partition (likely
> if you are using devstack or devstack's PXE images), then you can remedy
> the situation using a bit of a hack:
>
> ln -s /tmp /some/mount/with/space
>
> Best,
> -jay
>
>
> On 06/27/2012 08:52 AM, Leander Bessa Beernaert wrote:
>
>> I've tried to snapshot again today and i found this error in the
>> compute.log:
>> http://paste.openstack.org/**show/18882/<http://paste.openstack.org/show/18882/>
>>
>> Any ideas?
>>
>> On Tue, Jun 26, 2012 at 9:26 AM, Leander Bessa Beernaert
>> <leanderbb@xxxxxxxxx <mailto:leanderbb@xxxxxxxxx>> wrote:
>>
>>    I can't find any error traces in the glance api and registry log.
>>
>>
>>    On Mon, Jun 25, 2012 at 7:39 PM, Vishvananda Ishaya
>>    <vishvananda@xxxxxxxxx <mailto:vishvananda@xxxxxxxxx>**> wrote:
>>
>>        Usually queued means it didn't ever get uploaded into glance.
>>        Any errors in the glance log? I have never seen the error below,
>>        but it could be related.
>>
>>        Vish
>>
>>        On Jun 25, 2012, at 3:50 AM, Leander Bessa Beernaert wrote:
>>
>>         Hello,
>>>
>>>        I've performed snapshots over and over without ever running
>>>        into trouble, however now one of them is stuck in the Queued
>>>        state. I've searched the machine's compute.log for any
>>>        indication of an error, but nothing showed up. I did a quick
>>>        search and usually the erros appear in the compute.log or the
>>>        libivirtd.log. The only thing i found in the libvirtd.log were
>>>        these two lines:
>>>
>>>            2012-06-25 10:37:05.957+0000: 6830: warning :
>>>            qemuCapsInit:856 : Failed to get host power management
>>>            capabilities
>>>            2012-06-25 10:37:06.612+0000: 6831: error :
>>>            virExecWithHook:328 : Cannot find 'pm-is-supported' in
>>>            path: No such file or director
>>>
>>>        Could that be the problem?
>>>
>>>        Regards,
>>>        Leander
>>>        ______________________________**_________________
>>>        Mailing list: https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
>>>        Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>>        <mailto:openstack@lists.**launchpad.net<openstack@xxxxxxxxxxxxxxxxxxx>
>>> >
>>>
>>>        Unsubscribe : https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
>>>        More help   : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>>>
>>
>>
>>
>>
>>
>> ______________________________**_________________
>> Mailing list: https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
>> More help   : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>>
>>
>
> ______________________________**_________________
> Mailing list: https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
> More help   : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>