Error: rpccompat: dial tcp 127.0.0.1:7778: connect: connection refused

Hi.
I found this error code this morning: Error: rpccompat: dial tcp 127.0.0.1:7778: connect: connection refused
The node is online. Do I need to do anything?
Thanks

If your node has Online status and you are getting uploads/downloads without failing audits then your node is fine. The error could be temporary loss of connectivity at that timestamp.

Also this should be a different topic.

Usually such error is happening only on start, when the node is busy to calculate the usage

make change in config.yaml for second node:
before: server.private-address: 127.0.0.1:7778
after: server.private-address: 127.0.0.1:7779

and got the message:
rpccompat: dial tcp 127.0.0.1:7778: connect: connection refused

as far I’ve understand that I should change the inner port for every additional node, but the node still knocking in 7778 port.
what’s can be wrong?

Did you follow this guide ?

Yep, but it is no clean for me.
Current setup:

router: open port=28968; destination port=28968.
then
docker run -d --restart unless-stopped -p 28967:28967 -e WALLET=“the same wallet as 1st node” -e EMAIL=“unic with 2nd invitation” -e ADDRESS=“same ip as 1st node:28967” -e BANDWIDTH=“xxTB” -e STORAGE=“xxTB” --mount type=bind,source="__\Storj\Identity\storagenode2\",destination=/app/identity --mount type=bind,source=“2nd disk:\data\”,destination=/app/config --name storagenode2 storjlabs/storagenode:alpha

config.yaml (changes):

server address of the api gateway and frontend app

console.address: 127.0.0.1:14003

the public address of the node, useful for nodes behind NAT

contact.external-address: “same ip as 1st:28968”

private address to listen on

server.private-address: 127.0.0.1:7779

in Docker dashboard:
storagenode2
running
port: 28968

in the end:
Error: rpccompat: dial tcp 127.0.0.1:7778: connect: connection refused

Needs to be 28968:28967

Needs to be same ip as 1st node:28968

Instead you can use your docker command as shown in documentation with this minor change.

-p 127.0.0.1:14003:14002

Make sure you read the documentation as this command has updated to

storjlabs/storagenode:latest

now:
docker run -d --restart unless-stopped -p 28968:28967 -p 127.0.0.1:14003:14002 -e WALLET=“the same wallet as 1st node” -e EMAIL=“unic with 2nd invitation” -e ADDRESS=“same ip as 1st node:28968” -e BANDWIDTH=“xxTB” -e STORAGE=“xxTB” --mount type=bind,source="_\Storj\Identity\storagenode2\",destination=/app/identity --mount type=bind,source=“2nd disk:\data\”,destination=/app/config --name storagenode2 storjlabs/storagenode:latest

#storagenode:latest - Unable to find image ‘storjlabs/storagenode:latest’ locally
latest: Pulling from storjlabs/storagenode.
think that ‘:latest’ is excess

#output in sum of all changes:
Error: rpccompat: dial tcp 127.0.0.1:7778: connect: connection refused

I can see you didn’t click the documentation link yet so you should do that.

Remove the trailing \ from paths to make them source="_\Storj\Identity\storagenode2 & 2nd disk:\data

You can rename 2nd node’s config.yaml to config.yaml.bak and restart the node.

All goes up - thank you so much! I’ve never imagine how brainsurged I was in that case.

And another one question if I could:
do I need to roll up second watchtower for second node?

if you’ve talking about this one:

I have read it already before, got a decision to make separate nodes with separate new disks without hard or soft RAID. Just got stucked in 2nd layer port forwarding and the parameters of command promt. If you about that :slight_smile:

1 Like

No. You can add storagenode2 to the same watchtower command.

^ is the right approach and without RAID of course as recommended by many.

There is no goal to get extra tokens in short period with high risks to set up the users with data lost. I just entusiast with lack of many skills and if something can get wrong it goes wrong and I don’t need that pain. Cause life is fast and there is so much actions and desicions during the day so often no time to stop and get back and work the problem carefully.
So THANK you again for saving my time and nerves:)

2 Likes

like that:
docker run -d --restart=always --name watchtower -v /var/run/docker.sock:/var/run/docker.sock storjlabs/watchtower storagenode storagenode2 watchtower --stop-timeout 300s

1 Like

Yes. This is your second node but if you want you can post pictures of your setup here

The setup look too much scary for now cause I’m running home pc hardware not packed any case that attached to Supermicro 847E16-RJBOD1. I’ve bought that shelf for burstcoin mining purpose but the project won’t fly since march of 2018.
In 18th I’ve found and described myself as chinese plant worksman who’s screwing down one bolt day after day about 10 years in logistics. So I desperately tried to find some proccess that makes any sence and found the way in crypto.
And planning to get some server architect on amd epyc but price for that I can’t afford and there is no to much needs in that purchase right now.

1 Like

10 posts were merged into an existing topic: Error starting master database on storagenode: database: file is not a database

Well in my command there is the stop-timeout part:
sudo docker run -d --restart unless-stopped --stop-timeout 300

Yeah maybe it was killed then restarted and had a corrupted db then.
Thanks for the help. Next time I will check the DBs first and the report ;D

Hello everyone, I really appreciate everyone’s input. I’ve read and followed all the steps in this thread and i’ve read and followed all the steps in each linked article as well. I am unable to get the second node up and running on the same machine as the first node. Does anyone have any idea on how to resolve this?

I run the following command to see the CLI dashboard and get this readout:
Command:
docker exec -it storagenode2 /app/dashboard.sh

Readout:

2023-02-13T18:25:38.700Z INFO Configuration loaded {“Process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2023-02-13T18:25:38.701Z INFO Anonymized tracing enabled {“Process”: “storagenode”}
2023-02-13T18:25:38.704Z INFO Identity loaded. {“Process”: “storagenode”, “Node ID”: “12Jbp1aP3r57KnP5tLCkaEGUBvQxXb6basU9sXpfd28sGcjLqPQ”}
Error: rpc: dial tcp 127.0.0.1:7778: connect: connection refused

We need some more info about your configurations. Can you provide the Run commands of both nodes, but redact your personal info such as public IP (But leave the ports) and payout address, email, etc?

In addition, if port 7778 isn’t working you could try a different port. It’s possible the port you have chosen is occupied by another application.

Node1 Run:
docker run -d --restart unless-stopped --stop-timeout 300 \ -p 28967:28967/tcp \ -p 28967:28967/udp \ -p 14002:14002 \ -e WALLET=“0xf945cA2Db1C8A5387e85C490cf08301249283EAE” \ -e EMAIL=“<my_email>” \ -e ADDRESS=“:28967” \ -e BANDWIDTH=“500TB” \ -e STORAGE=“8500GB” \ --user $(id -u):$(id -g) \ --mount type=bind,source=“/root/.local/share/storj/identity/storagenode”,destination=/app/identity \ --mount type=bind,source=“/media/storj/”,destination=/app/config \ --name storagenode storjlabs/storagenode:latest

Node2 Run:
docker run -d --restart unless-stopped --stop-timeout 300 \ -p 28968:28967/tcp \ -p 28968:28967/udp \ -p 127.0.0.1:14003:14002 \ -e WALLET=“0xf945cA2Db1C8A5387e85C490cf08301249283EAE” \ -e EMAIL=“<same-as-node1” \ -e ADDRESS=“:28968” \ -e BANDWIDTH=“500TB” \ -e STORAGE=“8600GB” \ --user $(id -u):$(id -g) \ --mount type=bind,source=“/mnt/storagenode2/storagenode_id2/identity/storagenode2”,destination=/app/identity \ --mount type=bind,source=“/mnt/storagenode2/node2_data”,destination=/app/config \ --name storagenode2 storjlabs/storagenode:latest

In regards to the 7778 not working. Where and how do I adjust this?
config.yaml settings:

public address to listen on server.address: :28968

private address to listen on server.private-address: 127.0.0.1:7779

I am getting the error read out with the configurations above. let me know if there is anything else I can send you that might help.
Thanks