netopeer2-server crash after SSH socket error: connection timed out. about netopeer2 HOT 5 OPEN

There is another scenario that would cause the service's call home process to terminate：When there is a significant network latency， like this:
[INF]: NP: Session 18: thread 4 event new RPC.
[2024/06/22 15:06:47.292686, 1] ssh_socket_exception_callback: Socket exception callback: 1 (0)
[2024/06/22 15:06:47.292908, 1] ssh_socket_exception_callback: Socket error: disconnected
[ERR]: LN: Session 18: SSH channel poll error (Socket error: disconnected).
[INF]: NP: Session 18: thread 4 event session terminated.
[INF]: LN: Call Home client "default-client" session terminated.
[INF]: LN: Trying to connect via IPv4 to 192.168.30.1:4334.
[INF]: LN: getsockopt() error (Connection refused).
[ERR]: LY: Invalid union value "0▒^E" - no matching subtype found. (Schema location "/ietf-netconf-notifications:netconf-session-end/source-host".)
[ERR]: SR: Invalid union value "0▒^E" - no matching subtype found. (Schema location "/ietf-netconf-notifications:netconf-session-end/source-host".)
[WRN]: NP: Failed to send a notification (libyang error).
[ERR]: SR: Internal error (/home/wwh1/netop-1013/ntsim-compile/4_OpenSourceCode/2022_08_03/sysrepo-2.1.84/src/common.c:3976).
[ERR]: SR: Internal error (/home/wwh1/netop-1013/ntsim-compile/4_OpenSourceCode/2022_08_03/sysrepo-2.1.84/src/common.c:3976).
[ERR]: LN: Call Home client "default-client" was not found.
[INF]: LN: Call Home client "default-client" thread exit.

Is this normal? And how can it be restored?

from netopeer2.

Please update all the libraries and netopeer2, I cannot help you with such an outdated version, there were lots of problems fixed since.

from netopeer2.

Do you mean to use the latest Tag version of the libraries and netopeer2?
Eg:
netopeer2 V2.2.19
libyang V2.2.8
libnetconf2 V3.0.17
These library versions compatible with each other, right? Please provide guidance. Thank you so much.

from netopeer2.

You always see all the versions on netopeer2 release page (which correspond to the master branches of the projects). But there were some problems with this release so the safest is to use the devel branches. There should be a new release soon but I am still fixing some things.

from netopeer2.

Okay, I understand. Thank you very much for your prompt response.

from netopeer2.