I’m following the coin cashew guide, I’ve got 2 servers on AWS. My relay node seems to be functioning, gliveview shows the information accurately. My block producing node however is only showing 0 for most of the results. I’ve updated the firewall to only accept connection from my relay.
results of my block producing node
it’s saying starting… so try this
journalctl -e -f -u cardano-node and check for errors… the most of the issues are related with wrong topology format
1 Like
Failed to start all required subscriptions
my relay appears to be working fine.
Both servers are on AWS
why this message? Do u see any error inside the logs?
What step are you in the CoinCashew guide? When setting up my pool using that guide, the block producer node did not show up as “Core” until much later on. Also while you need to have connection 1 in and 1 out at the end of the process, you don’t need it while building the pool. You will need to have the blockchain synced, however.
What I would suggest is to delete what’s in your topology.json file on your BP and replace it with this for now:
{
"Producers": [
{
"addr": "relays-new.cardano-mainnet.iohk.io",
"port": 3001,
"valency": 2
}
]
}
This will allow the BP to sync to the blockchain, but it will not appear as “Core” yet. Continue with the steps and update me if you hit any more barriers. The BP should show up as core towards the end of the guide, I can’t remember which particular step.
PS. I had to make sure that port 6000 was open on my router for in & outs (on my relay). I also needed to find my relay node’s private IP address and ensure my topology had that IP in there (instead of my public IP). I use the public IP on my relay.
These were both steps that I corrected towards the end of the process. You can make sure 6000 is open at: Open Port Check Tool - Test Port Forwarding on Your Router – keep in mind that this will not show as open unless your BP is pulling information from the relay also.