Backup Qubes error: QubesDaemonNoResponseError

User Support
1

Hello,
I have an issue when I want to backup my qubes. This is the first time I use this software, perhaps I do something wrong.

I have try to backup only one or all vm in the same time and I still have an issue.

With the GUI, when I click next after the window when I enter password and path I have a message :
“Whoops. Acritical error has occured. This is most likely a bug in Qubes Global Settings application.
QubesDaemonNoResponseError: Got empty response from qubesd. See journalctl in dom for details.atline 81 of file base.py.”

By cli I have the same issue : “Backup preparation error :Got empty response from qubesd. See journalctl in dom for details”

In the last message of journalctl I see python traceback :
unhandled exception while calling src=b’dom0’ meth=b’admin.backup.Info’ dest=b’dom0’ …
…
AssertionError: nested calls to export()

It’s too long to write everything and I cannot copy paste because it’s in dom0.

The hard drive is mounted in an appvm and luks is used on it. I have tried with ext4 + luks and btrfs + luks…
What I am doing wrong ?

Thank you for your help.

2

Do you have dom0 updated to the latest version? Perhaps you could show the text from Qube Manager - About - Version Information.

3

I have updated this morning and it’s the R4.0.
qubes-core-dom0.x86_64 4.0.56-1.fc25

4

You can click on Qubes Clipboard in the system tray and choose “Copy dom0 clipboard”.

5

Thank you.
Here you will find error when I want to backup a small sized vm to a directory in dom0 :

Feb 14 20:11:55 dom0 qubesd[3091]: unhandled exception while calling src=b'dom0' meth=b'admin.backup.Execute' dest=b'dom0' arg=b'qubes-
Feb 14 20:11:55 dom0 qubesd[3091]: Traceback (most recent call last):
Feb 14 20:11:55 dom0 qubesd[3091]:   File "/usr/lib/python3.5/site-packages/qubes/api/__init__.py", line 275, in respond
Feb 14 20:11:55 dom0 qubesd[3091]:     untrusted_payload=untrusted_payload)
Feb 14 20:11:55 dom0 qubesd[3091]:   File "/usr/lib64/python3.5/asyncio/futures.py", line 381, in __iter__
Feb 14 20:11:55 dom0 qubesd[3091]:     yield self  # This tells Task to wait for completion.
Feb 14 20:11:55 dom0 qubesd[3091]:   File "/usr/lib64/python3.5/asyncio/tasks.py", line 310, in _wakeup
Feb 14 20:11:55 dom0 qubesd[3091]:     future.result()
Feb 14 20:11:55 dom0 qubesd[3091]:   File "/usr/lib64/python3.5/asyncio/futures.py", line 294, in result
Feb 14 20:11:55 dom0 qubesd[3091]:     raise self._exception
Feb 14 20:11:55 dom0 qubesd[3091]:   File "/usr/lib64/python3.5/asyncio/tasks.py", line 240, in _step
Feb 14 20:11:55 dom0 qubesd[3091]:     result = coro.send(None)
Feb 14 20:11:55 dom0 qubesd[3091]:   File "/usr/lib/python3.5/site-packages/qubes/api/admin.py", line 1487, in backup_execute
Feb 14 20:11:55 dom0 qubesd[3091]:     backup = yield from self._load_backup_profile(self.arg)
Feb 14 20:11:55 dom0 qubesd[3091]:   File "/usr/lib/python3.5/site-packages/qubes/api/admin.py", line 1461, in _load_backup_profile
Feb 14 20:11:55 dom0 qubesd[3091]:     **kwargs)
Feb 14 20:11:55 dom0 qubesd[3091]:   File "/usr/lib/python3.5/site-packages/qubes/backup.py", line 353, in __init__
Feb 14 20:11:55 dom0 qubesd[3091]:     self._files_to_backup = self.get_files_to_backup()
Feb 14 20:11:55 dom0 qubesd[3091]:   File "/usr/lib/python3.5/site-packages/qubes/backup.py", line 373, in get_files_to_backup
Feb 14 20:11:55 dom0 qubesd[3091]:     volume.export(),
Feb 14 20:11:55 dom0 qubesd[3091]:   File "/usr/lib/python3.5/site-packages/qubes/storage/file.py", line 272, in export
Feb 14 20:11:55 dom0 qubesd[3091]:     'nested calls to export()'
Feb 14 20:11:55 dom0 qubesd[3091]: AssertionError: nested calls to export()
6

(@anon42940733 added some markdown formatting to your last post and changed the title for clarity. I hope that’s fine)

7

Hi @anon42940733 ,

May be your backup profile setting file is corrupted, check the content of the below file (vm list, destination_path, …) if you see something wrong…

[userdom0 ~]$ sudo vim /etc/qubes/backup/qubes-manager-backup.conf
8

Thank you, I will do that next time I post a message.

1 Like
9

I find a solution here :

I do an update from the testing repo and the problem was solved.

Also, some vm were ‘dirty’, I solve this issue by starting the qube and shutdown it properly.
Another thing for noob like me is you cannot make a backup of a running qube except for dom0.

Thank you everyone.

2 Likes