dead dashboard after update & reboot

Nux! nux at li.nux.ro
Sun Jan 13 08:59:40 UTC 2013


On 13.01.2013 08:56, Nux! wrote:
> On 13.01.2013 02:11, Pádraig Brady wrote:
>> On 01/13/2013 01:58 AM, Pádraig Brady wrote:
>>> On 01/11/2013 09:30 PM, Nux! wrote:
>>>> Hi,
>>>>
>>>> Today after a "yum update" which did upgrade parts of my openstack 
>>>> installation and a reboot, I ended up with a "500 internal server 
>>>> error".
>>>
>>> What were the old and new versions of nova?
>>>
>>>> Here's last 100 log entried in httpd/error_log
>>>>
>>>> centos 6.3 + epel (up to date :> ), selinux is in permissive mode.
>>>
>>> This could be due to trying to start the metadata service twice:
>>>
>>> https://lists.launchpad.net/openstack/msg19294.html
>>> https://bugzilla.redhat.com/show_bug.cgi?id=877606
>>>
>>> You can probably get around the issue by disabling
>>> the separate metadata service or adjusting the
>>> enabled_apis option in nova.conf
>>
>> By the way, did you manually enable the metadata service,
>> as openstack-demo-install doesn't seem to at least.
>>
>> thanks,
>> Pádraig.
>> _______________________________________________
>> cloud mailing list
>> cloud at lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/cloud
>
> That was probably by mistake. :-/
>
> The dashboard is half-functioning now (no CSS, ajax etc) and
> nova-compute refuses to start:
> 2013-01-13 10:54:32 INFO nova.compute.manager
> [req-9c31b571-69e4-4e07-8cb2-cdf394837b72 None None] [instance:
> 9aec8016-e904-41ac-80ad-ee2cf95ab393] Rebooting instance after
> nova-compute restart.
> 2013-01-13 10:54:32 INFO nova.virt.libvirt.firewall
> [req-9c31b571-69e4-4e07-8cb2-cdf394837b72 None None] [instance:
> 9aec8016-e904-41ac-80ad-ee2cf95ab393] Called setup_basic_filtering in
> nwfilter
> 2013-01-13 10:54:32 INFO nova.virt.libvirt.firewall
> [req-9c31b571-69e4-4e07-8cb2-cdf394837b72 None None] [instance:
> 9aec8016-e904-41ac-80ad-ee2cf95ab393] Ensuring static filters
> 2013-01-13 10:54:36 8943 CRITICAL nova [-] Requested operation is not
> valid: domain is already running
>
> All the VMs are of course running, I'm using
> "start_guests_on_host_boot=true".

I think I'll leave this off as it creates issues and rely on 
libvirt-guests service to start them up.

-- 
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro


More information about the cloud mailing list