RequestPrivacy
commented
1 year ago After running roughly 20h just fine I have the same problem again. The connection closes but maybe its bitcoinds fault:
Mar 16 13:04:03 debian Fulcrum[1554690]: [2023-03-16 13:04:01.350] <BitcoinD.3> TCP BitcoinD.3 (id: 4) 127.0.0.1:8332: error 1 (The remote host closed the connection)
Mar 16 13:04:03 debian Fulcrum[1554690]: [2023-03-16 13:04:02.192] <BitcoinD.3> Lost connection to bitcoind, will retry every 5 seconds ...
Mar 16 13:04:03 debian Fulcrum[1554690]: [2023-03-16 13:04:01.350] <BitcoinD.2> TCP BitcoinD.2 (id: 3) 127.0.0.1:8332: error 1 (The remote host closed the connection)
Mar 16 13:04:03 debian Fulcrum[1554690]: [2023-03-16 13:04:02.193] <SynchMempool> 762083: FAIL: bitcoind connection lost
Mar 16 13:04:03 debian Fulcrum[1554690]: [2023-03-16 13:04:01.885] <Controller> 13115 mempool txs involving 149643 addresses
Mar 16 13:04:03 debian Fulcrum[1554690]: [2023-03-16 13:04:01.680] <BitcoinD.1> TCP BitcoinD.1 (id: 2) 127.0.0.1:8332: error 1 (The remote host closed the connection)
Mar 16 13:04:03 debian Fulcrum[1554690]: [2023-03-16 13:04:02.193] <BitcoinD.2> Lost connection to bitcoind, will retry every 5 seconds ...
Mar 16 13:04:03 debian Fulcrum[1554690]: [2023-03-16 13:04:02.193] <BitcoinD.1> Lost connection to bitcoind, will retry every 5 seconds ...
Mar 16 13:04:03 debian Fulcrum[1554690]: [2023-03-16 13:04:02.193] <Controller> Failed to synch blocks and/or mempool
Mar 16 13:04:06 debian Fulcrum[1554690]: [2023-03-16 13:04:06.945] <BitcoinD.1> Unable to open cookie file '/home/bitcoin/.bitcoin/.cookie': Permission denied
Mar 16 13:04:06 debian Fulcrum[1554690]: [2023-03-16 13:04:06.945] <BitcoinD.2> Unable to open cookie file '/home/bitcoin/.bitcoin/.cookie': Permission denied
Mar 16 13:04:06 debian Fulcrum[1554690]: [2023-03-16 13:04:06.945] <BitcoinD.3> Unable to open cookie file '/home/bitcoin/.bitcoin/.cookie': Permission deniedIt seems that the .cookie file has been newly created at the same time fulcrum fails to connect:
# compare to "Mar 15" of OP
pi@debian: $ ls -la | grep .cookie
-rw-r----- 1 bitcoin btcCookie 75 Mar 16 13:04 .cookie
pi@debian: $ bitcoin-cli uptime
7032 # roughly 2h which is consistent with the creation time of the cookie file Will investigate why bitcoind shuts itself down. Any thoughts/help is appreciated though.
Going to close this off as it doesn't look like fulcrum is the problem here but handles the matter rather superb!
cculianu
Note - investigation revealed this issue isn't related to fulcrum
Description
I run a bitcoind (Bitcoin Core v22.0.0) and fulcrum (1.7.0) on the same Pi 4 and use cookie authentication.
To keep permission to an absolute minimum I allow read access to the .cookie file to a dedicated btcCookie group in which the fulcrum user is a member:
To achieve the above group setting I use
-startupnotifyin mybitcoind.servicefileDuring start-up fulcrum has no problem to connect to bitcoind.
Problem
Sometimes fulcrum looses connection to bitcoind. I'm not yet sure why.
So my question is: a.) what could be the cause that the connection is lost in the first place? The pi is only running bitcoind, fulcrum and sparrow server (a wallet with minimal terminal GUI). Load averages 3.05G RAM of the total 3.7G available, no swap. b.) what's the matter with the cookie-file (fulcrum is denied access but after a while re-allowed to read the .cookie?)
Regarding a.) is there a setting to minimize fulcrums load on the RAM? Maybe a spike in load is causing the issue for fulcrum (and bitcoind for that matter)?