-
Notifications
You must be signed in to change notification settings - Fork 1
Install Troubleshooting
Home | Installation Guide | User Guide | Admin Guide | User Tests
- The firewall prevents DASHER building successfully
- The Uploader builds but is not accessible on the browser
- Containers do not start on Windows
- Containers do not start - "Error initializing swarm: could not choose an IP address"
- Container cannot connect to outside world
- Logging in Issues with the pseudonymised XNAT server
The build script needs to download data from dockerhub and ubuntu websites. If your firewall blocks this, an error will appear in the build process. If you are unable to bypass the firewall, it is possible to build DASHER on a computer with access to the internet and then move DASHER to the computer behind the firewall.
On the computer with unrestricted access, follow the instructions on the wiki, installing docker etc. In the xnat.cfg file, make sure that xnat_host= is set to the ip address of the computer you intend to use, not the computer you are building DASHER on! Run build.bat (windows) or build.sh (linux). When the build script is complete, On Windows run:
save_and_restore.bat save
or on linux:
save_and_restore.sh save
A directory ./backup will be created. On the computer behind the firewall, install the dependencies (Docker) and get DASHER code. Do not run the build script. Instead copy the backup directory from the old computer to DASHER directory of the new computer. Run:
save_and_restore.bat restore
or on linux
save_and_restore.bat restore
The Uploader should start.
Do not use xnat_host=http://localhost. It may work but often not accesible via localhost. Sometimes http://127.0.0.1 will work.
Check to see if other software is running on the host that may conflict with DASHER, for example httpd or nginx. A server may already be running and preventing DASHER using the url and ports.
It is likelt to be a problem reading windows paths. To solve:
- Open cmd terminal
- Run the command "set COMPOSE_CONVERT_WINDOWS_PATHS=1"
- Restart Docker
- Go to Settings > Shared Drives > Reset credentials and then select drive and then apply
- From the command line, kill the containers (docker container rm -f )
- Run .\Windows\restart_and_clean.bat.
The build.sh will have to be edited to allow docker to choose the IP address of the host. Replace the following line:
docker swarm init
with
docker swarm init --advertise-addr [IP address]
- Usually this is a DNS error due to corporate networks and apt-get (or yum) fails during the build. Try changing the DNS server to fixed (8.8.8.8) and restarting Docker. On windows this can be done in the setti ng panel, as shown below:
After reinstalling the Uplaoder you may have trouble logging into the pseudonmyised XNAT server. Under your broswer settings, select clear cookies. This should fix this issue.
Navigate: Home | Installation Guide | User Guide | Admin Guide | User Tests
New Pages:
- Test Release Version 4 Notes
- First time install on Windows
- First time install on Linux
- Updating DASHER on Windows
- Updating DASHER on Linux
- Editing xnat.cfg
- Building DASHER on Windows
- Building DASHER on Linux
- Installing the Processing Pipelines
- Setting up XSync
- Troubleshooting
- Logging in to the Servers
- Overview of DASHER
- Importing Data into DASHER
- Pseudonymising Data
- Uploading Data to a Remote Server
- Exporting Data from DASHER
- The QUARANTINE Project
- Create and Edit Users
- Adding Clinical Trials
- Managing the QUARANTINE Project
- Setting Quarantine Protocol
- Adding a Project for Local Research
- Adding a Project for a Remote Server
- Changing the Pseudonymisation
- Installing SSL Certificates
- Maintenance
- Download Test Data
- Installing DASHER
- Installing Plugins
- Adding Clinical Trial
- Creating a New User
- Importing Data into DASHER
- Pseudonymising Data 1
- Export Pseudonymised Data Locally
- Upload Data (XSync)
- Import - DICOM push
- Import - Duplicate
- Import - Single RTSTRUCT
- Import - Quarantine
- Pseudonymise - Edits
- Pseudonymise - Missing structure
- Pseudonymise - Local research
- Restarting Docker