Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cli: solana validator-info get does not display information for all validators #278

Open
dubalda opened this issue Mar 16, 2024 · 11 comments

Comments

@dubalda
Copy link

dubalda commented Mar 16, 2024

I checked on several validators and this command did not output anything.

For example:

solana validators -ut | grep 7arMwy1BnRTC995TVdgZYU8n9V2gwxTpWmVNDdeJihdA
  7arMwy1BnRTC995TVdgZYU8n9V2gwxTpWmVNDdeJihdA  66597J13dfdXhKu76VCEiKt6aDE4YP1Seccj2JGkXHYo   10%  258716111 (  0)  258716074 ( -2)   0.00%   269417   1.18.6     39025.815318832 SOL (0.02%)

solana validator-info get -ut | grep 7arMwy1BnRTC995TVdgZYU8n9V2gwxTpWmVNDdeJihdA

On the site I see information on these validators. For example:
https://www.validators.app/validators/7arMwy1BnRTC995TVdgZYU8n9V2gwxTpWmVNDdeJihdA?locale=en&network=testnet

Name: 	Moovi
Details: 	Moovi | Solana Validator
Identity: 	7arMwy1BnRTC995TVdgZYU8n9V2gwxTpWmVNDdeJihdA
Software: 	1.18.6
Keybase: 	moovi
Website: 	https://moovi.work
Vote Account: 	66597J13dfdXhKu76VCEiKt6aDE4YP1Seccj2JGkXHYo 

I can assume that information is not displayed for those validators who published information a long time ago.

Checked on versions:
solana-cli 1.17.26 (src:4c418143; feat:3580551090, client:SolanaLabs)
solana-cli 1.18.5 (src:928d8ac2; feat:3352961542, client:SolanaLabs)

@dubalda dubalda changed the title solana validator-info get does not display information for all validators cli: solana validator-info get does not display information for all validators Mar 16, 2024
@Nagaprasadvr
Copy link

image

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

@dubalda
Copy link
Author

dubalda commented Mar 17, 2024

image

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.

@Nagaprasadvr
Copy link

image
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?

@dubalda
Copy link
Author

dubalda commented Mar 17, 2024

image
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)

@steviez
Copy link

steviez commented Mar 17, 2024

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

@steviez steviez closed this as not planned Won't fix, can't repro, duplicate, stale Mar 17, 2024
@diman-io
Copy link

@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.

@steviez
Copy link

steviez commented Mar 20, 2024

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

@steviez steviez reopened this Mar 20, 2024
@CriesofCarrots
Copy link

(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?

@dubalda
Copy link
Author

dubalda commented Mar 21, 2024

(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.

@kubanemil
Copy link

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

@kubanemil
Copy link

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants