Failed to run wifi example "Aug 12 20:31:35.277987: main: 716: FATAL: clicon_sock_group option not set"

[AlbrechtL]

I'm able to build and run the wifi docker container, but the backend refuses to start with the message Aug 12 20:31:35.277987: main: 716: FATAL: clicon_sock_group option not set.

Full log

$ docker logs wifi
+ echo /usr/local/bin/startsystem.sh
/usr/local/bin/startsystem.sh
+ DBG=0
+ echo 'Set disable_coredump false'
+ echo 'start clixon_backend:'
start clixon_backend:
+ /usr/local/sbin/clixon_backend -FD 0 -s startup -l e
Aug 12 20:31:35.277987: main: 716: FATAL: clicon_sock_group option not set
+ /bin/sleep 100000000

I just cloned and the example without any changes.

[olofhagsand]

Is that a regular docker run following https://github.com/clicon/clixon-examples/blob/master/wifi/docker/README.md?
It works on my machine:

eric> sudo docker logs wifi
+ echo /usr/local/bin/startsystem.sh
/usr/local/bin/startsystem.sh
+ DBG=0
+ echo 'Set disable_coredump false'
+ echo 'start clixon_backend:'
start clixon_backend:
+ /usr/local/sbin/clixon_backend -FD 0 -f /usr/local/etc/clixon.xml -s startup -l e
Aug 15 10:36:44: clixon_backend: 7 Started

The error typically occurs natively if CLICON_SOCK_GROUP (defult "clicon") is not setup as described here:
https://github.com/clicon/clixon/blob/master/doc/FAQ.md#do-i-need-to-setup-anything
But in the docker the group is created here:

clixon-examples/wifi/docker/Dockerfile

Line 115 in a518eee

RUN adduser -D -H clicon

Also, the configure file defines CLICON_SOCK_GROUP to be that:

clixon-examples/wifi/src/wifi.xml.in

Line 20 in a518eee

<CLICON_SOCK_GROUP>@CLICON_GROUP@</CLICON_SOCK_GROUP>

However, one can check if local file wifi/src/wifi.xml has the line (after running configure):

  <CLICON_SOCK_GROUP>clicon</CLICON_SOCK_GROUP>

And that the config file is copied into the container.

[AlbrechtL]

However, one can check if local file wifi/src/wifi.xml has the line (after running configure):

Yepp, in my wifi.xml file <CLICON_SOCK_GROUP>clicon</CLICON_SOCK_GROUP> is missing (see full wifi.xml below). I followed your Readme files. But in my docker host system, the user group clicon does not exist because I expected that everything runs inside docker.

Full wifi.xml

<clixon-config xmlns="http://clicon.org/config">
  <CLICON_CONFIGFILE>/usr/local/etc/clixon/wifi.xml</CLICON_CONFIGFILE>
  <CLICON_CONFIGDIR>/usr/local/etc/clixon/wifi</CLICON_CONFIGDIR>
  <CLICON_FEATURE>ietf-netconf:startup</CLICON_FEATURE>
  <CLICON_FEATURE>clixon-restconf:allow-auth-none</CLICON_FEATURE>
  <CLICON_YANG_DIR>/usr/local/share/clixon</CLICON_YANG_DIR>
  <CLICON_YANG_DIR>/usr/local/share/openconfig/public/release/models</CLICON_YANG_DIR>
  <CLICON_YANG_MODULE_MAIN>clixon-wifi</CLICON_YANG_MODULE_MAIN>
  <CLICON_CLI_MODE>wifi</CLICON_CLI_MODE>
  <CLICON_CLI_LINESCROLLING>0</CLICON_CLI_LINESCROLLING>
  <CLICON_CLI_TAB_MODE>0</CLICON_CLI_TAB_MODE>
  <CLICON_CLISPEC_DIR>/usr/local/lib/wifi/clispec</CLICON_CLISPEC_DIR>
  <CLICON_BACKEND_DIR>/usr/local/lib/wifi/backend</CLICON_BACKEND_DIR>
  <CLICON_SOCK>/usr/local/var/wifi/wifi.sock</CLICON_SOCK>
  <CLICON_BACKEND_PIDFILE>/usr/local/var/wifi/wifi.pidfile</CLICON_BACKEND_PIDFILE>
  <!-- true here means restconf config is in datastore -->
  <CLICON_BACKEND_RESTCONF_PROCESS>true</CLICON_BACKEND_RESTCONF_PROCESS>
  <CLICON_XMLDB_DIR>/usr/local/var/wifi</CLICON_XMLDB_DIR>
  <CLICON_STARTUP_MODE>init</CLICON_STARTUP_MODE>
  <CLICON_SOCK_GROUP></CLICON_SOCK_GROUP>
  <CLICON_RESTCONF_USER></CLICON_RESTCONF_USER>
  <CLICON_RESTCONF_PRIVILEGES>drop_perm</CLICON_RESTCONF_PRIVILEGES>
  <CLICON_RESTCONF_INSTALLDIR>/usr/local/sbin</CLICON_RESTCONF_INSTALLDIR>
</clixon-config>

