Closed Krisscut closed 8 months ago
Use the latest release, the notifications work differently so it makes no sense of fixing any problem in the older version. Also, please attach such long logs as attachments next time.
Ok I will create another ticket or get back to this one if reproduced on latest version. Thanks
Versions:
Netopeer2-server: netopeer2-2.1.71 sysrepo: sysrepo-2.2.105 libnetconf2: libnetconf2-2.1.37 libyang: libyang-2.1.111I'm having an issue with the notification, with the error message [ERR]: SR: Waiting for subscription of "ietf-netconf-notifications" failed, previous event "notif" ID 2 was not processed. It occurs sporadically, like in 1 run out of 50.
We have an app "CallHomeManager" which load the listen.xml & callhome.xml in sysrepo using the command line, and it triggers the ietf-netconf-notifications Between the passed & failed logs below, the difference is that in the log UE_APP-OAM/sysrepo, EV LISTEN: "ietf-netconf-notifications" "notif" ID 2 priority 0 success., the remaining subscribers is 1 when failing and 0 in working case. So I guess something is stuck not answering but can this be investigated ? I don't see anything in the log about the other subscribers not answering in time.
Maybe by dumping the sysrepo state and checking the connection id, process id ?
also one thing that puzzles me is why we have 4 subscribers on the ietf-netconf-notifications when we actually only have one app on it and it answers just fine (orusw). Could it be netopeer2-server that doesn't handle process it ?
Failing log:
Working log: