Fulcrum.service running but connection refused

[shishna]

fulcrum.service - Fulcrum
Loaded: loaded (/etc/systemd/system/fulcrum.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2023-07-19 13:17:54 BST; 5min ago
Main PID: 7464 (Fulcrum)
Tasks: 23 (limit: 9324)
Memory: 9.8M
CPU: 162ms
CGroup: /system.slice/fulcrum.service
└─7464 /home/lenovo/fulcrum/Fulcrum /home/lenovo/fulcrum/fulcrum.conf

Jul 19 13:22:44 ideapad-laptop Fulcrum[7464]: [2023-07-19 13:22:44.492] <BitcoinD.3> TCP BitcoinD.3 (id: 4): error 0 (Connection refused)
Jul 19 13:22:44 ideapad-laptop Fulcrum[7464]: [2023-07-19 13:22:44.496] <BitcoinD.2> TCP BitcoinD.2 (id: 3): error 0 (Connection refused)
Jul 19 13:22:44 ideapad-laptop Fulcrum[7464]: [2023-07-19 13:22:44.500] Waiting for bitcoind...
Jul 19 13:22:49 ideapad-laptop Fulcrum[7464]: [2023-07-19 13:22:49.491] <BitcoinD.3> TCP BitcoinD.3 (id: 4): error 0 (Connection refused)
Jul 19 13:22:49 ideapad-laptop Fulcrum[7464]: [2023-07-19 13:22:49.491] <BitcoinD.2> TCP BitcoinD.2 (id: 3): error 0 (Connection refused)
Jul 19 13:22:49 ideapad-laptop Fulcrum[7464]: [2023-07-19 13:22:49.495] <BitcoinD.1> TCP BitcoinD.1 (id: 2): error 0 (Connection refused)
Jul 19 13:22:54 ideapad-laptop Fulcrum[7464]: [2023-07-19 13:22:54.491] <BitcoinD.2> TCP BitcoinD.2 (id: 3): error 0 (Connection refused)
Jul 19 13:22:54 ideapad-laptop Fulcrum[7464]: [2023-07-19 13:22:54.494] <BitcoinD.3> TCP BitcoinD.3 (id: 4): error 0 (Connection refused)
Jul 19 13:22:54 ideapad-laptop Fulcrum[7464]: [2023-07-19 13:22:54.495] <BitcoinD.1> TCP BitcoinD.1 (id: 2): error 0 (Connection refused)
Jul 19 13:22:54 ideapad-laptop Fulcrum[7464]: [2023-07-19 13:22:54.499] Waiting for bitcoind...

[shishna]

In case it matters. I was following ministry of nodes guide.

[EchterAgo]

Is your bitcoind running properly?

[shishna]

Is your bitcoind running properly?

yes I SNAP installed bitcoin core on ubuntu, it is fully synced and running properly

[EchterAgo]

What bitcoind setting do you have in the configuration file and is that port actually open? The message says it is closed.

You can check using ss -tulpn for listeners.

[shishna]

I checked ss -tulpn and this is what I get
lenovo@ideapad-laptop:$ ss -tulpn
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:57704 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:631 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:*
udp UNCONN 0 0 [::]:43841 [::]:*
udp UNCONN 0 0 [fe80::6d02:c297:f021:8b71]%wlp8s0:546 [::]:*
udp UNCONN 0 0 :54349 : users:(("firefox",pid=4810,fd=64))
udp UNCONN 0 0 [::]:5353 [::]:
udp UNCONN 0 0 :34757 : users:(("firefox",pid=4810,fd=122))
tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:
tcp LISTEN 0 128 0.0.0.0:8333 0.0.0.0:* users:(("bitcoin-qt",pid=2347,fd=41))
tcp LISTEN 0 128 127.0.0.1:8334 0.0.0.0:* users:(("bitcoin-qt",pid=2347,fd=40))
tcp LISTEN 0 128 127.0.0.1:631 0.0.0.0:*
tcp LISTEN 0 128 [::1]:631 [::]:*
tcp LISTEN 0 128 [::]:8333 [::]:* users:(("bitcoin-qt",pid=2347,fd=39)) lenovo@ideapad-laptop:$ ss -tulpn
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:57704 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:631 0.0.0.0:*
udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:*
udp UNCONN 0 0 [::]:43841 [::]:*
udp UNCONN 0 0 [fe80::6d02:c297:f021:8b71]%wlp8s0:546 [::]:*
udp UNCONN 0 0 :54349 : users:(("firefox",pid=4810,fd=64))
udp UNCONN 0 0 [::]:5353 [::]:
udp UNCONN 0 0 :34757 : users:(("firefox",pid=4810,fd=122))
tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:
tcp LISTEN 0 128 0.0.0.0:8333 0.0.0.0:* users:(("bitcoin-qt",pid=2347,fd=41))
tcp LISTEN 0 128 127.0.0.1:8334 0.0.0.0:* users:(("bitcoin-qt",pid=2347,fd=40))
tcp LISTEN 0 128 127.0.0.1:631 0.0.0.0:*
tcp LISTEN 0 128 [::1]:631 [::]:*
tcp LISTEN 0 128 [::]:8333 [::]:* users:(("bitcoin-qt",pid=2347,fd=39))

[EchterAgo]

There is no port 8332 open. You seem to not have set up bitcoind RPC correctly. Also the listeners there are from bitcoin-qt, not bitcoind, are you sure that is what you want?

[shishna]

Not sure to be honest. I dont know what the difference is. What do you recommend ? Do I have to reinstall everything again ?

[EchterAgo]

bitcoin-qt is the graphical application and bitcoind is the daemon application without user interface. I think you could make this work with bitcoin-qt, but it is unlikely what you want. To me it looks like you didn't follow the guide properly, however I don't have the attention span to watch a video about this. Usually the setup is that you connect Fulcrum to bitcoind, and yours is not running.

[shishna]

So I just need to open port 8332 and that should fix it ?

[EchterAgo]

The default RPC port is port 8332, but what you end up using depends on your configuration. But yes, Fulcrum needs an RPC port to connect to and yours is not open. If you can't use the bitcoin-cli tool with either bitcoin-qt or bitcoind then your RPC is not set up right. In any case, this is not an issue with Fulcrum.

[shishna]

Yeah I tried using bitcoin-cli and command is not found. So can I go back and setup RPC correctly now or too late ?

[EchterAgo]

From the Fulcrum side everything should be fine once you get an RPC port up and running. You should consult the documentation / help forums of the node software you are using on how to get RPC working.

[shishna]

thanks for your help