GNMI CLI Subscribes With No Namespace Results GNMI Crashes on Multi-Asic Chassis #20510
Comments
|
Log from gnmi.log when that's happening. 2024 Oct 16 15:52:03.976726 ixre-egl-board30 INFO gnmi#supervisord: gnmi-native I1016 15:52:03.976540 21 db_client.go:675] Invalid db table Path STATE_DB NEIGH_STATE_TABLE |
Description
We are using multi-asic chassis (Nokia-7250) to test telemetry. It is found if I provide the following CLI from ptf server without providing namespace information, GNMI container crashes and restarts.
python /root/gnxi/gnmi_cli_py/py_gnmicli.py -g -t 10.250.6.233 -p 50052 -m subscribe -x NEIGH_STATE_TABLE -xt STATE_DB -o ndastreamingservertest --subscribe_mode 0 --submode 1 --interval 0 --update_count 2 --create_connections 1
Sending SubscribeRequest
subscribe {
prefix {
target: "STATE_DB"
}
subscription {
path {
elem {
name: "NEIGH_STATE_TABLE"
}
}
mode: ON_CHANGE
}
}
Received an exception from server side and error message is: '<_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "Connection reset by peer"
debug_error_string = "{"created":"@1729002509.589264167","description":"Error received from peer ipv4:10.250.6.233:50052","file":"src/core/lib/surface/call.cc","file_line":1070,"grpc_message":"Connection reset by peer","grpc_status":14}"
Look at chassis: GNMI container restarts by that command.
root@ixre-egl-board30:/# admin@ixre-egl-board30:~$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c93e2246ff1f docker-snmp:latest "/usr/local/bin/supe?" 2 weeks ago Up 26 minutes snmp
c4c5e555d8d9 docker-sonic-mgmt-framework:latest "/usr/local/bin/supe?" 2 weeks ago Up 27 minutes mgmt-framework
f2784babf897 docker-lldp:latest "/usr/bin/docker-lld?" 2 weeks ago Up 27 minutes lldp1
ec0b77ec803f docker-lldp:latest "/usr/bin/docker-lld?" 2 weeks ago Up 27 minutes lldp0
fbec90b49288 docker-sonic-gnmi:latest "/usr/local/bin/supe?" 2 weeks ago Exited (0) 4 seconds ago gnmi
Steps to reproduce the issue:
Describe the results you received:
GNMI crashes.
Describe the results you expected:
No crash no matter what wrong CLI input provided.
Output of
show version:2405
The text was updated successfully, but these errors were encountered: