Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ironfish node stop syncing on ironfish@0.1.49
See original GitHub issueWhat happened?
node keeps getting disconnected and the current node is idle
Connection closing WebSocket for Uwmwtea (ynHwCi): read ECONNRESET
PEER Uwmwtea (ynHwCi) STATE CONNECTING -> DISCONNECTED
CONN WebSocket unidentified STATE CONNECTING -> DISCONNECTED
Connection closing WebSocket for NhkhRJb (ironbarra43): read ECONNRESET
PEER NhkhRJb (ironbarra43) STATE CONNECTING -> DISCONNECTED
RECV WebSocket SPuAELH: PeerListRequest (10)
RECV WebRtc f+dl8ZG: PeerListRequest (10)
CONN WebSocket unidentified STATE CONNECTING -> WAITING_FOR_IDENTITY
SEND WebSocket unidentified: Identify (6)
Received non-buffer message {"type":0,"destinationIdentity":null,"disconnectUntil":1665048864765,"reason":1,"sourceIdentity":"1FOWDS/vsKU+Yk6b
6zcCHq5+8pCAZ+xzWfH0pfj9qUY="}
CONN WebSocket unidentified STATE WAITING_FOR_IDENTITY -> DISCONNECTED
Connection closing WebSocket for 1FOWDS/ (ahamohar): Received non-buffer message
PEER 1FOWDS/ (ahamohar) STATE CONNECTING -> DISCONNECTED
CONN WebRtc unidentified STATE DISCONNECTED -> CONNECTING
PEER 6WuINBQ (aabo43) STATE DISCONNECTED -> CONNECTING
Attempted to establish a WebRTC connection to JVTIBa+ (Bula_va_Ironfish), but couldn't find a peer to broker the connection.
CONN WebSocket unidentified STATE DISCONNECTED -> CONNECTING
PEER JVTIBa+ (Bula_va_Ironfish) STATE DISCONNECTED -> CONNECTING
CONN WebRtc unidentified STATE DISCONNECTED -> CONNECTING
PEER EmzfRcM (slafi) STATE DISCONNECTED -> CONNECTING
RECV WebRtc HnFsnuN: PeerListRequest (10)
RECV WebRtc Ud8uLUs: Disconnecting (0)
2fdadA+ (rkds75) requested we disconnect until 1665048865000. Current time is 1665048565693
RECV WebRtc Ud8uLUs: Disconnecting (0)
2fdadA+ (rkds75) requested we disconnect until 1665048865000. Current time is 1665048565693
RECV WebRtc Ud8uLUs: Disconnecting (0)
SEND WebRtc Ud8uLUs: Disconnecting (0)
2fdadA+ (rkds75) requested we disconnect until 1665048865000. Current time is 1665048565693
Ignoring signaling request from 2fdadA+hprh/3mvgWuewyBD/htyDGUsPGDU4rRWY5XI=, at max peers
SEND WebRtc Ud8uLUs: Disconnecting (0)
Ignoring signaling request from 2fdadA+hprh/3mvgWuewyBD/htyDGUsPGDU4rRWY5XI=, at max peers
SEND WebRtc Ud8uLUs: Disconnecting (0)
Ignoring signaling request from 2fdadA+hprh/3mvgWuewyBD/htyDGUsPGDU4rRWY5XI=, at max peers
Ignoring signaling request from 2fdadA+hprh/3mvgWuewyBD/htyDGUsPGDU4rRWY5XI=, at max peers
Version 0.1.49 @ ec57ed3
Node STARTED
Node Name DarrzDC
Block Graffiti DarrzDC
Memory Heap: 109.72 MiB -> 126.67 MiB / 2.01 GiB (5.3%), RSS: 1.56 GiB (20.8%), Free: 4.87 GiB (35.2%)
CPU Cores: 16, Current: 67.6%
P2P Network CONNECTED - In: 13.81 KB/s, Out: 2.79 KB/s, peers 44
Mining STARTED - 0 miners, 0 mined
Mem Pool Size: 0 tx, Bytes: 0 B
Syncer IDLE - avg time to add block 13801.5 ms, progress: 97.82%
Blockchain 0000000000003f258accc4de083e8b4a45491676ea33354a1a06e01e09557f1f (210966), Since HEAD: 78h (NOT SYNCED)
Accounts 0000000000003f258accc4de083e8b4a45491676ea33354a1a06e01e09557f1f (210966)
Telemetry STARTED - 6620 <- 0 pending
Workers STARTED - 0 -> 0 / 6 - 0 jobs Δ, 0 jobs/s
Version
0.1.49
Debug output
Iron Fish version 0.1.49 @ ec57ed3
Iron Fish library 0.0.26 @ ec57ed3
Operating system Linux x64
CPU model(s) 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz
CPU threads 16
RAM total 7.53 GiB
Heap total 2.01 GiB
Node version v16.17.1
ironfish in PATH true
Garbage Collector Exposed false
Telemetry enabled true
Node name DarrzDC
Block graffiti DarrzDC
Relevant log output
No response
Graffiti
DarrzDC
Issue Analytics
- State:
- Created a year ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Stop syncing 0.1.47 · Issue #2236 · iron-fish/ironfish - GitHub
I've seen some of our long-running nodes stop syncing due to CPU issues. We're currently investigating CPI bottlenecks.
Read more >Health of your node | Iron Fish - Private, anonymous, and easy ...
Run the following command to display your chain status. Heaviest head is the latest block synced to the genesis block in your chain....
Read more >New Privacy Coin Iron Fish Launches Testnet With $5.3M in ...
“Iron Fish is a new privacy-focused cryptocurrency where every transaction is private, using the strongest privacy mechanism known today based ...
Read more >hrt breast cancer: Topics by Science.gov
Positive Axillary Lymph Node; Stage 0 Breast Cancer AJCC v6 and v7; ... Adolescent intakes of iron, heme iron, fish, eggs, legumes and...
Read more >Untitled
... Berlingo load dimensions, Geia sas re paidia, Rich in iron fish, Narara creek tides! ... Bluestar 60 inch range, Stop loss limit...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you, guys! With version 0.1.50 I’m finally synced for the first time in 1.5 months ❤️
Hey @darrencavell and @D-Elektra thanks for reporting an issue and sorry for the late reply. We’ve made some measurable improvements on syncing speed which should be seen either in v0.1.50 or the next version. So it should be a lot less likely for the node to go out of sync
That being said, finding peers to sync from is still an issue sometimes which would cause the syncer to go
IDLE. We’re working on this in some of our upcoming projects on our roadmap so hopefully that should be addressed. I will leave this issue open because we have ongoing work but expect a while before another update as this is a longer running effort