Viktor Ransmayr schrieb am Sonntag, 7. November 2021 um 13:07:14 UTC+1:
> I've installed Whonix 16 on my Qubes OS R4.0 system - and - have switched
> 'sys-whonix' to 'whonix-gw-16' as well as 'anon-whonix' to 'whonix-ws-16'.
>
> Everything seems to work fine - but - Qubes Updater reports that updates
> are available for 'whonix-[gw | ws]-16' but always fails to update the
> templates with error msgs similar to
>
> ###
>
> Updating whonix-gw-16
>
> Error on updating whonix-gw-16: Command '['sudo', 'qubesctl',
> '--skip-dom0', '--targets=whonix-gw-16', '--show-output', 'state.sls',
> 'update.qubes-vm']' returned non-zero exit status 20
> whonix-gw-16:
> ----------
> ID: update
> Function: pkg.uptodate
> Result: False
> Comment: E: Release file for tor+
> https://fasttrack.debian.net/debian/dists/bullseye-fasttrack/InRelease is
> not valid yet (invalid for another 14min 36s). Updates for this repository
> will not be applied.
> Started: 11:15:16.396556
> Duration: 8366.294 ms
> Changes:
> ----------
> ID: notify-updates
> Function: cmd.run
> Name: /usr/lib/qubes/upgrades-status-notify
> Result: False
> Comment: Command "/usr/lib/qubes/upgrades-status-notify" run
> Started: 11:15:24.765086
> Duration: 2514.791 ms
> Changes:
> ----------
> pid:
> 1782
> retcode:
> 100
> stderr:
> stdout:
>
> Summary for whonix-gw-16
> ------------
> Succeeded: 0 (changed=1)
> Failed: 2
> ------------
> Total states run: 2
> Total run time: 10.881 s
>
> Updating whonix-ws-16
>
> Error on updating whonix-ws-16: Command '['sudo', 'qubesctl',
> '--skip-dom0', '--targets=whonix-ws-16', '--show-output', 'state.sls',
> 'update.qubes-vm']' returned non-zero exit status 20
> whonix-ws-16:
> ----------
> ID: update
> Function: pkg.uptodate
> Result: False
> Comment: E: Release file for tor+
> https://fasttrack.debian.net/debian/dists/bullseye-fasttrack/InRelease is
> not valid yet (invalid for another 16min 48s). Updates for this repository
> will not be applied.
> Started: 11:13:10.907970
> Duration: 2607.219 ms
> Changes:
> ----------
> ID: notify-updates
> Function: cmd.run
> Name: /usr/lib/qubes/upgrades-status-notify
> Result: False
> Comment: Command "/usr/lib/qubes/upgrades-status-notify" run
> Started: 11:13:13.517469
> Duration: 2907.295 ms
> Changes:
> ----------
> pid:
> 1789
> retcode:
> 100
> stderr:
> stdout:
>
> Summary for whonix-ws-16
> ------------
> Succeeded: 0 (changed=1)
> Failed: 2
> ------------
> Total states run: 2
> Total run time: 5.515 s
>
> ###
>
> What are the recommended steps to resolve this issue?
>
> With kind regards,
>
> Viktor
>
> PS: I obviously tried this several time - but - the error msg stays the
> same - only - with changing "invalid for ..." times ...
>
This time I have new information on the reported issue. - Template updates
were reported for 'fedora-33' as well as 'whonix-gw-16'.
I started Qubes Updater w/o adjusting the time in both templates. - The
update of 'fedora-33' succeeded, while 'whonix-gw-16' failed.
Relevant log from 'fedora-33':
Updating fedora-33
fedora-33:
----------
ID: dnf-and-rpm
Function: pkg.installed
Result: True
Comment: All specified packages are already installed and are at
the desired version
Started: 17:24:48.153995
Duration: 1836.538 ms
Changes:
Relevant log from 'whonix-gw-16':
Updating whonix-gw-16
Error on updating whonix-gw-16: Command '['sudo', 'qubesctl',
'--skip-dom0', '--targets=whonix-gw-16', '--show-output', 'state.sls',
'update.qubes-vm']' returned non-zero exit status 20
whonix-gw-16:
----------
ID: update
Function: pkg.uptodate
Result: False
Comment: E: Release file for
tor+https://fasttrack.debian.net/debian/dists/bullseye-fasttrack/InRelease
is not valid yet (invalid for another 33min 20s). Updates for this
repository will not be applied.
Started: 16:26:39.418126
Duration: 14041.933 ms
Changes:
The difference is that 'fedora-33' is using CET, while 'whonix-gw-16' is
using UTC.
If I set the time in the 'whonix-gw-16' template to the current CET value,
the update succeeds ...
Relevant log from 'whonix-gw-16':
Updating whonix-gw-16
whonix-gw-16:
----------
ID: update
Function: pkg.uptodate
Result: True
Comment: Upgrade ran successfully
Started: 17:55:42.134676
Duration: 24195.111 ms
Changes:
I don't want to adjust the time for the two Whonix templates manually to
the (wrong?) CET values, whenever an update is necessary.
I don't think I had this issue with Whonix 15 & believe it only started
with Whonix 16.
Do you have any ideas or suggestions?
With kind regards,
Viktor
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/ae9c192f-4348-442c-9f50-c7538991c3edn%40googlegroups.com.