Update
After manually adding <CLICON_SOCK_GROUP>clicon</CLICON_SOCK_GROUP> to wifi.xml the container works fine.

$ docker logs wifi
+ echo /usr/local/bin/startsystem.sh
/usr/local/bin/startsystem.sh
+ DBG=0
+ echo 'Set disable_coredump false'
+ echo 'start clixon_backend:'
start clixon_backend:
+ /usr/local/sbin/clixon_backend -FD 0 -s startup -l e
Aug 15 11:26:52.414751: clixon_backend: 6 Started
Aug 15 11:26:52.414806: clixon_proc_background '/usr/local/sbin/clixon_restconf', '-f', '/usr/local/etc/clixon.xml', '-E', '/usr/local/etc/clixon/wifi', '-D', '0', '-l', 'f/var/log/clixon_restconf.log'

[olofhagsand]

Can you please run ./configure in the root dir of clixon-examples and check if wifi.xml gets populated OK?
I dont see any conditional in setting CLICON_GROUP="clicon".
That is, if you run the configure script, wifi.xml should be OK, regardless of host setup.

[AlbrechtL]

Here you go

albrecht@aus-latitude:~/src/clixon-examples$ ./configure --disable-native-compile
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for main in -lm... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... (cached) gcc
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to enable C11 features... (cached) none needed
checking how to run the C preprocessor... gcc -E
compiler is gcc
debug is no
CPPFLAGS is -DHAVE_CONFIG_H 
CFLAGS is -O2 -Wall
INSTALLFLAGS is -s
checking native-compile: no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating hello/Makefile
config.status: creating hello/src/Makefile
config.status: creating hello/src/hello.xml
config.status: creating hello/docker/Makefile
config.status: creating wifi/Makefile
config.status: creating wifi/src/Makefile
config.status: creating wifi/src/wifi.xml
config.status: creating wifi/yang/Makefile
config.status: creating wifi/docker/Makefile
config.status: creating openconfig/Makefile
config.status: creating openconfig/src/Makefile
config.status: creating openconfig/src/openconfig.xml
config.status: creating openconfig/yang/Makefile
config.status: creating openconfig/docker/Makefile
config.status: creating 3gpp/Makefile
config.status: creating 3gpp/src/Makefile
config.status: creating 3gpp/src/3gpp.xml
config.status: creating 3gpp/yang/Makefile
config.status: creating 3gpp/docker/Makefile
albrecht@aus-latitude:~/src/clixon-examples$ cat wifi/src/wifi.xml
<clixon-config xmlns="http://clicon.org/config">
  <CLICON_CONFIGFILE>/usr/local/etc/clixon/wifi.xml</CLICON_CONFIGFILE>
  <CLICON_CONFIGDIR>/usr/local/etc/clixon/wifi</CLICON_CONFIGDIR>
  <CLICON_FEATURE>ietf-netconf:startup</CLICON_FEATURE>
  <CLICON_FEATURE>clixon-restconf:allow-auth-none</CLICON_FEATURE>
  <CLICON_YANG_DIR>/usr/local/share/clixon</CLICON_YANG_DIR>
  <CLICON_YANG_DIR>/usr/local/share/openconfig/public/release/models</CLICON_YANG_DIR>
  <CLICON_YANG_MODULE_MAIN>clixon-wifi</CLICON_YANG_MODULE_MAIN>
  <CLICON_CLI_MODE>wifi</CLICON_CLI_MODE>
  <CLICON_CLI_LINESCROLLING>0</CLICON_CLI_LINESCROLLING>
  <CLICON_CLI_TAB_MODE>0</CLICON_CLI_TAB_MODE>
  <CLICON_CLISPEC_DIR>/usr/local/lib/wifi/clispec</CLICON_CLISPEC_DIR>
  <CLICON_BACKEND_DIR>/usr/local/lib/wifi/backend</CLICON_BACKEND_DIR>
  <CLICON_SOCK>/usr/local/var/wifi/wifi.sock</CLICON_SOCK>
  <CLICON_BACKEND_PIDFILE>/usr/local/var/wifi/wifi.pidfile</CLICON_BACKEND_PIDFILE>
  <!-- true here means restconf config is in datastore -->
  <CLICON_BACKEND_RESTCONF_PROCESS>true</CLICON_BACKEND_RESTCONF_PROCESS>
  <CLICON_XMLDB_DIR>/usr/local/var/wifi</CLICON_XMLDB_DIR>
  <CLICON_STARTUP_MODE>init</CLICON_STARTUP_MODE>
  <CLICON_SOCK_GROUP></CLICON_SOCK_GROUP>
  <CLICON_RESTCONF_USER></CLICON_RESTCONF_USER>
  <CLICON_RESTCONF_PRIVILEGES>drop_perm</CLICON_RESTCONF_PRIVILEGES>
  <CLICON_RESTCONF_INSTALLDIR>/usr/local/sbin</CLICON_RESTCONF_INSTALLDIR>
</clixon-config>

[olofhagsand]

OK, I see that happens when configuring with --disable-native-compile
Mark this as bug, but your work-around seems to work,...