Updater Troubleshooting
These are pretty generic "something went wrong" logs, but a good place to start because they will tell you which VM(s) being provisioned saw an error. Once you know which VM saw an error, you can look at the Salt provisioning logs to learn more.
In dom0, check:
journalctl -f
tail -f ~/.securedrop_launcher/logs/launcher.log
tail -f ~/.securedrop_launcher/logs/launcher-detail.log
These are the logs from the disposable VMs that are used for Salt provisioning during a run of the SDW Updater.
In dom0, check: /var/log/qubes/mgmt-*
In addition, if the dom0 file manager thunar has been initialized, you may be able to find logs in journalctl. To follow the logs while an update is running, type: journalctl -f | grep FileManager
In dom0, check: ~/.securedrop_launcher/sdw-last-updated
In dom0, run: /opt/securedrop/launcher/sdw-launcher.py --skip-delta 0
If your timezone isn't set correctly in Qubes, the SDW Updater may fail with a Salt provisioning log message such as this:
2020-06-30 14:54:52,993 output: Comment: E: Release file for https://deb.debian.org/debian-security/dists/buster/updates/InRelease is not valid yet (invalid for another 6min 44s). Updates for this repository will not be applied.
Or
2020-06-30 14:54:52,993 output: Comment: E: Release file for https://apt-test.freedom.press/dists/buster/InRelease is not valid yet (invalid for another 1min 18s). Updates for this repository will not be applied.
To set your timezone correctly in Qubes, follow these steps: https://www.qubes-os.org/doc/change-time-zone/. You'll also need to set the system clock in the Qubes settings panel in the upper right-hand corner by following these steps:
- Right click on the OS clock in the Qubes panel and select "Properties"
- Type in your timezone in the timezone field. To see a list of options, run
sudo timedatectl list-timezonesindom0.