[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.
--
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/8314bf81-544c-d188-7415-6cf033d1bfad%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.
