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?
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
DIRECTORY=$NODE_HOME
PORT=6000
HOSTADDR=0.0.0.0
TOPOLOGY=${DIRECTORY}/topology.json
DB_PATH=${DIRECTORY}/db
SOCKET_PATH=${DIRECTORY}/db/socket
CONFIG=${DIRECTORY}/config.json
KES=${DIRECTORY}/kes.skey
VRF=${DIRECTORY}/vrf.skey
CERT=${DIRECTORY}/node.cert
/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}
EOF
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.
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.
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.