Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

in my test i only found he first time model change notify MSG on the sr client log, and the follow-up notify MSG seems can not receive,is any one can do me a favor,thanks a lot. #206

Closed
ZhaoGuangYue1986 opened this issue Jun 27, 2016 · 1 comment
Labels
is:question Issue is actually a question.

Comments

@ZhaoGuangYue1986
Copy link

ZhaoGuangYue1986 commented Jun 27, 2016

in my test i only found he first time model change notify MSG on the sr client log, and the follow-up notify MSG seems can not receive,is any one can do me a favor,thanks a lot.

===first time model change log ===

netopeer2-server[14610]: (rp_dt_commit:697) Commit (3/7): all modified models loaded successfully
netopeer2-server[14610]: (rp_dt_commit:706) Commit (4/7): replay of operation succeeded
netopeer2-server[14610]: (rp_dt_commit:715) Commit (5/7): merged models validation succeeded
netopeer2-server[14610]: (rp_dt_commit:720) Commit (6/7): data write succeeded
netopeer2-server[14610]: (dm_commit_notify:2488) Sending notifications about the changes made in running datastore...
netopeer2-server[14610]: (np_subscription_notify:751) Sending module-change notification to '/tmp/sysrepo-subscriptions/ManagedElement/14610.x02Lih.sock' @ 1843744969.
netopeer2-server[14610]: (cl_sm_notif_process:556) Received a notification for subscription id=1843744969 (source address='/tmp/sysrepo-local-14610.sock').

netopeer2-server[14610]: (sm_session_create:467) New session created successfully, real user=root, effective user=(null), session id=665374554.
netopeer2-server[14610]: (cl_sm_notif_process:609) Calling module-change callback for subscription id=1843744969.
netopeer2-server[14610]: *** Handle change of module ManagedElement ... ***
netopeer2-server[14610]: (dm_unlock_datastore:786) Unlock datastore request
netopeer2-server[14610]: (rp_dt_commit:741) Commit (7/7): finished successfully
netopeer2-server[14610]: EDIT-CONFIG: done.

===second time model change log === --can not see the _cl_sm_notif_process receive msg

netopeer2-server[14610]: (rp_dt_commit:697) Commit (3/7): all modified models loaded successfully
netopeer2-server[14610]: (rp_dt_commit:706) Commit (4/7): replay of operation succeeded
netopeer2-server[14610]: (rp_dt_commit:715) Commit (5/7): merged models validation succeeded
netopeer2-server[14610]: (rp_dt_commit:720) Commit (6/7): data write succeeded
netopeer2-server[14610]: (dm_commit_notify:2488) Sending notifications about the changes made in running datastore...
netopeer2-server[14610]: (np_subscription_notify:751) Sending module-change notification to '/tmp/sysrepo-subscriptions/ManagedElement/14610.x02Lih.sock' @ 1843744969.
netopeer2-server[14610]: (dm_unlock_datastore:786) Unlock datastore request
netopeer2-server[14610]: (rp_dt_commit:741) Commit (7/7): finished successfully
netopeer2-server[14610]: EDIT-CONFIG: done.

@ZhaoGuangYue1986 ZhaoGuangYue1986 changed the title when in my test i only found he first time model change notify MSG on the sr client log, and the follow-up notify MSG seems can not receive,is any one can do me a favor,thanks a lot. Jun 27, 2016
@rastislavs
Copy link
Contributor

Hi,

we would need some more information to be able to help you:

What application has subscribed for changes in ManagedElement? What API call has been used? Are you sure that in the moment of the second change, the subscribed application was still running?

Could you please isolate the issue to some minimalistic unit-test code, so that we can reporoduce it?

Thanks,
Rastislav

@rastislavs rastislavs added the is:question Issue is actually a question. label Jun 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is:question Issue is actually a question.
Projects
None yet
Development

No branches or pull requests

2 participants