Fixed
Created: Jan 10, 2018
Updated: Dec 3, 2018
Resolved Date: Mar 21, 2018
Found In Version: 8.0.0.23
Fix Version: 8.0.0.25
Severity: Standard
Applicable for: Wind River Linux 8
Component/s: Userspace
Can not start opensafd on WRL8.
I tried the following steps:
# cat /usr/local/share/opensaf/immxml/README
---
This file documents how to generate the imm.xml file.
After installing opensaf follow this process to generate imm.xml:
$ cd /usr/local/share/opensaf/immxml
# generate a config file (nodes.cfg) for a 8 node cluster
immxml-clustersize -s 2 -p 6
# if needed edit the nodes.cfg (e.g. using non-standard hostnames etc TBD)
# This is not needed for now....
$ vi ./nodes.cfg
# generate the imm.xml
$ immxml-configure
# copy the generated imm.xml file to the location of imm loader
cp imm.xml.20100217_2201 /etc/opensaf/imm.xml
---
For more defail, please see the attached opensafd-err.log.
1. configure
/opt/wrs/wrlinux/8.0/WindRiver/wrlinux-8/wrlinux/configure --enable-board=intel-x86-64 --enable-kernel=standard --enable-rootfs=glibc-std --enable-build=production --with-rcpl-version=0023
2. add opensaf package
$ make linux-windriver.rebuild
$ make opensaf.addpkg
$ make fs
[Boot target]
# cat /proc/cmdline
BOOT_IMAGE=(hd0,2)/images/intel-x86-64-bzImage-WR8.0.0.23_standard console=ttyS0,115200 printk.time=1 debug rw root=/dev/nfs nfsroot=128.224.233.72:/02/export/intel64.wrl8 ip=128.224.234.130:128.224.233.72:128.224.234.1:255.255.254.0:WRL8:eth0:off
# cd /usr/share/opensaf/immxml/
# ./immxml-clustersize -s 2 -p 2
# cat nodes.cfg
SC SC-1 SC-1
SC SC-2 SC-2
PL PL-3 PL-3
PL PL-4 PL-4
# ./immxml-configure
Successfully generated the imm file: ./imm.xml.20180110_2152
# cp ./imm.xml.20180110_2152 /etc/opensaf/imm.xml
# vi /etc/opensaf/nid.conf:
---
-export MDS_TRANSPORT=TCP
+export MDS_TRANSPORT=TIPC
...
-export OPENSAF_GROUP=opensaf
+export OPENSAF_GROUP=root
-export OPENSAF_USER=opensaf
+export OPENSAF_USER=root
----
# systemctl start opensafd
Job for opensafd.service failed because the control process exited with error code. See "systemctl status opensafd.service" and "journalctl -xe" for details.
