Bitcoin Cash - BCH - Linux "failed after select(): Connection refused"

[zoltanb]

I installed Bitcoin Cash on a linux distribution.
For some reason, the blockchain is not getting downloaded. I checked debug.log and see similar entries:

2017-09-11 21:39:23 connect() to 198.245.51.212:8333 failed after select(): Connection refused (111)

What can be wrong?

[melea]

why you try to do that , to your machine?
, bitcoin only one. and Bitcoin works fine,
 Bitcoincash is for noobs and ponzy
Please download Bitcoin core wallet
https://bitcoin.org/es/descargar
cheers

[zoltanb]

why you try to do that , to your machine?
, bitcoin only one. and Bitcoin works fine,
 Bitcoincash is for noobs and ponzy
Please download Bitcoin core wallet
https://bitcoin.org/es/descargar
cheers

I also have Bitcoin Core on another machine. Works well but I wanted to also explore Bitcoin Cash.

[vbspam]

why you try to do that , to your machine?
, bitcoin only one. and Bitcoin works fine,
 Bitcoincash is for noobs and ponzy
Please download Bitcoin core wallet
https://bitcoin.org/es/descargar
cheers

I also have Bitcoin Core on another machine. Works well but I wanted to also explore Bitcoin Cash.

Hi,

I did hit the same issue. And it looks I have a fix.

With no warranty: While having the BitcoinABC client OFF (not running "bitcoin-qt" and/or not running "bitcoind"), just rename the file peers.dat to something else. Then run the client again. It will download new peers from the network and recreate the "peers.dat" file for you.

Technically looks like 111 code aka ECONNREFUSED means that "No-one listening on the remote address." (source https://linux.die.net/man/2/connect). Then by quick check of the bitcoind documentation the only candidate who caches the peers table is the peers.dat file.


Have fun and enjoy your BCH coins :-)

[zoltanb]

why you try to do that , to your machine?
, bitcoin only one. and Bitcoin works fine,
 Bitcoincash is for noobs and ponzy
Please download Bitcoin core wallet
https://bitcoin.org/es/descargar
cheers

I also have Bitcoin Core on another machine. Works well but I wanted to also explore Bitcoin Cash.

Hi,

I did hit the same issue. And it looks I have a fix.

With no warranty: While having the BitcoinABC client OFF (not running "bitcoin-qt" and/or not running "bitcoind"), just rename the file peers.dat to something else. Then run the client again. It will download new peers from the network and recreate the "peers.dat" file for you.

Technically looks like 111 code aka ECONNREFUSED means that "No-one listening on the remote address." (source https://linux.die.net/man/2/connect). Then by quick check of the bitcoind documentation the only candidate who caches the peers table is the peers.dat file.


Have fun and enjoy your BCH coins :-)

I already tried it. It does not work.

[vbspam]

why you try to do that , to your machine?
, bitcoin only one. and Bitcoin works fine,
 Bitcoincash is for noobs and ponzy
Please download Bitcoin core wallet
https://bitcoin.org/es/descargar
cheers

I also have Bitcoin Core on another machine. Works well but I wanted to also explore Bitcoin Cash.

Hi,

I did hit the same issue. And it looks I have a fix.

With no warranty: While having the BitcoinABC client OFF (not running "bitcoin-qt" and/or not running "bitcoind"), just rename the file peers.dat to something else. Then run the client again. It will download new peers from the network and recreate the "peers.dat" file for you.

Technically looks like 111 code aka ECONNREFUSED means that "No-one listening on the remote address." (source https://linux.die.net/man/2/connect). Then by quick check of the bitcoind documentation the only candidate who caches the peers table is the peers.dat file.


Have fun and enjoy your BCH coins :-)

I already tried it. It does not work.

What is your client version?

I was unable to do anything with the new client version 15.x. When downgraded to 14.6 and did the trick with the peers.dat, it started to work.

[zoltanb]

why you try to do that , to your machine?
, bitcoin only one. and Bitcoin works fine,
 Bitcoincash is for noobs and ponzy
Please download Bitcoin core wallet
https://bitcoin.org/es/descargar
cheers

I also have Bitcoin Core on another machine. Works well but I wanted to also explore Bitcoin Cash.

Hi,

I did hit the same issue. And it looks I have a fix.

With no warranty: While having the BitcoinABC client OFF (not running "bitcoin-qt" and/or not running "bitcoind"), just rename the file peers.dat to something else. Then run the client again. It will download new peers from the network and recreate the "peers.dat" file for you.

Technically looks like 111 code aka ECONNREFUSED means that "No-one listening on the remote address." (source https://linux.die.net/man/2/connect). Then by quick check of the bitcoind documentation the only candidate who caches the peers table is the peers.dat file.


Have fun and enjoy your BCH coins :-)

I already tried it. It does not work.

What is your client version?

I was unable to do anything with the new client version 15.x. When downgraded to 14.6 and did the trick with the peers.dat, it started to work.

Had to add a few nodes manually from this list:
https://bitnodes.21.co/nodes/?q=Bitcoin%20ABC:0.14.6
Used command: bitcoin-cli "node:port" "add"

Once added them, it started downloading the blockchain. Now, it is already up to date. My client version is 0.15.something.

[immakingacoin]

I am having this same issue with a Litecoin clone I made.

[Ariaty]

I am having this same issue with a Litecoin clone I made.

Just figured it out. Add -listen=1 to the main PC you are running the first instance from.

So in my case I was using the command: $ ./barcoind -testnet -connection=x.x.x.x &

Now I use this command for the main instance: $ ./barcoind -testnet -listen=1 -connection=x.x.x.x &

[Clashicly]

This happened to some Bitcoin Core Sq daemons when ufw firewall was enabled on Ubuntu.
If enabled like below:

Code:

# ufw status
Status: active
To                         Action      From
--                         ------      ----

Then enable the daemon's listening port (replace 10333 with your coin's default listening port):

Code:

sudo ufw allow 10333

Code:

# ufw status
Status: active

To                         Action      From
--                         ------      ----
10333                      ALLOW       Anywhere
22                         ALLOW       Anywhere
10333 (v6)                 ALLOW       Anywhere (v6)
22 (v6)                    ALLOW       Anywhere (v6)