Hey,

this error showed up and qubes-manager got frozen.

The journalctl output is from the timestamp of my screenshot, so it
might be correlated.

Best Regards,
Nukama

On Thu, Sep 18, 2014 at 08:54:36AM +0000, Hakisho Nukama wrote:
> Hey,
>
> this error showed up and qubes-manager got frozen.
>
> The journalctl output is from the timestamp of my screenshot, so it
> might be correlated.

Could you post whole "show details" contents and which version of
qubes-manager you are running?


--
regards
WZJP

Hi,

I'm running qubes-manager 2.0.35.
I couldn't hit "show details" as qubes-manager was not responsive.

Best Regards,
Hakisho Nukama

On Thu, Sep 18, 2014 at 10:06:39AM +0000, Hakisho Nukama wrote:
> On Thu, Sep 18, 2014 at 9:58 AM, Wojciech Zygmunt Porczyk
> <wojc...@porczyk.eu> wrote:
> > On Thu, Sep 18, 2014 at 08:54:36AM +0000, Hakisho Nukama wrote:
> >> Hey,
> >>
> >> this error showed up and qubes-manager got frozen.
> >>
> >> The journalctl output is from the timestamp of my screenshot, so it
> >> might be correlated.
> >
> > Could you post whole "show details" contents and which version of
> > qubes-manager you are running?
>

> I'm running qubes-manager 2.0.35.
> I couldn't hit "show details" as qubes-manager was not responsive.

1) Has it happened when you right-clicked qubes-manager icon in systray?

2) Has it happened randomly or you can reproduce it? (don't reboot to check yet)

3) Hard to tell without trace, but I guess it has something to do with
attached block devices. Attribute "name" in this code path is in context
of vm = QubesVmCollection.get_vm_by_name(name), name is from block
device manager.

Could you post result of qvm-block and then from this command (this will
list block devices and names of vms they're attached to, as seen by
qubesmanager):

  python -c 'import qubes.qubes, qubesmanager.block; qvmc = qubes.qubes.QubesVmCollection(); qvmc.lock_db_for_reading(); qvmc.load(); qvmc.unlock_db(); blkman = qubesmanager.block.QubesBlockDevicesManager(qvmc); print([(k, v["attached_to"]) for k, v in blkman.attached_devices.items()]);'

?

--
best regards,
WZJP

On Thu, Sep 18, 2014 at 1:05 PM, Wojciech Zygmunt Porczyk

<wojc...@porczyk.eu> wrote:
> On Thu, Sep 18, 2014 at 10:06:39AM +0000, Hakisho Nukama wrote:
>> On Thu, Sep 18, 2014 at 9:58 AM, Wojciech Zygmunt Porczyk
>> <wojc...@porczyk.eu> wrote:
>> > On Thu, Sep 18, 2014 at 08:54:36AM +0000, Hakisho Nukama wrote:
>> >> Hey,
>> >>
>> >> this error showed up and qubes-manager got frozen.
>> >>
>> >> The journalctl output is from the timestamp of my screenshot, so it
>> >> might be correlated.
>> >
>> > Could you post whole "show details" contents and which version of
>> > qubes-manager you are running?
>>
>> I'm running qubes-manager 2.0.35.
>> I couldn't hit "show details" as qubes-manager was not responsive.
>
> 1) Has it happened when you right-clicked qubes-manager icon in systray?
>

Maybe, I was working with some winvms, and was killing/deleting/creating them.

> 2) Has it happened randomly or you can reproduce it? (don't reboot to check yet)
>

Happened randomly, as far as I can tell.
Sorry, I've rebooted two days ago. Next time I'll try to leave it as
it is, but I couldn't kill
qubes-manager and had some work to do..
And one of my winvms had a full screen window appear, but I couldn't
close it and therefore I rebooted.

Are there steps, I can run, when I encounter another error in qubes-manager?

Maybe we need some *separate* qubes-generate-report tool, that is
collecting all information useful for debugging
problems from appvms and dom0.

> 3) Hard to tell without trace, but I guess it has something to do with
> attached block devices. Attribute "name" in this code path is in context
> of vm = QubesVmCollection.get_vm_by_name(name), name is from block
> device manager.
>
> Could you post result of qvm-block and then from this command (this will
> list block devices and names of vms they're attached to, as seen by
> qubesmanager):
>

I've symlnked my private.img files to my ZFS filesystem under /mnt/qubes:
dom0:sdc    59 GiB
dom0:loop24    /mnt/qubes/appvms/1/private.img 63 GiB (attached to '1'
as 'xvdb')
dom0:loop27    /mnt/qubes/appvms/2/private.img 320 GiB (attached to
'2' as 'xvdb')
dom0:loop10    /mnt/qubes/appvms/3/private.img 2 GiB (attached to '3' as 'xvdb')
dom0:sdc2    59 GiB
dom0:sdc1    500 MiB
dom0:loop21    /mnt/qubes/appvms/4/private.img 16 GiB (attached to '4'
as 'xvdb')
dom0:loop17    /mnt/qubes/appvms/5/private.img 16 GiB (attached to '5'
as 'xvdb')
dom0:loop19    /mnt/qubes/appvms/personal/private.img 32 GiB (attached
to 'personal' as 'xvdb')
dom0:loop9    /mnt/qubes/appvms/3/root.img 512 GiB (attached to '3' as 'xvda')
dom0:loop29    /mnt/qubes/appvms/storage/private.img 2048 GiB
(attached to 'storage' as 'xvdb')

>   python -c 'import qubes.qubes, qubesmanager.block; qvmc = qubes.qubes.QubesVmCollection(); qvmc.lock_db_for_reading(); qvmc.load(); qvmc.unlock_db(); blkman = qubesmanager.block.QubesBlockDevicesManager(qvmc); print([(k, v["attached_to"]) for k, v in blkman.attached_devices.items()]);'

AttributeError: QubesBlockDeviceManager instance has no attribute
'attached_devices'

>
> ?
>
> --
> best regards,
> WZJP

Best Regards,
Nukama

I have some debugging patch in
http://git.woju.eu/qubes/qubes-manager.git branch debug, which more or
less allows to break qubes-manager into python debugger, but it requires
qubes-manageer to be started from console _before_ encountering
particular bug. Requires some knowledge of qubes-manager code and at
least basic python, so it remains in a branch and is not included in

> Maybe we need some *separate* qubes-generate-report tool, that is
> collecting all information useful for debugging
> problems from appvms and dom0.

Maybe, but bug reports will invariably reveal much of the particular
qubes install, so people may not like to post them anyway to ticket
tracker. For the record, https://wiki.qubes-os.org/ticket/901, left for
Joanna to assign when it will be done. :)
My error. should be "attached_devs". Now useless, I suspected that I saw
None (of NoneType) somewhere there. Definitely not an universal recovery
tool, just test case for this particular code path.

Thank you for cooperation.


--
best regards,
WZJP