rdlrt
commented
2 years ago it already appears in the adapool dashboard but when I run the gLiveview in it it shows me as if it were running in the relay.
What you see on chain is your pool registration information, what you see on gLiveView is your node status .
I have a somewhat custom configuration of folders, I use CVM to create the pool, this has worked well for me so far or the only strange thing that happens is that the cnode folder is deleted from the tree, that is, my cardano path is /opt/cardano
This might be unrelated to your issue statement. When using custom folders, you'd need to uncomment and set variables to point the script to individual folders. The common folder tree assumption from tools is documented here - when customising, you'd need to read the script and replace all variables available (ensure you disable auto update in that case by editing env file).
The reason to have a subfolder underneath cardano is to allow different instance folders (eg: across different networks), you can customise the top level folder using CNODE_HOME post deployment, but I would wonder about that choice
Describe the bug I just set up the pool from scratch, it already appears in the adapool dashboard but when I run the gLiveview in it it shows me as if it were running in the relay.
I have a somewhat custom configuration of folders, I use CVM to create the pool, this has worked well for me so far or the only strange thing that happens is that the cnode folder is deleted from the tree, that is, my cardano path is /opt/cardano . And on the other hand, when I use cntools to manage the pool, it creates a cardano folder inside the existing one with its priv folder and the keys inside. I leave a screenshot of my current folder tree.
The folder marked "cardano" is the one created by cntool.