08-10-2022 10:11 PM
Hi I am facing an issue while automate gnmi operation.
Error Trace:
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
"Database is locked for writing. Please retry: the configuration database is locked by session 18 yang_mgmt_infra tcp (system from 127.0.0.1) on since XXXXXX
%GENIE-ERROR: IOS-XE YANG Infrastructure. Additional info: locked"
%GENIE-ERROR: debug_error_string = "{"created":"@1660193967.406907508","description":"Error received from peer ipv4:ip:port","file":"src/core/lib/surface/call.cc","file_line":966,"grpc_message":"Database is locked for writing. Please retry: the configuration database is locked by session 18 yang_mgmt_infra tcp (system from 127.0.0.1) on since 2022-08-07 03:41:28\n IOS-XE YANG Infrastructure. Additional info: locked","grpc_status":14}"
%GENIE-ERROR: ERROR: Database is locked for writing. Please retry: the configuration database is locked by session 18 yang_mgmt_infra tcp (system from 127.0.0.1) on since 2022-08-07 03:41:28
%GENIE-ERROR: IOS-XE YANG Infrastructure. Additional info: locked.
Anyone have any idea on this?
08-11-2022 04:41 AM - edited 08-11-2022 04:41 AM
I'm not sure this is an NSO subject. Or are you doing some fancy gNMI stuff with NSO?
08-11-2022 05:33 AM
The error showing that the database is locked for editing because it is locked by session 18.
I am automating GNMI with python code.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide