Unable to Change Relay to Core

I stopped the node. I updated startup scripts and have the key pair and operational cert. Then started the node.

After I did that I went to gliveview and it doesn’t change from relay to core. And my below categories are missing, core and block production. Everything else looks fine. My connections stay up and it’s all synched.

I also get no slot schedule. It runs, but then doesn’t show any entries. What am I missing here?

What did you update the start up script with? Was the BP running before? Or are you getting your pool set up for the first time?

We have been live since epoch 401, but wasn’t getting any blocks. Wasn’t sure if it was bad luck at first. I used the coincashew guide to set up the stake pool, and we have over 800k ada staked.

This is the startup script I used:
cat > $NODE_HOME/startBlockProducingNode.sh << EOF
/usr/local/bin/cardano-node run +RTS -N -A16m -qg -qb -RTS --topology ${TOPOLOGY} --database-path ${DB_PATH} --socket-path ${SOCKET_PATH} --host-addr ${HOSTADDR} --port ${PORT} --config ${CONFIG} --shelley-kes-key ${KES} --shelley-vrf-key ${VRF} --shelley-operational-certificate ${CERT}

Is your node fully synced? Maybe add a screenshot of your gliveview for context if you like.


Did you check your env file?

1 Like

Can you have a look at the log from when the node started? Are you using the service from the coincashew guide? Maybe you have referenced the relay script instead of the BP script for start up.

try to use the explicit path for these files. also check if you changed the permision for vrf.skey file


Have you updated your systemd service file cardano-node with your startup script : startBlockProducingNode.sh ?

Checking through the env file I noticed that my operation certificate is called op.cert and the my certificate is node.cert. I changed the name in env to match, but that didn’t work.

Okay, now I have the explicit paths for each. I have the vrf.skey file set to read only. Is that correct?

should be. now restart the node

Restarted, but no luck.

did u start the server manually or via systemd ?

I think you and @kirael are on to something. The service was referencing a different startup script.
I changed it in the service, and looking at the logs, it says permission denied.

I ran this again: sudo chmod 644 /etc/systemd/system/cardano-node.service

ok, check the owner… is root or ur user? try with chmod 750 also

It was permissions for the startup script I was missing that time. Now… It’s fixed!

1 Like

THANK YOU EVERYONE FOR THE HELP!!! We are now operational!


Good news : )

I wrote an audit script that can help you check if everything is ok on your coincashew setup :


Thanks! This will be nice to have. I’m going to give a run.