Skip to main content

Tutorial: Troubleshooting

1 minTutorials

Troubleshooting.

// symptom · cause · fix · the failures operators actually hit

The common failures and how to clear each one, with the diagnostic command to copy where one applies. When in doubt, run parallelix-node verify: it checks Node, the node key, Ollama, a model, and coordinator reachability, and prints remediation hints.

Ollama not running

causeparallelix-node verify reports 'ollama not running', and start refuses to launch. The node serves inference through Ollama, so it cannot start without it.

fixInstall Ollama (https://ollama.com/download) and start it. On Linux the one-line installer does this for you; otherwise run `ollama serve`. Then pull a model and re-verify.

parallelix.nodenode · pull a model, then re-verify
$parallelix-node models pull llama3.2
pulling llama3.2 into ollama
layers ✓ 4.7 GB
llama3.2 ready
DIAGNOSERUNCLI1.2.1// sample
pull a model, then re-verify
parallelix-node models pull llama3.2
Node will not come online (not_staked)

causestart prints that node <id> is 'no longer staked on-chain' and exits. The nodeId you passed is not backed by a stake (never registered, or the stake was withdrawn).

fixRegister the node in the Console, then start with the nodeId it assigns. Confirm the machine's nodeKeyHash matches the one you registered with parallelix-node status.

parallelix.nodenode · confirm nodeId + nodeKeyHash
$parallelix-node status
node status
nodeKeyHash 0x9c27a4f1…e83b
tier 3
staking CA 0x7068…82b6
DIAGNOSERUNCLI1.2.1// sample
confirm nodeId + nodeKeyHash
parallelix-node status
Node will not come online (in_cooldown)

causestart prints that node <id> is 'in unstake cooldown' and exits. You called requestUnstake on this node, so nothing is dispatched to it.

fixTo keep running it, cancelUnstake(nodeId) in the Console Staking page, then start again. Otherwise wait out the 7-day cooldown and withdraw.

Repeated 403 rejections

causestart stops after three rejections with a hint about --node-id and nodeKeyHash. The coordinator does not recognise this machine for that node.

fixCheck the --node-id is correct and that this machine's nodeKeyHash (from init) is exactly the one you registered on-chain. verify confirms the key and coordinator reachability.

parallelix.nodenode · check key + coordinator
$parallelix-node verify
verify
node key present, perms 600
coordinator reachable
all checks passed · ready to start
DIAGNOSERUNCLI1.2.1// sample
check key + coordinator
parallelix-node verify
registerNode transaction fails: low ETH

causeMetaMask rejects the approve or registerNode transaction for insufficient gas. Registration is two on-chain transactions (approve $PRLX, then registerNode) on Ethereum mainnet.

fixHold a little ETH for gas in the staking wallet. Remember the 4% buy tax when acquiring $PRLX: buy a little more than 50,000 to clear the floor after tax.

Windows: nothing installs

causeThe installer or CLI does not run on native Windows. Native Windows is not supported.

fixInstall WSL2 (https://learn.microsoft.com/windows/wsl/install), open Ubuntu, and run the one-line installer and every command inside it.

parallelix.nodenode · inside WSL2 Ubuntu
$curl -fsSL https://parallelix.io/install.sh | sh
installing Node 22.x ✓
installing Ollama ✓
installing parallelix-node ✓ v1.2.1
DIAGNOSERUNCLI1.2.1// sample
inside WSL2 Ubuntu
curl -fsSL https://parallelix.io/install.sh | sh
Apple Silicon shows tier 3, not 4

causeprobe reports tier 3 (GPU · high) on a high-memory Mac. Apple Silicon shares unified memory between CPU and GPU, so the CLI caps the Metal GPU at tier 3 rather than datacenter tier 4.

fixThis is expected. Declare tier 3 when you register. Run probe to read the exact tier the CLI assigns this machine.

parallelix.nodenode · read the assigned tier
$parallelix-node probe
hardware probe
gpu Apple M-series · Metal
maps to tier 3 (GPU · high)
DIAGNOSERUNCLI1.2.1// sample
read the assigned tier
parallelix-node probe
Node orphaned after init --force

causeAfter running init --force, the running daemon's heartbeats stop being accepted. --force generates a new node key and a new nodeKeyHash, so the old on-chain registration no longer matches this machine.

fixEither restore the backed-up previous key, or register a fresh node with the new nodeKeyHash. Use --force deliberately. status prints the current nodeKeyHash so you can compare it against the Console.

parallelix.nodenode · read the current nodeKeyHash
$parallelix-node status
node status
nodeKeyHash 0x3ea90b7c…61df (new)
tier 3
DIAGNOSERUNCLI1.2.1// sample
read the current nodeKeyHash
parallelix-node status
Node goes idle when the machine is off

causeThe Console shows the node in Idle and earnings stop accruing. A node only accrues while it is online and heartbeating; if the machine is off, asleep, or paused, it earns nothing for that time.

fixRun it as a service so it survives reboot and auto-restarts, rather than a foreground start that dies with the terminal.

parallelix.nodenode · install as a 24/7 service
$parallelix-node service --node-id 4217 --gpu
installed + started as systemd service 'parallelix-node'
logs: journalctl -u parallelix-node -f
DIAGNOSERUNCLI1.2.1// sample
install as a 24/7 service
parallelix-node service --node-id 4217 --gpu