Stop syncing 0.1.47

[hairtail]

What happened?

Version              0.1.47 @ src
Node                 STARTED
Memory               Heap: 433.23 MiB -> 473.46 MiB / 4.00 GiB (10.6%), RSS: 4.94 GiB (2.0%), Free: 241.84 GiB (4.0%)
P2P Network          CONNECTED - In: 56.53 KB/s, Out: 83.27 KB/s, peers 49
Mining               STARTED - 0 miners, 0 mined
Mem Pool             Size: 86844 tx, Bytes: 132.81 MiB
Syncer               IDLE - avg time to add block 2929.95 ms
Blockchain           000000000000077513ecf806001d0bebcd9504c32b65cd179a0eee4e3898d279 (194993), Since HEAD: 6h 12m (SYNCED)
Accounts             000000000000077513ecf806001d0bebcd9504c32b65cd179a0eee4e3898d279 (194993)
Telemetry            STARTED - 86079 <- 1 pending
Workers              STARTED - 0 -> 1 / 315 - 10.52 jobs Δ, 32.94 jobs/s

Version

0.1.47 @ src

Debug output

Iron Fish version               0.1.47 @ src
Iron Fish library               0.0.24 @ src
Operating system                Linux x64
CPU model(s)                    AMD Ryzen Threadripper 3970X 32-Core Processor
CPU threads                     64
RAM total                       251.84 GiB
Heap total                      3.98 GiB
Node version                    v16.15.1
ironfish in PATH                false
Garbage Collector Exposed       false
Telemetry enabled               true
Accounts head hash              00000000000070f70efc51e0c84c9b1338dc48eae6f973e8f543a0eea6b3f448
Accounts head in chain          true
Accounts head sequence          195279

Relevant log output

No response

Graffiti

miningKing

[hairtail]

stop again after restart.

[hughy]

This looks like the same issue as #2164

I've seen some of our long-running nodes stop syncing due to CPU issues. We're currently investigating CPI bottlenecks.

[terrancewong]

this is #2236

[hughy]

this is #2236

Thanks! Updated to 2164!

[Shekelme]

I observe the same behavior of my nodes. The nodes run on dedicated physical servers, Threadripper PRO 3955WX processors, the DB runs on NVME. 512 GB of DDR4-3200 memory.

[Shekelme]

Moreover, on 0.1.49 the problem still exists.

Version              0.1.49 @ ec57ed3
Node                 STARTED
Node Name            len08
Block Graffiti       saturnia
Memory               Heap: 164.09 MiB -> 205.20 MiB / 4.01 GiB (4.0%), RSS: 1.77 GiB (0.4%), Free: 450.99 GiB (10.4%)
CPU                  Cores: 32, Current: 61.7%
P2P Network          CONNECTED - In: 35.11 KB/s, Out: 661 B/s, peers 18
Mining               STARTED - 0 miners, 0 mined
Mem Pool             Size: 389 tx, Bytes: 595.83 KiB
Syncer               IDLE - avg time to add block 2200.74 ms
Blockchain           0000000000003d1fda08d1e50819d28ab25209dab4b6f5ffaf347b55f885a30a (215607), Since HEAD: 14m 42s (SYNCED)
Accounts             0000000000003d1fda08d1e50819d28ab25209dab4b6f5ffaf347b55f885a30a (215607)
Telemetry            STARTED - 223 <- 0 pending
Workers              STARTED - 0 -> 0 / 31 - -0.1 jobs Δ, 18.69 jobs/s

[D-Elektra]

Guys if somebody knows how to fix the sync, please share. Its been a month I cannot sync and cannot send any transactions.

[leoncryp]

Guys if somebody knows how to fix the sync, please share. Its been a month I cannot sync and cannot send any transactions.

Make sure you are on the latest node0.1.49 change blocksPerMessage from 20 to 5, this help me and other people a lot regards sync.

stop your node yarn --cwd ~/ironfish/ironfish-cli/ ironfish config:set blocksPerMessage 5

[D-Elektra]

Didn't help 10 and didn't help 5... I almost gave up with sync...

[holahula]

Closing due to staleness. If the issue persists in versions 1.0.0+ - please file a new issue