Troubleshooting

Tools are unable to connect to downloads.gamebench.net

gbserver.sh shows the message:

Unable to retrieve latest version of this script from downloads.gamebench.net

gbctl shows the message:

Unable to check latest version

Please ensure you’re able to connect to downloads.gamebench.net from within your network.

Unable to pull images

If you get the following error when attempting to pull the Docker images, please check you have logged into the quay.io registry.

Pulling backend (quay.io/gamebench/node-backend:v1.10.0)...
ERROR: unauthorized: access to the requested resource is not authorized

Some session zips aren’t uploading and there are 413 (Request Entity Too Large) errors

Please increase the client max body size setting by either:

Updating the gamebench.toml configuration file, setting nginxClientMaxBodySize to the required value i.e. nginxClientMaxBodySize = "200m". Then run ./gbctl --no-interaction to regenerate the configuration.
Running ./gbserver.sh and entering the required value when prompted during the interactive configuration.

Please restart the frontend container after making either of these changes: docker restart frontend.

Web dashboard is just a white screen

To start with, ensure you can successfully make an API call. Please check using the following command:

curl <web dashboard host>:<web dashboard port>/v1/info/version

You should get a response like:

"v1.10.0"

If you don’t get a successful response. Try restarting the backend container using: docker restart backend. If the curl command still fails, please check the logs using docker logs backend. If there isn’t anything immediately obvious in there, please contact support@gamebench.net with the output from gbserver.sh support-info. It would also be very helpful if you could share the output of your web browser developer tools console. In Chrome you can save the console output by opening the developer tools and going to the “Console” tab, there you can right click on the console and choose “Save as…”.

Accessing the web dashboard results in a “This site can’t be reached” error

Check that the frontend container is running using: docker ps.

You should see something like (for a standard single server install):

CONTAINER ID        IMAGE                                                 COMMAND                  CREATED             STATUS              PORTS                                      NAMES
874a290fbda9        quay.io/gamebench/ang4-frontend:v1.10.0               "/entrypoint.sh ngin…"   10 minutes ago      Up 10 minutes       0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp   frontend
0c8a14f44564        quay.io/gamebench/node-backend:v1.10.0                "/wait-for elasticse…"   10 minutes ago      Up 10 minutes       0.0.0.0:8090->5000/tcp                     backend
0daf0148f43c        lewmpk/exim4:latest                                   "/docker-entrypoint.…"   2 weeks ago         Up 2 weeks          25/tcp                                     mail
519b5e36f7e4        docker.elastic.co/elasticsearch/elasticsearch:6.1.3   "/usr/local/bin/dock…"   2 weeks ago         Up 2 weeks          9200/tcp, 9300/tcp                         elasticsearch
97a343d04393        redis:alpine                                          "docker-entrypoint.s…"   2 weeks ago         Up 2 weeks          6379/tcp                                   redis
e5f458079d78        postgres:11                                           "docker-entrypoint.s…"   6 weeks ago         Up 6 weeks          5432/tcp                                   postgres

If the frontend container is present, try making a curl request locally to it. For example:

curl localhost:80/v1/info

If you get the response:

"v1.10.0"

That means the frontend and backend are running. In this case, please check you are using the correct host and port to connect to the web dashboard.

If the frontend container is not present, please check the logs and check for any issues:

docker logs frontend

If there isn’t anything immediately obvious in there, please contact support@gamebench.net with the output from gbserver.sh support-info. It would also be very helpful if you could share the output of your web browser developer tools console. In Chrome you can save the console output by opening the developer tools and going to the “Console” tab, there you can right click on the console and choose “Save as…”.

High disk watermark exceeded Elasticsearch error

If you encounter the following error in the Elasticsearch logs, you’ll need to either free up some disk space or adjust the disk watermark settings.

[2020-02-18T10:37:27,512][WARN ][o.e.c.r.a.DiskThresholdMonitor] [tAx7kEu] high disk watermark [90%] exceeded on [tAx7kEuAQ062JanbVSHzIA][tAx7kEu][/usr/share/elasticsearch/data/nodes/0] free: 96.9gb[5.2%], shards will be relocated away from this node

Disk space could be freed up by:

Running docker system prune
Clearing up old session data

It’s also possible to adjust the watermark settings like so, replacing the example values with those appropriate to your disk:

curl \
    -X PUT \
    -H "Content-Type: application/json" \
    -d '{ "persistent": { "cluster.routing.allocation.disk.watermark.low": "20gb", "cluster.routing.allocation.disk.watermark.high": "10gb", "cluster.routing.allocation.disk.watermark.flood_stage": "5gb" } }'
    $(docker inspect --format '{{ range .NetworkSettings.Networks }}{{ .IPAddress }}{{ end }}' elasticsearch):9200/_cluster/settings

Once you’ve either increased the available disk space or adjusted the watermark settings, run the following to take Elasticsearch out of read only mode:

curl \
    -X PUT \
    -H 'Content-Type: application/json' \
    -d'{ "index.blocks.read_only_allow_delete" : null } }' \
    "$(docker inspect --format '{{ range .NetworkSettings.Networks }}{{ .IPAddress }}{{ end }}' elasticsearch):9200/_all/_settings"

Finally, restart the backend container using:

docker restart backend

Last updated on March 18, 2024

Enterprise Support Configuration Reference