envoyproxy/envoy
在 GitHub 查看backtrace.h:104 Caught Aborted, suspect faulting address 0x38aba00000011
Open
#21,239 建立於 2022年5月11日
area/sdsbughelp wanted
倉庫指標
- Star
- (27,997 star)
- PR 合併指標
- (平均合併 8天) (30 天內合併 378 個 PR)
描述
Hi,
Randomly but quite frequently just at startup of the POD the envoy process is got a segmentation fault:
[2022-05-11 08:50:41.718][17][debug][upstream] [source/common/upstream/strict_dns_cluster.cc:178] DNS refresh rate reset for 10.139.91.137, refresh rate 5000 ms
[2022-05-11 08:50:41.724][17][debug][main] [source/server/server.cc:242] flushing stats
[2022-05-11 08:50:41.741][17][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:315] dns resolution for stub-server-1.test-1 started
[2022-05-11 08:50:41.742][17][debug][dns] [source/extensions/network/dns_resolver/cares/dns_impl.cc:236] dns resolution for stub-server-1.test-1 completed with status 0
[2022-05-11 08:50:41.742][17][debug][upstream] [source/common/upstream/upstream_impl.cc:256] transport socket match, socket default selected for host with address 10.109.138.97:5050
[2022-05-11 08:50:41.742][17][debug][upstream] [source/common/upstream/strict_dns_cluster.cc:178] DNS refresh rate reset for stub-server-1.test-1, refresh rate 5000 ms
[2022-05-11 08:50:42.548][17][debug][file] [source/common/filesystem/inotify/watcher_impl.cc:72] notification: fd: 1 mask: 80 file: ..data
[2022-05-11 08:50:42.548][17][debug][file] [source/common/filesystem/inotify/watcher_impl.cc:88] matched callback: directory: ..data
[2022-05-11 08:50:42.548][17][debug][config] [source/extensions/transport_sockets/tls/ssl_socket.cc:435] Secret is updated.
[2022-05-11 08:50:42.548][17][debug][file] [source/common/filesystem/inotify/watcher_impl.cc:72] notification: fd: 1 mask: 80 file: ..data
[2022-05-11 08:50:42.548][17][debug][file] [source/common/filesystem/inotify/watcher_impl.cc:88] matched callback: directory: ..data
[2022-05-11 08:50:42.548][17][critical][main] [source/exe/terminate_handler.cc:12] std::terminate called! (possible uncaught exception, see trace)
[2022-05-11 08:50:42.548][17][critical][backtrace] [./source/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers):
[2022-05-11 08:50:42.548][17][critical][backtrace] [./source/server/backtrace.h:92] Envoy version: af50070ee60866874b0a9383daf9364e884ded22/1.21.1/Modified/RELEASE/BoringSSL
[2022-05-11 08:50:42.549][17][critical][backtrace] [./source/server/backtrace.h:98] #0: [0x55b11677b963]
[2022-05-11 08:50:42.549][17][critical][backtrace] [./source/server/backtrace.h:98] #1: [0x55b11677b7e9]
[2022-05-11 08:50:42.549][17][critical][backtrace] [./source/server/backtrace.h:98] #2: [0x55b116bed9b8]
[2022-05-11 08:50:42.549][17][critical][backtrace] [./source/server/backtrace.h:104] Caught Aborted, suspect faulting address 0x38aba00000011
[2022-05-11 08:50:42.549][17][critical][backtrace] [./source/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers):
[2022-05-11 08:50:42.549][17][critical][backtrace] [./source/server/backtrace.h:92] Envoy version: af50070ee60866874b0a9383daf9364e884ded22/1.21.1/Modified/RELEASE/BoringSSL
[2022-05-11 08:50:42.549][17][critical][backtrace] [./source/server/backtrace.h:96] #0: __restore_rt [0x7f24f39918c0]
[2022-05-11 08:50:42.549][17][critical][backtrace] [./source/server/backtrace.h:98] #1: [0x55b11677b7e9]
[2022-05-11 08:50:42.549][17][critical][backtrace] [./source/server/backtrace.h:98] #2: [0x55b116bed9b8]
Is a known issue? Any idea?