-
Notifications
You must be signed in to change notification settings - Fork 337
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
Bee 0.6.0-67cc8f24 segfaults on arm64 (Raspberry Pi 4, 8GB) #1806
Comments
Is this an already existing node? Did you migrate the local storage first? |
Yes, it is already an existing node. I torched the |
can you share your configuration file? |
Sure, sorry for the obvious omission.
|
What is the size of the statestore directory and capacity of your machine? |
The
|
There seems to be an issue with the You had no issues running your node on this machine before? |
Good sleuth work there! Correct, no issue when running the node previously. FYI, a member in the discord indicated that they had some success running |
I'm seeing the same |
Followed same procedure as @mfw78, have the same hardware, and bee |
There was a recent update to go v1.16, we suspect this may be causing the issue. May I ask you to compile and run your node w/ go 1.15? |
Hi, same proble here, with same hardware. Also tried bee 0.6.1. Still "segmentation violation" |
same hardware and same issue with you when i run 0.6.1, but when i apt install golang-go (which verison is go version go1.13.8 linux/arm64), i can run bee node, and log is "Error: chequebook init: insufficient ETH for initial deposit", so next step is funding my bee node |
Installation
Unfortunatly installation of golang-go did not solve my issue: May 22 16:25:26 raspi bee[6331]: time="2021-05-22T16:25:26+02:00" level=info msg="debug api address: 127.0.0.1:1635" |
when I restart bee-clef and bee, the bug comes back again |
@esadakar I can confirm that compiling with go 1.15 seems to resolve this issue as of commit 4d918bf. @snowicepeng @beckman76 Just installing a different version of |
Thx, I also found the same problem on github, maybe using 0.0.3 version of snappy (bee uses version 0.0.2) can solve the problem on Raspberry Pi 4. |
That's what I thought, just was curious, why installation of go compiler solved somebodies issue. But it seems that he was lucky just once. ;-) |
Did the following:
Runs fine now! (Using Either the Golang build version needs to be decremented or the issue with |
go-ethereum v1.10.3 updated to snappy v0.0.3 for the same issue |
Same issue here with 0.6.1 on a jetson tx2 Also same issue on commit |
With the following go.mod patch it works fine:
|
it works for me: |
@paralin You mentioned with the upgrade worked. Did you use go 1.16? |
@haroldcy Can you confirm go 1.16 works on arm64 with go-ethereum v1.10.3 update? |
Summary
After following the upgrade instructions, installing bee-clef
0.4.12
and bee0.6.0
,bee
fails to start - segfaulting.The
/var/lib/bee
folder was sanitised to contain only as follows:Steps to reproduce
Apply standard upgrade instructions.
Expected behavior
Bee to start gracefully and connect to the networking, collecting some of that sweet, sweet pollen to make some gBZZ.
Actual behavior
The text was updated successfully, but these errors were encountered: