Node Mining Errors

General
1

Heyo! Mining on an ubuntu VPS and getting these logs

D (17:42:55) mining: starting mining attempt on thread 4 on header "By5Fra1ueTPYhcjzJZ3QjL6NC2pm3dF2MconB1V6ssT377htTzt93p1"with nonce: “Bf7EqBGJ1jaFGzTNo3XcgqjgvD6ZgMVmTVnNTNXN3iJxWh6QN1jtzKE”
D (17:42:55) mining: starting mining attempt on thread 5 on header "By5Fra1ueTPYhcjzJZ3QjL6NC2pm3dF2MconB1V6ssT377htTzt93p1"with nonce: “y4H1ttUR4ai6shpc6EZgse2bde8wN619SFtxtDDydnKjDYU1dVCnT5”
D (17:42:55) mining: starting mining attempt on thread 2 on header "By5Fra1ueTPYhcjzJZ3QjL6NC2pm3dF2MconB1V6ssT377htTzt93p1"with nonce: “7qFBkLfmYttm6Na9WwJXSTPp665s3iGHVay1aCjwt95kqJzS83YSLJX”
D (17:42:55) mining: starting mining attempt on thread 3 on header "By5Fra1ueTPYhcjzJZ3QjL6NC2pm3dF2MconB1V6ssT377htTzt93p1"with nonce: “5DEZWYp3FP1rMdoBD8BQ71HePQfojSY8SBoKBm8FFYG1UwH1ykPZi4N”
I (17:42:55) handle-command: timer
D (17:42:55) mining: starting mining attempt on thread 0 on header "By5Fra1ueTPYhcjzJZ3QjL6NC2pm3dF2MconB1V6ssT377htTzt93p1"with nonce: “DXp2L6uDcAQ9SjsJJZN4TckvMgfugZQMjw9sf2kMPq1ndk5HMZBujnm”
I (17:42:55) handle-fact: heard-block
I (17:42:56) serf: cold: register: could not match parent battery at given axis: compute-size-without-txs 7
I (17:42:56) serf: cold: register: could not match parent battery at given axis: txs-size-by-id 7
I (17:42:56) validate-page-with-txs: Block validated: 5Lot4S9U2abMgynR3XjkBQxEkoVGrJncdeFoswWhAAkcpoT4xkprvru

getting the mining attempts but not sure if machine is actually mining because of
register: could not match parent battery at given axis: txs-size-by-id 7

are these logs expected?

2

That serf notification does not appear to be coming from your Debug-level Nockchain process logging. Do you know what Info-level log that is coming from?

3

I (18:05:40) handle-fact: heard-block

I (18:05:40) serf: cold: register: could not match parent battery at given axis: compute-size-without-txs 7

I (18:05:40) serf: cold: register: could not match parent battery at given axis: txs-size-by-id 7

I (18:05:40) validate-page-with-txs: Block validated: 4okqghtX5XnpoXGMQAW4uUwAsDnjkLpowA8XFTreDj4qGAmhW6p21XJ

looks like info

4

W (18:05:41) driver: IP address 5.39.222.251 exceeded the request-per-interval threshold with 181 requests
W (18:05:41) driver: IP address 5.39.222.251 exceeded the request-per-interval threshold with 182 requests
W (18:05:41) driver: IP address 5.39.222.251 exceeded the request-per-interval threshold with 183 requests
W (18:05:41) driver: IP address 5.39.222.251 exceeded the request-per-interval threshold with 184 requests
W (18:05:41) driver: IP address 5.39.222.251 exceeded the request-per-interval threshold with 185 requests
W (18:05:41) driver: IP address 5.39.222.251 exceeded the request-per-interval threshold with 186 requests

also getting these pretty consistently so wanted to see if that was throttling. Haven’t set up the tracer for efficiency yet but wanted to make sure i was actually mining first haha

5

Haven’t been able to get this log yet
cat logs | grep -a mining-on
2025-05-22T19:36:03.637735Z INFO poke{src=“libp2p”}:do_poke:slam:interpret: slogger: [%mining-on 16.403.360.192.242.793.373 3.729.916.137.565.976.388 4.841.179.700.730.650.850 15.348.244.770.755.086.673 692.083.285.147.958.964]
2025-05-22T19:37:31.094231Z INFO poke{src=“libp2p”}:do_poke:slam:interpret: slogger: [%mining-on 7.747.443.845.271.629.095 5.660.899.446.013.130.014 16.240.482.680.428.274.828 10.632.268.164.621.327.291 10.770.059.714.026.683.921]
2025-05-22T19:38:58.104678Z INFO poke{src=“libp2p”}:do_poke:slam:interpret: slogger: [%mining-on 9.123.727.458.387.341.179 1.197.520.098.285.115.729 6.224.300.754.256.307.542 2.517.191.640.729.909.646 14.926.170.594.679.154.006]

only attempts at mining

6

This one may also be the issue - I (18:08:47) missing-parent-effects: Heard block AZqzjAdNZNAwmyrPsrvZu5Rsqr8h1Y5vQbu3Hrgqg7f2sB5WDYG3bpm at height 28789 but we only have blocks up to height 3635: requesting next highest block.

I (18:08:47) peek: %heavy-n

not even close to the highest block

7

Right. If you are not at the tip of the chain, the proof attempt can’t actually pass.

8

Hmm any ideas on how to fix this?

9

Run the node to the current block height.

10

Is there an explicit command to this? Assumed that mining would auto fetch the latest block

11

Saw this on another thread - ( State Jams - Google Drive ) - do I compile hoon with the latest jam?

12

Jams/State Jams/.chkjams go in the data.nockchain.checkpoints folder, do not require recompiling, the running node will see it and process it.

13

Hmm so imported statejam and now i’m getting a wrong peer id message and then the node gets killed

I (20:45:21) [%build-hash 0vr.36606]
I (20:45:21) [%nockchain-state-version %6]
I (20:45:21) [%check-checkpoints-mainnet [~ %.y]]
I (20:45:21) took: 5.520932ms
I (20:45:38) took: 16.733090393s
I (20:48:57) [%build-hash 0vr.36606]
I (20:48:57) [%nockchain-state-version %6]
I (20:48:57) [%check-checkpoints-mainnet [~ %.y]]
I (20:48:57) took: 4.841259ms
I (20:49:14) took: 16.718833041s
I (20:49:16) [no] kernel::boot: Successfully imported kernel state from: "statejam_contents/38455.jam"
I (20:49:16) nockchain: Discarding existing peer ID and generating a new one
I (20:49:16) nockchain: Generated new identity as peer 12D3KooWArmdTErBMAYYsruEYBV6asDuyYP3jsPLo2oTkFo6H5KH
allowed_peers_path: None
I (20:49:16) peek: %mainnet
I (20:49:16) peek: %genesis-seal-set
I (20:49:16) handle-command: btc-data
W (20:49:16) handle-command: Kernel no longer in init phase, cannot do init-only command
I (20:49:18) handle-command: set-mining-key-advanced
I (20:49:18) [no] private_nockapp::driver: Starting private gRPC server on 127.0.0.1:5555
I (20:49:18) [no] private_nockapp::server: Starting private gRPC server on 127.0.0.1:5555
I (20:49:18) libp2p_swarm: local_peer_id=12D3KooWArmdTErBMAYYsruEYBV6asDuyYP3jsPLo2oTkFo6H5KH
I (20:49:18) driver_init: driver 'libp2p' initialized
I (20:49:18) driver: Failed to bootstrap: No known peers.
I (20:49:18) driver: Logging current peer status...
W (20:49:18) driver: No current peers connected! connected_peers=0 peers=[]
W (20:49:18) driver: Routing table is empty! routing_table_size=0
I (20:49:18) driver: SEvent: Listening on /ip4/127.0.0.1/udp/60543/quic-v1
I (20:49:18) driver: SEvent: Listening on /ip4/168.231.116.56/udp/60543/quic-v1
I (20:49:19) handle-command: timer
I (20:49:20) handle-command: enable-mining
I (20:49:20) heard-new-block: Generating new candidate block with parent: 4ri6fLmUZkicDZCtUMPNqJP39fFfzydJWJEMcScVgCQnyTP5E337MYL
I (20:49:20) heard-new-tx: Miner received new transaction: 5juES7MacTrk3hFcP27dZ5NgaCgw2zShP1urS4QmxrszMQGwK1Z2hcj
I (20:49:20) serf: cold: register: could not match parent battery at given axis: process 7
I (20:49:20) serf: cold: register: could not match parent battery at given axis: compute-size-without-txs 7
I (20:49:20) serf: cold: register: could not match parent battery at given axis: txs-size-by-set 7
I (20:49:20) heard-new-tx: Miner received new transaction: Carw5HnNuerLxFx4BtzVpDigKndYVtoiocKnhTPhZ7KvrBa5jGwxRmD
I (20:49:20) serf: cold: register: could not match parent battery at given axis: process 7
I (20:49:20) serf: cold: register: could not match parent battery at given axis: compute-size-without-txs 7
I (20:49:20) serf: cold: register: could not match parent battery at given axis: txs-size-by-set 7
I (20:49:20) heard-new-tx: Miner received new transaction: 61FCepiBmuBGkpYjypDCxwt8gkdvCjvBF2MDbWkbjj7rCPyTj3wx5fP
I (20:49:20) serf: cold: register: could not match parent battery at given axis: process 7
I (20:49:20) serf: cold: register: could not match parent battery at given axis: compute-size-without-txs 7
I (20:49:20) serf: cold: register: could not match parent battery at given axis: txs-size-by-set 7
I (20:49:21) mining: Starting mining driver with 5 threads
I (20:49:21) driver_init: driver 'mining' initialized
I (20:49:21) driver_init: all drivers initialized, born poke sent
I (20:49:21) handle-command: born
I (20:49:21) [%constants [v1-phase=39.000 data=[max-size=2.048 min-fee=256] base-fee=32.768 [max-block-size=0x7a1200 blocks-per-epoch=2.016 target-epoch-duration=1.209.600 update-candidate-interval=~m5 max-future-timestamp=7.200 min-past-blocks=11 genesis-target-atom=130.370.302.333.636.102.422.056.264.229.955.163.909.308.806.223.299.818.849.658.877.692.896.509.855.179.799.805.421.158.400 max-target-atom=2.135.987.033.434.293.902.082.969.833.143.585.405.490.115.481.162.544.232.032.811.052.120.416.417.467.265.840.012.020.259.225.600 check-pow-flag=%.y coinbase-timelock-min=100 pow-len=64 max-coinbase-split=2 first-month-coinbase-min=4.383]]]
I (20:49:21) do-born: Dumbnet born
I (20:49:22) handle-fact: heard-block
I (20:49:22) mining: starting mining threads
I (20:49:22) serf: cold: register: could not match parent battery at given axis: compute-size-without-txs 7
I (20:49:22) serf: cold: register: could not match parent battery at given axis: txs-size-by-id 7
I (20:49:22) serf: cold: register: could not match parent battery at given axis: process 7
I (20:49:22) serf: cold: register: could not match parent battery at given axis: process 7
I (20:49:22) validate-page-with-txs: Block validated: 6TMzgN4gFAY6wUPVhqaVoeJaZSMzNUQzjeT5SDZ8m6ycTiU7TJCvi6t
I (20:49:22) accept-block: block 6TMzgN4gFAY6wUPVhqaVoeJaZSMzNUQzjeT5SDZ8m6ycTiU7TJCvi6t added to validated blocks at 38461 with proof version 2
I (20:49:22) update-heaviest: Checking if block 6TMzgN4gFAY6wUPVhqaVoeJaZSMzNUQzjeT5SDZ8m6ycTiU7TJCvi6t is heaviest
I (20:49:22) update-heaviest: Block 6TMzgN4gFAY6wUPVhqaVoeJaZSMzNUQzjeT5SDZ8m6ycTiU7TJCvi6t is new heaviest block
I (20:49:22) accept-block: New heaviest block!
I (20:49:22) heard-new-block: Generating new candidate block with parent: 6TMzgN4gFAY6wUPVhqaVoeJaZSMzNUQzjeT5SDZ8m6ycTiU7TJCvi6t
I (20:49:22) heard-new-tx: Miner received new transaction: Carw5HnNuerLxFx4BtzVpDigKndYVtoiocKnhTPhZ7KvrBa5jGwxRmD
I (20:49:22) serf: cold: register: could not match parent battery at given axis: process 7
I (20:49:22) serf: cold: register: could not match parent battery at given axis: compute-size-without-txs 7
I (20:49:22) serf: cold: register: could not match parent battery at given axis: txs-size-by-set 7
I (20:49:23) handle-fact: heard-block
W (20:49:23) heard-block: Duplicate block
I (20:49:25) handle-fact: heard-block
I (20:49:25) heard-block: Missing transactions, requesting from peers
I (20:49:25) heard-block: Gossiping new heaviest block (transactions pending validation)
I (20:49:26) handle-fact: heard-block
W (20:49:26) heard-block: Duplicate block
I (20:49:27) handle-fact: heard-tx
I (20:49:27) heard-tx: Received raw transaction
I (20:49:27) heard-tx: Raw transaction id: BSCdCxw8pxoUywAa9SfscZigF6RukzKk9raQP7gspTZDvUGXtEoBTw3
I (20:49:27) heard-tx: Processing ready blocks
W (20:49:27) driver: Wrong peer id 12D3KooWAv6WLTwsu2WUhqc42M17bugpquucEe4fC1vAYqd6CKyo from address /ip4/15.235.216.78/udp/3601/quic-v1/p2p/12D3KooWMZpBXc4dd8rJPPaFEp94daCahTFkhoKrZAxdpBQSnUND
I (20:49:28) handle-fact: heard-tx
I (20:49:28) heard-tx: Received raw transaction
I (20:49:28) heard-tx: Raw transaction id: 2QwwE4WhcoAVFYjveTDcLeBe4qxkdRVe59A884dWtZ2yRy7gDDduchK
I (20:49:28) heard-tx: Processing ready blocks
I (20:49:37) mining: mining threads started with 5 threads
I (20:49:38) handle-command: timer
I (20:49:40) handle-fact: heard-tx
I (20:49:40) heard-tx: Received raw transaction
I (20:49:40) heard-tx: Raw transaction id: 5F3t9JaP3yuFF8RZ7V9RXZLFRaBFsYdXwyQK8UCqZWprCGMUvN2sC7X
I (20:49:40) heard-tx: Processing ready blocks
W (20:49:50) driver: Wrong peer id 12D3KooWPb8vq6GCJFPik2UDeisErh86x8Yd1MqQKdYXDVH7CcZS from address /ip4/15.235.216.78/udp/3600/quic-v1/p2p/12D3KooWPsmT7Sj2uXoSeW6tMSh648QJh1zgSnuZ5sru6wViS57e
I (20:49:58) handle-command: timer
I (20:50:01) handle-fact: heard-tx
I (20:50:01) heard-tx: Received raw transaction
I (20:50:01) heard-tx: Raw transaction id: CZzppctpqEELwE3z3GKdR1p1MtQjCekiuJzkxKKj9KpM1MvdNo6s6ZJ
I (20:50:01) heard-tx: Processing ready blocks
W (20:50:11) driver: Wrong peer id 12D3KooWAv6WLTwsu2WUhqc42M17bugpquucEe4fC1vAYqd6CKyo from address /ip4/15.235.216.78/udp/3601/quic-v1/p2p/12D3KooWPGvHxmUeSnqmajgdXMNrjeYPwS72jgR5qLjq3Tx3smCG
14

