ezpect:
“qrexec.exc.ExecutionFailed: qrexec-client failed: [‘/usr/lib/qubes/qrexec-client’ .”
This is basically what it says everywhere i look (Not everywhere, I meant when I see an error - it is this one), when it comes to errors, but I also do get a lot of:
If you shutdown all your qubes with blockchain nodes will you still see these errors?
ezpect
December 13, 2023, 8:00pm
22
In dom0. Maybe I should have done it in both? Why? I’ll do it once I use the qubes computer tomorrow again.
ezpect
December 13, 2023, 8:01pm
23
I have not checked. I don’t think so necessarily since the blockchain qube for example was running (I was installing bitcoin core) and it was allowed Qrexec access then and there. Why? I can check that as well.
qrexec-agent is only used in VMs:
(This page is about qrexec v3. For qrexec v2, see here.) The qrexec framework is used by core Qubes components to implement communication between domains. Qubes domains are strictly isolated by design. However, the OS needs a mechanism to allow the...
There was a comment that running monero blockchain in qube could cause these errors:
The plot just seemed to show that qubesd.service took over 15 minutes again.
journalctl -u qubesd.service
gave helpful info though, for each reboot major stalls occur with this each time:
May 29 21:30:33 dom0 systemd[1]: Starting Qubes OS daemon...
May 29 21:35:06 dom0 qubesd[1974]: Reflinked file: '/var/lib/qubes/appvms/crypto/private.img' -> '/var/lib/qubes/appvms/crypto/private.img.44@2023-05-30T03:56:38Z~j3nypgxl'
May 29 21:35:09 dom0 qubesd[1974]: Renamed file: '/var/lib/qubes/appvms/c…
1 Like
