Can't run beacon-chain on macOS 10.13.6 #5240

alrevuelta · 2020-03-29T18:57:25Z

I'm trying to run the beacon-chain under macOS 10.13.6 following the doc with the following command, but I'm getting an error:

./prysm.sh beacon-chain --clear-db --datadir=$HOME/prysm

At the beginning of the output I can see this:

Latest Prysm version is v0.3.8.
Beacon chain is up to date.
Validator is up to date.
Starting Prysm beacon-chain

But right after it I get the following error

dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin
  Referenced from: /Users/alr/Desktop/prysm/./dist/beacon-chain-v0.3.8-darwin-amd64
  Expected in: flat namespace

dyld: Symbol not found: ____chkstk_darwin
  Referenced from: /Users/alr/Desktop/prysm/./dist/beacon-chain-v0.3.8-darwin-amd64
  Expected in: flat namespace

...

I don't get the flat namespace. Any ideas?

The text was updated successfully, but these errors were encountered:

prestonvanloon · 2020-03-29T20:05:19Z

Can any Mac owner take a look please?
@rauljordan @terencechain @0xKiwi

terencechain · 2020-03-30T17:30:39Z

it works for me, running 10.15.2 (19C57)

prestonvanloon · 2020-03-30T17:35:41Z

I talked with @0xKiwi and he wasn't able to reproduce. Can you try on a newer version of Mac OS?

rauljordan · 2020-03-30T18:24:02Z

Hi @alrevuelta can you try brew install cmake && brew install make and retry? Seems like that worked in other projects that encountered the similar error message: nodegui/nodegui#391

rauljordan · 2020-03-30T18:24:30Z

Confirmed it works for me, I am running 10.15.3

rauljordan · 2020-04-08T14:20:10Z

Closing due to inactivity

hacktar · 2020-04-20T09:28:57Z

Some error here even after i try brew install cmake && brew install make

Latest Prysm version is v1.0.0-alpha.4.

