bitcoin-cli: error: couldn't connect to server: EOF reached (code 1) #10763

issue BitWaspBitWasp opened this issue on July 7, 2017

BitWaspBitWasp commented at 12:31 PM on July 7, 2017: none

sometimes I have the problem(Debian):

bitcoin-cli listtransactions

error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port)

How can I fix it ?
achow101 commented at 8:13 PM on July 28, 2017: member

This error happens when bitcoin-cli is unable to connect to the RPC server. Make sure the rpc server is running (bitcoind runs it automatically, with bitcoin-qt, you need the server=1 option in your bitcoin.conf file.
fanquake closed this on Aug 13, 2017
Jeans5 commented at 9:50 PM on September 17, 2018: none

I have the same issue here, while the option server=1 is confirmed in bitcoin.conf file
constantinedev commented at 4:38 AM on April 28, 2019: none

I have the same problem
generalsnout commented at 9:37 PM on March 19, 2020: none

How do you edit the bitcoin-cli file?
kiminuo commented at 7:41 AM on June 19, 2020: contributor
We have a test machine with Windows 10 and we can confirm that the bug is present in Bitcoin Core 0.19.1 and Bitcoin Core 0.20.0.

Additionally, we know:
- Restart of the daemon does not help to solve the problem (it helps for like 30 seconds and RPC responds for that time being).
- Restart of the machine helps (until it breaks again).
- The bug affects both Qt and daemon.
- There is no useful information in debug.log.
- Node works as expected other than this issue.
- Normally, it takes several weeks until the bug presents itself.
Note: We had Bitcoin Core 0.19.1 running, found the bug, tried to upgrade to avoid the bug but to no avail.
MarcoFalke reopened this on Jun 19, 2020
MarcoFalke added the label Utils/log/libs on Jun 19, 2020
MarcoFalke renamed this:
~~error: couldn't connect to server: EOF reached (code 1)~~
bitcoin-cli: error: couldn't connect to server: EOF reached (code 1)
on Jun 19, 2020
SsNiPeR1 commented at 7:35 PM on March 21, 2021: none

It's not fixed in 2021!!!! @bitcoin
milkcoke commented at 2:50 AM on November 15, 2021: none
🔒 Cause

Maybe you didn't kill all bitcoind process. so you can't start bitcoind with same port number since another bitcoind daemon is already running state

You can check it below command
```
$ netstat -tnlp
```
🔑 Solution

Kill them all.

Case 1. Could find PID/Program name

ex) 30375/bitcoind
```
$ kill -9 [PID-of-bitcoind]
```
Case 2. Not found PID/Program of bitcoind
```
$ pkill bitcoind
```
start daemon again
```
$ bitcoind --datadir=[path-of-data]
```
fanquake commented at 9:28 AM on August 15, 2022: member

Normally, it takes several weeks until the bug presents itself.

Re-closing this. Without any concrete steps to reproduce this issue, I'm not sure there's anything we can do here.
fanquake closed this on Aug 15, 2022
bitcoin locked this on Aug 15, 2023