Troubleshooting

Docker unauthorized

Suppose you see an error message like this when trying to run an experiment using Docker:

 => ERROR [internal] load metadata for registry.gitlab.com/psynetdev/psynet:v10.4.0
 => [auth] psynetdev/psynet:pull token for registry.gitlab.com
------
 > [internal] load metadata for registry.gitlab.com/psynetdev/psynet:v10.4.0:
------
Dockerfile:1
--------------------
   1 | >>> # syntax = docker/dockerfile:1.2
   2 |     #
   3 |     # Note - the syntax of this Dockerfile differs in several ways from the sample Dockerfile
--------------------
ERROR: failed to solve: failed to authorize: failed to fetch oauth token: unexpected status: 401 Unauthorized

This normally means you have out-of-date credentials in your Docker client. Try running the following:

docker login registry.gitlab.com

Docker no space left on device

Docker unauthorized

Suppose you see an error message like this when trying to run an experiment using Docker:

ERROR: failed to solve: failed to copy: write /var/lib/docker/buildkit/content/ingest/ae8153b11f4d4f00d8b937b5de83ad657bae8a815251f89f9476de4147382577/data: no space left on device

This means too many old Docker images have accumulated on your system. This can be fixed by running the following command:

docker system prune

Database connection refused

Suppose you see an error message like this:

connection to server at "localhost" (::1), port 5432 failed: Connection refused
    Is the server running on that host and accepting TCP/IP connections?

This means that your local Postgres database cannot be accessed. This would normally only happen if you are not using PsyNet through Docker.

If you are on a Mac, you can check the status of your database by running this command:

brew services

If you don’t see a line with postgresql, you have not installed PostgreSQL. Follow the developer installation instructions to do so.

If you do see a line with postgresql, it probably has error written next to it. You need to get access to the logs to debug this error. To do so, look at the File column of the brew services output, find the value corresponding to postgresql. Print that file in your terminal using cat, for example:

cat ~/Library/LaunchAgents/homebrew.mxcl.postgresql@14.plist

Look for a line like this:

<key>StandardErrorPath</key>

The error log path is contained underneath it, between the <string> identifiers. View the last few lines of that file in your terminal using tail, for example:

tail /usr/local/var/log/postgresql@14.log

Have a look at the error message. One possible message is something like this:

2023-04-25 16:53:51.224 BST [28527] FATAL:  lock file "postmaster.pid" already exists
2023-04-25 16:53:51.224 BST [28527] HINT:  Is another postmaster (PID 716) running in data directory "/usr/local/var/postgresql@14"?

If you see this error message, try restarting your computer and trying again.

Another possible error message is this:

Reason: tried: '/usr/local/opt/icu4c/lib/libicui18n.72.dylib' (no such file)

It has proved possible in the past to fix this problem by running the following:

brew reinstall postgresql@14
brew services restart postgresql@14

where postgresql@14 should be replaced with the exact name for the Postgres service that you saw in ``brew services`.

If that doesn’t work, try searching Google for help. If you find another solution, please share your experience here.

MISCONF Redis is configured to save RDB snapshots

If you you see an error beginning ‘MISCONF Redis is configured to save RDB snapshots’, and you are using MacOS, then you may be able to fix your problem by running the following command:

brew services restart redis