cli: solana validator-info get does not display information for all validators about agave HOT 11 OPEN

after looking at all validators info i see that account might have been updated!

from agave.

after looking at all validators info i see that account might have been updated!

@Nagaprasadvr You were looking at the wrong cluster. An example is written in the description.

which cluster ? testnet?

from agave.

after looking at all validators info i see that account might have been updated!

@Nagaprasadvr You were looking at the wrong cluster. An example is written in the description.

from agave.

after looking at all validators info i see that account might have been updated!

@Nagaprasadvr You were looking at the wrong cluster. An example is written in the description.

which cluster ? testnet?

Yes. You can see what the options mean in the documentation. This is option -u (--url)

from agave.

This is not a bug; this is expected behavior. solana validator-info get PUBKEY will not return results for validator's who have not explicitly published:

$ solana validator-info --help        
solana-validator-info 
Publish/get Validator info on Solana
...

SUBCOMMANDS:
    get        Get and parse Solana Validator info
    help       Prints this message or the help of the given subcommand(s)
    publish    Publish Validator info on Solana

https://docs.solanalabs.com/operations/guides/validator-info

from agave.

@steviez At first, I thought the same, but then I reread the initial message, and it seems that the information had been published before (otherwise, where would it have come from on va).

I checked the information with my test validator. There's no information there either. But it is present on va as well. And I definitely didn't delete it.
I made an HTTP request to rpc to get all the Config111... accounts, and the information isn't there either.

So either the information was removed from the snapshot during restarts, or there's a problem with retrieving all the program's accounts.

from agave.

Hmm, ok. Apologies for the potential early close; there may be something here. If I'm being honest, I have other higher priority items so I probably wouldn't be able to look at this for a bit.

If anyone reading this is interested in helping out, looking at the underlying RPC calls for solana validators vs. solana validator-info get would probably be a good start. You should be able to trace it down from the CLI commands in this directory:
https://github.com/anza-xyz/agave/tree/master/cli

from agave.

(otherwise, where would it have come from on va)

I think this is an important question to answer to determine if this is a wild goose chase. Is validator-info the only place validators.app gets validator details?

from agave.

(otherwise, where would it have come from on va)

I think this is an important question to answer to determine if this is a wild goose chase. Is validator-info the only place validators.app gets validator details?

I think it doesn't really matter where the VA stores the information.

It is important that both Diman and I published information about the validator earlier, and now it is not visible.

from agave.

I am taking this issue. Will try to identify the problem

from agave.

The RPC call is functioning properly.
It appears that the info account was removed from the Config program.
I tested publishing and retrieving a new info account, and it worked without issue.
Additionally, using the RPC call from solana validators won't provide the necessary information, as it utilizes getVoteAccounts(), whereas the former relies on getProgramAccounts(Config1111111111111).

from agave.