Next line after that is just killed, is there any way to maybe clear all the data, maybe something got messed up since was syncing after running node till block 7000. Got the latest jam from

1 Like
15

What OS are you on? Did you build according to the ReadMe? How are you launching the node?

16

Haha actually after using the jam, i think i ran out of memory. trying again with 3 CPU threads vs 6 and seeing

17

Running a node is not threaded. How are you launching Nockchain?

18

TRACY_NO_INVARIANT_CHECK=1 nockchain --mining-pubkey <//> --mining-pkh <//> --mine --num-threads 2 --state-jam statejam_contents/38455.jam

is what i’m using, whether i include the statejam or not, get terminated with 5-10 minutes, if i move down to 2 threads get a little bit longer. Didn’t have this issue before the statejam, it ran for 1hr non stop

running on a hostiner KVM8 - 8 vCPU cores

32 GB RAM

400 GB NVMe disk space

32 TB bandwidth

lmk if i’m doing something wrong

had to use new account since last one was blocked for a bit

19

This is the node script:

“#!/bin/bash

source .env

export RUST_LOG

export MINIMAL_LOG_FORMAT

nockchain

”

That’s all you need to run.

20

I mean this is getting run in effect

TRACY_NO_INVARIANT_CHECK=1 nockchain --mining-pubkey <//> --mining-pkh <//> --mine --num-threads 2 --state-jam statejam_contents/38455.jam

none of these params would affect the CPU usage would it?