1

I am running an RPC node and using the quic client to send transactions on the same machine. The node will run for a few hours, with many successful transactions sent via quic and then crash with the following error.

thread 'sol-warm-quic-service' panicked at 'QuicLazyInitializedEndpoint::create_endpoint bind_in_range: Custom { kind: Other, error: "No available UDP ports in (8000, 10000)" }', client/>

In the comments in this post the solution provided is to modify the VALIDATOR_PORT_RANGE to (8000, 60000) in the quic no blocking file. I have done this and am still encountering the same issue. How can I better specify who is using which ports?

Improve this question
4
  • Very strange... Maybe you can see how all of those ports are being used with something like ss -tulpn?
    – Jon C
    Commented Jan 30, 2023 at 15:19
  • Hi Jon. I ran ss - tulpn, I am getting validator process, and transaction sender process in port range between 8000, 10000. I am also seeing validator process and transaction sender process in ports > 10000. I assume this is unexpected as only the transaction sender process should be > 10000? Further context - I didn't modify any validator code, only the solana_client crate which is imported into the transaction sender bot.
    – guccimane
    Commented Jan 31, 2023 at 23:26
  • This may be a silly suggestion, but how about keeping the validator to (8000, 10000), and changing your client to (10001, 60000)?
    – Jon C
    Commented Feb 1, 2023 at 12:05
  • Ok I think this might be working. Thanks for your help
    – guccimane
    Commented Feb 4, 2023 at 12:55

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Browse other questions tagged or ask your own question.