Error when opening the TCP socket

Support
, , ,
1

subspace farmer can’tstart

Started Subspace Farmer.
[2022-04-27T10:02:02Z INFO  subspace_farmer::commands::farm] Opening plot
[2022-04-27T10:02:03Z INFO  subspace_farmer::commands::farm] Opening commitments
[2022-04-27T10:02:07Z INFO  subspace_farmer::commands::farm] Opening object mapping
[2022-04-27T10:02:08Z INFO  subspace_farmer::commands::farm] Connecting to node at ws://127.0.0.1:9944
Error: Networking or low-level protocol error: Error when opening the TCP socket: Connection refused (os error 111)
Caused by:
    Error when opening the TCP socket: Connection refused (os error 111)
subspace-farmer.service: Main process exited, code=exited, status=1/FAILURE
subspace-farmer.service: Failed with result 'exit-code'.
subspace-farmer.service: Scheduled restart job, restart counter is at 7.
Stopped Subspace Farmer.
Started Subspace Farmer.
[2022-04-27T10:02:18Z INFO  subspace_farmer::commands::farm] Opening plot
[2022-04-27T10:02:21Z INFO  subspace_farmer::commands::farm] Opening commitments
[2022-04-27T10:02:25Z INFO  subspace_farmer::commands::farm] Opening object mapping
[2022-04-27T10:02:26Z INFO  subspace_farmer::commands::farm] Connecting to node at ws://127.0.0.1:9944
Error: Networking or low-level protocol error: Error when opening the TCP socket: Connection refused (os error 111)
Caused by:
    Error when opening the TCP socket: Connection refused (os error 111)
subspace-farmer.service: Main process exited, code=exited, status=1/FAILURE
subspace-farmer.service: Failed with result 'exit-code'.
subspace-farmer.service: Scheduled restart job, restart counter is at 8.
Stopped Subspace Farmer.

subspace-node log:

Started Subspace Node.
2022-04-27 13:00:35 Subspace
2022-04-27 13:00:35 ✌️  version 0.1.0-042302e-x86_64-linux-gnu
2022-04-27 13:00:35 ❤️  by Subspace Labs <https://subspace.network>, 2021-2022
2022-04-27 13:00:35 📋 Chain specification: Subspace testnet
2022-04-27 13:00:35 🏷  Node name: maestro-subspace01
2022-04-27 13:00:35 👤 Role: AUTHORITY
2022-04-27 13:00:35 💾 Database: RocksDb at /var/lib/subspace/.local/share/subspace-node/chains/subspace_test/db/full
2022-04-27 13:00:35 ⛓  Native runtime: subspace-100 (subspace-1.tx1.au1)
2 Likes
2

Your subspace-node log doesnot show detail information for your problem. You should check whether your node use 9944 port.

3

Thanks for the answer. No, I don’t have a process listening on port 9944. What could be the reason?

root@subspace01:~# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      625/systemd-resolve
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      698/sshd: /usr/sbin
tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN      1446/sshd: maestro@
tcp6       0      0 :::22                   :::*                    LISTEN      698/sshd: /usr/sbin
tcp6       0      0 ::1:6010                :::*                    LISTEN      1446/sshd: maestro@
udp        0      0 127.0.0.53:53           0.0.0.0:*                           625/systemd-resolve
udp        0      0 10.0.99.235:68          0.0.0.0:*                           623/systemd-network
4

Solved.

sudo systemctl stop subspace-node subspace-farmer
sleep 1s
cd $HOME

wget -O subspace-node https://github.com/subspace/subspace/releases/download/snapshot-2022-mar-09/subspace-node-ubuntu-x86_64-snapshot-2022-mar-09
wget -O subspace-farmer https://github.com/subspace/subspace/releases/download/snapshot-2022-mar-09/subspace-farmer-ubuntu-x86_64-snapshot-2022-mar-09
sudo mv subspace* /usr/local/bin/
sudo chmod +x /usr/local/bin/subspace*

sudo -u subspace subspace-farmer wipe
printf 'y' | sudo -u subspace subspace-node purge-chain --chain testnet
sleep 1s
sudo systemctl start subspace-node subspace-farmer
1 Like
5

Thanks for posting @Andre I’m glad you were able to find a solution for your problem, I also wanted to bring up the topic of systemd.

I see you are running the systemd script that some of the community members had created, this is hard for us to troubleshoot we suggest switching over to our docker route to help prevent networking issues like this from occurring :smile: