-
Notifications
You must be signed in to change notification settings - Fork 5
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
Added recovery steps for common install errors #31
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -31,6 +31,9 @@ In order to install SecureDrop Workstation and configure it to use an existing S | |
|
||
- A Qubes-compatible computer with at least 16GB of RAM (32 GB is recommended). SecureDrop Workstation has mainly been tested against Lenovo 6th-gen T480 and X1 models - see Qubes' `Hardware Compatibility List <https://www.qubes-os.org/hcl/>`_ and the SecureDrop Workstation :doc:`hardware` page for more options . | ||
- Qubes installation medium - this guide assumes the use of a USB 3.0 stick. Qubes may also be installed via optical media, which may make more sense depending on your `security concerns <https://www.qubes-os.org/doc/install-security/>`_. | ||
|
||
.. note:: A USB stick with a Type-A connector is recommended, as USB-C ports may be disabled on your computer when the BIOS settings detailed below are applied. | ||
|
||
- The SecureDrop instance's Admin Workstation and Secure Viewing Station (SVS) USBs, and the full GPG fingerprint of the submission key. | ||
- A working computer (Linux is recommended and assumed in this guide) to use for verification and creation of the Qubes installation medium. | ||
- A password manager or other system to generate and store strong passphrases for Qubes full disk encryption (FDE) and user accounts. | ||
|
@@ -337,6 +340,56 @@ To start the SecureDrop Workstation client, double-click the SecureDrop desktop | |
|
||
Once the update check is complete, the client will launch. Log in using an existing journalist account and verify that sources are listed and submissions can be downloaded, decrypted, and viewed. | ||
|
||
Troubleshooting installation errors | ||
----------------------------------- | ||
|
||
"Recurse failed: none of the specified sources were found" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Note that this is expected to be resolved by freedomofpress/securedrop-workstation#530 but until that makes its way into a release (and we've verified that the issue no longer occurs) it makes sense to document this. |
||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
An error similar to the following may be displayed during the installation, after which the installation will fail: | ||
|
||
.. code-block:: none | ||
|
||
______ID: dom0-securedrop-launcher-directory | ||
Function: file.recurse | ||
Name: /opt/securedrop/launcher | ||
Result: False | ||
Comment: Recurse failed: none of the specified sources were found | ||
Started: 20:52:46.766870 | ||
Duration: 2.371 ms | ||
Changes: | ||
|
||
To clear this error, clear the Salt cache and resynchronize by running the following commands in a ``dom0`` terminal: | ||
|
||
.. code-block:: sh | ||
|
||
sudo rm -rf /var/cache/salt | ||
sudo qubesctl saltutil.sync_all refresh=true | ||
|
||
Then, run ``securedrop-admin --apply`` again. | ||
|
||
"Failed to return clean data" | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
An error similar to the following may be displayed during an installation or update: | ||
|
||
.. code-block:: none | ||
|
||
sd-log: | ||
---------- | ||
_error: | ||
Failed to return clean data | ||
retcode: | ||
None | ||
stderr: | ||
stdout: | ||
deploy | ||
|
||
This is a transient error that may affect any of the SecureDrop Workstation VMs. To clear it, run the installation command or update again. | ||
|
||
"Temporary failure resolving" | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
Transient network issues may cause an installation to fail. To work around this, verify that you have a working Internet connection, and re-run the ``securedrop-admin --apply`` command. | ||
|
||
Uninstalling SecureDrop Workstation | ||
----------------------------------- | ||
To uninstall SecureDrop Workstation, open a ``dom0`` terminal and run the following command: | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO if we are borking USB-C we should consider if those BIOS settings are too aggressive instead of considering this a standard troubleshooting issue / hardware restriction to carry forward with us indefinitely.