geth和macOS Sierra问题

Question

有没有人幸运地跑到macOS塞拉贝塔？在升级和试用之后，我会经常崩溃。

每次在崩溃日志中，原因似乎是不同的。以下是一个例子：

> Last login: Fri Aug 12 20:10:42 on ttys000 Erics-MacBook:~ Eric$
> /Applications/Ethereum-Wallet.app/Contents/Frameworks/node/geth/geth ;
> exit; I0812 20:17:43.023333 cmd/utils/flags.go:678] You're one of the
> lucky few that will try out the JIT VM (random). If you get a
> consensus failure please be so kind to report this incident with the
> block hash that failed. You can switch to the regular VM by setting
> --jitvm=false I0812 20:17:43.024375 ethdb/database.go:82] Alloted 128MB cache and 1024 file handles to
> /Users/Eric/Library/Ethereum/chaindata I0812 20:17:43.726820
> cmd/utils/flags.go:842]
> ------------------------------------------------------------------------------------------------ I0812 20:17:43.726847 cmd/utils/flags.go:843] Geth is currently
> configured to SUPPORT the DAO hard-fork! I0812 20:17:43.726854
> cmd/utils/flags.go:844] You can change your choice prior to block
> #1920000 with --support-dao-fork or --oppose-dao-fork. I0812 20:17:43.726860 cmd/utils/flags.go:845] After the hard-fork block
> #1920000 passed, changing chains requires a resync from scratch! I0812 20:17:43.726866 cmd/utils/flags.go:846]
> ------------------------------------------------------------------------------------------------ I0812 20:17:43.729552 ethdb/database.go:169] closed
> db:/Users/Eric/Library/Ethereum/chaindata I0812 20:17:43.759195
> ethdb/database.go:82] Alloted 128MB cache and 1024 file handles to
> /Users/Eric/Library/Ethereum/chaindata I0812 20:17:44.369724
> ethdb/database.go:82] Alloted 16MB cache and 16 file handles to
> /Users/Eric/Library/Ethereum/dapp I0812 20:17:44.388661
> eth/backend.go:172] Protocol Versions: [63 62], Network Id: 1 I0812
> 20:17:44.388851 eth/backend.go:201] Blockchain DB Version: 3 I0812
> 20:17:44.397691 core/blockchain.go:206] Last header: #2060244
> [4f8d7f31…] TD=47316740849566229470 I0812 20:17:44.397747
> core/blockchain.go:207] Last block: #2060244 [4f8d7f31…]
> TD=47316740849566229470 I0812 20:17:44.397767 core/blockchain.go:208]
> Fast block: #2060244 [4f8d7f31…] TD=47316740849566229470 I0812
> 20:17:44.412012 p2p/server.go:313] Starting Server I0812
> 20:17:44.416381 p2p/nat/nat.go:111] mapped network port udp:30303 ->
> 30303 (ethereum discovery) using NAT-PMP(10.0.1.1) I0812
> 20:17:44.428095 p2p/discover/udp.go:217] Listening,
> enode://9d12afe2cd3a38fe3b2184bc60767cd4a94f21eca3500373ce8fa75b885fb7035288de6740f538410c25145c81dbf4b90eeacf2c00f8839cb478ea13f6a54d34@107.3.116.31:30303
> I0812 20:17:44.428776 p2p/server.go:556] Listening on [::]:30303 I0812
> 20:17:44.430634 node/node.go:296] IPC endpoint opened:
> /Users/Eric/Library/Ethereum/geth.ipc I0812 20:17:44.433749
> p2p/nat/nat.go:111] mapped network port tcp:30303 -> 30303 (ethereum
> p2p) using NAT-PMP(10.0.1.1) I0812 20:18:00.641616
> eth/downloader/downloader.go:320] Block synchronisation started panic:
> sync: inconsistent mutex state
> 
> goroutine 331 [running]: panic(0x48f6ea0, 0xc822880430)
>   /Users/jeffrey/goroot16/src/runtime/panic.go:464 +0x3e6
> sync.(*Mutex).Lock(0xc82288eca0)
>   /Users/jeffrey/goroot16/src/sync/mutex.go:75 +0x16d
> github.com/ethereum/go-ethereum/p2p.(*rlpx).ReadMsg(0xc82288ec90, 0x0,
> 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
>   /Users/jeffrey/go/src/github.com/ethereum/go-ethereum/p2p/rlpx.go:86
> +0x8a github.com/ethereum/go-ethereum/p2p.(*Peer).readLoop(0xc820aa0000,
> 0xc82145c000)
>   /Users/jeffrey/go/src/github.com/ethereum/go-ethereum/p2p/peer.go:214
> +0x90 created by github.com/ethereum/go-ethereum/p2p.(*Peer).run  /Users/jeffrey/go/src/github.com/ethereum/go-ethereum/p2p/peer.go:145
> +0xf9 logout Saving session... ...copying shared history... ...saving history...truncating history files... ...completed.
> 
> [Process completed]

Answer 1

确保没有使用命令geth运行的重复的ps -ef | grep geth副本。

然后运行将清除现有区块链数据的geth removedb。

然后运行geth --fast --support-dao-fork console启动块链数据的新下载。

您还可以尝试将现有的~/.ethereum/chaindata目录重命名为类似于~/.ethereum/chaindata_problems的目录。然后运行geth --fast --support-dao-fork console开始重新下载区块链数据。如果问题仍然存在，问题更有可能出现在二进制文件中。然后，您可以将旧的chaindata目录移回同步时继续。

Answer 2

我发现了修复，但如果我是完全诚实的，我并不真正理解它，但想把它传递给开发团队。

https://forums.docker.com/t/docker-beta-for-mac-does-not-work-and-hangs-frequently-on-macos-10-12/18109/5

禁用ntpd通过sudo launchctl卸载/System/Library/LaunchDaemons/org.ntp.ntpd.plist现在允许我同步！不知道这是苹果虫还是去虫什么的。