cockroachdb / cockroachdb/cockroach

cli: start can fail with 'deadline below read timestamp is nonsensical'

Open
#135,273 6 comments 0 reactions 1 assignee Claimed by @Nukitt View on GitHub
branch-master C-bug O-25.4-scale-testing P-3 T-db-server
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

Seen in `acceptance/mismatched-locality` in CI: https://github.com/cockroachdb/cockroach/actions/runs/11848818308/job/33021009108#step:6:3973

Sadly, no stack trace as it got printed with `%v` [here](https://github.com/cockroachdb/cockroach/blob/3ca8cac48a1b7d141417319412cfc76d2be0b8ae/pkg/cli/clierror/check.go#L17-L32) and not with `%+v`.

```
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 ‹ERROR: server startup failed: cockroach server exited with error: deadline below read timestamp is nonsensical; txn has would have no chance to commit. Deadline: 1731636738.475235118,0. Read timestamp: 1731636738.783272120,0 Previous Deadline: 0,0.›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹SQLSTATE: XX000›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹HINT: You have encountered an unexpected error.›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹Please check the public issue tracker to check whether this problem is›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹already tracked. If you cannot find it there, please report the error›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹with details by creating a new issue.›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹If you would rather not post publicly, please contact us directly›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹using the support form.›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹We appreciate your feedback.›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +HINT: ‹You have encountered an unexpected error.›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹Please check the public issue tracker to check whether this problem is›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹already tracked. If you cannot find it there, please report the error›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹with details by creating a new issue.›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹If you would rather not post publicly, please contact us directly›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹using the support form.›
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +
E241115 02:12:18.788665 1 1@cli/clierror/check.go:30 ⋮ [-] 168 +‹We appreciate your feedback.›

```

Jira issue: CRDB-44432

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.