Closed x15zhang closed 5 years ago
I suspect there are some problems with the format of your YAML file.
cat -A yam_file
I used yaml validation tool to validate it and the result shows it is valid.
@x15zhang you have to specify stat_prefix
for dubbo filter. it is required: https://www.envoyproxy.io/docs/envoy/latest/api-v2/config/filter/network/dubbo_proxy/v2alpha1/dubbo_proxy.proto#envoy-api-msg-config-filter-network-dubbo-proxy-v2alpha1-dubboproxy
It is the format issue because name and config is not aligned. Thanks @lizan and @zyfjeff for clarifing.
I am running envoy v1.11.0 with dubbo config as following:
and I get bellow error: [2019-08-01 14:46:28.008][9713][info][upstream] _[external/envoy/source/common/upstream/cluster_manager_impl.cc:148] cm init: all clusters initialized [2019-08-01 14:46:28.008][9713][info][config] [external/envoy/source/server/configurationimpl.cc:71] loading 1 listener(s) [2019-08-01 14:46:28.009][9713][critical][main] [external/envoy/source/server/server.cc:93] error initializing configuration 'dubbo.yaml': Proto constraint validation failed (DubboProxyValidationError.StatPrefix: ["value length must be at least " '\x01' " bytes"]): [2019-08-01 14:46:28.009][9713][info][main] [external/envoy/source/server/server.cc:560] exiting Proto constraint validation failed (DubboProxyValidationError.StatPrefix: ["value length must be at least " '\x01' " bytes"]):