blockscout/blockscout-rs

user ops service: configuration

Closed this issue · 2 comments

InoMurko commented

Describe the bug

Release https://github.com/blockscout/blockscout-rs/releases/tag/user-ops-indexer%2Fv1.2.2

"RUST_BACKTRACE": "full",
        "USER_OPS_INDEXER__API__MAX_PAGE_SIZE": "100",
        "USER_OPS_INDEXER__DATABASE__CONNECT__URL": "<URL>",
        "USER_OPS_INDEXER__DATABASE__CREATE_DATABASE": "true",
        "USER_OPS_INDEXER__DATABASE__RUN_MIGRATIONS": "true",
        "USER_OPS_INDEXER__INDEXER__CONCURRENCY": "20",
        "USER_OPS_INDEXER__INDEXER__ENTRYPOINTS__V06": "true",
        "USER_OPS_INDEXER__INDEXER__ENTRYPOINTS__V06_ENTRY_POINT": "0x5ff137d4b0fdcd49dca30c7cf57e578a026d2789",
        "USER_OPS_INDEXER__INDEXER__ENTRYPOINTS__V07": "false",
        "USER_OPS_INDEXER__INDEXER__PAST_DB_LOGS_INDEXER__ENABLED": "true",
        "USER_OPS_INDEXER__INDEXER__PAST_DB_LOGS_INDEXER__END_BLOCK": "0",
        "USER_OPS_INDEXER__INDEXER__PAST_DB_LOGS_INDEXER__START_BLOCK": "-100000",
        "USER_OPS_INDEXER__INDEXER__PAST_RPC_LOGS_INDEXER__BLOCK_RANGE": "500",
        "USER_OPS_INDEXER__INDEXER__PAST_RPC_LOGS_INDEXER__ENABLED": "true",
        "USER_OPS_INDEXER__INDEXER__REALTIME__ENABLED": "true",
        "USER_OPS_INDEXER__INDEXER__RPC_URL": "http://rollup-proxy-service:8545",
        "USER_OPS_INDEXER__JAEGER__ENABLED": "false",
        "USER_OPS_INDEXER__METRICS__ADDR": "0.0.0.0:6060",
        "USER_OPS_INDEXER__METRICS__ENABLED": "true",
        "USER_OPS_INDEXER__METRICS__ROUTE": "/metrics",
        "USER_OPS_INDEXER__SERVER__GRPC__ADDR": "0.0.0.0:8051",
        "USER_OPS_INDEXER__SERVER__GRPC__ENABLED": "false",
        "USER_OPS_INDEXER__SERVER__HTTP__ADDR": "0.0.0.0:8050",
        "USER_OPS_INDEXER__SERVER__HTTP__ENABLED": "true",
        "USER_OPS_INDEXER__SERVER__HTTP__MAX_BODY_SIZE": "2097152",
        "USER_OPS_INDEXER__TRACING__ENABLED": "true",
        "USER_OPS_INDEXER__TRACING__FORMAT": "default"

Observed behavior

thread 'main' panicked at user-ops-indexer-server/src/main.rs:9:38:
failed to read config: unknown field `v06_entry_point`, expected `v06` or `v07`
stack backtrace:
   0:     0x55d5e6816c95 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h1e1a1972118942ad
   1:     0x55d5e684103b - core::fmt::write::hc090a2ffd6b28c4a
   2:     0x55d5e6813bcf - std::io::Write::write_fmt::h8898bac6ff039a23
   3:     0x55d5e6816a6e - std::sys_common::backtrace::print::ha96650907276675e
   4:     0x55d5e6817ed9 - std::panicking::default_hook::{{closure}}::h215c2a0a8346e0e0
   5:     0x55d5e6817c1d - std::panicking::default_hook::h207342be97478370
   6:     0x55d5e6818373 - std::panicking::rust_panic_with_hook::hac8bdceee1e4fe2c
   7:     0x55d5e6818254 - std::panicking::begin_panic_handler::{{closure}}::h00d785e82757ce3c
   8:     0x55d5e6817159 - std::sys_common::backtrace::__rust_end_short_backtrace::h1628d957bcd06996
   9:     0x55d5e6817f87 - rust_begin_unwind
  10:     0x55d5e5ad37d3 - core::panicking::panic_fmt::hdc63834ffaaefae5
  11:     0x55d5e5ad3c86 - core::result::unwrap_failed::h82b551e0ff2b2176
  12:     0x55d5e5c5b005 - user_ops_indexer_server::main::{{closure}}::h7991675417472327
  13:     0x55d5e5c4c579 - tokio::runtime::park::CachedParkThread::block_on::h50fef40b3f00c1b7
  14:     0x55d5e5c16b6f - tokio::runtime::context::runtime::enter_runtime::hf94ec412599b6e7b
  15:     0x55d5e5c549cd - user_ops_indexer_server::main::h0fd2ea2d964b9952
  16:     0x55d5e5d5bc03 - std::sys_common::backtrace::__rust_begin_short_backtrace::h72e1525d37e3f350
  17:     0x55d5e5c9190d - std::rt::lang_start::{{closure}}::hd3238e0ed8599b0f
  18:     0x55d5e680cc90 - std::rt::lang_start_internal::h3ed4fe7b2f419135
  19:     0x55d5e5c5c5d5 - main
  20:     0x7fc17991f083 - __libc_start_main
  21:     0x55d5e5ad3f2a - _start
  22:                0x0 - <unknown>

As per my reading of documentation, there shouldn't be anything wrong with my ENV settings.

k1rill-fedoseev commented

Please try running v1.2.2 without the USER_OPS_INDEXER__INDEXER__ENTRYPOINTS__V06_ENTRY_POINT variable, since you are using the default entrypoint anyway. This config option will be part of the v1.3.0, which is not released yet.

  • 🎉1