Hi All,
I am new to Klish and working on to bring-up Klish CLI environment with client and Klishd daemon by sysrepo as DB (with help of klish-plugin-sysrepo plugin).
In spite of debugging for more than a day along with usage of M365 Copilot help, not able to narrow down on issue or resolution where Copilot ended up suggesting for clean install after initial XML formats and .conf files correction though I might have missed to explain all context to Copilot.
Error:
klishd-listen: Service process for client was forked: 2350
klishd[2350]: Can't create KTPd session
klishd[2350]: Close connection 6
klishd-listen: Service process 2350 was terminated: 255
Environment/context:
libfaux 2.2.0
klish‑plugin‑sysrepo 3.1.0
libyang
NOTE: In same host and same sysrepo DB libraries, netopeer2 client and server setup works all for Netconf setup.
Checked similar errors on this group and followed below mentioned steps as well, however issue remain persists.
some config files corrected from Copilot.
localhost:/etc/klish#
ls -ltotal 16
-rw-r--r-- 1 root root 68 Mar 25 12:08 klish.conf
-rw-r--r-- 1 root root 138 Mar 25 11:59 klishd.conf
drwxr-xr-x 2 root root 4096 Mar 25 11:57 scheme
drwxr-xr-x 2 root root 4096 Jan 16 18:10 xml.bak
localhost:/etc/klish#
cat klish.conf klishd.conf scheme/main.xml[client]
scheme = default
unix-socket-path = /tmp/klish-unix-socket
[server]
dbs = libxml2
unix-socket-path = /tmp/klish-unix-socket
fork-mode = reuse
max-clients = 10
[scheme]
xml-dir = /etc/klish/scheme
<?xml version="1.0" encoding="UTF-8"?>
<KLISH
name="default"
xmlns="
https://src.libcode.org/pkun/klish/xml/klish"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
<STARTUP view="main"/>
<VIEW name="main">
<PROMPT>
<ACTION builtin="prompt">%u@%h> </ACTION>
</PROMPT>
<COMMAND name="echo" help="Print text">
<PARAM name="text" ptype="STRING"/>
<ACTION builtin="echo">
<ARG name="text"/>
</ACTION>
</COMMAND>
</VIEW>
</KLISH>
localhost:/etc/klish#
Any light on this about what I am missing or steps to narrow down this issue is highly appreciated.
Thank you very much.
Regards,
Sivaram