Get on /ietf-netconf-acm:nacm fails without a get on /sysrepo-monitoring:sysrepo-state/connection/nacm-stats

[PravalliSure]

I see that issuing a get on /ietf-netconf-acm:nacm or /ietf-netconf-acm:nacm/denied-operations or /ietf-netconf-acm:nacm/denied-data-writes or /ietf-netconf-acm:nacm/denied-notifications is giving this error

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="7">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>operation-failed</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">Timeout expired</error-message>
  </rpc-error>
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>operation-failed</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">User callback failed.</error-message>
  </rpc-error>
</rpc-reply>

But if I first issue a get on /sysrepo-monitoring:sysrepo-state/connection/nacm-stats and then do above it passes fine. Is there any problem with unlocking and locking mutexes in this case?

[michalvasko]

I could not reproduce anything like that, could you mention exact steps? But I would suggest updating netopeer2.