managed the download on 4.0.4 in the last days without any issues. Just did 
it with the qubes-dom0-update command and the enablerepo=community switch. 
No other commands or work. It just went through like it always do with 
downloads & installs of new templates.
Sorry, if I couldn't help more.

viktor....@gmail.com schrieb am Dienstag, 9. November 2021 um 14:49:04 
UTC-5:

> Viktor Ransmayr schrieb am Sonntag, 7. November 2021 um 19:53:54 UTC+1:
>
>> Hello 'unman',
>>
>> unman schrieb am Sonntag, 7. November 2021 um 15:36:50 UTC+1:
>>
>>> On Sun, Nov 07, 2021 at 04:07:13AM -0800, Viktor Ransmayr wrote: 
>>> > 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 ... 
>>> > 
>>>
>>> Fix the time on your update qube,( and possibly your target). It is, as 
>>> you can see, wrong. 
>>>
>>
>> Thanks a lot for your feedback! - Using 'timedatectl set-time ...' for  
>> 'whonix-[gw | ws]-16' did resolve the issue.
>>
>> I started to read more on this topic now - but - did not (yet) find best 
>> practice recommendations on how to ensure that AppVMs & TemplateVMs are 
>> time-synced automatically, when they are started.
>>
>> Do you have any recommendation?
>>
>
> Any recommendation from someone in the community?
>
> 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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/60475ee5-267b-4944-83b8-968cae637c1an%40googlegroups.com.

Reply via email to