BlockchainCommons / GordianServer-macOS

Tor-protected full-node GordianServer for macOS
Other
63 stars 8 forks source link

BUG: Gordian Server Does Not Recognize Bitcoin is Running #162

Open shannona opened 2 years ago

shannona commented 2 years ago

Built Gordian Server #161 from Source, created a Notarized DMG, and installed from there. Started it up on a machine that had definitely run Gordian Server before.

It got immediately and permanently locked on "Checking if Bitcoin Core is Running ..."

Screen Shot 2021-10-26 at 9 03 42 AM

Bitcoin is running, and was starting by this new version of Bitcoin Core:

$ ps axuww | grep bitcoin
shannona          9813  10.9  2.6  4990180 440512   ??  Ss    9:00AM   0:28.73 /Users/shannona/.gordian/BitcoinCore/bitcoin-22.0/bin/bitcoind -datadir=/Users/shannona/Library/Application Support/Bitcoin -daemon
shannona         10214   0.0  0.0  4296636    564 s000  R+    9:07AM   0:00.00 grep bitcoin

The log shows nothing of particular note:

best=000000000000021825cb4b56ab892f89458894c075638eae584da5e9569e0f05 height=201025 version=0x00000002 log2_work=68.777962 tx=7510293 date='2012-09-29T06:24:15Z' progress=0.011108 cache=34.9MiB(182998txo)
2021-10-20T23:13:55Z UpdateTip: new best=0000000000000047bd1a83c4e4675fa691c145ea5c8c6989cf8ef85a0a51d846 height=201026 version=0x00000001 log2_work=68.777997 tx=7510296 date='2012-09-29T06:27:56Z' progress=0.011108 cache=34.9MiB(182991txo)
2021-10-20T23:13:55Z UpdateTip: new best=00000000000005554c7e1a7baea225cbb4dcb453e612fb6417ca7a18fedb6b74 height=201027 version=0x00000001 log2_work=68.778032 tx=7510408 date='2012-09-29T06:31:13Z' progress=0.011109 cache=34.9MiB(182992txo)
2021-10-20T23:13:55Z UpdateTip: new best=0000000000000194fe828744e0b44fc517dd54468a38e36a0473acd99be5390b height=201028 version=0x00000001 log2_work=68.778067 tx=7510519 date='2012-09-29T06:41:35Z' progress=0.011109 cache=34.9MiB(183080txo)
2021-10-20T23:13:55Z UpdateTip: new best=00000000000001a653271b46e546131841e1bf28add970f906cc0f1858813f7d height=201029 version=0x00000001 log2_work=68.778102 tx=7510525 date='2012-09-29T06:59:18Z' progress=0.011109 cache=34.9MiB(183104txo)
2021-10-20T23:13:55Z UpdateTip: new best=0000000000000523fe23d265f01ffb7ca9824bc222ba34c8f3a6fd3f886ac748 height=201030 version=0x00000002 log2_work=68.778137 tx=7510724 date='2012-09-29T06:57:26Z' progress=0.011109 cache=35.0MiB(183355txo)
2021-10-20T23:13:55Z UpdateTip: new best=0000000000000178057fd82902eeaa1c356ebe9ef3de6541ea17aeb150aa10ee height=201031 version=0x00000002 log2_work=68.778172 tx=7510914 date='2012-09-29T07:13:17Z' progress=0.011109 cache=35.0MiB(183665txo)
shannona commented 2 years ago

Closed and restarted: it recognized that the Bitcoin Core was running within a few seconds, as it should.

This wasn't the first time I've seen the check get stuck, but it was the most long-lived; that's usually cleared when I changed window focus.

Fonta1n3 commented 2 years ago

It can take time... Permanently seems like a while 😅

How long was it actually locked like that?

shannona commented 2 years ago

3-5 minutes. I waited. I walked around the house. I waited. I screenshot. I looked in the logs. I changed focus and back.

I finally gave up and restarted after which it immediately worked.

shannona commented 2 years ago

I also now have seen this in the #160-derived builds, @Fonta1n3 . Exact same circumstances. On startup, it checked if Bitcoin was running and never came back. Looked at the process table and it was running.

Time elapsed between startup and my closing it now that I've written this report: 8 minutes.