PubsubError while deploying program on self-deployed solana-test-validator
exqlnet opened this issue · comments
Problem
env
solana-cli 1.18.15 (src:767d24e5; feat:4215500110, client:SolanaLabs)
Because of some network problems and rate-limit of airdrop while developing on devnet/testnet. I build a docker image to deploy solana-test-validator on my eks cluster, and use kong ingress gateway to proxy the request. While trying to deploy a program, it doesn't work and shows the following output(Note that it works fine locally):
command
solana program deploy -u https://self-deployed --program-id target/deploy/keypair.json target/deploy/test.so
output
thread 'main' panicked at cli/src/program.rs:2809:26:
Should return a valid tpu client: PubsubError(ConnectionError(Http(Response { status: 405, version: HTTP/1.1, headers: {"content-type": "text/plain; charset=utf-8", "content-length": "61", "connection": "keep-alive", "date": "Fri, 31 May 2024 06:23:40 GMT", "x-kong-upstream-latency": "1", "x-kong-proxy-latency": "1", "via": "kong/3.6.1", "x-kong-request-id": "1a36405345a4531a12411c093e7b4f67"}, body: Some([85, 115, 101, 100, 32, 72, 84, 84, 80, 32, 77, 101, 116, 104, 111, 100, 32, 105, 115, 32, 110, 111, 116, 32, 97, 108, 108, 111, 119, 101, 100, 46, 32, 80, 79, 83, 84, 32, 111, 114, 32, 79, 80, 84, 73, 79, 78, 83, 32, 105, 115, 32, 114, 101, 113, 117, 105, 114, 101, 100, 10]) })))
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
more details
thread 'main' panicked at cli/src/program.rs:2809:26:
Should return a valid tpu client: PubsubError(ConnectionError(Http(Response { status: 405, version: HTTP/1.1, headers: {"content-type": "text/plain; charset=utf-8", "content-length": "61", "connection": "keep-alive", "date": "Fri, 31 May 2024 06:36:18 GMT", "x-kong-upstream-latency": "1", "x-kong-proxy-latency": "0", "via": "kong/3.6.1", "x-kong-request-id": "a2708700ab667f04946352298385037f"}, body: Some([85, 115, 101, 100, 32, 72, 84, 84, 80, 32, 77, 101, 116, 104, 111, 100, 32, 105, 115, 32, 110, 111, 116, 32, 97, 108, 108, 111, 119, 101, 100, 46, 32, 80, 79, 83, 84, 32, 111, 114, 32, 79, 80, 84, 73, 79, 78, 83, 32, 105, 115, 32, 114, 101, 113, 117, 105, 114, 101, 100, 10]) })))
stack backtrace:
0: 0x102c72eac - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h298c9ab285ff3934
1: 0x102c92e7c - core::fmt::write::h4e276abdb6d0c2a1
2: 0x102c6f520 - std::io::Write::write_fmt::hd421848f5f0bf9d0
3: 0x102c72ce8 - std::sys_common::backtrace::print::hd8bd9ecab1f94b94
4: 0x102c741f4 - std::panicking::default_hook::{{closure}}::h520eeb743fc98fb4
5: 0x102c73f3c - std::panicking::default_hook::ha6550ffe49b63df1
6: 0x102c7461c - std::panicking::rust_panic_with_hook::hddb0e884a202de7c
7: 0x102c7451c - std::panicking::begin_panic_handler::{{closure}}::hd2798398a2fd9077
8: 0x102c73314 - std::sys_common::backtrace::__rust_end_short_backtrace::h9201cc364dbb8a23
9: 0x102c742b8 - _rust_begin_unwind
10: 0x102ce73c8 - core::panicking::panic_fmt::h4d5168028d4c43c7
11: 0x102ce7768 - core::result::unwrap_failed::hc60ef978ea39e1b4
12: 0x1021a5d00 - solana_cli::program::send_deploy_messages::hcf10e659d4eda071
13: 0x1021a0e24 - solana_cli::program::do_process_program_write_and_deploy::h664c755ee652a7b6
14: 0x10219c7ec - solana_cli::program::process_program_subcommand::h232713cd7d33d880
15: 0x1021d678c - solana_cli::cli::process_command::h0e1f14b0ef8a0bdd
16: 0x1020fe638 - solana::main::hf335eedd94d9a56d
17: 0x102109114 - std::sys_common::backtrace::__rust_begin_short_backtrace::h65b1273811951d71
18: 0x10210852c - std::rt::lang_start::{{closure}}::hcf83cc605dd14111
19: 0x102c68e70 - std::rt::lang_start_internal::h5b246d44f1526226
20: 0x102108510 - std::rt::lang_start::hc97bfe6bc1fa7552
21: 0x1020ffa9c - _main
it seems trying to connect provider of JSON-RPC endpoint using websocket protocol?
Proposed Solution
This repository is no longer in use. Please re-open this issue in the agave repo: https://github.com/anza-xyz/agave