Hello all, we are getting some strange errors on starrocks 4.0.7 - on FE we get this error on mysql protocol Error executing query: SQL Error [1064] [42000]: Access storage error. Error message: failed to get file schema: A error occurred: errorCode=2001 errorMessage:Channel inactive error! and on CN log on kubernetes we get this segmentation fault error: start time: Thu Mar 19 005511 CST 2026, server uptime: 005511 up 1 day, 15:59, 0 users, load average: 3.22, 10.79, 18.03 Run with JEMALLOC_CONF: 'percpu_arenapercpu,oversize threshold0,muzzy_decay_ms5000,dirty decay ms5000,metadata_thpauto,background threadtrue,proftrue,prof activefalse' Ignored unknown config: enable_spill_to_disk Ignored unknown config: spill_to_disk_storage_path 4.0.7 RELEASE (build b75f536 distro ubuntu arch x86_64) query_id:00000000-0000-0000-0000-000000000000, fragment_instance:00000000-0000-0000-0000-000000000000, plan_node_id:-1 * Aborted at 1773853038 (unix time) try "date -d @1773853038" if you are using GNU date * PC: @ 0x7f8e3ec4c1d4 EVP_KEYMGMT_get0_name * SIGSEGV (@0x0) received by PID 27 (TID 0x7f8f29977640) LWP(321) from PID 0; stack trace: * @ 0x7f8f91f8eee8 (/usr/lib/x86_64-linux-gnu/libc.so.6+0x99ee7) @ 0x11fb5bc8 google::(anonymous namespace)::FailureSignalHandler(int, siginfo_t*, void*) @ 0x7f8f93135906 PosixSignals::chained_handler(int, siginfo_t*, void*) [clone .part.0] @ 0x7f8f9313637e JVM_handle_linux_signal @ 0x7f8f91f37520 (/usr/lib/x86_64-linux-gnu/libc.so.6+0x4251f) @ 0x7f8e3ec4c1d4 EVP_KEYMGMT_get0_name @ 0x7f8e3ec5a827 (/usr/lib/x86_64-linux-gnu/libcrypto.so.3+0x1a7826) @ 0x7f8f84493453 SSL_CTX_new_ex @ 0x7f8f90e1c95a Java_org_wildfly_openssl_SSLImpl_makeSSLContext0 @ 0x7f8e93267be1 (unknown) [1773853039.1][thread: 140252854842944] je_mallctl execute purge success [1773853039.1][thread: 140252854842944] je_mallctl execute dontdump success it appears to be an openssl error, it happens when trying to access a file in azure datalake storage: SELECT * FROM FILES( "path" = "abfss://landing@someaccount.dfs.core.windows.net/landing/data.parquet", "format" = "parquet", "azure.adls2.storage_account" = "someaccount", "azure.adls2.shared_key" = "***" ) LIMIT 1;

Maybe a OpenSSL version issue?

related to hadoop upgraded to v3.4.3, the wildfly-ssl library get upgraded in v3.4.3, introduces some unexpected behavior. https://hadoop.apache.org/docs/r3.4.3/hadoop-project-dist/hadoop-common/release/3.4.3/RELEASENOTES.3.4.3.html