Nakama docker works but after a while cockroachdb container falling

1
{
Nakama docker on digitalocean server works well. but after a while only cockroachdb container falls
nakama and prometheus containers keep running.

how can i determine problem and solve this?
}

{Details}

  1. Versions: Nakama {3.5}, {Windows, Mac, Linux binary or Docker}, {client library (SDK) and version}
  2. Server Framework Runtime language (If relevant) {Go, TS/JS, Lua}
{code or log snippet}

:tv: Media:

Hello @ennteresan,

You can start by checking the logs of the container running cockroachdb. The cmd is docker logs -t <container-name>.

I’ve been running a local CockroachDB for my local development server for a while. I’ve noticed that it’s not really that stable and periodically just crashes. Maybe once per week or so. It’s no big deal for me when developing, but I would not deploy a live game on CockroachDB.

I’m running Nakama on Digital Ocean, the default setup using docker and cockroachdb. I’ve noticed the service stopping too, usually after 24h or so. A restart brings everything back to normal, ie. connecting to Nakama works again and the permanent authoritative match resumes.

On startup, the cockroach init message says the logs are stored in /var/lib/cockroach/logs, but the “cockroach” directory doesn’t exist on the droplet.

Has anyone been able to solve this, or is there something else that could help figure out why cockroach stops unexpectedly?

ps. I’m using Cockroach 20.2.19 and Nakama 3.15.0.

Checking the logs doesn’t show anything apart from the startup messages from a day or so ago. No errors.

I’m assuming this happens because Cockroach runs out of resources, but I’d like to know that’s the case before upgrading the server.

Update: I upgraded the server to meet the minimum spec of Cockroachdb, and it’s stayed up for almost a week with no issues. So it looks like it ran out of resources before, fingers crossed. :crossed_fingers: