I created my producer node, started it and was able to sync up to the current epoch. Once it was synced, I updated my topology.json to point to the relay node that I already have set up. Upon restarting my producer node and running ./gLiveView.sh, it’s stuck on showing the Status: starting… for over 40 minutes. Any suggestions on what I did wrong?
Check the topology file… also check from producer
telnet Relay_IP Relay_port
U should see connected; if not check if the port in relay is opened
Cheers,
I will check that later today and give an update. Thank you for the response!
telnet does not result in a connected message, it just continually attempts to connect. Using sudo lsof -nP -i | grep LISTEN
on my relay returns with one of the results being TCP *:6001 (LISTEN)
. Does this mean that port is open and listening? If so I might have a topology issue that I must have missed. I believe that I checked all of my config locations.
Check ur relay port (if it’s open) here
should be open; if it’s saying closed … check the FW ( perhaps u have another FW in cloud)
You’re correct, looks like my cloud provider firewall was blocking access. I updated the rules and the node synced. I appreciate the help!
Now, the core node doesn’t say core, it still says relay-mainnet. Do I need to register the pool/generate keys before it can appear as core?
HI @Gemini_Gilbertson Yes in order for your node to appear as core node you need your pool key.
Hope it helps.
Go to cd $CNODE_HOME/priv/pool
ls -l
Copy the name of the pool folder
Paste in env to POOL NAME “name” (case sensitive)
Restart the node
Cheers,
I updated the Pool name to equal the name of the folder in /priv/pool, I’ve restarted the node a few times, including running ./deploy-as-systemd.sh once just to make sure it didn’t need to update anything. gLiveView still shows the node as Relay-Mainnet. Are there any other places I need to make sure are configured? Do I need to register the pool before it will show up as a core node?
Ok,
Type nano env and show me the output… did u uncommented the pool name line from env by deleting the # from the begining right?
Cheers,
Bottom left window is lists contents of /priv/pool, bottom right window is env
go to cd Raven_Pool
ls -l
Then u can delete the above image… it shows ur usernme of the node
Do I need to register the pool before it will show up as a core node?
Yes, because u need the opt.cert and the rest of the files
contents:
I will register the pool and then restart the node to see if it switches to a core node.
U don’t have the op.cert file
U will have it after u will register the pool;
Cheers,
Everything looks good! My pool appears on pooltool as well.
Congrats!
Cheers,