Glive not showing any KES information

Hi All,

Slightly confused why on my block producer glive is not showing any information about KES period.
when i run:

curl localhost:12798/metrics | grep KES

i get back:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1098    0  1098    0     0  36600      0 --:--:-- --:--:-- --:--:--  153k

and nothing else.

I have copied over the kes, vrf and node.cert and restarted the node

any advise would help, thanks

Can u share the glive output?

glive

Basically looks the same as a relay

Ok, and the startup script for Producer?

#!/bin/bash
DIRECTORY=/home/user/cardano-my-node
PORT=6001
HOSTADDR=0.0.0.0
TOPOLOGY=${DIRECTORY}/mainnet-topology.json
DB_PATH=${DIRECTORY}/db
SOCKET_PATH=${DIRECTORY}/db/socket
CONFIG=${DIRECTORY}/mainnet-config.json
KES=\${DIRECTORY}/kes.skey
VRF=\${DIRECTORY}/vrf.skey
CERT=\${DIRECTORY}/node.cert
/home/user/.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}

node.cert, kes.skey and vrf.skey definitely exist in ${DIRECTORY}

Hmm and if u type
journalctl -e -f -u cardano-node
or
sudo systemctl status cardano-node

What is the output?

seems to be working fine.

actually gives back:

Unit cnode.service could not be found.

not sure whats up with that

Did u started the node manually?

try with cardano-node (I corrected )

sudo systemctl status cardano-node

No errors with vrf file ? I know the permision of the file must be changed

BTW what is the ticker?

Active: active (running) since Sun 2021-11-14 00:28:13 UTC; 40min ago

Oh, let me check permissions.

ticker is: INFTY
(just registered an hour ago)

permissions on vrf.skey are read only, seems fine to me?

Yes, it’s fine… then should be something with the path

hmm, wait… the last line from script it’s not for producer… is for relay

should be


/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}

Modify the script and restart the node

ahh i see. However now im getting the error:

Failed to parse IPv4 address: ${HOSTADDR}. If you want to specify an IPv6 address, use --host-ipv6-addr option.

should HOSTADDR=0.0.0.0 actually have some IP in it other than 0.0.0.0 ?

Use 0.0.0.0

ok, let me see if i can figure out why its throwing that error all of a sudden

Because in your origina script u had


--host-addr ${HOSTADDR}

and in the new line u have


--host-addr \${HOSTADDR}

delete the \ for all but not for KES, vrf and cert (because when u defined the path above u used \ )

the node wont start with:

--shelley-kes-key \${KES} --shelley-vrf-key \${VRF} --shelley-operational-certificate \${CERT}

or

KES=\${DIRECTORY}/kes.skey
VRF=\${DIRECTORY}/vrf.skey
CERT=\${DIRECTORY}/node.cert
/home/user/.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}

It will only start with:

DIRECTORY=/home/user/cardano-my-node
PORT=6001
HOSTADDR=0.0.0.0
TOPOLOGY=${DIRECTORY}/mainnet-topology.json
DB_PATH=${DIRECTORY}/db
SOCKET_PATH=${DIRECTORY}/db/socket
CONFIG=${DIRECTORY}/mainnet-config.json
KES=${DIRECTORY}/kes.skey
VRF=${DIRECTORY}/vrf.skey
CERT=${DIRECTORY}/node.cert
/home/user/.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}

and still waiting for the node to move from “starting” status

Ok all is working now. thanks for your help @Alexd1985 :vulcan_salute: