search

CESNET / netopeer2

NETCONF toolset
BSD 3-Clause "New" or "Revised" License
290 stars 186 forks source link

netopeer2 debian package fails to install #1516

Open nhathaway opened 6 months ago

nhathaway commented 6 months ago

Install log below (on Ubuntu 22.04):

Selecting previously unselected package netopeer2. (Reading database ... 183185 files and directories currently installed.) Preparing to unpack .../netopeer2_2.1.71-ubuntu1_amd64.deb ... Unpacking netopeer2 (2.1.71-ubuntu1) ... Setting up netopeer2 (2.1.71-ubuntu1) ... [ERR] Datastore plugin "JSON notif" not found. sysrepoctl error: Failed to connect (Item not found) For more details you may try to increase the verbosity up to "-v3". [ERR] Datastore plugin "JSON notif" not found. sysrepoctl error: Failed to connect (Item not found) For more details you may try to increase the verbosity up to "-v3". dpkg: error processing package netopeer2 (--configure): installed netopeer2 package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.10.2-1) ... Errors were encountered while processing: netopeer2 E: Sub-process /usr/bin/dpkg returned an error code (1)

nhathaway commented 6 months ago

Versions:

libyang2_2.1.128 libsysrepo7_2.2.105 libnetconf2-3_2.1.37

I notice that the offending/missing plugin is mentioned in common.c of sysrepo.

nhathaway commented 6 months ago

$ sysrepoctl --version sysrepoctl - sysrepo YANG schema manipulation tool, compiled with libsysrepo v2.2.105 (SO v7.19.3)

$ sysrepoctl -L -v3 [ERR] Datastore plugin "JSON notif" not found. sysrepoctl error: Failed to connect (Item not found)

michalvasko commented 6 months ago

You most likely have some old version of sysrepo installed as well, which was compiled and installed manually, not from a package. I have just build packages from master branches of all the projects and installed them on Ubuntu 22, all worked fine.

nhathaway commented 6 months ago

No, that's not it. I do notice that there have been changes on the sysrepo master branch since the release in August. Can you build the release rather than the head of master?

nhathaway commented 6 months ago

https://github.com/sysrepo/sysrepo/commit/dcea390f83fb95151afb56f6e045c4d4b7fac10b

This may be significant

michalvasko commented 6 months ago

You are probably right, there were some problems because of the extra libyang release. So use the current master for now, a new release is planned early next year.

nhathaway commented 6 months ago

I built with libyang 2.1.111 and now that error is not present.

michalvasko commented 6 months ago

That should be fine as well.