Beacon chain is up to date.
Validator is up to date.
Starting Prysm validator accounts
reatem--keystore-path=/Users/xxxx/validator
assword=xxxx
^[[?1;2cSIGILL: illegal instruction
PC=0x406b270 m=0 sigcode=1

goroutine 1 [running, locked to thread]:
runtime.asyncPreempt()
	src/runtime/preempt_amd64.s:8 fp=0xc000066e90 sp=0xc000066e88 pc=0x406b270
time.init()
	GOROOT/src/time/format.go:394 fp=0xc000066e98 sp=0xc000066e90 pc=0x40d1f50
runtime.doInit(0x5b22c20)
	GOROOT/src/runtime/proc.go:5414 +0x8a fp=0xc000066ec8 sp=0xc000066e98 pc=0x4045c1a
runtime.doInit(0x5b25080)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000066ef8 sp=0xc000066ec8 pc=0x4045be7
runtime.doInit(0x5b29100)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000066f28 sp=0xc000066ef8 pc=0x4045be7
runtime.doInit(0x5b26820)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000066f58 sp=0xc000066f28 pc=0x4045be7
runtime.doInit(0x5b2fc00)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000066f88 sp=0xc000066f58 pc=0x4045be7
runtime.main()
	GOROOT/src/runtime/proc.go:190 +0x1ce fp=0xc000066fe0 sp=0xc000066f88 pc=0x403901e
runtime.goexit()
	src/runtime/asm_amd64.s:1373 +0x1 fp=0xc000066fe8 sp=0xc000066fe0 pc=0x40699f1

rax    0x5b22c20
rbx    0x7
rcx    0x0
rdx    0x5b22c58
rdi    0x30
rsi    0x40d1f50
rbp    0xc000066eb8
rsp    0xc000066e88
r8     0xe004e08
r9     0x203000
r10    0x6
r11    0xfb
r12    0xfb
r13    0x0
r14    0x51fc6c7
r15    0x0
rip    0x406b270
rflags 0x10202
cs     0x2b
fs     0x0
gs     0x0

Reopen the issue please.

nisdas · 2020-04-20T09:33:32Z

ok reopening this issue @hacktar . This looks like a regression which was introduced in go 1.14, the fix for this has been included in go 1.14.1 .
golang/go#37459
golang/go#37478

After we update prysm to 1.14.1, this issue should no longer be a problem

nisdas · 2020-04-20T10:06:47Z

@hacktar You can keep an eye on #5535, this should fix your issues.

hacktar · 2020-04-20T12:56:04Z

@hacktar You can keep an eye on #5535, this should fix your issues.

I pulled the branch

On branch updatego1.14.1
Your branch is up to date with 'origin/updatego1.14.1'.

But still doesn't work :-(

Latest Prysm version is v1.0.0-alpha.4.
Beacon chain is up to date.
Validator is up to date.
Starting Prysm validator accounts
reatem--keystore-path=/Users/xxxx/validator
assword=xxxx
^[[?1;2cSIGILL: illegal instruction
PC=0x406b270 m=0 sigcode=1

goroutine 1 [running, locked to thread]:
runtime.asyncPreempt()
	src/runtime/preempt_amd64.s:8 fp=0xc000185d70 sp=0xc000185d68 pc=0x406b270
github.com/syndtr/goleveldb/leveldb/memdb.init()
	external/com_github_syndtr_goleveldb/leveldb/memdb/memdb.go:22 fp=0xc000185d78 sp=0xc000185d70 pc=0x458db00
runtime.doInit(0x5b24ea0)
	GOROOT/src/runtime/proc.go:5414 +0x8a fp=0xc000185da8 sp=0xc000185d78 pc=0x4045c1a
runtime.doInit(0x5b30300)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000185dd8 sp=0xc000185da8 pc=0x4045be7
runtime.doInit(0x5b2a3e0)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000185e08 sp=0xc000185dd8 pc=0x4045be7
runtime.doInit(0x5b306c0)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000185e38 sp=0xc000185e08 pc=0x4045be7
runtime.doInit(0x5b35580)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000185e68 sp=0xc000185e38 pc=0x4045be7
runtime.doInit(0x5b33240)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000185e98 sp=0xc000185e68 pc=0x4045be7
runtime.doInit(0x5b29680)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000185ec8 sp=0xc000185e98 pc=0x4045be7
runtime.doInit(0x5b305c0)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000185ef8 sp=0xc000185ec8 pc=0x4045be7
runtime.doInit(0x5b2afc0)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000185f28 sp=0xc000185ef8 pc=0x4045be7
runtime.doInit(0x5b29880)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000185f58 sp=0xc000185f28 pc=0x4045be7
runtime.doInit(0x5b2fc00)
	GOROOT/src/runtime/proc.go:5409 +0x57 fp=0xc000185f88 sp=0xc000185f58 pc=0x4045be7
runtime.main()
	GOROOT/src/runtime/proc.go:190 +0x1ce fp=0xc000185fe0 sp=0xc000185f88 pc=0x403901e
runtime.goexit()
	src/runtime/asm_amd64.s:1373 +0x1 fp=0xc000185fe8 sp=0xc000185fe0 pc=0x40699f1

goroutine 8 [runnable]:
github.com/ethereum/go-ethereum/consensus/ethash.(*Ethash).remote(0xc0001401c0, 0x0, 0x0, 0x0, 0x0)
	external/com_github_ethereum_go_ethereum/consensus/ethash/sealer.go:200 +0x15c
created by github.com/ethereum/go-ethereum/consensus/ethash.New
	external/com_github_ethereum_go_ethereum/consensus/ethash/ethash.go:496 +0x35c

goroutine 7 [chan receive]:
github.com/ethereum/go-ethereum/metrics.(*meterArbiter).tick(0x5c4b140)
	external/com_github_ethereum_go_ethereum/metrics/meter.go:289 +0x78
created by github.com/ethereum/go-ethereum/metrics.NewMeterForced
	external/com_github_ethereum_go_ethereum/metrics/meter.go:70 +0x105

rax    0x5b24ea0
rbx    0x9
rcx    0x0
rdx    0x5b24ee8
rdi    0xc00006fe90
rsi    0x458db00
rbp    0xc000185d98
rsp    0xc000185d68
r8     0x11
r9     0x11
r10    0x51fc69c
r11    0x1
r12    0xffffffffffffffff
r13    0x1ea
r14    0x1e9
r15    0x200
rip    0x406b270
rflags 0x10202
cs     0x2b
fs     0x0
gs     0x0

do I have to wait for it to be released on the master?

nisdas · 2020-04-20T13:31:59Z

Hey it will not work like that. The script only fetches the precompiled binaries. So you will have to wait till the next release with this

hacktar · 2020-04-20T13:44:07Z

Hey it will not work like that. The script only fetches the precompiled binaries. So you will have to wait till the next release with this

sorry, what a shame! :-/

Thanks a lot ;-)

prestonvanloon · 2020-04-22T03:53:19Z

@hacktar v1.0.0-alpha.5 has been released with this change included. Thanks

hacktar · 2020-04-22T13:08:10Z

It doesn't work... maybe some problem with MacOS version!

dyld: Symbol not found: ____chkstk_darwin
  Referenced from: /Users/xxx/Documents/Code/prysm/./dist/validator-v1.0.0-alpha.5-darwin-amd64
  Expected in: flat namespace

It doesn't matter, carry on :-(

nisdas · 2020-04-22T13:12:39Z

something went wrong with cross-compiling it looks like, @prestonvanloon any idea ?
@hacktar re-opening this again.

prestonvanloon · 2020-04-23T19:26:38Z

Please install mac OS X 10.14 or greater. I'll update docs site requirements for Mac OS X

hacktar · 2020-04-23T21:21:01Z

Please install mac OS X 10.14 or greater. I'll update docs site requirements for Mac OS X

Unfortunately macOS High Sierra 10.13.6 version is the latest available for certain older types of mac computers.

Anyway thanks

prestonvanloon · 2020-04-23T21:25:25Z

Sorry to hear that. You can still run with docker or compile from source, but our precompiled binaries will only work on 10.14 or greater.

prestonvanloon self-assigned this Mar 30, 2020

rauljordan closed this as completed Apr 8, 2020

nisdas reopened this Apr 20, 2020

nisdas mentioned this issue Apr 20, 2020

Update to 1.14.1 #5535

Merged

prylabs-bulldozer bot closed this as completed in #5535 Apr 20, 2020

nisdas reopened this Apr 22, 2020

prestonvanloon closed this as completed Apr 23, 2020

Can't run beacon-chain on macOS 10.13.6 #5240

Can't run beacon-chain on macOS 10.13.6 #5240

Comments

alrevuelta commented Mar 29, 2020

prestonvanloon commented Mar 29, 2020

Uh oh!

terencechain commented Mar 30, 2020

Uh oh!

prestonvanloon commented Mar 30, 2020

Uh oh!

rauljordan commented Mar 30, 2020

Uh oh!

rauljordan commented Mar 30, 2020

Uh oh!

rauljordan commented Apr 8, 2020

Uh oh!

hacktar commented Apr 20, 2020

Uh oh!

nisdas commented Apr 20, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nisdas commented Apr 20, 2020

Uh oh!

hacktar commented Apr 20, 2020

Uh oh!

nisdas commented Apr 20, 2020

Uh oh!

hacktar commented Apr 20, 2020

Uh oh!

prestonvanloon commented Apr 22, 2020

Uh oh!

hacktar commented Apr 22, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nisdas commented Apr 22, 2020

Uh oh!

prestonvanloon commented Apr 23, 2020

Uh oh!

hacktar commented Apr 23, 2020

Uh oh!

prestonvanloon commented Apr 23, 2020 via email

Uh oh!

nisdas commented Apr 20, 2020 •

edited

Loading

hacktar commented Apr 22, 2020 •

edited

Loading