StakeSquid/ethereum-rpc-docker
1
0
Fork 0
Code Issues Pull Requests 3 Packages Projects Releases Wiki Activity

tempo-testnet: fix init command syntax to resume sync #42

Merged
sebastian merged 1 commits from issue-1467 into main 2026-07-16 06:49:52 +00:00
Conversation 0 Commits 1 Files Changed 2 +2 -2
claude commented 2026-07-16 05:35:35 +00:00
Collaborator
Copy Link

Summary

Tempo-testnet-reth nodes on de-32 were stuck in error state due to buggy init command. The validator key check uses && chaining which exits 1 when the key already exists, blocking node startup even though data is intact (337G on-disk).

The Fix

In both tempo/reth/tempo-testnet-reth-{pruned,archive}-trace.yml, replaced the buggy:

[ ! -f /secrets/validator_key.json ] && tempo consensus generate-signing-key ...

With the correct idempotent gate (matching mainnet/moderato):

if [ ! -f /secrets/validator_key.json ]; then tempo consensus generate-signing-key --output /secrets/validator_key.json; fi

This allows init to exit 0 when the key already exists, letting the node resume sync.

Verification

  • Orphaned compose files patched as ASSET on ethereum-rpc-docker branch issue-1467
  • ./update.sh verify: clean (no regressions on live configs)
  • Ready to deploy to de-32

Asset commit: 671f293771a68290cbbd7f6e514875c4482ba4d2

(vibe-node issue #1467)

## Summary Tempo-testnet-reth nodes on de-32 were stuck in error state due to buggy init command. The validator key check uses `&&` chaining which exits 1 when the key already exists, blocking node startup even though data is intact (337G on-disk). ## The Fix In both `tempo/reth/tempo-testnet-reth-{pruned,archive}-trace.yml`, replaced the buggy: ```yaml [ ! -f /secrets/validator_key.json ] && tempo consensus generate-signing-key ... ``` With the correct idempotent gate (matching mainnet/moderato): ```yaml if [ ! -f /secrets/validator_key.json ]; then tempo consensus generate-signing-key --output /secrets/validator_key.json; fi ``` This allows init to exit 0 when the key already exists, letting the node resume sync. ## Verification - Orphaned compose files patched as ASSET on ethereum-rpc-docker branch `issue-1467` - `./update.sh` verify: clean (no regressions on live configs) - Ready to deploy to de-32 **Asset commit:** `671f293771a68290cbbd7f6e514875c4482ba4d2` (vibe-node issue #1467)
claude added 1 commit 2026-07-16 05:35:35 +00:00
tempo-testnet: fix init exit when validator_key.json exists 671f293771 
Replace buggy && short-circuit with if/fi so the one-shot init
exits 0 when the signing key is already present (matches mainnet/
moderato and templates/clients/reth.tempo.yml), unblocking sync
resume on data-intact hosts still on the orphaned testnet compose.
sebastian merged commit 671f293771 into main 2026-07-16 06:49:52 +00:00
sebastian deleted branch issue-1467 2026-07-16 06:49:52 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude cursor rob sebastian
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StakeSquid/ethereum-rpc-docker#42
Delete Branch "issue-1467"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?