-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
alpha5 binary crash (amd64v2) #12570
Comments
The amd64 binary (w/o v2) also crashes. |
Might relate to #12556 |
I can confirm that node-real#547 resolves this problem. I've built erigon3-alpha5 with this single patch added and now it works. |
@thorstenhirsch If you run the same command you did but after compiling erigon from source (i.e. I would like to check if this could be a cross-compilation issue first. |
The command line was completely the same in both cases: 1.) erigon3 alpha5 binary* download from github: crash *) I tried the amd64v2 binary first, then amd64, but both crashed. So, I actually didn't run a self-compiled version of the original alpha5 release (w/o the patch). Do you want me to test that? |
@thorstenhirsch yes, I would like you to test on the self-compiled version of the original alpha5 release without the patch. |
@antonis19: The self-compiled version of the original alpha5 works successfully. :-( |
@thorstenhirsch thanks for checking. I think this indicates that there might be a problem with the way we are doing cross compilation, although I've checked this binary on an AMD cpu and it worked fine for me. I will need to investigate this further. |
@thorstenhirsch since we are not able to reproduce this crash on our end I would like you to assist us in the debugging process by running the following command using the downloaded erigon binary from the release to trace the system calls happening: strace -f -o erigon_binary_strace.log ./erigon --maxpeers=50 \
--nat=extip:$IP \
--chain=mainnet \
--http --ws \
--http.api=eth,admin,debug,net,trace,web3,erigon,txpool \
--http.addr=0.0.0.0 --http.port=8545 \
--http.vhosts=* --http.corsdomain=* \
--maxpeers=50 \
--prune.mode=archive And provide the cat erigon_binary_strace.log | grep "= -1" > erigon_binary_strace_errors.log and provide the |
Sure. Here we go. @antonis19 |
@thorstenhirsch , hi Do you have latest versions of packages on your Linux? |
Just to be sure, @lystopad, your questions are about the self-compiled erigon, which is working, right? The downloaded alpha5 binary is the one crashing. go env
ldd erigon
It's arch linux, all packages were up-to-date when compiling erigon last week (e.g. glibc 2.40, go 1.23.2). |
I guess a Ryzen 7 5xxx CPU should be able to run amd64v2 binaries, right?
System information
Erigon version:
./erigon --version
erigon version 3.00.0-alpha5-78f3647d
OS & Version: Windows/Linux/OSX
arch linux, kernel 6.11
/proc/cpuinfo
Erigon Command (with flags/config):
Consensus Layer:
internal
Consensus Layer Command (with flags/config):
Chain/Network:
mainnet
Expected behaviour
start (it's the initial start, datadir is empty)
Actual behaviour
Steps to reproduce the behaviour
start with given command
Backtrace
see "actual behaviour"
The text was updated successfully, but these errors were encountered: