-
Notifications
You must be signed in to change notification settings - Fork 192
Open
Labels
is:bugBug description.Bug description.status:completedFrom the developer perspective, the issue was solved (bug fixed, question answered,...)From the developer perspective, the issue was solved (bug fixed, question answered,...)
Description
Hi Team,
we are facing a crash issue in netopeer module ,
below are the versions used
netopeer2: 2.4.1
libnetconf2: 3.7.1
sysrepo: 3.6.11
libyang: 3.12.2
**backtrace: [**
{ a: 0000007f997e4130, s: sr_log_set_cb, o: 0x16b70, l: 0x330, e: 0, S: 0, f: "/usr/lib64/libsysrepo.so.7.33.5" },
{ a: 0000007f997ab0a4, e: 0, S: 0, f: "/usr/lib64/libsysrepo.so.7.33.5" },
{ a: 0000007f997b8850, s: sr_notif_subscribe_tree, o: 0x30, l: 0x3c, e: 0, S: 0, f: "/usr/lib64/libsysrepo.so.7.33.5" },
{ a: 0000007f998055d8, s: srsn_read_dispatch_destroy, o: 0x330c, l: 0x2f8, e: 0, S: 0, f: "/usr/lib64/libsysrepo.so.7.33.5" },
{ a: 0000007f99800bb0, s: srsn_subscribe, o: 0x1d0, l: 0x2bc, e: 0, S: 0, f: "/usr/lib64/libsysrepo.so.7.33.5" },
{ a: 0000005573d71814, e: 0, S: 0, f: "/usr/sbin/netopeer2-server" },
{ a: 0000005573d75f28, e: 0, S: 0, f: "/usr/sbin/netopeer2-server" },
{ a: 0000007f999c7b94, s: nc_ps_poll, o: 0xa14, l: 0x1080, e: 0, S: 0, f: "/usr/lib64/libnetconf2.so.4.6.1" },
{ a: 0000005573d670a4, e: 0, S: 0, f: "/usr/sbin/netopeer2-server" },
{ a: 0000007f996173c0, s: __libc_init_first, o: 0x80, l: 0xa4, e: 0, S: 0, f: "/usr/lib64/libc.so.6" },
{ a: 0000007f9961749c, s: __libc_start_main, o: 0x98, l: 0x154, e: 0, S: 0, f: "/usr/lib64/libc.so.6" },
{ a: 0000005573d678b0, e: 0, S: 0, f: "/usr/sbin/netopeer2-server" } ]
processing_time: 0.085278
As soon as the netopeer is starting it is crashing , command used here is netopeer2-server -d -t 5 -v 3 -p /tmp/netopeer_server.pid
Could you please let us know if there is any known issue in these above versions ??
Metadata
Metadata
Assignees
Labels
is:bugBug description.Bug description.status:completedFrom the developer perspective, the issue was solved (bug fixed, question answered,...)From the developer perspective, the issue was solved (bug fixed, question answered,...)