[email protected]:
El domingo, 28 de abril de 2019, 8:57:14 (UTC-3), awokd escribió:
[email protected] 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.
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
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.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/ca3d8bff-8351-da10-3c33-4c7efe64ef23%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.
