Panic when deploying self-hosted temporal server

Community Support Server Deployment
1

I am trying to deploy temporal server in GCP using the temporalio/server docker image. I successfully built and deployed the image, loaded the config and setup the temporal and visibility schemas. However, after all that is done I am getting a panic error:

panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x2798bd4] goroutine 1 [running]: go.temporal.io/server/temporal.ApplyClusterMetadataConfigProvider({0x38e5490, 0xc0008fce10}, 0xc000830a08, {0x3899080, 0x5760ca0}, 0x344e350, {0x0, 0x0}, {0x38e5760, 0x5760ca0}) /home/runner/work/docker-builds/docker-builds/temporal/temporal/fx.go:580 +0x1f4 reflect.Value.call({0x2d45120?, 0x344e388?, 0x30?}, {0x326711b, 0x4}, {0xc0002c1050, 0x6, 0x10?})…

I couldn’t find anything online to help with the investigation.
This is my config.yaml:
global:
dynamicConfig:
filepath: “/config/dynamic_config.yaml”
pollInterval: “10s”

persistence:
defaultStore: default
visibilityStore: visibility
numHistoryShards: 512
datastores:
default:
sql:
pluginName: “postgres12_pgx”
databaseName: “${DB_NAME}”
connectAddr: “${DB_HOST}”
connectProtocol: “tcp”
connectPort: “5432”
user: “${DB_USER}”
password: “${DB_PASSWORD}”
visibility:
sql:
pluginName: “postgres12_pgx”
databaseName: “${DB_VISIBILITY_NAME}”
connectAddr: “${DB_HOST}”
connectProtocol: “tcp”
connectPort: “5432”
user: “${DB_USER}”
password: “${DB_PASSWORD}”

services:
frontend:
rpc:
grpcPort: 7233
membershipPort: 6933
history:
rpc:
grpcPort: 7234
membershipPort: 6934
matching:
rpc:
grpcPort: 7235
membershipPort: 6935
worker:
rpc:
grpcPort: 7239
membershipPort: 6939
internal-frontend:
rpc:
grpcPort: 7236
membershipPort: 6936

2

Hi

I think the clusterMetadata section is missing.

You can use one if these files as a reference

3

Thanks for the suggestion.

I tried that, I also try to manually populated the cluster_metadata db table with the same values as json - unfortunately no luck and the error persists.