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

Starting GeyserPluginService crashes #426

Open
Pleidak opened this issue Sep 17, 2024 · 7 comments
Open

Starting GeyserPluginService crashes #426

Pleidak opened this issue Sep 17, 2024 · 7 comments

Comments

@Pleidak
Copy link

Pleidak commented Sep 17, 2024

INFO solana_geyser_plugin_manager::geyser_plugin_service] Starting GeyserPluginService from config files: ["/yellowstone-grpc/yellowstone-grpc-geyser/config.json"]
It seems to stop at this log and won't process anymore. I tried waiting for a long time and didn't see anything change
Any solution?
Thanks!

@AstroOrbis
Copy link

Likewise here - latest versions segfault after this

@Juanito87
Copy link
Contributor

Are you using the binary from the repo or a compiled version?
Consider that you need to match the rust version used for solana and the plugin.
And that you should run matching solana verisons between the plugin and solana.
In this case you would run solana 2.0.18 and geyser 3.0.1+solana.2.0.18 all compiled with rust 1.78.

@thetateman
Copy link

I'm also seeing segfaults with the latest geyser release. Solana and the plugin should have matching rust versions 1.78 since I'm using the Anza release for Solana 2.0.18 and the yellowstone release geyser 3.0.1+solana.2.0.18

@AstroOrbis
Copy link

It's a config issue everyone! Replace the line that goes something like "block_fail_action": "log" and you'll be all good!

@AstroOrbis
Copy link

(I'm embarassed to admit but I'll say it - it took me about 48 hours of bashing my head against the wall before thinking of using the config check script)

@AstroOrbis
Copy link

(Also, version mismatches could also be a culprit but for me and the 15 other people I've talked to with the same issue, this fixed it)

@thetateman
Copy link

It's a config issue everyone! Replace the line that goes something like "block_fail_action": "log" and you'll be all good!

TYSM! This was my issues as well :)

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

No branches or pull requests

4 participants