-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Containers do not start due to multiple IP addresses:
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]
Logfiles:
Docker Container logs can be found:
/var/lib/docker/containers
Or more easily type:
docker container logs [container id]
XNAT logfiles are located in:
[STORAGE PATH]/xnat/tomcat_log
The default _STORAGE PATH _is /xnat-data/ and is set in the xnat.cfg configuration file. When an error occurs, it is good to check the log files by modified date/time to see the latest files which may indicate the source of the error.
Nginx log files can be found in:
[STORAGE PATH]/xnat/nginx_logs
Postgresql Database debugging
Occasionally when starting XNAT, an sql error may occur. This will be found in /xnat-data/xnat/tomcat_logs/sql.log. You may have to reindex the database:
sudo [install path]/xnat-setup/docker/docker-bash.sh (if connecting to Dockerised XNAT)
psql -U xnat
\connect xnat
REINDEX DATABASE xnat;
Nginx errors
Error log files can be found in /var/log/nginx/
If the browser returns an 501 error or nothing:
Check to see if all docker containers are running:
docker ps
All three containers should be running - xnat-stack_xnat-nginx, xnat-stack_xnat-db, xnat-stack_xnat-web.
Try restarting tomcat:
cd [install dir]/Linux
sudo ./restart_tomcat.sh
If this does not solve the issue:
sudo ./restart.sh
If this still does not resolve the issue, check the tomcat_log and nginx_log files. Check the docker container logs, useful for containers that crash immediately. Check for possible issues with the server - space remaining, etc.