Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JWT authentication causing "Epoch 0 terminated with an error" in Envoy #15084

Closed
divya21raj opened this issue Jun 24, 2019 · 6 comments
Closed

JWT authentication causing "Epoch 0 terminated with an error" in Envoy #15084

divya21raj opened this issue Jun 24, 2019 · 6 comments

Comments

@divya21raj
Copy link

@divya21raj divya21raj commented Jun 24, 2019

Bug description
I'm trying to implement service to service JWT authentication like something shown in this repo. While it's working fine with Auth0, I'm having trouble while setting it up with my company's authentication service. I made the service architecture by following this article, you can see my repository here.

This is the policy I'm applying ->

apiVersion: authentication.istio.io/v1alpha1
kind: Policy
metadata:
  name: auth-policy
spec:
  targets:
  - name: sa-web-app
  origins:
  - jwt:
      issuer: "My-Issuer"
      jwksUri: "http://10.0.75.1:8080/pub_key.json"
  principalBinding: USE_ORIGIN

I'm hosting the public key locally, you can find it here too.
If I hit the service with an invalid access key (say it's expired), I'm getting a 401 as expected, but a valid access key gives a
503: upstream connect error or disconnect/reset before headers. reset reason: connection failure

Upon checking the logs for the envoy proxy of the publisher pod, I can see this ->
Epoch 0 terminated with an error: signal: segmentation fault (core dumped)

This log message isn't there when working successfully with Auth0, so I think this might be a hint. But looking at the lines in the source code where this log message is present, I can't figure out much....

One reason I think this might occur is the different keys in access token I'm passing. The Auth0 access token has the following keys ->

{
  "iss": "https://xyz-sa.auth0.com/",
  "sub": "0BH7c261T8X0nt9b9B3UE4mP0L5O057V@clients",
  "aud": "https://sentiment-analysis.io/webapp",
  "iat": 1561353753,
  "exp": 1561440153,
  "azp": "0BH7c261T8X0nt9b9B3UE4mP0L5O057V",
  "gty": "client-credentials"
}

And my access token looks like this ->

{
  "http://www.xyz.com/identity/claims/tenancy/slug": "4d8ad062-7f6d-4b4d-9a64-f1c3627a97b4",
  "subtype": "app",
  "nbf": 1561353003,
  "exp": 1561354803,
  "iss": "xyz.com"
}

Anybody has any ideas, I've been stuck for quite some time now, any help will be appreciated..!

Affected product area (please put an X in all that apply)

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[x] Policies and Telemetry
[x] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastrcture

Expected behavior
200 on valid Access Token

Steps to reproduce the bug
Sadly not possible, as the access token I'm using is private to my company :(
Version (include the output of istioctl version --remote and kubectl version)
version.BuildInfo{Version:"1.1.7", GitRevision:"eec7a74473deee98cad0a996f41a32a47dd453c2", User:"root", Host:"341b3bf0-76ac-11e9-b644-0a580a2c0404", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Clean", GitTag:"1.1.6-6-geec7a74"}

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:53:57Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.0", GitCommit:"ddf47ac13c1a9483ea035a79cd7c10005ff21a6d", GitTreeState:"clean", BuildDate:"2018-12-03T20:56:12Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
Helm template, I followed this article.

Environment where bug was observed (cloud vendor, OS, etc)
Windows 10, running the cluster on Minikube.

Additionally, please consider attaching a [cluster state archive](http://istio.io/help/bugs/#generating-a-cluster-state-archive
istio-dump.tar.gz
) by attaching
the dump file to this issue.

@howardjohn

This comment has been minimized.

Copy link
Member

@howardjohn howardjohn commented Jun 24, 2019

Can you provide the full log? After Epoch 0 terminated with an error: signal: segmentation fault (core dumped) there should be stack trace?

@divya21raj

This comment has been minimized.

Copy link
Author

@divya21raj divya21raj commented Jun 24, 2019

Can you provide the full log? After Epoch 0 terminated with an error: signal: segmentation fault (core dumped) there should be stack trace?

Here's the error bit, let me know if you want the full output of
kubectl.exe logs sa-web-app-599cf47c7c-94jb4 -c istio-proxy

opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #22: Envoy::Thread::ThreadImplPosix::ThreadImplPosix()::$_0::__invoke() [0xda0205]
[2019-06-24 05:56:50.954][35][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #23: start_thread [0x7f55289f26ba]
2019-06-24T05:56:50.988264Z     warn    Epoch 0 terminated with an error: signal: segmentation fault (core dumped)
2019-06-24T05:56:50.988305Z     warn    Aborted all epochs
2019-06-24T05:56:50.988349Z     info    Epoch 0: set retry delay to 400ms, budget to 8
2019-06-24T05:56:51.388570Z     info    Reconciling retry (budget 8)
2019-06-24T05:56:51.388716Z     info    Epoch 0 starting
2019-06-24T05:56:51.390011Z     info    Envoy command: [-c /etc/istio/proxy/envoy-rev0.json --restart-epoch 0 --drain-time-s 45 --parent-shutdown-time-s 60 --service-cluster sa-web-app.default --service-node sidecar~172.17.0.19~sa-web-app-599cf47c7c-94jb4.default~default.svc.cluster.local --max-obj-name-len 189 --allow-unknown-fields -l warning --concurrency 2]
[2019-06-24 05:56:51.461][42][warning][misc] [external/envoy/source/common/protobuf/utility.cc:174] Using deprecated option 'envoy.api.v2.Cluster.hosts' from file cds.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.
[2019-06-24 05:56:51.461][42][warning][misc] [external/envoy/source/common/protobuf/utility.cc:174] Using deprecated option 'envoy.api.v2.Cluster.hosts' from file cds.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.
[2019-06-24 05:56:51.461][42][warning][misc] [external/envoy/source/common/protobuf/utility.cc:174] Using deprecated option 'envoy.api.v2.Cluster.hosts' from file cds.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.
[2019-06-24 05:56:51.471][42][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:86] gRPC config stream closed: 14, no healthy upstream
[2019-06-24 05:56:51.471][42][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:49] Unable to establish new stream
[2019-06-24 05:56:52.099][42][warning][misc] [external/envoy/source/common/protobuf/utility.cc:174] Using deprecated option 'envoy.api.v2.Listener.use_original_dst' from file lds.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.
[2019-06-24 05:56:52.497][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:81] Caught Segmentation fault, suspect faulting address 0x0
[2019-06-24 05:56:52.497][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:69] Backtrace (use tools/stack_decode.py to get line numbers):
[2019-06-24 05:56:52.497][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #0: __restore_rt [0x7f265fb2c390]
[2019-06-24 05:56:52.502][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #1: Envoy::Http::JwtAuth::Verifier::Verify() [0x494f47]
[2019-06-24 05:56:52.508][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #2: Envoy::Http::JwtAuth::JwtAuthenticator::VerifyKey() [0x48aa0d]
[2019-06-24 05:56:52.514][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #3: Envoy::Http::JwtAuth::JwtAuthenticator::Verify() [0x48a52d]
[2019-06-24 05:56:52.523][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #4: Envoy::Http::JwtVerificationFilter::decodeHeaders() [0x489a34]
[2019-06-24 05:56:52.541][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #5: Envoy::Http::ConnectionManagerImpl::ActiveStream::decodeHeaders() [0xa91d98]
[2019-06-24 05:56:52.549][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #6: Envoy::Http::ConnectionManagerImpl::ActiveStream::decodeHeaders() [0xa90ffc]
[2019-06-24 05:56:52.554][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #7: Envoy::Http::Http1::ServerConnectionImpl::onHeadersComplete() [0xa9ff22]
[2019-06-24 05:56:52.560][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #8: Envoy::Http::Http1::ServerConnectionImpl::onHeadersComplete() [0xa9ffad]
[2019-06-24 05:56:52.566][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #9: Envoy::Http::Http1::ConnectionImpl::onHeadersCompleteBase() [0xa9f268]
[2019-06-24 05:56:52.573][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #10: http_parser_execute [0xc47e62]
[2019-06-24 05:56:52.579][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #11: Envoy::Http::Http1::ConnectionImpl::dispatchSlice() [0xa9ed4b]
[2019-06-24 05:56:52.584][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #12: Envoy::Http::Http1::ConnectionImpl::dispatch() [0xa9eb2f]
[2019-06-24 05:56:52.589][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #13: Envoy::Http::ConnectionManagerImpl::onData() [0xa8dcb9]
[2019-06-24 05:56:52.594][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #14: Envoy::Network::FilterManagerImpl::onRead() [0x8dd85a]
[2019-06-24 05:56:52.599][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #15: Envoy::Network::ConnectionImpl::onReadReady() [0x8da39e]
[2019-06-24 05:56:52.604][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #16: Envoy::Network::ConnectionImpl::onFileEvent() [0x8d9e71]
[2019-06-24 05:56:52.609][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #17: Envoy::Event::FileEventImpl::assignEvents()::$_0::__invoke() [0x8d5035]
[2019-06-24 05:56:52.614][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #18: event_process_active_single_queue [0xc399bd]
[2019-06-24 05:56:52.618][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #19: event_base_loop [0xc37f70]
[2019-06-24 05:56:52.624][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #20: Envoy::Event::DispatcherImpl::run() [0x8d462d]
[2019-06-24 05:56:52.630][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #21: Envoy::Server::WorkerImpl::threadRoutine() [0x8cf052]
[2019-06-24 05:56:52.635][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #22: Envoy::Thread::ThreadImplPosix::ThreadImplPosix()::$_0::__invoke() [0xda0205]
[2019-06-24 05:56:52.636][49][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #23: start_thread [0x7f265fb226ba]
2019-06-24T05:56:52.642033Z     warn    Epoch 0 terminated with an error: signal: segmentation fault (core dumped)
2019-06-24T05:56:52.642296Z     warn    Aborted all epochs
2019-06-24T05:56:52.642502Z     info    Epoch 0: set retry delay to 800ms, budget to 7
2019-06-24T05:56:52.656701Z     info    Envoy proxy is NOT ready: failed retrieving Envoy stats: Get http://127.0.0.1:15000/stats?usedonly: dial tcp 127.0.0.1:15000: connect: connection refused
2019-06-24T05:56:53.443022Z     info    Reconciling retry (budget 7)
2019-06-24T05:56:53.443075Z     info    Epoch 0 starting
2019-06-24T05:56:53.444079Z     info    Envoy command: [-c /etc/istio/proxy/envoy-rev0.json --restart-epoch 0 --drain-time-s 45 --parent-shutdown-time-s 60 --service-cluster sa-web-app.default --service-node sidecar~172.17.0.19~sa-web-app-599cf47c7c-94jb4.default~default.svc.cluster.local --max-obj-name-len 189 --allow-unknown-fields -l warning --concurrency 2]
[2019-06-24 05:56:53.557][52][warning][misc] [external/envoy/source/common/protobuf/utility.cc:174] Using deprecated option 'envoy.api.v2.Cluster.hosts' from file cds.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.
[2019-06-24 05:56:53.557][52][warning][misc] [external/envoy/source/common/protobuf/utility.cc:174] Using deprecated option 'envoy.api.v2.Cluster.hosts' from file cds.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.
[2019-06-24 05:56:53.557][52][warning][misc] [external/envoy/source/common/protobuf/utility.cc:174] Using deprecated option 'envoy.api.v2.Cluster.hosts' from file cds.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.
[2019-06-24 05:56:53.565][52][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:86] gRPC config stream closed: 14, no healthy upstream
[2019-06-24 05:56:53.565][52][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:49] Unable to establish new stream
[2019-06-24 05:56:54.214][52][warning][misc] [external/envoy/source/common/protobuf/utility.cc:174] Using deprecated option 'envoy.api.v2.Listener.use_original_dst' from file lds.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.
2019-06-24T05:56:54.669552Z     info    Envoy proxy is ready
@divya21raj

This comment has been minimized.

Copy link
Author

@divya21raj divya21raj commented Jun 24, 2019

This happens the moment I make a request with my access token.

@yangminzhu

This comment has been minimized.

Copy link
Contributor

@yangminzhu yangminzhu commented Jun 24, 2019

@divya21raj thanks for the report, we're looking into this issue and will get back to you soon.

@divya21raj

This comment has been minimized.

Copy link
Author

@divya21raj divya21raj commented Jun 27, 2019

Update, upon checking the envoy logs with this filter ->

kubectl exec $(kubectl get pods -l app=sa-web-app -o jsonpath='{.items[0].metadata.name}') -c istio-proxy -- curl -X POST "localhost:15000/logging?filter=debug" -s

I see this

attributes {
  key: "context.prox
[2019-06-27 06:03:41.926][38][debug][filter] [./src/envoy/utils/header_update.h:46] Mixer forward attributes set: CkAKCnNvdXJjZS51aWQSMhIwa3ViZXJuZXRlczovL3NhLXdlYi1hcHAtNTk5Y2Y0N2M3Yy05NGpiNC5kZWZhdWx0
[2019-06-27 06:10:02.733][37][debug][filter] [external/envoy/source/extensions/filters/listener/original_dst/original_dst.cc:18] original_dst: New connection accepted
[2019-06-27 06:10:02.733][37][debug][filter] [src/envoy/http/mixer/filter.cc:39] Called Mixer::Filter : Filter
[2019-06-27 06:10:02.733][37][debug][filter] [src/envoy/http/mixer/filter.cc:146] Called Mixer::Filter : setDecoderFilterCallbacks
[2019-06-27 06:10:02.733][37][debug][filter] [src/envoy/http/jwt_auth/jwt_authenticator.cc:62] Jwt authentication starts
[2019-06-27 06:10:02.734][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:81] Caught Segmentation fault, suspect faulting address 0x0
[2019-06-27 06:10:02.734][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:69] Backtrace (use tools/stack_decode.py to get line numbers):
[2019-06-27 06:10:02.734][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #0: __restore_rt [0x7fa363612390]
[2019-06-27 06:10:02.738][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #1: Envoy::Http::JwtAuth::Verifier::Verify() [0x494f47]
[2019-06-27 06:10:02.740][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #2: Envoy::Http::JwtAuth::JwtAuthenticator::VerifyKey() [0x48aa0d]
[2019-06-27 06:10:02.747][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #3: Envoy::Http::JwtAuth::JwtAuthenticator::Verify() [0x48a52d]
[2019-06-27 06:10:02.765][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #4: Envoy::Http::JwtVerificationFilter::decodeHeaders() [0x489a34]
[2019-06-27 06:10:02.767][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #5: Envoy::Http::ConnectionManagerImpl::ActiveStream::decodeHeaders() [0xa91d98]
[2019-06-27 06:10:02.771][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #6: Envoy::Http::ConnectionManagerImpl::ActiveStream::decodeHeaders() [0xa90ffc]
[2019-06-27 06:10:02.774][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #7: Envoy::Http::Http1::ServerConnectionImpl::onHeadersComplete() [0xa9ff22]
[2019-06-27 06:10:02.777][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #8: Envoy::Http::Http1::ServerConnectionImpl::onHeadersComplete() [0xa9ffad]
[2019-06-27 06:10:02.781][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #9: Envoy::Http::Http1::ConnectionImpl::onHeadersCompleteBase() [0xa9f268]
[2019-06-27 06:10:02.784][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #10: http_parser_execute [0xc47e62]
[2019-06-27 06:10:03.051][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #11: Envoy::Http::Http1::ConnectionImpl::dispatchSlice() [0xa9ed4b]
[2019-06-27 06:10:03.055][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #12: Envoy::Http::Http1::ConnectionImpl::dispatch() [0xa9eb2f]
[2019-06-27 06:10:03.060][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #13: Envoy::Http::ConnectionManagerImpl::onData() [0xa8dcb9]
[2019-06-27 06:10:03.064][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #14: Envoy::Network::FilterManagerImpl::onRead() [0x8dd85a]
[2019-06-27 06:10:03.068][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #15: Envoy::Network::ConnectionImpl::onReadReady() [0x8da39e]
[2019-06-27 06:10:03.071][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #16: Envoy::Network::ConnectionImpl::onFileEvent() [0x8d9e71]
[2019-06-27 06:10:03.075][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #17: Envoy::Event::FileEventImpl::assignEvents()::$_0::__invoke() [0x8d5035]
[2019-06-27 06:10:03.078][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #18: event_process_active_single_queue [0xc399bd]
[2019-06-27 06:10:03.082][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #19: event_base_loop [0xc37f70]
[2019-06-27 06:10:03.086][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #20: Envoy::Event::DispatcherImpl::run() [0x8d462d]
[2019-06-27 06:10:03.090][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #21: Envoy::Server::WorkerImpl::threadRoutine() [0x8cf052]
[2019-06-27 06:10:03.094][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #22: Envoy::Thread::ThreadImplPosix::ThreadImplPosix()::$_0::__invoke() [0xda0205]
[2019-06-27 06:10:03.094][37][critical][backtrace] [bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:73] #23: start_thread [0x7fa3636086ba]
2019-06-27T06:10:03.099664Z     warn    Epoch 0 terminated with an error: signal: segmentation fault (core dumped)
2019-06-27T06:10:03.099755Z     warn    Aborted all epochs
2019-06-27T06:10:03.099799Z     info    Epoch 0: set retry delay to 400ms, budget to 8
2019-06-27T06:10:03.499901Z     info    Reconciling retry (budget 8)
2019-06-27T06:10:03.499971Z     info    Epoch 0 starting

A seg fault after line 82 in jwt_authenticator.cc ?

@linsun

This comment has been minimized.

Copy link
Member

@linsun linsun commented Jun 28, 2019

should this be closed - I don't see a PR associated with it. this is referred as a fixed item in rel note.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
6 participants
You can’t perform that action at this time.