You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LOG_LEVEL will be equal to "null" telemetry.sh:L65
As a result "null" will be passed as a parameter: -v null to telemetry binary inside docker and it will cause fail of docker start
remove "log_level": "2" from config db if its present
run config reload -y.
run docker ps -a - telemetry will have status "Exited (0) About a minute ago"
Describe the results you received:
admin@sonic:~$ sudo grep -A 5 "telemetry invalid value" /var/log/telemetry.log
Oct 12 13:09:23.446046 ptr-sonic-n1-s1 INFO telemetry#/supervisord: telemetry invalid value "null" for flag -v: strconv.Atoi: parsing "null": invalid syntax
Oct 12 13:09:23.446143 ptr-sonic-n1-s1 INFO telemetry#/supervisord: telemetry Usage of /usr/sbin/telemetry:
Oct 12 13:09:23.446750 ptr-sonic-n1-s1 INFO telemetry#/supervisord: telemetry -allow_no_client_auth
Oct 12 13:09:23.447017 ptr-sonic-n1-s1 INFO telemetry#/supervisord: telemetry #011When set, telemetry server will request but not require a client certificate.
Oct 12 13:09:23.447120 ptr-sonic-n1-s1 INFO telemetry#/supervisord: telemetry -alsologtostderr
admin@sonic:~$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
52f45cdaa29f docker-sflow:latest "/usr/local/bin/supe…" 9 minutes ago Up 9 minutes sflow
35a3345daa84 docker-nat:latest "/usr/local/bin/supe…" 9 minutes ago Up 9 minutes nat
7f989da64f04 docker-sonic-mgmt-framework:latest "/usr/local/bin/supe…" 2 weeks ago Up 9 minutes mgmt-framework
67589a0b619c docker-sonic-telemetry:latest "/usr/local/bin/supe…" 2 weeks ago Exited (0) 5 minutes ago telemetry
59d8c54d96be docker-snmp:latest "/usr/local/bin/supe…" 2 weeks ago Up 8 minutes snmp
f97cb689f2e2 docker-router-advertiser:latest "/usr/bin/docker-ini…" 2 weeks ago Up 9 minutes radv
195019ff1d93 docker-lldp:latest "/usr/bin/docker-lld…" 2 weeks ago Up 9 minutes lldp
c59085bdf0de docker-platform-monitor:latest "/usr/bin/docker_ini…" 2 weeks ago Up 9 minutes pmon
5dca3589adc5 docker-syncd-mlnx:latest "/usr/local/bin/supe…" 2 weeks ago Up 9 minutes syncd
ef2d9a76f77e docker-teamd:latest "/usr/local/bin/supe…" 2 weeks ago Up 9 minutes teamd
d9db486987e2 docker-orchagent:latest "/usr/bin/docker-ini…" 2 weeks ago Up 9 minutes swss
f0590580c032 docker-fpm-frr:latest "/usr/bin/docker_ini…" 2 weeks ago Up 9 minutes bgp
d5d7ccef0e78 docker-database:latest "/usr/local/bin/dock…" 2 weeks ago Up 2 weeks database
Describe the results you expected:
Expect telemetry docker is up since missing just "log_level" configuration doesn't look so critical to prevent telemetry from running
Description
telemetry_vars.j2 file use config_db.json to generate set of parameters.
It uses following configs:
This config is converted by telemetry.sh:L13 :
But if log_level is not provided in condig_db.json than telemetry.sh can't handle it properly
for example:
LOG_LEVEL will be equal to "null" telemetry.sh:L65
As a result "null" will be passed as a parameter: -v null to telemetry binary inside docker and it will cause fail of docker start
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Expect telemetry docker is up since missing just "log_level" configuration doesn't look so critical to prevent telemetry from running
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: