search

CESNET / netopeer2

NETCONF toolset
BSD 3-Clause "New" or "Revised" License
296 stars 187 forks source link

Failed to send a notification (Timeout expired) and Waiting for subscription of "ietf-netconf-notifications" failed #1414

Closed jiantuo closed 4 months ago

jiantuo commented 1 year ago

Meet two errors during long term testing, and able to recovery without intervention. Would you please provide some advice?


Jun  1 21:04:26 A3-O daemon.info netopeer2-server[26912]: Published event "rpc" "/notifications:create-subscription" with ID 112 priority 0 for 1 subscribers.
Jun  1 21:04:26 A3-O daemon.info netopeer2-server[26912]: Processing "/notifications:create-subscription" "rpc" event with ID 112 priority 0 (remaining 1 subscribers).
Jun  1 21:04:27 A3-O daemon.err netopeer2-server[26912]: Waiting for subscription of "ietf-netconf-notifications" failed, previous event "notif" with ID 102 was not processed.
Jun  1 21:04:27 A3-O daemon.warn netopeer2-server[26912]: Failed to send a notification (Timeout expired).
Jun  1 21:04:29 A3-O daemon.err netopeer2-server[26912]: Waiting for subscription of "ietf-netconf-notifications" failed, previous event "notif" with ID 102 was not processed.
Jun  1 21:04:29 A3-O daemon.warn netopeer2-server[26912]: Failed to send a notification (Timeout expired).
Jun  1 21:04:29 A3-O daemon.info netopeer2-server[26912]: Published event "rpc" "/ietf-netconf:get" with ID 261 priority 0 for 1 subscribers.
michalvasko commented 1 year ago

I would need to see some previous messages because the problem origin is not seen in this output. But similar messages were seen in a different issue that should be fixed in the current sysrepo devel branch so you may try to use that and check whether the errors would appear again.