-
Notifications
You must be signed in to change notification settings - Fork 40
Open
Description
Description
The ephemeral-validator binary from @magicblock-labs/ephemeral-validator@0.8.2 (npm) exits immediately with exit code 0 and produces zero output (stdout/stderr) when attempting to connect to a local solana-test-validator started via mb-test-validator.
Environment
- OS: Ubuntu 24.04 (Linux 6.8.0-101-generic, x86_64)
- Node: v23.11.0
@magicblock-labs/ephemeral-validator: 0.8.2solana-cli: 2.3.13anchor-cli: 0.32.1
Steps to Reproduce
- Start the base layer validator:
mb-test-validator --reset
# Confirms running on :8899 with delegation programs loaded- Run the ephemeral validator:
ephemeral-validator --remotes localhost --lifecycle ephemeral -l 0.0.0.0:7799 --reset
# Exits immediately, code 0, no outputWhat I tried
- Different
--remotesformats:localhost,http://localhost:8899, explicit HTTP + WS pair - TOML config file instead of CLI args
RUST_LOG=trace RUST_BACKTRACE=full-- still zero stdout/stderr- Explicit
--storagedirectory - Running the platform binary directly (
ephemeral-validator-linux-x64/bin/ephemeral-validator)
All attempts produce the same result: the process exits with code 0 and no output.
Observations from strace
Running under strace shows the binary does start up briefly:
- Initializes RocksDB, creates storage files (rocksdb/, accountsdb/, sqlite files, keypair files)
- Binds to port 9000 momentarily
- Then exits cleanly
--version works fine and returns magicblock-config 0.8.2.
Expected Behavior
The ephemeral validator should stay running, bind to the specified listen port (7799), and connect to the local solana-test-validator as its base layer.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels