Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

0.75.0: Envoy can crash with websockets

See original GitHub issue

A user reports a crash in an Ambassador 0.75.0 with a websocket load:

[2019-08-24 08:49:22.119][167][critical][assert] [source/common/event/file_event_impl.cc:64] assert failure: events.
[2019-08-24 08:49:22.119][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:81] Caught Aborted, suspect faulting address 0xfffe0000009a
[2019-08-24 08:49:22.119][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:69] Backtrace (use tools/stack_decode.py to get line numbers):
[2019-08-24 08:49:22.119][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #0: [0x197d256]
[2019-08-24 08:49:22.119][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #1: [0x7fd147de64b0]
[2019-08-24 08:49:22.119][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #2: [0xf6fba4]
[2019-08-24 08:49:22.119][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #3: [0x1616609]
[2019-08-24 08:49:22.119][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #4: [0x1619bef]
[2019-08-24 08:49:22.119][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #5: [0xf92a52]
[2019-08-24 08:49:22.119][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #6: [0xf6ae9d]
[2019-08-24 08:49:22.120][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #7: [0xf5672e]
[2019-08-24 08:49:22.120][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #8: [0xf55fd0]
[2019-08-24 08:49:22.120][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #9: [0xf57021]
[2019-08-24 08:49:22.120][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #10: [0x5a60a4]
[2019-08-24 08:49:22.120][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #11: [0x19809da]
[2019-08-24 08:49:22.120][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #12: [0x19809fe]
[2019-08-24 08:49:22.120][167][critical][backtrace] [bazel-out/k8-dbg/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #13: [0x7fd147ddbcf8]
./entrypoint.sh: line 22: warning: run_pending_traps: bad value in trap_list[17]: 0x563be838bc97
./entrypoint.sh: line 19: warning: run_pending_traps: bad value in trap_list[17]: 0x563be838bc97
2019-08-24 08:49:22 AMBASSADOR INFO envoy exited with status 134
./entrypoint.sh: line 22: warning: run_pending_traps: bad value in trap_list[17]: 0x563be838bc97
./entrypoint.sh: line 19: warning: run_pending_traps: bad value in trap_list[17]: 0x563be838bc97
2019-08-24 08:49:22 AMBASSADOR INFO killing extant processes
kill: can't kill pid 154: No such process
time="2019-08-24T08:49:22Z" level=info msg=Done
[2019-08-24 08:49:22 +0000] [102] [INFO] Handling signal: term
./entrypoint.sh: line 192: warning: run_pending_traps: bad value in trap_list[17]: 0x563be838bc97
./entrypoint.sh: line 22: warning: run_pending_traps: bad value in trap_list[17]: 0x563be838bc97
./entrypoint.sh: line 19: warning: run_pending_traps: bad value in trap_list[17]: 0x563be838bc97
2019-08-24 08:49:22 AMBASSADOR INFO shutting down (1)

Downgrading to 0.74.1 prevents the crashes, though that’s obviously not a fix.

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

mnasercommented, Oct 7, 2019

@kflynn I see that you’ve closed this issue, but the Envoy team seems to mention that the release builds won’t have this behavior… is this because I’m somehow not running Envoy with the “release” version?

0reactions

miracle-jiacommented, Jan 10, 2020

@kflynn Could you reproduce the crash? We met the issue probability, too.

Top Results From Across the Web

0.75.0: Envoy can crash with websockets · Issue #1774 - GitHub

We got a coredump! and Envoy is crashing because it's getting an event callback which doesn't have any bits set to indicate the...

WebSockets — envoy 1.25.0-dev-367763 documentation

It demonstrates terminating a WebSocket connection with and without TLS , and provides some basic examples of proxying to encrypted and non-encrypted upstream ......

node.js websocket crashes when client disconnect

The problem is when a client close his browser, then my NodeJS websocket server crashes with the following error : root@WS-SERVER-2:~/app# node ...

WebSockets Crash Course - Handshake, Use-cases, Pros ...

WebSockets technology is a bidirectional, full-duplex protocol for communication between client and server over the web.

WebSocket Crash Course: Learn about WebSockets + Project!

This WebSocket crash course is will cover WebSockets in-depth and how you can create and work with them in Node.js as the backend...