basalt-26.3: roachtest: jepsen monotonic setup hit unstarted sqlliveness failed

**Note:** This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout.

roachtest.jepsen monotonic setup hit unstarted sqlliveness [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyGcePrivateBazel/21520424?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyGcePrivateBazel/21520424?buildTab=artifacts#/jepsen/monotonic/start-kill-2) on basalt-26.3 @ [5c33f90953648c401d6248bec79d37cbc854c363](https://github.com/cockroachdb/cockroach/commits/5c33f90953648c401d6248bec79d37cbc854c363):

Failed with:

```
test jepsen/monotonic/start-kill-2 failed: (jepsen.go:579).runJepsen: TRANSIENT_ERROR(jepsen monotonic setup hit unstarted sqlliveness): full command output in run_121246.854129088_n6_bash-e-c-cd-mntdata1.log: COMMAND_PROBLEM: exit status 254
test artifacts and logs in: /artifacts/jepsen/monotonic/start-kill-2/run_1
```
Cluster Node to Ip Mapping:
| Node | Public IP | Private IP |
| --- | --- | --- |
| teamcity-21520424-1789624545-97-n6cpu4-0001 | | 10.91.99.68 |
| teamcity-21520424-1789624545-97-n6cpu4-0002 | | 10.91.99.56 |
| teamcity-21520424-1789624545-97-n6cpu4-0003 | | 10.91.98.228 |
| teamcity-21520424-1789624545-97-n6cpu4-0004 | | 10.91.99.70 |
| teamcity-21520424-1789624545-97-n6cpu4-0005 | | 10.91.99.58 |
| teamcity-21520424-1789624545-97-n6cpu4-0006 | | 10.91.99.41 |

Parameters:
- arch=amd64
- cloud=gce
- coverageBuild=false
- cpu=4
- diskCount=0
- encrypted=false
- fs=ext4
- localSSD=true
- metamorphicLeases=default
- metamorphicWriteBuffering=true
- runtimeAssertionsBuild=true
Help

See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)

See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)

See: [Grafana](https://go.crdb.dev/roachtest-grafana/teamcity-21520424/jepsen-monotonic-start-kill-2/1789647023364/1789647417162)

_Logs were not uploaded to Datadog_

Same failure on other branches

- #173473 release-26.2: roachtest: jepsen monotonic setup hit unstarted sqlliveness failed [O-roachtest O-robot T-testeng X-infra-flake branch-release-26.2]
- #172693 roachtest: jepsen monotonic setup hit unstarted sqlliveness failed [O-roachtest O-robot T-testeng X-infra-flake branch-master]

/cc @cockroachlabs/test-eng

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*jepsen monotonic setup hit unstarted sqlliveness.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Jira issue: CRDB-68472

Start with the run_121246.854129088_n6_bash-e-c-cd-mntdata1.log artifact for jepsen/monotonic/start-kill-2 and the failure path at jepsen.go:579. Read the roachtest README, inspect the linked Grafana run, and compare recurring reports #173473 and #172693. Done requires identifying the cause of the unstarted sqlliveness failure and preventing this roachtest failure.

Written by the indexing model from the issue text.