oxidecomputer / oxidecomputer/omicron
Nexus was up and running but unresponsive to http requests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
The issue happened one of the three nexus zones on rack3 and here were the symptoms we saw:
- The health check performed by silo creation in cassette was not completing. It was continually failing with TLS errors, failing to complete a handshake with Nexus.
- We were unable to communicate with the Nexus instance via
omdb. All requests to the server were timing out. - Oximeter stopped collecting metrics.
(More details about each of the issues above noted in https://github.com/oxidecomputer/colo/issues/127.)
There were core files collected while nexus was in the problem state and via svcadm restart -d nexus. The issues were gone after the SMF service restart.
The core files and nexus logs can be found in /staff/rack3/2025-08-06.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Nexus core files and logs in /staff/rack3/2025-08-06, then review the linked colo issue 127 and the behavior around svcadm restart -d nexus. Done means identifying the cause of the TLS, omdb, and Oximeter failures and documenting or testing a fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100