-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sys-whonix launch error #3469
Comments
@adrelanos which part of this output is unexpected? |
Should be disabled by: https://github.com/Whonix/sdwdate/blob/master/debian/sdwdate.postinst
The question is what re-enabled it? |
I guess here: https://github.com/QubesOS/qubes-core-agent-linux/blob/master/vm-systemd/75-qubes-vm.preset#L97 But there is also https://github.com/QubesOS/qubes-core-agent-linux/blob/master/vm-systemd/systemd-timesyncd.service.d/30_qubes.conf, which should prevent starting the service everywhere but sys-net. @mossy-nw can you check if the service is really running? |
Sure. In sys-whonix, correct?
So it's loaded (enabled) but inactive (dead)? I'm not sure if this means it's really running or no. Thanks! |
FWIW it's running identically in sys-net:
also running in sys-usb:
and in an offline (via
so looks like the service is starting everywhere. |
|
According to systemd/systemd#1329 (comment), |
Marek Marczykowski-Górecki:
According to systemd/systemd#1329 (comment), `sdwdate.service` should have `Conflicts=systemd-timesyncd.service`
It has.
https://github.com/Whonix/sdwdate/blob/master/lib/systemd/system/sdwdate.service#L17
Conflicts=systemd-timesyncd.service
|
Should be really running there... As you can see, there is no "start condition failed", so it was prevented by something else. Can't find anything related in logs. |
I don't see this issue anymore in R4.0_rc4, so is it OK to close this issue? Don't want to close it if you all are still wanting to follow up on this or related things. Thanks! |
Sorry everyone @marmarek @andrewdavidwong @adrelanos it looks like on a fresh R4.0_rc4 install the original |
There was no update. Will be fixed in Whonix 14.
|
Wonderful. Thank you for all the work and care you take on this project! |
@adrelanos Another thing to note is that this commit hasn't made it to the current/stable repository. All of my Whonix VMs are up to date, and yet I was initially unable to hide the error because I was missing the When will those changes make it to the stable repo, or equivalently, how far away is Whonix 14? |
What is the workaround here? I updated earlier today and now I can't start VMs, breaking my workflow. |
Just to clarify - is it sys-whonix not starting at all, or displaying "Unexpected results by timedatectl" error message after the startup? The latter looks scary, but is a false positive (see discussion above) and in fact shouldn't break anything. |
It's displaying the error message and the VM starts, but connectivity in that VM appears to be broken:
There's a chance this is a coincidence (saying this because I haven't had time to do a root cause and figure out whether the issues are related), but the issues started happening at the same time and I never had connectivity issues with whonix VMs prior. My other VMs/templates are unaffected. |
This very issue #3469 certainly (and I say that seldom) is only a false positive graphical user interface message warning. For everything else, please create new issues. |
status of Whonix 14 development:
https://www.whonix.org/wiki/Upgrading_Whonix_13_to_Whonix_14 |
Fixed in Whonix 14. Close please. |
Qubes OS version:
R4.0_rc3
Affected TemplateVMs:
whonix-gw
Steps to reproduce the behavior:
launch sys-whonix
Expected behavior:
sys-whonix should start without errors
Actual behavior:
whonix seems to be working normally, but gives a popup error:
General notes:
apologies if this is a bug that should be reported directly to Whonix devs instead of QubesOS
Related issues:
The text was updated successfully, but these errors were encountered: