Scitz0
commented
3 years ago The error message could be better here, it expects a pool.cert file to be available indicating that the pool is registered. There is no good way to verify if the pool is registered or not so this is the current way for this detection. Created when first registering the pool.
You can easily fool CNTools by adding a dummy file with:
touch /opt/cardano/cnode/priv/pool/FLICK/pool.cert
The idea is to later use Koios for this purpose. See Catalyst fund6 proposal.
The current solution to query ledger through cli is not a viable solution due to node/memory load it adds.
Closing issue.
rknightion
Describe the bug When going in to modify or retire our pool, we get this message:
However, the pool files are there in /opt/cardano/cnode/priv/pool/FLICK
We've not changed any of the default path locations in the env file (only the POOL_NAME variable), and have run the unprotect script. As you'll see in the screenshot I've also tried lazing the file permissions (since undone) but to no avail.
One thing that I wonder if it's impacting this, is when doing pool > list the pool is showing as not registered, however it is registered on chain (shown when doing pool > show).
I'm wondering what kind of diagnostics or troubleshooting I can try here in order to be able to make modifications to the pool, or if there's something glaringly obvious that I've missed. The pool was originally created and registered using cntools (hybrid mode), although cntools does seem to give me the option to register the pool again. It does seem as if while the pool is registered, something in my setup makes cntools think it's not despite the keys being there and valid. It does give me the option to rotate KES keys successfully however.
Version: