Qubes does not work anymore, only have access to dom0

[juana23...@gmail.com]

r/Qubes
•Posted byu/dom0help
11 minutes ago
Qubes does not work anymore, only have access to dom0

Hi, Qubes0S was working perfectly until yesterday, I turned the machine on today and nothing works, a dom0 terminal is open on start (this didn't happen before), no VMs start, clicking on Qubes Global Settings give me the error

QubesDaemonCommunicationError: Failed to connect to qubesd service: [Errrno 2] No such file or directory at line 543 of file app.py

Tried updating dom0 and get some similar error about not connecting to qubesd service

Is this because without any VMs working, including NetVMs, there is no internet connection? I have no idea what happened, I just don't want to lose all my VMs, is there any way of doing a manual backup and just reinstalling?

[awokd]

juana23...@gmail.com wrote on 4/28/19 10:42 AM:

Look for qubesd related errors in 'sudo journalctl -b'.

[juana23...@gmail.com]

Tried it, I don't see any at least from what I can understand, I can't copy the output since I'm using another pc to post here, I could take photos of the screen and post them here?

[juana23...@gmail.com]

If it helps when I restart it tells me to check systemctl status qubesd.service

When I put that on terminal I do get errors

qubesd.service - Qubes OS daemon
Loaded: loaded (/usr/lib/systemd/system/qubesd.service; enabled; vendor preset; enabled)
Active: failed (Result: start-limit-hit) since Sun 2019-04-28 06:25:27 EDT; 54min ago
Process: 3939 ExecStart=/usr/bin/qubesd (code=existed, status=1/FAILURE)
Main PID: 3939 (code=exited, status=1/FAILURE)

Apr 28 06:25:26 dom0 systemd[1]: Failed to start Qubes OS daemon.
Apr 28 06:25:26 dom0 systemd[1]: qubesd.service: Unit entered failed state.
Apr 28 06:25:26 dom0 systemd[1]: qubesd.service: Failed qith result 'exit-code'.
Apr 28 06:25:26 dom0 systemd[1]: qubesd.service: Service hold-off time over, scheduling restart.
Apr 28 06:25:26 dom0 systemd[1]: Stopped Qubes OS daemon.
Apr 28 06:25:26 dom0 systemd[1]: qubesd.service: Start request repeated too quickly.
Apr 28 06:25:26 dom0 systemd[1]: Failed to start Qubes Os daemon.
Apr 28 06:25:26 dom0 systemd[1]: qubesd.service Uniter entered failed state
Apr 28 06:25:26 dom0 systemd[1]: qubesd.service: Failed with result 'start-limit-hit'.

[awokd]

juana23...@gmail.com wrote on 4/28/19 11:35 AM:

> If it helps when I restart it tells me to check systemctl status qubesd.service
>
> When I put that on terminal I do get errors
>
> qubesd.service - Qubes OS daemon
> Loaded: loaded (/usr/lib/systemd/system/qubesd.service; enabled; vendor preset; enabled)
> Active: failed (Result: start-limit-hit) since Sun 2019-04-28 06:25:27 EDT; 54min ago
> Process: 3939 ExecStart=/usr/bin/qubesd (code=existed, status=1/FAILURE)
> Main PID: 3939 (code=exited, status=1/FAILURE)
>
> Apr 28 06:25:26 dom0 systemd[1]: Failed to start Qubes OS daemon.
> Apr 28 06:25:26 dom0 systemd[1]: qubesd.service: Unit entered failed state.
> Apr 28 06:25:26 dom0 systemd[1]: qubesd.service: Failed qith result 'exit-code'.
> Apr 28 06:25:26 dom0 systemd[1]: qubesd.service: Service hold-off time over, scheduling restart.
> Apr 28 06:25:26 dom0 systemd[1]: Stopped Qubes OS daemon.
> Apr 28 06:25:26 dom0 systemd[1]: qubesd.service: Start request repeated too quickly.
> Apr 28 06:25:26 dom0 systemd[1]: Failed to start Qubes Os daemon.
> Apr 28 06:25:26 dom0 systemd[1]: qubesd.service Uniter entered failed state
> Apr 28 06:25:26 dom0 systemd[1]: qubesd.service: Failed with result 'start-limit-hit'.
>

That looks right. Check for "Qubes OS daemon" related errors in the log
again; should be shortly before where you see the above.

You can also try 'sudo systemctl start qubesd' to do it manually, then
check the end of the log.

[juana23...@gmail.com]

sudo systemctl start qubesd outputs this
Job for qubesd.service failed because the control process exited with error code.
See "systemctl status qubesd.service" and "journalctl -xe" for details
.

sudo journalctl -b outputs 3200 lines of code of which I understand none, here are the first 3 images where the error appears, or here you can see the 90 images of the complete output but it's too much https://www.dropbox.com/sh/cf76o849zxepwd0/AAAytY5-KPCEY6UJsU3DhFE5a?dl=0

[awokd]

juana23...@gmail.com:

Don't care about all the lines, just qubesd related errors. They were in
your third attached screenshot. It says you don't have a default
template assigned. What does qubes-prefs show for it? Try setting it to
a known good template with 'qubes-prefs default_template debian-9' if
you have that one installed, then start the qubesd service again or reboot.

[juana23...@gmail.com]

I have no idea why the photo doesn't show now, I'll just copy it

qubes-prefs outputs
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/qubesadmin/app.py", line 540, in qubesd_call
client_socket.connect(qubesadmin.config.QUBESD_SOCKET)
FileNotFoundError:[Errno 2] No such file or directory

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/bin/qubes-prefs", line 5, in <module>
sys.exit(main())
File "/usr/lib/python3.5/site-package/qubesadmin/tools/qubes_prefs.py", line 42, in main
return qubesadmin.tools.qvm_prefs.process_actions(parser, args, target)
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_prefs.py, line 93, in process_actions
properties = target.property list()
File "/usr/lib/python3.5/site-packages/qubesadmin/base.py", line 117, in property_list
None)
File "/usr/lib/python3.5/site-packages/qubesadmin/app.py", line 543, in qubesd_call
"Failed to connect to qubesd service: %s", srt(e))
qubesadmin.exc.QubesDaemonCommunicationError: Failed to connect to qubesd service: [Errno 2] No such file or directory



And qubes-prefs default_template debian-9 (I did check that I have debian-9 installed)

qubes-prefs: error: Failed to connect to qubesd service: [Errno 2] No such file or directory

[awokd]

juana23...@gmail.com:

> And qubes-prefs default_template debian-9 (I did check that I have debian-9 installed)
>
> qubes-prefs: error: Failed to connect to qubesd service: [Errno 2] No such file or directory
>

Well that's not going to do us much good if we need to have it running
to fix an error.

Try this approach:
nano /var/lib/qubes/qubes.xml
Look for the property name="default_template" line towards the top, what
is it set to?
If it doesn't look right, change it to:
<property name="default_template">debian-9</property>
Ctrl-X to exit, save changes
Reboot

[juana23...@gmail.com]

I did that, the default and netvms had nothing set to them, I fixed that now, I know how to use nano so I'm sure that's ok now, but the qubes-prefs command keeps giving me the same error.

Qubesd it's still not starting (if I'm following this right)

[juana23...@gmail.com]

FIXED IT! I change again the default netvm from sys-whonix to sys-net, I don't know what the problem with sys-whonix is yet but I think I can take ti from here, THANKS A LOT!

[awokd]

juana23...@gmail.com:

I think it must have been a combination of things. Those entries in
qubes.xml definitely should not have been empty. Glad you got it working!