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

Failed to unlink SHM sub_ietf-subscribed-notifications.oper (No such file or directory) #1634

Open
rydy opened this issue Aug 28, 2024 · 10 comments
Labels
is:bug Bug description. status:invalid Issue is not reproducible.

Comments

@rydy
Copy link

rydy commented Aug 28, 2024

Hi,
I'm using version 2.2.19, When "Failed to unlink SHM sub_ietf-subscribed-notifications.oper (No such file or directory)" occurs, netopeer2-server cannot be started. Is there any other way except redeploy sysrepo? What causes this error?

[INF]: SR: Connection 16683 created.
[INF]: SR: Session 16694 (user "root", CID 16683) created.
[WRN]: SR: Recovering module "ietf-subscribed-notifications" operational get subscription of CID 12.
[ERR]: SR: Failed to unlink "/dev/shm/OM_DUsub_ietf-subscribed-notifications.oper.d4cc6de2" SHM (No such file or directory).
[ERR]: NP: Subscribing for providing "ietf-subscribed-notifications" state data failed (System function call failed).
[ERR]: NP: Server data subscribe failed.
[INF]: NP: Server terminated.

thanks.

@rydy
Copy link
Author

rydy commented Aug 31, 2024

Is it possible that sysrepo will delete these files?

@michalvasko
Copy link
Member

Please update sysrepo to the latest release and try again.

@michalvasko michalvasko added is:bug Bug description. status:invalid Issue is not reproducible. labels Sep 2, 2024
@rydy
Copy link
Author

rydy commented Sep 2, 2024

Please update sysrepo to the latest release and try again.

Can you provide this fix commit? I want to update only this fix.

1 similar comment
@rydy
Copy link
Author

rydy commented Sep 2, 2024

Please update sysrepo to the latest release and try again.

Can you provide this fix commit? I want to update only this fix.

@michalvasko
Copy link
Member

Can you provide this fix commit?

I cannot because I really do not know, there were hundreds of commits since the version you are using, sorry.

@rydy
Copy link
Author

rydy commented Oct 25, 2024

The 2.2.19 version has a open() on "/dev/shm/srsub_o-ran-file-management.notif" failed (No such file or directory). , Are these two errors the same bug?

netopeer2-server log:

[2024-10-22 06:59:54.615] [INF]: NP: Session 2: thread 0 event new RPC.
[2024-10-22 06:59:54.640] [INF]: SR: EV ORIGIN: "/ietf-netconf:get" "rpc" ID 2 priority 0 for 1 subscribers published.
[2024-10-22 06:59:54.640] [INF]: SR: EV LISTEN: "/ietf-netconf:get" "rpc" ID 2 priority 0 processing (remaining 1 subscribers).
[2024-10-22 06:59:54.657] [INF]: SR: EV LISTEN: "/ietf-netconf:get" "rpc" ID 2 priority 0 success (remaining 0 subscribers).
[2024-10-22 06:59:54.657] [INF]: SR: EV ORIGIN: "/ietf-netconf:get" "rpc" ID 2 priority 0 succeeded.
[2024-10-22 06:59:54.672] [INF]: NP: Session 2: thread 1 event new RPC.
[2024-10-22 06:59:54.677] [INF]: SR: EV ORIGIN: "/notifications:create-subscription" "rpc" ID 1 priority 0 for 1 subscribers published.
[2024-10-22 06:59:54.677] [INF]: SR: EV LISTEN: "/notifications:create-subscription" "rpc" ID 1 priority 0 processing (remaining 1 subscribers).
[2024-10-22 06:59:54.794] [INF]: SR: There are no subscribers for "ietf-netconf-notifications" notifications.
[2024-10-22 06:59:54.794] [INF]: NP: Generated new event (netconf-session-start).
[2024-10-22 07:00:00.098] [ERR]: SR: open() on "/dev/shm/srsub_o-ran-file-management.notif" failed (No such file or directory).
[2024-10-22 07:00:00.852] [INF]: SR: EV LISTEN: "/notifications:create-subscription" "rpc" ID 1 priority 0 fail (remaining 1 subscribers).
[2024-10-22 07:00:00.852] [WRN]: SR: EV ORIGIN: "/notifications:create-subscription" "rpc" ID 1 priority 0 failed (System function call failed).
[2024-10-22 07:00:00.853] [ERR]: SR: User callback failed.
[2024-10-22 07:00:00.853] [ERR]: NP: Failed to send an RPC (User callback failed).
[2024-10-22 07:00:00.853] [INF]: NP: Session 2: thread 2 event new RPC.
[2024-10-22 07:00:00.853] [INF]: NP: Session 2: thread 2 event reply error.
[2024-10-22 07:00:01.063] [INF]: NP: Session 2: thread 2 event new RPC.
[2024-10-22 07:00:01.063] [INF]: NP: Session 2: thread 2 event session terminated.
[2024-10-22 07:00:01.513] [INF]: SR: Connection 3414 created.
[2024-10-22 07:00:01.516] [INF]: SR: Session 204839 (user "root", CID 3414) created.
[2024-10-22 07:00:01.519] [WRN]: SR: Connection with CID 3413 is dead.

@michalvasko
Copy link
Member

So what version of sysrepo/netopeer2 is this? Have you modified any compile paths or using any run-time variables used by sysrepo? The file path is completely wrong, there are no .notif files supposed to be in /dev/shm and every .notif file name is followed by the timestamps of the stored notifications so I really do not understand where it is coming from.

@rydy
Copy link
Author

rydy commented Oct 25, 2024

So what version of sysrepo/netopeer2 is this? Have you modified any compile paths or using any run-time variables used by sysrepo? The file path is completely wrong, there are no .notif files supposed to be in /dev/shm and every .notif file name is followed by the timestamps of the stored notifications so I really do not understand where it is coming from.

I'm using version netopeer2-2.2.19,
run-time variable:

export SYSREPO_REPOSITORY_PATH=/etc/sysrepo
export SYSREPO_SHM_PREFIX=sr

This is also the first time I have encountered this problem. It may happen again after a long time,some logs are as follows
netopeer2-server-srsub_o-ran-file-management.notif_No such file .txt

@michalvasko
Copy link
Member

I see, then like I said previously, I am sorry but I am unable to provide support for too old versions if there were too many relevant changes made.

@rydy
Copy link
Author

rydy commented Oct 28, 2024

I see, then like I said previously, I am sorry but I am unable to provide support for too old versions if there were too many relevant changes made.

ok, I updated to 2.2.31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is:bug Bug description. status:invalid Issue is not reproducible.
Projects
None yet
Development

No branches or pull requests

2 participants