Internal Server Error - container restarts every couple of seconds

[suntrop]

I can't reach my dashboard or any page in Plausible any more. I got an error message saying "Internal Server Error".
Last Friday everything was working fine. Did not update or change anything on my VPS. It is behind an Apache reverse proxy.
There is a lot of error logs for the domain, but mostly because my webpages sending tracking request can't be resolved.

I asked the tech staff of my VPS and they said there is something wrong with the container. It automatically restarts every couple of seconds. I did look at the docker logs, but I can't see if those are new or old errors. Those are without a full timestamp, so it's hard to tell.

Loading plausible..
Starting dependencies..
Starting repos..
create Plausible.Repo database if it doesn't exist
11:47:09.113 [error] Postgrex.Protocol (#PID<0.173.0>) failed to connect: ** (Postgrex.Error) ERROR XX000 (internal_error) cache lookup failed for type 1028
11:47:09.139 [error] Postgrex.Protocol (#PID<0.172.0>) failed to connect: ** (Postgrex.Error) ERROR XX000 (internal_error) cache lookup failed for type 1028
create Plausible.ClickhouseRepo database if it doesn't exist
Creation of Db successful!
Loading plausible..
Starting dependencies..
Starting repos..
Running migrations for Elixir.Plausible.Repo
11:47:10.507 [error] Postgrex.Protocol (#PID<0.172.0>) failed to connect: ** (Postgrex.Error) ERROR XX000 (internal_error) cache lookup failed for type 1028
11:47:10.512 [error] Postgrex.Protocol (#PID<0.173.0>) failed to connect: ** (Postgrex.Error) ERROR XX000 (internal_error) cache lookup failed for type 1028
11:47:11.630 [error] Postgrex.Protocol (#PID<0.172.0>) failed to connect: ** (Postgrex.Error) ERROR XX000 (internal_error) cache lookup failed for type 1028
11:47:12.804 [error] Postgrex.Protocol (#PID<0.173.0>) failed to connect: ** (Postgrex.Error) ERROR XX000 (internal_error) cache lookup failed for type 1028
11:47:13.232 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create".

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create". Alternatively you may configure Ecto to use
another table and/or repository for managing migrations:

    config :plausible, Plausible.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2747ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:

  1. Ensuring your database is available and that you can connect to it
  2. Tracking down slow queries and making sure they are running fast enough
  3. Increasing the pool_size (although this increases resource consumption)
  4. Allowing requests to wait longer by increasing :queue_target and :queue_interval

See DBConnection.start_link/2 for more information

    (ecto_sql 3.8.3) lib/ecto/adapters/sql.ex:932: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.13.4) lib/enum.ex:1593: Enum."-map/2-lists^map/1-0-"/2
    (ecto_sql 3.8.3) lib/ecto/adapters/sql.ex:1024: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.8.3) lib/ecto/migrator.ex:696: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.8.3) lib/ecto/migrator.ex:510: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.8.3) lib/ecto/migrator.ex:422: Ecto.Migrator.run/4
    (ecto_sql 3.8.3) lib/ecto/migrator.ex:146: Ecto.Migrator.with_repo/3
    (plausible 0.0.1) lib/plausible_release.ex:91: Plausible.Release.run_migrations_for/1

[Debcharon]

Something wrong with database, check your Postgres status.

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)