mosn icon indicating copy to clipboard operation
mosn copied to clipboard

load config from : /etc/istio/proxy/envoy-rev0.json json unmarshal config failed

Open ggjjlldd opened this issue 3 years ago • 1 comments

Your question

Describe your question clearly. load config from : /etc/istio/proxy/envoy-rev0.json json unmarshal config failed

Environment

[root@linuxtestacb9 ~]# kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:56:40Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:48:36Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

istio 1.9.2

  • MOSN Version mosnio/proxyv2:1.5.10-mosn

Logs

  • Paste the logs you see.

2021-07-13 07:04:25,602 [INFO] register a new handler maker, name is default, is default: true 2021-07-13 07:04:25,603 [INFO] [config] processor added to configParsedCBMaps 2021-07-13 07:04:25,609 [INFO] [network] [ register pool factory] register protocol: Http1 factory 2021-07-13 07:04:25,609 [INFO] [network] [ register pool factory] register protocol: Http2 factory 2021-07-13 07:04:25,610 [INFO] [network] [ register pool factory] register protocol: X factory 2021-07-13 07:04:25,616 [INFO] load config from : /etc/istio/proxy/envoy-rev0.json 2021-07-13 07:04:25,616 [FATAL] [config] [default load] json unmarshal config failed, error: invalid character ']' looking for beginning of value 2021-07-13T07:04:25.620870Z error Epoch 0 exited with error: exit status 1 2021-07-13T07:04:25.620914Z info No more active epochs, terminating

ggjjlldd avatar Jul 13 '21 07:07 ggjjlldd

@ggjjlldd I previously fixed a similar issue before istio 1.5.x, which was caused by the pilot- Agent rendering of the file envoys -rev0.json not following the JSON specification. But MOSN is parsed strictly according to the JSON specification, so the error will be reported. Now, you can try using envoy_bootstrap_v2.json instead of envoy_bootstrap.json or modify the file envoy_bootstrap.json to fix json format.

wangfakang avatar Aug 01 '21 08:08 wangfakang