ironfish: Segmentation fault (core dumped)

What happened?

Node Crashed while mining / running the node.

Running Ubuntu 22.04 using docker images.

Version

v0.1.61

Debug output

No response

Relevant log output

╰─$ docker run --rm --tty --interactive --network host --volume ~/.ironfishPhase3:/root/.ironfish ghcr.io/iron-fish/ironfish:latest start              

                                           
::::::::::          :::::::::::::::::         
::::::::::::       :::::::::::::::::::        
:::::::::::::     :::::::::::::::::::::       
::::::::::::::   ::::::::::::::::::::::::     
 ::::::::::::: ::::::::::        :::::::::    
   :::::::::::::::::::::          ::::::::::  
   :::::::::::::::::::::          :::::::::   
 ::::::::::::: ::::::::::        :::::::::    
::::::::::::::   ::::::::::::::::::::::::     
:::::::::::::     :::::::::::::::::::::       
::::::::::::       :::::::::::::::::::        
::::::::::           ::::::::::::::::         

Version       0.1.61 @ 009c85e
Node Name     NONE
Graffiti      DarkPool
Peer Identity pk+9bQ9YJoMO+2+kVlDEy6X2RZZKJj2Vy/8A2FYD0l8=
Peer Agent    ironfish/0.1.61/009c85e
Peer Port     9033
Bootstrap     test.bn1.ironfish.network
 
WebSocket server started at :::9033
Connected to the Iron Fish network
Starting sync from ZLVbvcx (minitag09). work: +3524627118, ours: 65, theirs: 69
Finding ancestor using linear search on last 3 blocks starting at 00000...db549 (65) from peer ZLVbvcx (minitag09) at 69
Found peer ZLVbvcx (minitag09) ancestor 00000...db549, syncing from 65 -> 69 (4) after 1 requests
Reorganizing chain from 00000...4eb7d (414) for 00000...81b61 (414) on prev 00000...4593c (413)
Reorganized chain. blocks: 1, old: 00000...4eb7d (414), new: 00000...4593c (413), fork: 00000...4593c (413)
PID 7 received SIGSEGV for address: 0x0
/usr/src/app/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x3236)[0x7fc1bd817236]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x13140)[0x7fc1c0316140]
node(napi_delete_reference+0x23)[0xb1cb73]
/usr/src/app/node_modules/@ironfish/rust-nodejs/ironfish-rust-nodejs.linux-x64-gnu.node(+0x5be72)[0x7fc1a23e8e72]
node[0xb30aca]
node[0x164ca86]
node[0x165f1c4]
node(uv_run+0x138)[0x164d3d8]
node(_ZN4node13SpinEventLoopEPNS_11EnvironmentE+0x145)[0xaad9e5]
node(_ZN4node6worker6Worker3RunEv+0xf6f)[0xc35e0f]
node[0xc363c8]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7ea7)[0x7fc1c030aea7]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fc1c022aa2f]
Segmentation fault (core dumped)

Graffiti

DarkPool

About this issue

Original URL
State: closed
Created a year ago
Comments: 28 (5 by maintainers)

Most upvoted comments

still seeing this on v 0.1.62

PID 60238 received SIGSEGV for address: 0x30
/root/ironfish/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x37a5)[0x7fd198b6c7a5]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x7fd198806420]
/usr/bin/node(_ZN2v88internal13GlobalHandles6CreateENS0_6ObjectE+0x23)[0xed5833]
/usr/bin/node(_ZN2v812api_internal18GlobalizeReferenceEPNS_8internal7IsolateEPm+0x13)[0xd53223]
/usr/bin/node(_ZN6v8impl9Reference3NewEP10napi_env__N2v85LocalINS3_5ValueEEEjbPFvS2_PvS7_ES7_S7_+0xae)[0xb113ee]
/usr/bin/node(napi_create_reference+0x9c)[0xb18efc]
/root/ironfish/ironfish-rust-nodejs/ironfish-rust-nodejs.linux-x64-gnu.node(+0x57cd6)[0x7fd1733e6cd6]
/root/ironfish/ironfish-rust-nodejs/ironfish-rust-nodejs.linux-x64-gnu.node(+0x4950e)[0x7fd1733d850e]
/root/ironfish/ironfish-rust-nodejs/ironfish-rust-nodejs.linux-x64-gnu.node(+0x2b82f)[0x7fd1733ba82f]
/root/ironfish/ironfish-rust-nodejs/ironfish-rust-nodejs.linux-x64-gnu.node(+0x4607c)[0x7fd1733d507c]
/usr/bin/node[0xb10d7d]
/usr/bin/node[0xdb0230]
/usr/bin/node(_ZN2v88internal21Builtin_HandleApiCallEiPmPNS0_7IsolateE+0xaf)[0xdb176f]
/usr/bin/node[0x16ef579]

Iron Fish version                  0.1.62 @ src
Iron Fish library                  0.0.39 @ src
Operating system                   Linux x64
CPU model(s)                       AMD EPYC 7401P 24-Core Processor
CPU threads                        48
RAM total                          62.50 GiB
Heap total                         3.99 GiB
Node version                       v18.13.0
ironfish in PATH                   true
Garbage Collector Exposed          true
Telemetry enabled                  true
Node name                          wd021
Block graffiti                     wd021
Account d0d44c uuid                d0d44c99-5537-4fa1-b267-4382e04f85f2
Account d0d44c name                default
Account d0d44c head hash           000000000003e2fbab3c5420f7bd9f2d36692ab6313835b939e67ce362b40df2
Account d0d44c head in chain       true
Account d0d44c sequence            4567

wd021 on Jan 20, 2023

Mine dumped again:

rtm@ironfishnode-01:~$ ironfish debug Iron Fish version 0.1.62 @ 4ab43f3 Iron Fish library 0.0.39 @ 4ab43f3 Operating system Linux x64 CPU model(s) Common KVM processor CPU threads 6 RAM total 7.67 GiB Heap total 2.00 GiB Node version v18.13.0 ironfish in PATH true Garbage Collector Exposed false Telemetry enabled true Node name Chadwicksracing Block graffiti Chadwicksracing Account c44b49 uuid c44b495d-378d-4119-b154-c2ea2d9510c2 Account c44b49 name default Account c44b49 head hash 000000000042d02da103add64f94852877361a0ba8cd4e13f56bdfb4c6b679d0 Account c44b49 head in chain true Account c44b49 sequence 4579

Chadwicksracing on Jan 20, 2023

Upgrading now. Will report back in the morning

On Thu, Jan 19, 2023, 8:56 PM mat-if @.***> wrote:

Hey folks, we’ve released a new version (0.1.62) that should fix this. Can you try upgrading and seeing if it fixes the problem? Thanks!

— Reply to this email directly, view it on GitHub https://github.com/iron-fish/ironfish/issues/2985#issuecomment-1397831729, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKAQTI2RSEURHPJBFN4PGH3WTHWFFANCNFSM6AAAAAAT7PVH2A . You are receiving this because you commented.Message ID: @.***>

Chadwicksracing on Jan 20, 2023

Hey folks, we’ve released a new version (0.1.62) that should fix this. Can you try upgrading and seeing if it fixes the problem? Thanks!

mat-if on Jan 20, 2023

To anyone else seeing this issue, can you run the command ironfish debug and post the contents here please? It will help us track down the issue faster.

mat-if on Jan 19, 2023