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

[Bug] Envoy proxy container failing #39

Open
felixfaisal opened this issue Jan 3, 2022 · 3 comments · May be fixed by #49
Open

[Bug] Envoy proxy container failing #39

felixfaisal opened this issue Jan 3, 2022 · 3 comments · May be fixed by #49
Assignees
Labels
language/rust Rust related

Comments

@felixfaisal
Copy link
Contributor

Description
Proxy container(Envoy) container exits due to an issue with configuration

Expected Behavior
Should run the TCP metrics succesfully

Error

proxy_1        | [2022-01-03 16:20:08.763][8][info][main] [external/envoy/source/server/server.cc:372]   envoy.request_id: envoy.request_id.uuid
proxy_1        | [2022-01-03 16:20:08.766][8][critical][main] [external/envoy/source/server/server.cc:114] error initializing configuration '/etc/envoy.yaml': Protobuf message (type envoy.config.bootstrap.v3.Bootstrap reason INVALID_ARGUMENT:(static_resources.clusters[0]) hosts: Cannot find field.) has unknown fields
proxy_1        | [2022-01-03 16:20:08.766][8][info][main] [external/envoy/source/server/server.cc:891] exiting
proxy_1        | [2022-01-03 16:20:08.766][8][debug][main] [external/envoy/source/common/access_log/access_log_manager_impl.cc:21] destroyed access loggers
proxy_1        | [2022-01-03 16:20:08.766][8][debug][main] [external/envoy/source/common/event/dispatcher_impl.cc:82] destroying dispatcher main_thread
proxy_1        | [2022-01-03 16:20:08.766][8][debug][init] [external/envoy/source/common/init/watcher_impl.cc:31] init manager Server destroyed
proxy_1        | Protobuf message (type envoy.config.bootstrap.v3.Bootstrap reason INVALID_ARGUMENT:(static_resources.clusters[0]) hosts: Cannot find field.) has unknown fields
tcp-metrics_proxy_1 exited with code 1

Environment:

  • OS: Ubuntu
  • Version: 21.10
  • Device: Laptop

To Reproduce
Follow the steps for TCPmetrics to reproduce this error,
However I've used make run to see docker logs

@welcome
Copy link

welcome bot commented Jan 3, 2022

Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Contributors' Welcome Guide and sure to join the community Slack.

@leecalcote
Copy link
Member

Thank you, @felixfaisal 👍

acald-creator added a commit to nebula-aac/wasm-filters that referenced this issue Aug 21, 2022
Description: This fixes a previous open issue layer5io#39

Updated envoy.yaml
- Envoy now calls for typed_config
- Rearranged placement of the filters, but it probably can be reworked to make it cleaner
- Clusters is now set up with individual load assignment, no longer uses hosts
@acald-creator
Copy link
Contributor

Hello

I would like to contribute to this. I already started working on this issue, and I have a working envoy.yaml file where I was able to build the docker compose and test the endpoint. I just need to go back and amend my last commit to show that it is properly signed.

acald-creator added a commit to nebula-aac/wasm-filters that referenced this issue Aug 29, 2022
Description: This fixes a previous open issue layer5io#39

Updated envoy.yaml
- Envoy now calls for typed_config
- Rearranged placement of the filters, but it probably can be reworked to make it cleaner
- Clusters is now set up with individual load assignment, no longer uses hosts
acald-creator added a commit to nebula-aac/wasm-filters that referenced this issue Aug 29, 2022
Description: This fixes a previous open issue layer5io#39

Updated envoy.yaml
- Envoy now calls for typed_config in `v3`
- Rearranged placement of the filters, but it probably can be reworked to make it cleaner
- Clusters is now set up with an endpoint, instead of `hosts`
- Probably need to fix spacing

Signed-off-by: Antonette Caldwell <[email protected]>
acald-creator added a commit to nebula-aac/wasm-filters that referenced this issue Aug 30, 2022
Description: This fixes a previous open issue layer5io#39

Updated envoy.yaml
- Envoy now calls for typed_config in `v3`
- Rearranged placement of the filters, but it probably can be reworked to make it cleaner
- Clusters is now set up with an endpoint, instead of `hosts`
- Probably need to fix spacing

Signed-off-by: Antonette Caldwell <[email protected]>
acald-creator added a commit to nebula-aac/wasm-filters that referenced this issue Aug 30, 2022
Description: This fixes a previous open issue layer5io#39

Updated envoy.yaml
- Envoy now calls for typed_config in `v3`
- Rearranged placement of the filters, but it probably can be reworked to make it cleaner
- Clusters is now set up with an endpoint, instead of `hosts`
- Probably need to fix spacing

Signed-off-by: Antonette Caldwell <[email protected]>
@acald-creator acald-creator linked a pull request Sep 3, 2022 that will close this issue
acald-creator added a commit to nebula-aac/wasm-filters that referenced this issue Sep 5, 2022
Description: This fixes a previous open issue layer5io#39

Updated envoy.yaml
- Envoy now calls for typed_config in `v3`
- Rearranged placement of the filters, but it probably can be reworked to make it cleaner
- Clusters is now set up with an endpoint, instead of `hosts`
- Probably need to fix spacing

Signed-off-by: Antonette Caldwell <[email protected]>
@acald-creator acald-creator self-assigned this Nov 9, 2022
@acald-creator acald-creator added language/rust Rust related and removed issue/remind labels Jan 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
language/rust Rust related
Development

Successfully merging a pull request may close this issue.

4 participants