[Bug] Can't start server

[vadim-su]

What are you really trying to do?

I just run docker compose up

Describe the bug

After starting I get these messages

{"level":"info","ts":"2025-09-20T13:21:20.974Z","msg":"loaded user data from db","component":"matching-engine","wf-task-queue-name":"temporal-sys-processor-parent-close-policy","wf-task-queue-type":"Workflow","wf-namespace":"temporal-system","user-data-version":0,"timestamp":"1970-01-01T00:00:00.000Z","logging-call-at":"/home/runner/work/docker-builds/docker-builds/temporal/service/matching/user_data_manager.go:690"}
{"level":"info","ts":"2025-09-20T13:21:20.976Z","msg":"Current reachable members","component":"service-resolver","service":"worker","addresses":["172.21.0.4:7239"],"logging-call-at":"/home/runner/work/docker-builds/docker-builds/temporal/common/membership/ringpop/service_resolver.go:305"}
{"level":"info","ts":"2025-09-20T13:21:20.980Z","msg":"loaded user data from db","component":"matching-engine","wf-task-queue-name":"temporal-sys-delete-namespace-activity-tq","wf-task-queue-type":"Workflow","wf-namespace":"temporal-system","user-data-version":0,"timestamp":"1970-01-01T00:00:00.000Z","logging-call-at":"/home/runner/work/docker-builds/docker-builds/temporal/service/matching/user_data_manager.go:690"}
{"level":"info","ts":"2025-09-20T13:21:20.992Z","msg":"loaded user data from db","component":"matching-engine","wf-task-queue-name":"default-worker-tq","wf-task-queue-type":"Workflow","wf-namespace":"temporal-system","user-data-version":0,"timestamp":"1970-01-01T00:00:00.000Z","logging-call-at":"/home/runner/work/docker-builds/docker-builds/temporal/service/matching/user_data_manager.go:690"}
{"level":"info","ts":"2025-09-20T13:21:20.993Z","msg":"loaded user data from db","component":"matching-engine","wf-task-queue-name":"temporal-sys-migration-activity-tq","wf-task-queue-type":"Workflow","wf-namespace":"temporal-system","user-data-version":0,"timestamp":"1970-01-01T00:00:00.000Z","logging-call-at":"/home/runner/work/docker-builds/docker-builds/temporal/service/matching/user_data_manager.go:690"}
{"level":"info","ts":"2025-09-20T13:21:20.994Z","msg":"loaded user data from db","component":"matching-engine","wf-task-queue-name":"temporal-sys-per-ns-tq","wf-task-queue-type":"Workflow","wf-namespace":"temporal-system","user-data-version":0,"timestamp":"1970-01-01T00:00:00.000Z","logging-call-at":"/home/runner/work/docker-builds/docker-builds/temporal/service/matching/user_data_manager.go:690"}
time=2025-09-20T13:21:28.785 level=ERROR msg="failed reaching server: context deadline exceeded"
Waiting for Temporal server to start...
time=2025-09-20T13:21:37.800 level=ERROR msg="failed reaching server: context deadline exceeded"
Waiting for Temporal server to start...
time=2025-09-20T13:21:46.816 level=ERROR msg="failed reaching server: context deadline exceeded"
Waiting for Temporal server to start...
time=2025-09-20T13:21:55.831 level=ERROR msg="failed reaching server: context deadline exceeded"
Waiting for Temporal server to start...
time=2025-09-20T13:22:04.844 level=ERROR msg="failed reaching server: context deadline exceeded"
Waiting for Temporal server to start...
time=2025-09-20T13:22:13.860 level=ERROR msg="failed reaching server: context deadline exceeded"
Waiting for Temporal server to start...

Waiting for Temporal server to start...
time=2025-09-20T13:22:13.860 level=ERROR msg="failed reaching server: context deadline exceeded"
Waiting for Temporal server to start...

Minimal Reproduction

git clone org-56493103@github.com:temporalio/docker-compose.git
docker compose up

Environment/Versions

• OS and processor: Linux 6.16.7-1-cachyos
• Temporal Version: 1.28.1

[adrianlzt]

In my case is a problem with DNS (note the dot after the "temporal" and before the port):

73121f5aca49:/etc/temporal$ TEMPORAL_ADDRESS=temporal.:7233 temporal operator cluster health
SERVING
73121f5aca49:/etc/temporal$ TEMPORAL_ADDRESS=temporal:7233 temporal operator cluster health
time=2025-11-22T05:51:26.187 level=ERROR msg="failed reaching server: context deadline exceeded"

That command is called from the auto-setup.sh script (called from entrypoint.sh).

One of my domains in "search" takes too long to answer hitting some timeout before being able to resolve the domain. Looks like, before trying to resolve "temporal" it tries to resolve "_grpclb._tcp.temporal", and that one timeouts.