Skip to content

ws Gateway URL connection causes application to panic #18

@timpel-fcs

Description

@timpel-fcs

It looks like there is a misconfiguration between protocols on the client side and the websocket gateway, causing the worker to panic and restart. This occurs when running the latest worker (v1.1.8) with the provided mainnet ws gateway_url

ERROR lgn_worker: lgn-worker/src/main.rs:135: Panic occurred:    0: lgn_worker::main::{{closure}}::{{closure}}
   1:std::panicking::rust_panic_with_hook
   2:std::panicking::begin_panic_handler::{{closure}}
   3:std::sys::backtrace::__rust_end_short_backtrace
   4: rust_begin_unwind
   5: core::panicking::panic_fmt
   6: lgn_worker::main::{{closure}}
   7: lgn_worker::main
   8: std::sys::backtrace::__rust_begin_short_backtrace
   9: std::rt::lang_start_internal
  10: main
  11: <unknown>
  12: __libc_start_main
  13: _start
, msg: "Worker exited due to an error: connecting `worker_to_gw`\n\nCaused by:\n    0: status: Unknown, message: \"h2 protocol error: http2 error\", details: [], metadata: MetadataMap { headers: {} }\n    1: transport error\n    2: http2 error\n    3: connection error detected: frame with invalid size\n\nStack backtrace:\n   0: lgn_worker::run_worker::{{closure}}\n   1: lgn_worker::run::{{closure}}\n   2: lgn_worker::main::{{closure}}\n   3: lgn_worker::main\n   4: std::sys::backtrace::__rust_begin_short_backtrace\n   5: std::rt::lang_start_internal\n   6: main\n   7: <unknown>\n   8: __libc_start_main\n   9: _start", file: "lgn-worker/src/main.rs", lineno: 149, col: 9

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions