-
Notifications
You must be signed in to change notification settings - Fork 16
Troubleshooting FAQS
If none of these solutions worked, feel free to message one of the managers/leads and ask for their assistance.
Permission not allowed.
Solution:
On Linux, use the keyword sudo before the command. On Windows, run the terminal as an administrator.
Port 80 is already being used by another service.
Solution:
On Linux, use the command sudo netstat -plnt to list what ports the services are using. Then use the command sudo kill <service_number_using_port_80> On Windows, open a terminal as administrator and use the command netstat -aon | findstr :80 to list what ports the services are using. Then use `kill <service_number_using_80>'.
Cannot find the container <ystemandchess|chessserver|chessclient|middleware|stockfishserver>
Solution:
The build for the containers errored out somewhere. Run the tag_build_containers.sh script again and READ the log to figure out where it errors out.
I did all the commands but when I go to localhost, nothing appears.
Solution:
Use the command docker-compose ps and see if any of the containers have an Exit Code. If there is, you can see why the container exited by using the command docker-compose logs <container_name_here>. Fix the error from the container and then rebuild the container.
Bash script can't be executed due to unknown symbols/characters.
Solution:
Run the script in Git Bash as an administrator or convert the EOL of the file to Unix. You can use NotePad++ to convert the EOL of the file.
####### Case #6:
Cannot create container for service... container name is already in use.
Solution:
On Linux, use the command sudo -i to login as root. Then use the commands: docker rm -vf
On Windows, just delete the images from the application Docker Desktop and then rebuild.
######## Case #7:
Only chessserver, stockfishserver, and reverse-proxy-server have exit.
Solution:
Do an npm install in their respective folders and rebuild the containers.